UPDATE:

If you would like to try out windows 7 you should since it's a great OS. But if you like me need to connect to VmWare's VsPhere 4 you need to read this post. It's taken from a tread at vmware communities.

In short this is what you need to do is the following:

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

2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+).

3. 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 as shown below. Save the file.

<?xml version="1.0" encoding="utf-8"?> 
<configuration> 
... 
<runtime> 
<developmentMode developerInstallation="true"/> 
</runtime> 
</configuration> 

3. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. 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. For example,

SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"

4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.

You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.

Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.

I've attached the DLL-file so you don't have to look around for the file.

System.dll.zip (1.05 mb)

My work laptop is a HP 6730b and i'm not that pleased with it. Especially when I place it in the dock and power it up. The problem is that I need to have the laptop open and to login with the laptop. Then I can close the lid. If I don't follow this procedure I wont get the desired effect. I've thought this is a HP problem since I did not experience this at all with my last Fujitsu Lifebook.

Then I found some articles about Transiet Multimon Manager and how this is a service in Vista that helps me with my displays or at least it tries to help me.

Toms hardware explains this service in short.
Transient Multi-Monitor Manager or  Transient Multimon Manager (TMM) is a cool Windows Vista Feature that simplifies the setup of display configurations on mobile computers.Windows Vista Transient Multimon Manager is targeted at improving the user experience of connecting and disconnecting external displays Transient Multimon Manager (TMM) can place a mobile computer display (for example, a laptop computer display) into clone view when a new monitor is detected.TMM is enabled by default in Windows Vista. TMM automatically finds external displays at boot, it can also remember settings of the same external display if you connect it later.If you are not using an external monitor, or don't switch back and forth always then turn TMM off.This is the 2-3 second delay followed by a blank black screen as Windows Vista searches for monitor changes when you startup Vista.

So I need to start my computer without having it in the docking station and then logon and afterwards place it in the dock. Before I had to restart my computer to get the external screen working.

Conclusion is that Microsoft have made feature that work for persons who have a docking station at work and then work at home sometimes and always shutting their PC down. I use my computer alot and when I leave one customer i hibernate or put the computer in sleep mode. So this is a nice feature for some but not implemented right. In other words a normal windows feature.