Windows 7 God Modes

In Windows 7, there are a whole bunch of shortcuts you can build to really useful places such as a Monster Control Panel, and other useful links that will save you a lot of searching.
To get access to these “God Modes”, all you need to do is open a “cmd” Command Prompt window, and paste in this bunch of commands:

cd \
mkdir GodModes
cd GodModes
mkdir "Monster Control Panel.{ED7BA470-8E54-465E-825C-99712043E01C}"
mkdir "Enter a default location.{00C6D95F-329C-409a-81D7-C46C66EA7F33}"
mkdir "Use biometric devices with Windows.{0142e4d0-fb7a-11dc-ba4a-000ffe7ab428}"
mkdir "Select a power plan.{025A5937-A6BE-4686-A844-36FE4BEC8B6D}"
mkdir "Select which icons and notifications appear on taskbar.{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9}"
mkdir "Store credentials for automatic logon.{1206F5F1-0569-412C-8FEC-3204630DFB70}"
mkdir "Install a program from the network.{15eae92e-f17a-4431-9f28-805e482dafd4}"
mkdir "Choose the programs that Windows uses by default.{17cd9488-1228-4b2f-88ce-4298e93e0966}"
mkdir "Assembly Cache Viewer.{1D2680C9-0E2A-469d-B787-065558BC7D43}"
mkdir "Manage wireless networks.{1FA9085F-25A2-489B-85D4-86326EEDCD87}"
mkdir "Network.{208D2C60-3AEA-1069-A2D7-08002B30309D}"
mkdir "Computer.{20D04FE0-3AEA-1069-A2D8-08002B30309D}"
mkdir "Devices and Printers.{2227A280-3AEA-1069-A2DE-08002B30309D}"
mkdir "RemoteApp and Desktop Connections.{241D7C96-F8BF-4F85-B01F-E2B043341A4B}"
mkdir "Windows Firewall.{4026492F-2F69-46B8-B9BF-5654FC07E423}"
mkdir "Windows Explorer.{62D8ED13-C9D0-4CE8-A914-47DD628FB1B0}"
mkdir "System.{78F3955E-3B90-4184-BD14-5397C15F1EFC}”

Then just open “Computer” from the Start Menu, double click on C: then on “GodModes” and you will see the list. Double click on any one of them to see what it can do for you!

vSphere Client will not Run on Windows 7

When you start the vSphere Client on Windows 7, you get an error about it being unable to read the "clients.xml" file, followed by an another error "The type initializer for "VirtualInfrastructure.Utils.HttpWebRequestProxy" threw an exception".

The workaround is this:
  • Create a folder (e.g. Lib) in the Windows 7 machine where the vSphere client is installed (%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\).
  • Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non-Windows 7 machine that has .NET 3.5 SP1 installed. Copy this file into the folder created in Step 1.
  • In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element within the <configuration> element. Save the file.
  • <?xml version="1.0" encoding="utf-8"?>
    <developmentMode developerInstallation="true"/>

  • Create a batch file (e.g. VpxClient.cmd) in a suitable location (e.g. Desktop). In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file.
  • SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
    VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
NOTE: If you are running 64-bit Windows, replace all instances of Program Files with Program Files (x86).
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
This workaround bypasses the normal .NET Framework loading mechanism. Assembly versions found in the DEVPATH folder are not checked.