Automate SQL Server Client-Network Configuration
December 1, 1999
When connecting to SQL Server the Client network configuration determines which network library will be used.
With SQL Server
comes the Client Network Utility which allows the setting of the library
and some other options. If you do not want to use the default settings (Named
Pipes/Auto Ansi To OEM conversion), you can either manually change the settings
on each computer or use a policy file.
In this article you will learn how to create a policy file
to automatically configure the Network Library settings for computers in your
domain You can then deploy that file on your domain controllers to automatically
configure the clients upon logon. (Remember that this only updates the settings
on the machine. This process cannot be used to install new network libraries on
Policy Files and Policy Templates
Policy files can be used for Windows 9x and Windows NT Clients. When logging on to a domain controller the information from the policy file will be applied to the local registry of the client.
With Windows NT and
Windows 9x ship predifined Policy templates which allow the setting of many
Operation System settings. This articles describes how to create a new
Policy Template to create Policies that update the registry information for the
SQL Server Network Library.
A warningIf you use system policies the local registries will be modified when a user logs on to the network. There is NO way to undo these registry changes. So make sure you only specifiy the settings for the computers you wish to update!
Download Policy Template filesEnglish Version: SQLE.ADM
German Version: SQLG.ADM
Please send comments