Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 361
  • Last Modified:

Converting a Server 2003 DC / TS to Vmware

hi guys,

I have picked up a client who has an old Windows Server 2003 terminal server, which also is the solo domain controller in his office, and also runs an SQL database he had developed many years ago.  The office only has about five PCs and there are two external users/shops who remote into the server.

He is unable to reinstall this customised SQL application as he no longer has a relationship with the people who built it, so as the hardware it is on starts to fail, he has been installing a Shadowprotect image of it onto an identical physical server (he bought a bunch of HP xw8600 workstations some years ago for this purpose).  He has done this a couple of times successfully.

I've suggested to him we virtualise the server so then it is hardware independant and easier to backup and restore in the future.

So my question is - what do i need to look out for when virtualising a domain controller?  I have read many articles warning about the process, and recommending either not doing it, or building another DC first, promoting it, then demoting the original DC to a member server before converting it to a VM.  However, many of the warnings relating to USN issues seem to relate to multiple DC structures and replication problems.  I'm wondering if this would not be so much an issue for a single DC.  If i did virtualise it as is, what steps should i take to minimse any AD issues?  I read somewhere about problems relating to the new NIC created in a VM.

I have actually already created a VM of the server from a recent Shadowprotect image in the workshop just to see if it worked and what obvious issues may arise, and it boots up ok.  I can't see any glaring errors in the event log but I'm not really sure what to look for.

Any advise appreciated.

cheers
nathan
0
natrat22
Asked:
natrat22
2 Solutions
 
MaheshArchitectCommented:
I am not aware with ShadowProtect (may be something like Norton Ghost)

What u can do, setup one physical server with two virtual machines, at client place.
add it to above solo domain as member servers.
Now just promote one VM to ADC of above domain
just transfer all your FSMO roles on new virtual ADC
Then demote physical terminal server to member server
Now take complete server backup (Specially SQL)
Now you can make image (P2V) of physical terminal server and deploy it as a VM on new server.Note that remove any device drivers from physical terminal server prior to start P2V so that you will not face drivers issue most probably after P2V conversion.
may be you can use vmware converter or some else solution for P2V
OR

You can create new VM and just migrate Terminal server role with SQL if possible.

For 2003 domain controller servers, I personally not recommend to virtualalize with P2V technology

Mahesh
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
All you need to do is install VMware vCenter Converter Standalone 5.5, in the computer you want to convert, and click the Convert Computer button.

Copy or Convert this file to VMware ESXi, and your almost done.

HOW TO:  P2V, V2V for FREE - VMware vCenter Converter Standalone 5.5

HOW TO: Improve the transfer rate of a Physical to Virtual (P2V), Virtual to Virtual Conversion (V2V) using VMware vCenter Converter Standalone 5.0

HOW TO:  Synchronize changes when completing a P2V or V2V with VMware vCenter Converter Standalone 5.1

If you do this operation, when all the workstations in the office are off, and stop many of the services on the computer you are converting you will be fine.
0
 
diperspCommented:
You are correct - the warnings and "DO NOT DO THIS" threads for DCs are for when you have multiple DCs.  If you have a single DC, you're fine virtualizing it doing a P2V.

However, I would NOT recommend a DC and TS on the same box.  Split the DC and TS machines from each other.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
natrat22Author Commented:
Thanks, yes I totally agree, but it is difficult to convince him to do this due to the cost, and the fact he has been running it this way without issues for some years.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Just ask "him" what would do do if the current server failed? e.g. the hardware.

A virtualised server is very easy for DR purposes! As the virtual hardware is the same.
0
 
HaslerctCommented:
Hi,

There will be NO issue to P2v for your client, as he is only running with 1 single DC.

Thanks
0
 
natrat22Author Commented:
ESX standalone converter continually crashed when trying to live convert.  In the end I stripped out all the file shares to reduce the conversion size, then took a Shadowprotect image, then converted the shadowprotect image to a VM using the standalone converter.  There have been no issues with it being a DC.  Thanks guys.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now