WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • 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.

More from my site

  • Quick Tip - Using the CLI to upgrade to a specific VM virtual hardware version in vSphere 5.5
  • Blocking vSphere C# Client Logins
  • vSphere UI Client Plugin named N/A after vSphere 8 upgrade
  • A trip down memory lane with the vSphere C# Client and ESXi 6.7 & 7.0
  • Installing the Horizon View Agent on a Domain Controller

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

Comments

  1. Jason 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. Christopher 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

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • How to disable the Efficiency Cores (E-cores) on an Intel NUC? 03/24/2023
  • Changing the default HTTP(s) Reverse Proxy Ports on ESXi 8.0 03/22/2023
  • NFS Multi-Connections in vSphere 8.0 Update 1 03/20/2023
  • Quick Tip - How to download ESXi ISO image for all releases including patch updates? 03/15/2023
  • SSD with multiple NVMe namespaces for VMware Homelab 03/14/2023

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 © 2023