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.
|How to –
Step by Step
|Step 1:||Creating the Policy
The Client network configuration for SQL Server can be
The Policy Template file (a normal text file) starts by specifying the relevant Section
To be open for further amendments I include another
Now the Policies can be defined. The first policy will
The keyname specifies where the values are stored in the
For this value a dropdown list is created. The entries
So that is the end of the first policy. In policy editor (POLEDIT.EXE)
The following lines show, how the settings for
These lines define the values for checkboxes. For SQL
|Step 2:||Save the Policy Template
|Now you can save the File as SQL.ADM in the INF directory (Under
|Step 3:||Use the Template with
Then you can start Policy Editor and open the Template (Options,
Once this is done, a Policy file can be created or modified.
|Step 4:||Create a new policy file|
|To create a new policy file click on File, New.
Here you can either define the settings for all computers
Unfortunately there is no option to group computers. The
|Step 5:||Save the Policy File|
Save the file as NTCONFIG.POL in your NETLOGON share. (Remember
The next time a user logs on the NTCONFIG.POL file will be
To quick check whether your Policy Template works, open
If 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
English Version: SQLE.ADM
German Version: SQLG.ADM
Please send comments