Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Hyper-V > Newbe Question
Ask a questionAsk a question
Search Forums:
 

AnswerNewbe Question

  • Monday, October 26, 2009 10:39 PMdkon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Just breaking into Hyper-V . . . got ahold of the syternals disk2vhd app.
    Thought this would be a great way to virtualize a production machine to test updates/etc.

    Problems arise once new VHD is brought up, as there are now 2 machines w/same name -one virtualized and one original (yes my hyper-v machine is production as well)

    Lots of issues with AD, as you can guess.

    Is there a way to bring the VM up and not have it conflict in AD the way I have thinngs setup?

    Thanks . . .

    -D
    dkon
     

Answers

  • Wednesday, October 28, 2009 2:14 AMTanner SMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    It doesn't happen all the time, but the things to remember about newSID. Running the tool on a system, makes it totally unsupported and if it does blue screen the system on the newer machines, it is an unrecoverable blue screen.
     

All Replies

  • Monday, October 26, 2009 11:05 PMBrianEhMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Take the VM offline.

    unjoin (while offline so it does not delete the record in AD).

    rename.

    join back to AD.

    Hyper-V or the VM are not really the problem - you have two computers with the exact same GUID in AD (and cuomter name - thus causing DNS problems as well).

    The best solution is to create a new machine SID before re-joining to AD (this can break some apps - but then renaming can as well).
    You can use sysprep or newSID for that (newSID is is easier when not deploying multiple new copies).

    Brian Ehlert (hopefully you have found this useful)
     
  • Tuesday, October 27, 2009 4:41 AMTanner SMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote
    Do not use newSID on a 2008 + greater machine, you will then experience a non-recoverable Blue screen.

    Tanner
    • Marked As Answer bydkon Tuesday, October 27, 2009 9:37 PM
    • Unmarked As Answer byBrianEhMVP, ModeratorTuesday, October 27, 2009 9:57 PM
    •  
     
  • Tuesday, October 27, 2009 9:37 PMdkon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    thanks much!
    dkon
     
  • Tuesday, October 27, 2009 10:30 PMj2 Global Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I've personally never had any bsod issues with running newsid on win 7, 2008, and 2008 r2.
     
  • Wednesday, October 28, 2009 2:14 AMTanner SMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    It doesn't happen all the time, but the things to remember about newSID. Running the tool on a system, makes it totally unsupported and if it does blue screen the system on the newer machines, it is an unrecoverable blue screen.
     
  • Thursday, October 29, 2009 5:15 PMNathan Lasnoski Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Have you thought about P2Ving several systems (including a domain controller) and creating a self-contained lab?  That can be an effective test strategy if your goal is to create as much similarity between your production and test environments as possible.
     
  • Friday, November 06, 2009 10:01 AMYassine_Souabni Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote


    Is there a way to bring the VM up and not have it conflict in AD the way I have thinngs setup?

    dkon

    I think no.
    You will have to rename the physical or newly captured virtual machine and ensure these machines have not the same SID.

    Capturing a server with the Disk2Vhd tool means that you will use that VM instead of the Physical one.

    So you can test your VM on production
    ensure that you've set your physical machine not connected to the network during that test period
    and the VM runs correctly, you can rebuild the physical machine for another use.