Applying Computer Setting

[M1NZ]

We are just P2V a Server that has to NICS installed. Once the VM Tools are installed and we reboot the machine just hungs on Applying Computer Setting.

Any ideas

[DLeid]

Are you logging on to a domain or locally?

How are you accessing the converted server? (VI client, Virtual Center, Remote Console)

Were you able to log on before to install the vmtools?

Which virtual network adapter is being used?

NICs should not stop you from logging on.

[M1NZ]

Hi,

I am logging into the domain. With the VM tools installed the Server is fine untill you assign the IP address. We aew usinf VI client to access the server

[DLeid]

Can you ping the domain controller after you assign the IP address?

Does it give you a dhcp address when set to automatically obtain IP address?

What version of VMware are you using?

If it's ESX 3.5, look at the configuration tab in the VI client and select the networking to confirm how your virtual switches and network adapters are configured.

You can consider to remove the virtual nic and re-add it.

How many network adapters are configured on the host?

[Rob_Bohmann1]

This may be a "ghosted" nic. Did you get a warning when you try to enter the IP about duplicate IP addresses?

To see if this is the case, open a command prompt and enter (without quotes) " set devmgr_show_nonpresent_devices=1 " then enter

" start devmgmt.msc " From the Device Manager view menu, select "Show hidden devices" and look for the ghosted nic, right click and choose uninstall.

[M1NZ]

The server has a static IP and not on dhcp and the vlan is on static ip. We have checked the ghosted nic but nothing is shown. We have done 5 servers now and all seem fine. Its only on 3 servers we are having issues on. We can ping the servers. We are on ESX 3.5

[DLeid]

Sorry to keep asking some many questions but :?:|

Are all five of the virtual servers connected to the same virtual switch?

[M1NZ]

They are core switches at are on static ip address for all our servers. Will have to try and get into safe mode and see if this driver related issues

[DLeid]

They are core switches at are on static ip address for all our servers.

The virtual machines should be connected to a virtual switch which in turn is connected to a physical network adapter. The physical network card is then connected to a physical switch (core switch). I am a little confused as mention the virtual machine are connected to the core switch as they must go through a virtual switch first to get to the network card connected to a physical switch for network access.

I know you also said that you could ping the servers - but from where are you pinging? I am trying to find out if all of your virtual machines are connected to the same virtual switch.

Will have to try and get into safe mode and see if this driver related issues

All the drivers in the virtual servers should be vmware drivers. Are all the virtual network drivers for all five virtual machines the same type? (vlance or vmxnet)

You could also try to go through the virtual machine creation procedure chooosing the proper OS and drivers. When you get to creating a virtual disk drive for the new vm choose existing disk and select the vmdk of a virtual server that's giving you problems. You should copy that vmdk to a different folder to try it.

[aldikan]

Hi M1NZ,

The physical box you virtualized, did it have any iSCSI or NFS drives?

I had similar situation and server would hang for 15-20 min trying to access those drives until timed out. We did corrected the issue and it was good after.

Alex

[paul_xtravirt]

Have you checked that the virtual NIC is set to be connected when the VM is powered on?

If you found this helpful, please consider awarding points

[M1NZ]

So far this has happened to 3 servers we currenly p2v

The issue only happen when we reassign the IP address to the server and reboot and then it hangs at Applying Computer Settings. We have waited 20mins and looks like the Server service and Browser service has issue starting. If we unassinged the IP address and reboot the Server would boot up fine.

To Fix this before we assigned the IP address we ran at the command promt NETSH WINSOCK RESET and rebooted.

[depping]

I removed the other topic to get things centrally logged in this one...

Duncan

VMware Communities User Moderator

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[M1NZ]

If you still have the issue please check .

The issue is that the Server service has hung on startup. This effects The Distributed File System service and The Computer Browser service which both depend on the Server service which failed to start because of the following error: After starting, the service hung in a start-pending state.

This issue may occur if the Spooler service tries to start before the Server service.

Edit the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler\DependOnService

and add the data value LanmanServer also keep RPCSS and reboot the server.

This has worked for us