Windows Vista Forums
Vista Forums Home Join Vista Forums Windows 7 Forum Vista Tutorials Tags
Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks.

Go Back   Vista Forums > Misc Newsgroups > Virtual Server

Vista - P2V bizarre?

Reply
 
Old 10-30-2008   #1 (permalink)
John


 
 

P2V bizarre?

Hi all,

By mistake, I did P2V one of our W2K3 domain controller and the domain
controller's GUID can not be resolved to IP address now(lots of error NTDS
KCC 1865,1311 and 1566). Does it mean that the physical machine has to be
shut down after P2V? What if I just need to create several physical machine
VHDs by using P2V and later put them on different hosts?

Here is the Dcdiag test results's failed parts:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: SITE3\DC3
Starting test: Connectivity
The host 626cd4d2-53e4-47ff-98e5-e33898be1555._msdcs.INTERNAL.LOCAL
could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(626cd4d2-53e4-47ff-98e5-e33898be1555._msdcs.eisner.biz) couldn't be
resolved, the server name (DC3.INTERNAL.LOCAL) resolved to the IP
address (192.168.2.10) and was pingable. Check that the IP address
is
registered correctly with the DNS server.
......................... DC3 failed test Connectivity




My System SpecsSystem Spec
Old 10-30-2008   #2 (permalink)
Bill Grant


 
 

Re: P2V bizarre?



"John" <John@xxxxxx> wrote in message
news:C5CDC6CE-D48E-4FD6-ACBC-F086D0DF752B@xxxxxx
Quote:

> Hi all,
>
> By mistake, I did P2V one of our W2K3 domain controller and the domain
> controller's GUID can not be resolved to IP address now(lots of error NTDS
> KCC 1865,1311 and 1566). Does it mean that the physical machine has to be
> shut down after P2V? What if I just need to create several physical
> machine
> VHDs by using P2V and later put them on different hosts?
>
> Here is the Dcdiag test results's failed parts:
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> Done gathering initial info.
>
> Doing initial required tests
>
> Testing server: SITE3\DC3
> Starting test: Connectivity
> The host
> 626cd4d2-53e4-47ff-98e5-e33898be1555._msdcs.INTERNAL.LOCAL
> could not be resolved to an
> IP address. Check the DNS server, DHCP, server name, etc
> Although the Guid DNS name
> (626cd4d2-53e4-47ff-98e5-e33898be1555._msdcs.eisner.biz) couldn't
> be
> resolved, the server name (DC3.INTERNAL.LOCAL) resolved to the IP
> address (192.168.2.10) and was pingable. Check that the IP
> address
> is
> registered correctly with the DNS server.
> ......................... DC3 failed test Connectivity
>
>
>
I doubt that this has anything to do with virtualization. Have you ever
tried to do the same thing using P2P or restore from an image backup?

My System SpecsSystem Spec
Reply

Thread Tools


Similar Threads
Thread Forum
Bizarre WLM behavior: Live Mail
Bizarre internet problem Browsers & Mail
Bizarre performance issue Vista performance & maintenance
Bizarre problem. Software
Bizarre Vista DHCP/DNS Bug? Vista networking & sharing


Vista Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows Vista", the Start Orb, and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46