KB2008.909
FAQ: How to configure Domain Time Client or Server when making a cloned OS image

    This article applies to Domain Time II.

    Last Updated: 16 March 2016

    Question

      How do I configure Domain Time Client or Server properly when making a cloned OS image for installation?

    Answer

      To prepare Domain Time Client or Server on a machine being used for OS installation by cloning, perform the following steps:

      1. Install a new, fresh copy of Domain Time Client or Server onto the machine you want to create your master image.

      2. Set the configuration settings for the Client exactly the way that you want your cloned machines to operate.

      3. Do some test synchronizations and check the logs. Verify that the machine is working as expected.

      4. Prepare the installation for cloning. You may choose to use the Automatic Prep method or you may manually finish the client prep process:

         

        Automatic Prep Method (preferred) Version 5.2.b.20110831 or newer only
        1. Run the following command from the command-prompt elevated to administrative privileges (Run As Administrator):

            DTCheck /prepclone

          This performs all of the steps described in the Manual Prep Method below for you automatically. Once you've run the command, your machine is ready to be cloned.

        2. Make your master image copy of the operating system. Do not restart the Domain Time service before making the image. The Client will repopulate the deleted values on the cloned machine based on the new machine's hardware when the Domain Time service restarts.

         

        Manual Prep Method
        1. Stop (but do not disable) the Domain Time service.

          Important:
          If you fail to delete the following registry values with the Domain Time service stopped before making your image, your new machine may have the wrong clock rate and/or a duplicate serial number. Wrong clock rates will result in poor timekeeping. Unique serial numbers are critical for correct auditing; unique ClockIdentity values are critical for PTPv2 operation. Duplicated serial numbers will prevent machines from being added to Audit Server.

        2. Delete all registry values that start with the words "Clock Adjustment" from the HKLM\Software\Greyware\Domain Time Client[Server]\Parameters key, i.e.
          • Clock Adjustment (100-ns intervals)
          • Clock Adjustment Maximum
          • Clock Adjustment Minimum
            etc...

        3. Delete all registry values (if present) that start with the words "Critical Timing" from the HKLM\Software\Greyware\Domain Time Client[Server]\Parameters key, i.e.
          • Critical Timing Boost (ms)
          • Critical Timing Detected 'UsePlatformClock'
          • Critical Timing Interpolation Period
            etc...

        4. Delete all registry values (if present) from the HKLM\Software\Greyware\Domain Time Client[Server]\History\Clock key.

        5. Delete this registry value from HKLM\Software\Greyware\Domain Time Client[Server]\Time Sources\PTPv2 (IEEE 1588):
          • ClockIdentity Cache

        6. Delete this registry value from HKLM\Software\Classes\Gap\DT2\Info:
          • Serial Number

        7. Make your master image copy of the operating system. Do not restart the Domain Time service before making the image. Domain Time will repopulate the deleted values on the cloned machine based on the new machine's hardware when the Domain Time service restarts.

           

        Note: If you have already installed a cloned image without performing the above steps, you may fix any misbehaving machines by performing the Automatic Prep Method or the steps of the Manual Prep Method on the new machine, then rebooting the machine or restarting the Domain Time service.

Domain Time II Software distributed by Microsemi, Inc.
Documentation copyright © 1995-2017 Greyware Automation Products, Inc.
All Rights Reserved
All Trademarks mentioned are the properties of their respective owners.