7 Replies Latest reply on Dec 16, 2009 8:34 AM by Manisanjay

    Converter Standalone changes system drive letter

    cleanair Novice

      I have a Windows 2003 server that I am trying to convert from a physial server to a VM guest using vCenter Converter Standalone.  The original drive letters for this server are f: and g: where F: drive is my system boot drive.  As I go through the process, the target says F: and G: drive but when it is done it gives me an error that no operating sytem found.  I start the machine up and choose Windows Recovery mode and now see that the drive letters are changed to c: and d: drives which is why it will not start. I tried using diskpart from recovery mode but it will not allow me to change these drive letters.  How do I get it to change or remain at F: and G: when using the vcenter converter?

      Thanks.

        • 1. Re: Converter Standalone changes system drive letter
          continuum Guru
          User ModeratorsvExpert

          tricky - Converter does not handle unusual layouts well. You may have to fix this manually.

           

          Please post screenshot of old disklayout and the  new one - (screenshot of diskmanagement)

          One workaround is to use dummy-disks so that the old layout is preserved.

           

          The other workaround involves non-trivial registry hacks






          ___________________________________

           

          VMX-parameters- VMware-liveCD - VM-Sickbay

          1 person found this helpful
          • 2. Re: Converter Standalone changes system drive letter
            IamTHEvilONE Champion

            Also include boot.ini in your response.  This is part of the algorithm that Converter uses to detect the OS drive.

             

            However, I think converter manually remaps at least the OS drive letter .... but the logs will tell us that.



            Regards,

            EvilOne

            VMware vExpert 2009

            http://communities.vmware.com/servlet/JiveServlet/downloadImage/5441/VMW_vExpert_Q109_200px.jpg

            NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

            1 person found this helpful
            • 3. Re: Converter Standalone changes system drive letter
              cleanair Novice

              This server was a domain controller.  I ended up promoting another server to DC and then taking it offline to seize all the FSMO roles. 

              Just to let you know what I tried.  I could not send a screen shot of the new disk layout because the server would not start windows to even get to the disk management for layout.  All it would allow me to do was get to the recovery console which gave me limited commands.  I then did an NT backup of the server and tried to restore to a fresh install windows 2003 server but when I tried to do NT restore it would not restore because the new server had c and d drives and no f or g.  I then try to add an f and g and restore.  Even though I could restore the server, it still had the c and d drive and the restore did no good.  So I tried to build a new 2003 server with an f and g as system drives, but windows 2003 server will not allow that.  Come to find out, the server with the f and g was originally a Windows 2000 server that had been upgraded to a windows 2003 server so that was the only reason that server was able to have the disk layout like that to start with.  So after hours of trying this and that, I found it much easier just to promote another server as the PDC, seize the roles and just forget about trying to restore or convert the server with the not supported disk layout.

              • 4. Re: Converter Standalone changes system drive letter
                cleanair Novice

                Also tried the boot.ini change but basically as you can see from my last post, it didn't do any good because 2003 server does not support that disk layout and the only reason it worked was because it had been upgraded from a windows 2000 server.  I do appreciate everyones responses and trying to assist me.  Thanks.

                • 5. Re: Converter Standalone changes system drive letter
                  IamTHEvilONE Champion

                  Well, that explains a lot .. being a domain controller too.

                   

                  There's a KB on that ...

                   

                  Virtualizing existing domain controllers

                  http://kb.vmware.com/kb/1006996



                  Regards,

                  EvilOne

                  VMware vExpert 2009

                  http://communities.vmware.com/servlet/JiveServlet/downloadImage/5441/VMW_vExpert_Q109_200px.jpg

                  NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

                  • 6. Re: Converter Standalone changes system drive letter
                    continuum Guru
                    vExpertUser Moderators

                    ... because 2003 server does not support that disk layout

                     

                    what ? - here I am using 2003 fresh installed with even more weird disklayouts.

                     

                    Having system drive as F: is no problem in itself




                    ___________________________________

                     

                    VMX-parameters- VMware-liveCD - VM-Sickbay

                    • 7. Re: Converter Standalone changes system drive letter
                      Manisanjay Novice

                      Hi

                       

                      You can try this option but it is a long process. You can create one new virtual disk  say 5 GB on the same vm and install fresh OS on the new 5 GB virtual disk .Then boot the server and goto disk management and change the drive letter of the old disk to F and restart.

                       

                      Once you are able to boot from your f drive then delete the 5 GB virtual disk.