I have a client with sbs2003 and its server refresh time. Moving to sbs2011 and VMware ESxi but they have a server based app that is based around cobol and the 3rd party dev company want to charge a sizeable fee to migrate which I would rather avoid asking my client to pay. So, I am looking at ways to workaround this.

1. We will be using vmware in this new sbs2011 and I was wondering if I could p2V the existing sbs2003 box and that way still have access to the app on a virtual server.

2.Or have the sbs2003 machine just as a second server on the network - the pc's accessing the server app as usual?

As always your advice is welcome.


asked 10/26/2011 05:29

pabby061203's gravatar image

pabby061203 ♦♦

6 Answers:
You could P2V the existing installation using VMware Converter, but it would depend if the license was OEM.

Note: Physical-to-virtual hard drive migration of a Windows installation is a valid function for customers with Software Assurance and full retail copies of Windows XP, Windows Vista, and Windows 7. Software Assurance provides users valuable benefits—please contact Microsoft Corporation for further information. Windows XP, Windows Vista and Windows 7 installed by Original Equipment Manufacturers (OEM) using OEM versions of these products may not be transferred to a virtual hard drive in accordance with Microsoft licensing terms.
hanccocka's gravatar image


there is very little issue having sbs on the same network. but..
make sure only one server is running dhcp - the new one
make sure you have two domains - and the old sbs server is the only machine on the old domain.

you could do a migration to get the sbs 2003 server upgraded to the sbs 2011 environment, and then leave the demoted sbs 2003 running just as a server to have old app running.

the virtualization shouldnt realy effect things - you will have the same issues as if you had physical servers.
wolfcamel's gravatar image


Once you have migrated the users, exchange etc to the new server, you can uninstall the SBS components from your SBS 2003, and then should be able to join the EX-SBS box to the domain.

Whether you do this in a VM or Physical, the process is the same.

<edited by leew>
CSIPComputing's gravatar image


The above answers are largely INCORRECT.

You CANNOT have two SBS servers in the same domain.  SBS is licensed to be the FSMO master DC.  You CANNOT change this.  In a migration, a new SBS server becomes the FSMO master DC and the old one begins a grace period that ends a few weeks later - when it ends, the old server starts shutting down every couple of hours or so (somewhat random in the EXACT amount of time) because you are violating licensing.

There is nothing that can be done to get around this requirement - any attempt to do so would be considered a license violation - which we cannot help you with.
leew's gravatar image


Apologies, an honest mistake.
CSIPComputing's gravatar image


OK - Thanks for all responses. I understand the idea - no two sbs boxes on the same domain. P2v OK if its not OEM. I have a new workaround to this. A standard server  - member server -2003 on the same domain /network and migrate the app to that instead of an sbs box. Thanks again and points to LEEW
pabby061203's gravatar image


Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments



Asked: 10/26/2011 05:29

Seen: 307 times

Last updated: 11/01/2011 07:45