WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / Uncategorized / You no longer can install vSphere C# Client on Windows Domain Controller in vSphere 5.5

You no longer can install vSphere C# Client on Windows Domain Controller in vSphere 5.5

09.25.2013 by William Lam // 2 Comments

In the last couple of days I have noticed several folks comment on a new check that has been put in place in vSphere 5.5 which prevents a user from installing the vSphere C# Client onto a Windows Domain Controller system. If you try to install the vSphere C# Client on a Domain Controller system, you will get the following error message:

It is generally not recommended to install additional software on a Windows Domain Controller and I suspect this check was put in place to deter users from installing additional software, including VMware software onto a Domain Controller system. However, for a development environment or home lab, you may want to consolidate multiple applications onto a single system and help reduce the number of Windows systems that you may need to deploy. Luckily there is a way to by-pass this check and I am actually glad one exists as this is something I will need while building out some of internal labs.

Disclaimer: This is not officially supported by VMware, please use at your own risk.

To by-pass the check, you will need to launch the vSphere C# Client install from the command-line and pass in the following arguments:

VMware-viclient.exe /v "SKIP_OS_CHECKS=1"

Now the installer should allow you to proceed with the vSphere C# Client installation.

Categories // Uncategorized Tags // domain controller, vSphere 5.5, vsphere C# client, vsphere client

Comments

  1. *protectedJason Ruiz says

    09/25/2013 at 7:24 pm

    I found that I had to run it with VMware-viclient.exe /VSKIP_OS_CHECKS="1"

    Reply
  2. *protectedChristopher Vallee says

    09/26/2013 at 2:27 pm

    This can also be done by adding the /v arguments in the Target field of the shortcut that launches the vSphere Client. Might save a little time if you don't want to open a command prompt every time you want to launch a client.

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Quick Tip - Downloading VMware Cloud Foundation (VCF) Consumption CLI for Air-Gapped Environments 12/10/2025
  • Automating VCF Operations Objects & Metrics Reporting 12/08/2025
  • Quick Tip - Using VCF CLI to login to vSphere Supervisor when configured with VCF Automation 12/05/2025
  • Automating the Reporting of VCF Workload Domain Import Pre-Check Validations 12/04/2025
  • Import vCenter Server with Single ESX Host as new VCF Workload Domain? 12/03/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025