Networknet.nl

I tried to install Windows Server 2008 x64 on one of my Dell PowerEdge 2900 servers, because the storage driver was failing for x64 bit OS installations of Windows I was forced to install Windows Server 2003 R2 Enterprise x86. The server is up and running and I installed Virtual Server 2005R2 SP1 Enterprise. Through the SCVMM console I initiated the Add Host of this new Windows server. The job failed with message the server did have the WS-Management service installed.

I did not install the WS-Management service before and I found somewhere to install the Hardware Management option in Add/Remove Windows Components to get this working.

Than I retried to add the server as host in SCVMM but the installation stopped with the message below.

Error (421) Agent installation failed on ref-vmh-02 because of a WS-Management configuration error.

I reboot the server couple of times; reviewed the eventlog and nothing worked to get the Virtual Machine Manager 2007 agent installed. There is hotfix which you can use and install the WinRM component manually without control panel. Go here and download and install the fix http://go.microsoft.com/fwlink/?LinkId=84599. This fixed my problem and errors 10101 WinRM in the application eventlog.

System Center Virtual Machine Manager 2007 is out for a while and I have been testing this product for two months now.

If you manually install SCVMM 2007 than Virtual Machine Manager 2007 Server Setup wizard may stop just before the installation is finished. I have also seen errors within the available SCVMM 2007VHD appliance from Microsoft’s website. Jobs are failing and Manager complaining about network paths incorrect.

Main reason why the setup fails is that the computername contains ‘-’ . For example I named the server REF-SCVMM-01 and the setup failed with error id 2917.

• The network path was not found on the REF-SCVMM-01. Ensure that the share name provided maps to a valid local path, and then try the operation again. ID: 2917. Details: The network path was not found.

In the background PowerShell is not able to get the computername variable correct within the scripts it uses. In my case I renamed the computername to REF_SCVMM_01 and setup finished successfully.