I'm looking at deploying a vSphere 6 environment and want to use an External PSC for a dual site SRM deployment later.
Can an EXTERNAL PSC be deployed as an appliance (no vCenter server etc), or can I only install an external PSC on a Windows Server?
Ideal result:
Server 1) VCSA (Appliance) No embedded PSC
Server 2) PSC (Appliance) No vCenter server
Resulting in no Windows licenses being required.
Thanks
Correct. No windows license needed for PSC and VC. Both can be VCSA itself.
VUM is still supported in windows. So you need windows for VUM
SRM works well with VCSA. I have tried that.
You should probably listen to the vmworld video on vcsa . It is a good one ( https://www.youtube.com/watch?v=jbbFbdrQMXY&index=32&list=PLeFlCmVOq6yt484cUB6N4LhXZnOso5VC7)
If I understand your question
>>
Can an EXTERNAL PSC be deployed as an appliance (no vCenter server etc), or can I only install an external PSC on a Windows Server?
>>
VCSA ( vcenter appliance) can be installed as independent PSC. VCSA is in par with vcenter windows in almost all scenarios from 6.0 onward
Great, so just to clarify:
I can deploy a vCenter server as an appliance, and another appliance with just the external PSC.
Therefore no Windows licenses required for a full vCenter and External PSC deployment?
The component I might need a Windows Server for is update manger as I understand SRM 6.1 will work with the VCSA.
Thanks
Correct. No windows license needed for PSC and VC. Both can be VCSA itself.
VUM is still supported in windows. So you need windows for VUM
SRM works well with VCSA. I have tried that.
You should probably listen to the vmworld video on vcsa . It is a good one ( https://www.youtube.com/watch?v=jbbFbdrQMXY&index=32&list=PLeFlCmVOq6yt484cUB6N4LhXZnOso5VC7)
I actually just deployed this model, with two external PSC's and two VCSA's (6.0 U1, w/o embedded PSC's), with the PSC's replicating and the VCSA's in enhanced linked mode. They are both installed from the same media, you just have to deploy the PSC's first. Make sure to use the same SSO domain and SSO Site Name for each.