Setting DNS Domain Suffix Search Order During Unattend Install

Last reviewed: March 12, 1998
Article ID: Q178277
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the "Restoring the Registry" online Help topic in Regedit.exe or the "Restoring a Registry Key" online Help topic in Regedt32.exe.

SUMMARY

The unattended setup mode of Windows NT does not offer a way to specify the domain suffix search order. The ability to use a domain suffix search order may be very useful in certain business situations and can be accomplished at the end of the unattended installation process.

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

Method 1

  1. Create a text file with the following two lines of text and save it as Suffix.txt. The spacing must be exactly as shown below, where "xxxxxxxx.xxx" signifies a domain suffix. Up to six domain suffixes may be specified. The search order is left to right.

          \\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP
          \Parameters
          SearchList=testxxxx.com test2xxxx.net test3xxxx.gov
    

    NOTE: The above registry key is one path; it has been wrapped for readability.

  2. Copy Regini.exe and Suffix.txt to the $OEM$ subdirectory at the installation sharepoint. Regini.exe is a Windows NT Resource Kit Utility

  3. If one does not exist, create a Cmdlines.txt file in the $OEM and add the following line including the quotes:

          [Commands]
          ".\REGINI SUFFIX.TXT"
    

    Only one instance of the [Commands] heading should exist in the Cmdlines.txt file.

  4. Make sure the entry OEMPREINSTALL = Yes exists in the [UNATTEND] section of your Unattended.txt file.

Method 2

  1. Create a registry file with the following two lines of text and save it as Suffix.reg. The spacing must be exactly as shown below, where "xxxxxxxx.xxx" signifies a domain suffix. Up to six domain suffixes may be specified. The search order is left to right.

          \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip
          \Parameters
          "SearchList"="testxxxx.com test2xxxx.net test3xxxx.gov"
    

    NOTE: The above registry key is one path; it has been wrapped for readability.

  2. Copy Regedit.exe and Suffix.reg to the $OEM$ subdirectory at the installation sharepoint. Regedit.exe is provided with Windows NT.

  3. If one does not exist, create a Cmdlines.txt file in the $OEM and add the following line including the quotes:

          [Commands]
          ".\REGEDIT /s SUFFIX.REG"
    

    Only one instance of the [Commands] heading should exist in the Cmdlines.txt file.

  4. Make sure the entry OEMPREINSTALL = Yes exists in the [UNATTEND] section of your Unattended.txt file


Additional query words: unattended registry suffix domain
Keywords : ntsetup NTSrvWkst kbsetup
Version : WinNT:4.0
Platform : winnt
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.