Announcement

Collapse
No announcement yet.

VMware image of NT 4.0 Domain Controller

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • VMware image of NT 4.0 Domain Controller

    As far as I know we cannot take vmware image of windows 2000 domain controllers (We can take the image but it will not work). What about NT 4.0 DC? I have one NT 4.0 DC which I need to move to a Vmware server. Will it work?

  • #2
    Re: VMware image of NT 4.0 Domain Controller

    It is possible to convert a Windows NT DC, see below instructions from VMware. It's just highly recommended you don't, you can also do Windows 2000. See more instructions at the link.

    http://kb.vmware.com/selfservice/mic...rnalId=1006996

    To convert a Windows NT domain controller:
    Verify that you have the latest version of VMware Converter. Older versions do not support all Windows NT Fault Tolerant disk types. Use VMware Converter version 3.0.3 or higher.
    Ensure the server is running Windows NT Service Pack 4 or higher (Service Pack 6a is recommended).

    To determine this:

    Click Start > Run.
    Run the winver command. Do not proceed any further if the service pack requirement is not met.

    Create a Rescue Diskette. Click Start > Run, and run the rdisk command. If there is a problem with the new virtual machine you may be able to repair the problem using the Rescue Diskette.
    Ensure you have a complete and working backup of the server, especially if the Windows NT server is a Primary Domain Controller (PDC).
    Ensure another domain controller is available to service user logins.

    Note: If you are taking a PDC server offline, you cannot join any other DCs to the domain until it is online again as a virtual machine.

    Install the Microsoft loopback adapter and assign it an unused static IP address.
    Set any static IP addresses of the physical network adapters to DHCP.
    Properly shut down the source server. Click Start > Shutdown > Shutdown the computer. Power off the server with its physical power switch.
    Boot the Converter cold clone CD.

    Warning: The Converter cold clone CD upgrades the NTFS version on the disk on the destination virtual machine to version 3.0 (NTFS5). This may prevent disk check (chkdsk ) and defrag utilities (Diskeeper) from working on the volume. For more information, see Windows NT 4.0 CHKDSK Refuses to Check NTFS 3.0/3.1 Volumes (http://support.microsoft.com/kb/196707).

    Warning: Performing a hot clone of a Windows NT server may result in a corrupted NTDS.DIT on the destination virtual machine. Do not hot clone a Windows NT domain controller.

    Perform the conversion to a new virtual machine, and power off the source server.

    Warning: Do not power the server back on again for any reason after the new virtual machine is powered on with a network connection. Doing so may break synchronization with other domain controllers.

    Review the virtual hardware settings on the new virtual machine:

    Adjust the number of virtual NICs.
    Remove any unnecessary devices such as USB controllers, COM ports or floppy drives.

    Power on the new virtual machine with the network card disconnected.
    Click Start > Settings > Control Panel > Add / Remove Programs. Remove any unnecessary programs used to install or support device drivers, such a RAID management tools, network teaming or management software, wireless card management software, and video and sound drivers.

    Caution: Do not restart if prompted by an uninstall program.

    Restart the virtual machine properly.
    Remove any additional devices or device drivers that were used to support hardware on the physical server. Use the Control Panel to remove any necessary devices especially COM ports, SCSI controllers, video, and network cards.

    Do not remove the following devices:

    Buslogic SCSI controller
    IDE CD-ROM ATAPI controller
    AMD PCNET network card

    Restart the virtual machine properly.
    Attempt to install the VMware Tools. If you are missing the CD-ROM drive in the virtual machine or if you are unable to get the network adapter installed or working, see After converting a physical server running Windows NT the CD-ROM or networking does not work on the VM (100227.
    Restart the virtual machine properly.
    Assign the static IP addresses used on the source server to the new virtual network adapters, if applicable.
    Restart the virtual machine properly.
    Ensure the DNS and directory services are started and bound to a valid adapter and start correctly.
    Remove the Microsoft loopback adapter.
    Restart the virtual machine properly.
    Review the server's Event Logs and ensure the necessary services are starting correctly without failures. To view the Event Log, click Start > Run, and run the eventvwr command.

    Note: Some failures may be due to device drivers or services still being installed. You may need to manually disable or remove these services in the Control Panel to prevent these errors.

    Shut down the virtual machine properly, then connect the network cards in the virtual device settings.
    Start the virtual machine normally.
    Ensure the DNS and directory services are started and bound to a valid adapter and start correctly.
    Check the Event Logs for any remaining errors and correct as needed.
    Important Notes:

    Avoid converting Windows NT domain controllers if possible.
    Before attempting conversion, always be sure another domain controller is online and properly synchronized.
    Never use the customization option in the Conversion Wizard. Using this process destroys the server on the destination.
    Always ensure that the source server is powered off or decommissioned before starting the new virtual machine with the network cards connected.


    Best of luck!! Cheers, Ravi Shanghavi, Ottawa

    Comment


    • #3
      Re: VMware image of NT 4.0 Domain Controller

      Supported Guest Operating Systems

      Converter Standalone 4.0.1 supports the following guest operating systems:

      Windows NT SP6 and later
      Windows 2000 SP4

      http://www.vmware.com/support/conver...401.html#platf

      Comment


      • #4
        Re: VMware image of NT 4.0 Domain Controller

        Thank You,

        The link says

        Converting a Windows NT domain controller is a very involved process that may be trouble prone. VMware does not recommend converting a Windows NT domain controller if at all possible.


        What about installing a new NT 4.0 BDC in vmware, promote it to PDC and then removing the physical machine?
        Last edited by avilt; 27th July 2010, 08:10.

        Comment


        • #5
          Re: VMware image of NT 4.0 Domain Controller

          What about removing the NT4 PDC at all?
          Marcel
          Technical Consultant
          Netherlands
          http://www.phetios.com
          http://blog.nessus.nl

          MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
          "No matter how secure, there is always the human factor."

          "Enjoy life today, tomorrow may never come."
          "If you're going through hell, keep going. ~Winston Churchill"

          Comment


          • #6
            Re: VMware image of NT 4.0 Domain Controller

            I wish I could, but we are running a legacy application on a NT 4.0 member server which will be phased out next year. Until then I have to manage this domain.

            Comment


            • #7
              Re: VMware image of NT 4.0 Domain Controller

              For a member server, there is no need for a NT4 PDC
              Marcel
              Technical Consultant
              Netherlands
              http://www.phetios.com
              http://blog.nessus.nl

              MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
              "No matter how secure, there is always the human factor."

              "Enjoy life today, tomorrow may never come."
              "If you're going through hell, keep going. ~Winston Churchill"

              Comment


              • #8
                Re: VMware image of NT 4.0 Domain Controller

                I mean this legacy application server is a member of NT 4.0 domain with only one DC. I have no users in this domain. My current production domain is 2008 R2 with trusts to NT domain and some users of my production domain need access to this legacy application.

                Comment


                • #9
                  Re: VMware image of NT 4.0 Domain Controller

                  Ok in that case you can follow your current proposal or try to do a P2V
                  Also remember this article in case you have network issues.

                  http://kb.vmware.com/selfservice/mic...rnalId=1007168
                  Marcel
                  Technical Consultant
                  Netherlands
                  http://www.phetios.com
                  http://blog.nessus.nl

                  MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
                  "No matter how secure, there is always the human factor."

                  "Enjoy life today, tomorrow may never come."
                  "If you're going through hell, keep going. ~Winston Churchill"

                  Comment

                  Working...
                  X