Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After P2V, Exchange 2007 does not appear to be receiving any messages from internal clients (Outlook 2010) for delivery.

We can receive messages sent from external recipients, and we can receive messages from devices and services running internally that use their own smtp servers, and when we send messages, they appear to go through, showing up in our Sent boxes, but we do not receive any messages sent from internal Outlook clients either at our internal clients or at our external accounts.

Looking at the Exchange server, viewing the queues, these internal messages never appear in the queues for processing. It is as if the Outlook clients think they are connecting successfully, but the messages are never picked up by the Exchange server.

The old physical server is not powered on. The IP address and network name is configured properly (the same).

share|improve this question

Verify the settings on the "Client" Receive Connector that the appropriate authentication is set and that the permission group is set to Exchange Users.

share|improve this answer
up vote 0 down vote accepted

System details: VMWare - ESXi 4 Windows Server 2008 sp2 (not R2) Exchange 2007

P2V steps: Used VConverter (current version), stopped Exchange services prior to P2V, left config default.

Verified NIC config. Ghost NIC in system, but 2008 removing config from Ghost when config on new (virtual) NIC takes over same config.


This turned out to be quite the beast, and it's not even fully vanquished.

I did not ever figure out what was going on with the first P2V process, it was just bad in some way. All the configuration matched exactly with the physical (functioning) exchange server, and there was just no communication over what appeared to be valid connections.

Not having enough time to continue diagnosing, we ran a second P2V on a subsequent evening, which also didn't work, but this time it was just that the new VM never loaded the OS. Third try appeared to be similar, but turned out to actually be a good copy. At first it appeared to have the not loading issue of try #2 and so I backed out of that too. However, it turned out the issue was a compatibility problem between the RDP console and the vSphere machine viewer resulting in nothing showing in the viewer window when viewed over an RDP connection.

We used this good copy to test the sending and verified it was all working OK. Some Outlook clients needed to have the Cache disabled and then reenabled to "see" the new server in test. It seems the Cache keeps some record besides the domain name and IP address and so if the client is running during the migration, it can get hung up looking in the wrong place for the Exchange server once it comes back online.

So, we've figured out that and I'll be giving it another try tonight, eschewing the RDP console to ensure maximal chance of success.

Regarding the initial issue, Microsoft and our Consultants both recommended simply re- P2Ving as there was no reason they were aware of that the original issue should have occurred.

share|improve this answer
You seem to be skipping some troubleshooting here. It's not uncommon for the P2V process (what platform? vmware?) will bust the NIC configuration up a bit. Did you remove the hidden NIC that is sometimes left behind after the process and then put the correct IP addressesing in? – SpacemanSpiff Jan 27 '12 at 15:32

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.