Services, permissions, registry problems after p2v.

[daddmac]

I have converted an IIS server several times and have had this problem each time. 

Environment:

Windows Server 2008 r2.

ESXi 4.1 and ESXi 4.1 Update 1.

IIS services only.

ASP 4.

.Net 4.

Fully patched.

AV is present. 

Converter standalone. 

Process:

use converter to p2v to local drive.

copy the files to another system.

use Converter to load the vm onto the ESXi server. 

Problem:

1. MSDTC fails to start.  Resolved by deleting the msdtc folder, creating a new one, run msdtc -resetlog, explicitly grant network service full perm to the new folder. 
2. Web pages not served, even when browing from within IIS manager.  Unresolved.
3. Logging won't start for MS diagnostic logs.  Unresolved:
   1. +"The event logging service encountered an error (res=5) while initializing logging resources for channel Microsoft-Windows-Diagnosis..."

Services all run normally on the physical server.  I'm a rookie with ESXi and Converter, but not to virtualization or IT. 

TIA for sharing.  :smileyhappy:

[a_p_]

Welcome to the Community,

I assume you reconfigured all IP settings after conversion and DNS resolved properly!? Are there any messages/errors in the Windows Event logs?

André

[bulletprooffool]

Double check all your NIC settings / DNS etc on the VM.

When you P2V a host, the original NIC is replaces by a new NIC - meaning the new NIC gets new Mac Address, TCPIP settings / Coinfig etc.

As such, if your previous physuical NIC had multiple IP addresses or anything similar, these settings will all be lost.

generally, where I have seen similar issues, they have been related tothe change in the underlying Network infrastructure (NIC settings etc)

[continuum]

use netsh to dumb the current network-config to a file pre P2V
run Converter
after first boot into the VM restore network config from file with netsh

[daddmac]

First, thanks for responding, and so quickly!  It's very encouraging! 

I found that the reason the web pages are not being served is because I needed to reinstall the site's ssl certificate.  I don't know why this is, but i saw a reference to it in a posting about another VM product that runs on top of the other OS.  After I reinstalled the cert the web sites immediately started working. 

I'm still looking into the logging problem. 

[daddmac]

It's been awhile since the original post, but hopefully I can spare someone else the time I took on this. 

Some things will not covert cleanly when cloning p2v. 

After some testing, I found that none of the above problems occur when cloning v2v.  So, for me the solution was to work with v2v only.  My conversion to a virtual environment is complete so I don't have to deal with this anymore, but my lesson learned is to convert one, correct as above, and then on do cold clone v2v after that. 

Many thanks for the info/suggestions.