vSphere Client (5.5) on DC *workaround*

jibbajabbajibbajabba Member Posts: 4,317 ■■■■■■■■□□

Right, I know it is bad practice, however, what if you got a lab, like in my case, where the only available Windows Server at the moment of installation, is your DC ?

How do you connect to your hosts in order to install a non-DC ? You cannot officially. Sure you could argue you will have SOME windows server SOMEWHERE, but not me.. I am currently working on my lab from the office and the only windows jump box to that network is a terminal server. The Terminal server's vCenter client cannot be upgraded so at the moment, until I have the actual infrastructure working (including VPN), I am unable to connect to the hosts.

However, there is a workaround
.\VMware-viclient-all-5.5.0-1281650.exe  /VSKIP_OS_CHECKS="1"

Will skip the OS check.

On the VMware forums someone posted a response from VMware
We did this deliberately to enforce a Microsoft standard that our guys agree with - don't install software on a DC, but they made that decision in isolation. Nothing more than that. So use the workaround safely and hopefully we can undo this in the future.

So thought I share that, in case someone has a requirement to do that too.
My own knowledge base made public: http://open902.com :p


Sign In or Register to comment.