U R @ vSphere Admin's Space

If your Windows Server 2008 box is in a WorkGroup and you require access to one of the admin shares, it can be a little more complicated than with Server 2003. I had to setup a Veeam backup job for backing up a VM running Windows 2008 in WorkGroup. Initial backup job with default settings went well and I had the enabled “Application Aware Image Processing” and “Guest File System Indexing”. For this I had setup a local admin account on Windows 2008 and provided the credentials in Veeam backup job. Job failed on the test run with below error 'ServerHostName' Error: Failed to connect to guest agent. Errors: 'Cannot connect to the host's administrative share. Host: [10.0.0.11]. Account: []. Win32 error:Logon failure: unknown user name or bad password. Code: 1326 ' 10.0.0.11 is the Server IP and I tried to access \\10.0.0.11\C$ and I got the windows asking for credentials. With the local admin account created and it worked from same server. When I tried remotely from Bac

I am sure that the below message is pretty familiar to you if you are working on P2V migrations. Basically, when you try to configure PROD/Mail ip back to the VM after P2V, you will come across this message.   "The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter" Message says that the earlier NIC with this IP is still there in the VM, but not visible as it is not attached to the Hardware/OS currently. Windows shows the above message to remind you that there was a NIC earlier with the same IP.  I have seen this message after VMware hardware upgrade also.. It is always better to do clean up post a P2V, instead of just skipping this message. Below mentioned the simple, two line step, which you can run on a VM after P2V to clean up these old NIC card devices and associated drives as we no longer need them. 1) Go to Start > Run 2) Type "cmd" and Enter 3) execute below mentioned commands set devmgr_show_nonpre