A place for info I've learnt in IT & stuff. (I get a little kick back from affiliate ads & links, just so you are aware)

Browsing Posts published in December, 2010

Run into this annoying issue trying to convert a Server 2008 RC2 VM to an ESX server.

Nice simple fix. Run Convertor as admin.

NOTE: This is relating to a Physical machine to Virtual. But this fix worked for me where my server 2008 R2 is Virtual in VMware Workstation and wanted to move it to an ESX box.

Use command

net time \\servername /set /y

This is fixed in vSphere in 4.1 I think but I can’t get hold of it.


Copy .dll to

C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib


C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

If Lib don’t exist, then create it.

Many of you, like myself, have started running Windows 7 as their primary desktop OS and find it to be a massive improvement over Windows Vista on so many levels.

One of the very few inconveniences I have found with it, and this is not an bug or problem with Windows 7 itself, is the inability to run the VMware vSphere Client.

UPDATE: Good News – This issue has now been resolved in VMware ESX/ESXi 4.0 Update 1 (U1).

When attempting to run the client the following errors are received and you are unable to proceed any further:

“Error parsing the server “ C:\Program Files).

Follow these 4 basic steps and you’ll be up and running in no time!
Step 1.

imageDownload this DLL called system.dll

*Note: This DLL is usually found in the %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a non Windows 7 PC with .NET v3.5 SP1 installed.

Step 2.

Once downloaded install it in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib” directory. If the ‘lib’ directory doesn’t exist then create it and drop the dll file into it.

VMware vSphere Client Windows 7
Step 3.

Next edit the “VpxClient.exe.config” file which can be found in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher” directory and add the following three lines to it in the location specified in the screenshot below. Then save the changes.

VMware vSphere Client Windows 7

Step 4.

From the Windows 7 ‘System Properties’ click the ‘Advanced’ tab and then the ‘Environment Variables’ button as we want to add a new ‘System’ variable.

VMware vSphere Client Windows 7

Create a new ‘System’ variable called ‘DEVPATH’ and assign the following variable value:

C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

VMware vSphere Client Windows 7

You are now ready to start using the VMware vSphere Client on your Windows 7 machine! Some people have reported having to run the client as an ‘Administrator’ so if you are having difficulties it may pay to try this – I luckily didn’t experience this problem. Also you will likely have to reboot your machine (or restart the explorer.exe process) for your new path information to come into effect.

VMware vSphere Client Windows 7

Dan and Dan Films

Quality comedy from Dan and Dan. They play off each other really well.

Dan and Dan Films

By default, the Administrator account is not displayed on the Welcome Screen. To log in to the Administrator account, press Ctrl+Alt+Del, release the Del key, and press it again, while still holding down the Ctrl+Alt keys. This will change the Welcome Screen login to the Windows 2000 style log in, where you can now type Administrator and the password for the Admin account.

You could also add the Administrator to the Welcome Screen:

1. Start the Registry Editor
2. Go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon \ SpecialAccounts \ UserList \
3. Right-click an empty space in the right pane and select New > DWORD Value
4. Name the new value Administrator
5. Double-click this new value, and enter 1 as it’s Value data
6. Close the registry editor

Manual Update

These are the short instructions, if you want more check out the extended upgrade instructions. If you experience problems with the Three Step Update, you may want to review the more detailed upgrade instructions

For these instructions, it is assumed that your blog’s URL is
Step 1: Replace WordPress files

1. Get the latest WordPress zip (or tar.gz) file.
2. Unpack the zip file that you downloaded.
3. Delete the old wp-includes and wp-admin directories on your web host (through your FTP or shell access).
4. Using FTP or your shell access, upload the new WordPress files to your web host, overwriting old files.

NOTE – you should replace all the old WordPress files with the new ones, including those in the root directory like index.php, wp-login.php and so on. Simply copying the contents of the zip you downloaded over the top of your existing files should achieve this. Make sure you copy all the sub-directories as well. Don’t worry – your wp-config.php will be safe.

Be careful when you come to copying the wp-content directory. You should make sure that you only copy the files from this directory, rather than replacing your existing wp-content directory. This is where your themes and plugins live, so you will want to keep them. If you have customized the default or classic themes without renaming them, make sure not to overwrite those files, otherwise you will lose your changes. (Though you might want to compare them for new features or fixes..)

Lastly you should take a look at the wp-config-sample.php file, to see if any new settings have been introduced that you might want to add to your own wp-config.php.