ArtinSoft's Blogs

Software Migration Experts
Welcome to ArtinSoft's Blogs Sign in | Join | Help
in Search

Christian Saborío's Blog

The blog deals mostly with problems and their respective solutions that I find on day to day basis at my current workplace. Most of the issues so far deal specifically with Virtualization (mostly Microsoft related), 64-bit migration, and Windows 2003 issues. Many of the problems I have faced in various projects have been solved by reading someone else's blog. This is an effort to pay back and hopefully someone will be able to solve some of their problems by reading something within these pages.

June 2007 - Posts

  • Huge Advice When Upgrading Windows Server 2003 R2 to SP2

    I just found out (the hard way) about something (that I could not find documented anywhere) that should be done when you are upgrading a WIndows 2003 R2 SP1 box to SP2 if you are planning on using WDS.

    If you upgrade Windows Server without belonging to a domain, WDS will NOT work when you try and configure it. You will get a very useful error instead:

    WDS Error Code: 0xe0000102

    which can be translated to: "You should have been on a domain prior to installing SP2!"

    AFAIK, there is no turning back. I tested this theory using virtual machines and it holds - no domain, no WDS, no cigar.
  • Importing a VM from another Product? Uninstall the Additions!

    VMWare, VirtualPC, Virtual Server, Parallels - they all have one thing in common: in order to work faster, they install a set of drivers that patch the VM. This has a very positive effect on the virtual experience, but what happens when, say - the VMWare drivers are running under Virtual Server?

    As you might have guessed it, no good things happen. Products such as Parallels and VMWare Virtual Server allow you to import machines that were created with Microsoft's virtualization products. If you grab a machine from Microsoft's VHD test drive program and import it right away, you are in for a nasty surprise. The drivers for the previous product are still there, and they *will* conflict when you install the additions of the new product.

    So remember, get rid of your product's "additions" *before* migrating virtual machines.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems