Welcome To NetTech Solutions

Warm Welcome to Every Visitor. Here we serve best technical support, all the posts here you find will help you solving and facing the day to day problems.
Every one is welcome to comment on our Posts.

Saturday, May 31, 2008

IP Addressing and Subnetting for New Users

IP Addressing and Subnetting for New Users
By Yusuf Usmani
Introduction
Prerequisites
Requirements Components Used Additional Information Conventions
Understanding IP Addresses Network Masks
Understanding Subnetting Examples
Sample Exercise 1 Sample Exercise 2
VLSM Example
VLSM Example
CIDR
Appendix
Sample Config
Host/Subnet Quantities Table
NetPro Discussion Forums - Featured Conversations Related Information
Introduction

This document gives you basic information needed to configure your router for routing IP, such as how addresses are broken down and how subnetting works. You learn how to assign each interface on the router an IP address with a unique subnet. There are many examples to help tie everything together.
Prerequisites
Requirements

There are no specific prerequisites for this document.
Components Used

This document is not restricted to specific software and hardware versions.
Additional Information

If definitions are helpful to you, use these vocabulary terms to get you started:

· Address_The unique number ID assigned to one host or interface in a network.
· Subnet_A portion of a network sharing a particular subnet address.
· Subnet mask_A 32-bit combination used to describe which portion of an address refers to the subnet
and which part refers to the host.
· Interface_A network connection.


If you have already received your legitimate address(es) from the InterNIC (Internet Network Information Center), you are ready to begin. If you are not planning on connecting to the Internet, we strongly suggest that you use reserved addresses from RFC 1918 .
Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.
Understanding IP Addresses

An IP address is an address used to uniquely identify a device on an IP network. The address is made up of 32 binary bits which can be divisible into a network portion and host portion with the help of a subnet mask. The 32 binary bits are broken into four octets (1 octet = 8 bits). Each octet is converted to decimal and separated by a period (dot). For this reason, an IP address is said to be expressed in dotted decimal format (for example, 172.16.81.100). The value in each octet ranges from 0 to 255 decimal, or 00000000 - 11111111 binary.

Here is how binary octets convert to decimal: The right most bit, or least significant bit, of an octet holds a value of 20. The bit just to the left of that holds a value of 21. This continues until the left-most bit, or most significant bit, which holds a value of 27. So if all binary bits are a one, the decimal equivalent would be 255 as shown here:

1 1 1 1 1 1 1 1
128 64 32 16 8 4 2 1 (128+64+32+16+8+4+2+1=255)

Here is a sample octet conversion when not all of the bits are set to 1.

0 1 0 0 0 0 0 1
0 64 0 0 0 0 0 1 (0+64+0+0+0+0+0+1=65)

And this is sample shows an IP address represented in both binary and decimal.

10. 1. 23. 19 (decimal)
00001010.00000001.00010111.00010011 (binary)
These octets are broken down to provide an addressing scheme that can accommodate large and small networks. There are five different classes of networks, A to E. This document focuses on addressing classes A to C, since classes D and E are reserved and discussion of them is beyond the scope of this document.

Note: Also note that the terms "Class A, Class B" and so on are used in this document to help facilitate the understanding of IP addressing and subnetting. These terms are rarely used in the industry anymore because of the introduction of classless interdomain routing (CIDR).
Given an IP address, its class can be determined from the three high-order bits. Figure 1 shows the significance in the three high order bits and the range of addresses that fall into each class. For informational purposes, Class D and Class E addresses are also shown.

Figure 1



In a Class A address, the first octet is the network portion, so the Class A example in Figure 1 has a major network address of 10. Octets 2, 3, and 4 (the next 24 bits) are for the network manager to divide into subnets and hosts as he/she sees fit. Class A addresses are used for networks that have more than 65,536 hosts (actually, up to 16777214 hosts!).

In a Class B address, the first two octets are the network portion, so the Class B example in Figure 1 has a major network address of 172.16. Octets 3 and 4 (16 bits) are for local subnets and hosts. Class B addresses are used for networks that have between 256 and 65534 hosts.

In a Class C address, the first three octets are the network portion. The Class C example in Figure 1 has a major network address of 193.18.9. Octet 4 (8 bits) is for local subnets and hosts - perfect for networks with less than 254 hosts.
Network Masks

A network mask helps you know which portion of the address identifies the network and which portion of the address identifies the node. Class A, B, and C networks have default masks, also known as natural masks, as shown here:

Class A: 255.0.0.0 Class B: 255.255.0.0 Class C: 255.255.255.0

An IP address on a Class A network that has not been subnetted would have an address/mask pair similar to:
8.20.15.1 255.0.0.0. To see how the mask helps you identify the network and node parts of the address, convert the address and mask to binary numbers.

8.20.15.1 = 00001000.00010100.00001111.00000001 255.0.0.0 = 11111111.00000000.00000000.00000000

Once you have the address and the mask represented in binary, then identifying the network and host ID is easier. Any address bits which have corresponding mask bits set to 1 represent the network ID. Any address bits that have corresponding mask bits set to 0 represent the node ID.

8.20.15.1 = 00001000.00010100.00001111.00000001 255.0.0.0 = 11111111.00000000.00000000.00000000

net id host id

netid = 00001000 = 8
hostid = 00010100.00001111.00000001 = 20.15.1
Understanding Subnetting

Subnetting allows you to create multiple logical networks that exist within a single Class A, B, or C network. If you do not subnet, you are only able to use one network from your Class A, B, or C network, which is unrealistic.

Each data link on a network must have a unique network ID, with every node on that link being a member of the same network. If you break a major network (Class A, B, or C) into smaller subnetworks, it allows you to create a network of interconnecting subnetworks. Each data link on this network would then have a unique network/subnetwork ID. Any device, or gateway, connecting n networks/subnetworks has n distinct IP addresses, one for each network / subnetwork that it interconnects.

In order to subnet a network, extend the natural mask using some of the bits from the host ID portion of the address to create a subnetwork ID. For example, given a Class C network of 204.17.5.0 which has a natural mask of 255.255.255.0, you can create subnets in this manner:

204.17.5.0 - 11001100.00010001.00000101.00000000
255.255.255.224 - 11111111.11111111.11111111.



--------------------------sub---
By extending the mask to be 255.255.255.224, you have taken three bits (indicated by "sub") from the original host portion of the address and used them to make subnets. With these three bits, it is possible to create eight subnets. With the remaining five host ID bits, each subnet can have up to 32 host addresses, 30 of which can actually be assigned to a device since host ids of all zeros or all ones are not allowed (it is very important to remember this). So, with this in mind, these subnets have been created.

204.17.5.0 255.255.255.224 host address range 1 to 30
204.17.5.32 255.255.255.224 host address range 33 to 62
204.17.5.64 255.255.255.224 host address range 65 to 94
204.17.5.96 255.255.255.224 host address range 97 to 126
204.17.5.128 255.255.255.224 host address range 129 to 158



204.17.5.160 255.255.255.224 host address range 161 to 190



204.17.5.192 255.255.255.224 host address range 193 to 222



204.17.5.224 255.255.255.224 host address range 225 to 254
Note: There are two ways to denote these masks. First, since you are using three bits more than the "natural" Class C mask, you can denote these addresses as having a 3-bit subnet mask. Or, secondly, the mask of 255.255.255.224 can also be denoted as /27 as there are 27 bits that are set in the mask. This second method is used with CIDR. Using this method, one of these networks can be described with the notation prefix/length. For example, 204.17.5.32/27 denotes the network 204.17.5.32 255.255.255.224. When appropriate the prefix/length notation is used to denote the mask throughout the rest of this document.

The network Subnetting scheme in this section allows for eight subnets, and the network might appear as:

Figure 2

Notice that each of the routers in Figure 2 is attached to four subnetworks, one subnetwork is common to both routers. Also, each router has an IP address for each subnetwork to which it is attached. Each subnetwork could potentially support up to 30 host addresses.
This brings up an interesting point. The more host bits you use for a subnet mask, the more subnets you have available. However, the more subnets available, the less host addresses available per subnet. For example, a Class C network of 204.17.5.0 and a mask of 255.255.255.224 (/27) allows you to have eight subnets, each with 32 host addresses (30 of which could be assigned to devices). If you use a mask of 255.255.255.240 (/28), the break down is:

204.17.5.0 - 11001100.00010001.00000101.00000000
255.255.255.240 - 11111111.11111111.11111111.11110000 --------------------------sub --
Since you now have four bits to make subnets with, you only have four bits left for host addresses. So in this case you can have up to 16 subnets, each of which can have up to 16 host addresses (14 of which can be assigned to devices).
Take a look at how a Class B network might be subnetted. If you have network 172.16.0.0 ,then you know that its natural mask is 255.255.0.0 or 172.16.0.0/16. Extending the mask to anything beyond 255.255.0.0 means you are subnetting. You can quickly see that you have the ability to create a lot more subnets than with the Class C network. If you use a mask of 255.255.248.0 (/21), how many subnets and hosts per subnet does this allow for?

172.16.0.0 -10101100.00010000.00000000.00000000
255.255.248.0 -11111111.11111111.11111000.



----------------- sub ----------
You are using five bits from the original host bits for subnets. This allows you to have 32 subnets (25). After using the five bits for subnetting, you are left with 11 bits for host addresses. This allows each subnet so have 2048 host addresses (211), 2046 of which could be assigned to devices.
Note: In the past, there were limitations to the use of a subnet 0 (all subnet bits are set to zero) and all ones subnet (all subnet bits set to one). Some devices would not allow the use of these subnets. Cisco Systems devices allow the use of these subnets when the ip subnet zero command is configured.
Examples
Sample Exercise 1


Now that you have an understanding of subnetting, put this knowledge to use. In this example, you are given two addresses / mask combinations, written with the prefix/length notation, which have been assigned to two devices. Your task is to determine if these devices are on the same subnet or different subnets. You can do this
by using the address and mask of each device to determine to which subnet each address belongs.



Device A: 172.16.17.30/20
Device B: 172.16.28.15/20

Determining the Subnet for Device A:

172.16.17.30 - 10101100.00010000.00010001.00011110
255.255.240.0 - 11111111.11111111.11110000.00000000
----------------- sub-----------
subnet = 10101100.00010000.00010000.00000000 = 172.16.16.0
Looking at the address bits that have a corresponding mask bit set to one, and setting all the other address bits to zero (this is equivalent to performing a logical "AND" between the mask and address), shows you to which subnet this address belongs. In this case, Device A belongs to subnet 172.16.16.0.

Determining the Subnet for Device B:

172.16.28.15 - 10101100.00010000.00011100.00001111
255.255.240.0 - 11111111.11111111.11110000.00000000
----------------- sub-----------
subnet = 10101100.00010000.00010000.00000000 = 172.16.16.0

From these determinations, Device A and Device B have addresses that are part of the same subnet.
Sample Exercise 2

Given the Class C network of 204.15.5.0/24, subnet the network in order to create the network in Figure 3 with the host requirements shown.

Figure 3


Looking at the network shown in Figure 3, you can see that you are required to create five subnets. The largest subnet must support 28 host addresses. Is this possible with a Class C network? and if so, then how?
You can start by looking at the subnet requirement. In order to create the five needed subnets you would need to use three bits from the Class C host bits. Two bits would only allow you four subnets (22).
Since you need three subnet bits, that leaves you with five bits for the host portion of the address. How many hosts does this support? 25 = 32 (30 usable). This meets the requirement.
Therefore you have determined that it is possible to create this network with a Class C network. An example of how you might assign the subnetworks is:

netA: 204.15.5.0/27 host address range 1 to 30
netB: 204.15.5.32/27 host address range 33 to 62
netC: 204.15.5.64/27 host address range 65 to 94


netD: 204.15.5.96/27 host address range 97 to 126
netE: 204.15.5.128/27 host address range 129 to 158
VLSM Example

In all of the previous examples of subnetting, notice that the same subnet mask was applied for all the subnets. This means that each subnet has the same number of available host addresses. You can need this in some cases, but, in most cases, having the same subnet mask for all subnets ends up wasting address space. For example, in the Sample Exercise 2 section, a class C network was split into eight equal-size subnets; however, each subnet did not utilize all available host addresses, which results in wasted address space. Figure 4 illustrates this wasted address space.

Figure 4

Figure 4 illustrates that of the subnets that are being used, NetA, NetC, and NetD have a lot of unused host address space. It is possible that this was a deliberate design accounting for future growth, but in many cases this is just wasted address space due to the fact that the same subnet mask is being used for all the subnets.
Variable Length Subnet Masks (VLSM) allows you to use different masks for each subnet, thereby using address space efficiently.


Given the same network and requirements as in Sample Exercise 2 develop a subnetting scheme using VLSM, given:
VLSM Example

netA: must support 14 hosts netB: must support 28 hosts netC: must support 2 hosts netD: must support 7 hosts netE: must support 28 host

Determine what mask allows the required number of hosts.

netA: requires a /28 (255.255.255.240) mask to support 14 hosts netB: requires a /27 (255.255.255.224) mask to support 28 hosts netC: requires a /30 (255.255.255.252) mask to support 2 hosts netD*: requires a /28 (255.255.255.240) mask to support 7 hosts netE: requires a /27 (255.255.255.224) mask to support 28 hosts
* a /29 (255.255.255.248) would only allow 6 usable host addresses therefore netD requires a /28 mask.

The easiest way to assign the subnets is to assign the largest first. For example, you can assign in this manner:

netB: 204.15.5.0/27 host address range 1 to 30
netE: 204.15.5.32/27 host address range 33 to 62 netA: 204.15.5.64/28 host address range 65 to 78 netD: 204.15.5.80/28 host address range 81 to 94 netC: 204.15.5.96/30 host address range 97 to 98

This can be graphically represented as shown in Figure 5:

Figure 5
Figure 5 illustrates how using VLSM helped save more than half of the address space.

CIDR

Classless Interdomain Routing (CIDR) was introduced to improve both address space utilization and routing scalability in the Internet. It was needed because of the rapid growth of the Internet and growth of the IP routing tables held in the Internet routers.

CIDR moves way from the traditional IP classes (Class A, Class B, Class C, and so on). In CIDR , an IP network is represented by a prefix, which is an IP address and some indication of the length of the mask. Length means the number of left-most contiguous mask bits that are set to one. So network 172.16.0.0 255.255.0.0 can be represented as 172.16.0.0/16. CIDR also depicts a more hierarchical Internet architecture, where each domain takes its IP addresses from a higher level. This allows for the summarization of the domains to be done at the higher level. For example, if an ISP owns network 172.16.0.0/16, then the ISP can offer 172.16.1.0/24, 172.16.2.0/24,and so on to customers. Yet, when advertising to other providers, the ISP only needs to advertise 172.16.0.0/16.

For more information on CIDR, see RFC 1518 and RFC 1519 .
Appendix
Sample Config

Routers A and B are connected via serial interface.
Router A
Hostname router A!
ip routing !
int e 0
ip address 172.16.50.1 255.255.255.0 !(subnet 50)
int e 1 ip address 172.16.55.1 255.255.255.0 !(subnet 55)
int t 0 ip address 172.16.60.1 255.255.255.0 !(subnet 60) int s 0
ip address 172.16.65.1 255.255.255.0 (subnet 65) !S 0 connects to router B
router rip
network 172.16.0.0

Router B
Hostname router B!
ip routing !
int e 0
ip address 192.1.10.200 255.255.255.240 !(subnet 192)
int e 1
ip address 192.1.10.66 255.255.255.240 !(subnet 64)
int s 0
ip address 172.16.65.2 (same subnet as router A's s 0) !Int s 0 connects to router A
router rip
network 192.1.10.0
Network 172.16.0.0
Host/Subnet Quantities Table

Class B Effective Effective
# bits Mask Subnets Hosts

1 255.255.128.0 2 32766
2 255.255.192.0 4 16382
3 255.255.224.0 8 8190
4 255.255.240.0 16 4094
5 255.255.248.0 32 2046
6 255.255.252.0 64 1022
7 255.255.254.0 128 510
8 255.255.255.0 256 254
9 255.255.255.128 512 126
10 255.255.255.192 1024 62
11 255.255.255.224 2048 30
12 255.255.255.240 4096 14
13 255.255.255.248 8192 6
14 255.255.255.252 16384 2

Class C Effective Effective
# bits Mask Subnets Hosts

1 255.255.255.128 2 126
2 255.255.255.192 4 62
3 255.255.255.224 8 30
4 255.255.255.240 16 14
5 255.255.255.248 32 6
6 255.255.255.252 64 2

*Subnet all zeroes and all ones included. These might not be supported on some legacy systems. *Host all zeroes and all ones excluded.








Friday, May 30, 2008

User Profile Management


User Profile Management

By Yusuf Y. Usmani.

A new user should get a decent default configuration when he logs into his new account for the first time. On UNIX we copy a .profile or .cshrc and a few more bits to his new home and are done. On windows we can do this too, its just a wee little bit more complex. Who would have thought?

Central Default Profile

When a user accesses his account for the first time, Windows copies an initial profile for the user from C:\Documents and Settings\Default User.

This is not ideal because the Default User directory is local to every machine and not easy to customize. We would rather have this on our server. This fortunately is a features which is built into windows already. When you login on a machine and windows can not find your profile it first looks for a directory called

%LOGONSERVER%\NETLOGON\Default User

if this exists its contents is used as a default profile for the user. Windows will only use the local Default User if this global directory does not exist.

Folder Redirection

All the users’ configuration ends up in his profile. Whenever a user logs in or out on a machine the whole profile directory gets copied back and forth between the server. This is nice for disconnected operation. But since we run our desktops on a network this has no real advantages except making things SLLLLLOOOOOOW.

Fortunately windows allows you to redirect most things which are located in the profile to other places. This is called Folder Redirection. In the GPO editor you even find a plug-in where you can define the location for (only) 4 folders. Well there are many more in the users profile directory, just have a look. In the registry we find:

HKEY_CURRENT_USER
     \Software\Microsoft\Windows
          \CurrentVersion\Explorer
                  \User Shell Folders

This key contains a long list of folders which can be redirected. By default all these entries point to folder in:

%USERPROFILE%\...

as expected. Logon time can be improved massively by moving as much material as possible out of the profile into a directory which gets shared from the server. In our setup we keep these folders a special subdirectory in the users home share called Windows Config. So we change the Folder Redirection settings to:

%LOGONSERVER%\home\%USERNAME%\Windows Config\...

Note: If you have a setup with several LOGON Servers, this approach will not do as the users home directories will not be on all servers. You may want to assign a drive letter to the users home in the account settings (not in the logon script) and then redirect to this drive letter.

Only the Local Settings and Temp directories should remain in the profile. By default these folders do not get roamed. They stay local on each machine and are therefor no problem for us. They can even be removed if space is tight and will get recreated when the user logs in again. The folders that do not get roamed are controlled by:

HKEY_CURRENT_USER
    \Software\Microsoft\Windows NT
                   \CurrentVersion\Winlogon
"ExcludeProfileDirs" =
      "Local Settings;Temporary Internet Files;History;Temp"

The only thing that remains in the users profile is the registry database: ntuser.dat.

We have defined a home directory for each user in his active directory account and have set the profile path to

%LOGONSERVER%\home\%USERNAME%\profile

Now we have a second directory in every users home:

%LOGONSERVER%\home\%USERNAME%\Windows Config

Note, which we have chosen to redirect My Documents to

%LOGONSERVER%\home\%USERNAME%\data

To make sure it stays separate from the application configuration data.

Customizing the Default User

The reason for having a central Default User directory on the NETLOGON share is that we now can easily define default settings for our new accounts. The easy way is:

  • create a new user
  • login and modify all the settings to your hearts delight, especially also the User Shell Folders section of the registry
  • logout login as domain administrator and copy the ntuser.dat from this new users profile to Default User directory on the NETLOGON share of your server.

now whenever a new user logs in he gets this customized ntuser.dat.

The 'modify all the settings to your hearts delight' bit is not exactly reproducible, so we have chosen to use a more controlled approach. Using the Install Capture function of our software packaging tool (Wise for Windows Installer) we figured out the registry keys making up the necessary changes we wanted in our environment and then used regedit to save this information into a reg file. Now you can use regedit32 to load a pristine copy of ntuser.dat under the name 'MyDefaultUser'. Edit the reg file and replace all occurrences of HKEY_CURRENT_USER with HKEY_LOCAL_MACHINE\MyDefaultUser. Now double click (aargh) the reg file to load it into the registry. Its information will go into the loaded hive. Now unload the hive and use this patched copy of ntuser.dat in your NETLOGON share.

You might also want to look at the reg utility from the resource kit; it allows loading hives from the command line as well as applying reg files.

Distributing Default Configuration Files

In a normal setup all the user’s data lives in his profile directory. And when he logs in for the first time all the necessary default files and directories get copied from the Default User directory. With our approach where most of the folders live outside the profile, users will not get a default setup for their Start Menu or other structures living outside the registry.

To solve this we must provide a default set of files to the user when he logs in for the first time. One way to solve this would be to supply a logon script which copies the files if they do not exist. We found a more elegant solution by using the:

HKEY_CURRENT_USER
  \Software\Microsoft\Windows\CurrentVersion\Runonce

key. We set it (in the Default Users's ntuser.dat) to

inituser=%LOGONSERVER%\NETLOGON\inituser.cmd

And in the initusers.cmd file we do a (all on one line!)

start "Copying ..." /min
  xcopy /I /E /H /K /Y
     "%LOGONSERVER%\NETLOGON\Default Windows Config"
                              "%HOMESHARE%\Windows Config"

In the Default Windows Config directory we keep copies of all the directories and files which we have redirected away from the Default Users tree.

Note on Fixing Internet Explorer Favorites

If IE can not access the Favorites Folder in its location on the server it picks a new folder to store it. This folder is on the local machine. Even when the server comes back, IE will remain hooked to the local favorite’s folder (which is empty). To fix this:

  • Delete local profile.
  • Connect to profile server:
  • Run regedt32. Open HKLM Registry - > Load Hive and from profile server\home\user_name\profile open NTUSER.DAT
·                Key Name: user_name
 
  • Open user_name\Software\Microsoft\Windows\CurrentVersion\Explorer

In UserShellFolders write:

Favourites: REG_EXPAND_SZ: %logonserver%\home\%username%\WindowsConfig\Favorites

In ShellFolders write:

Favorites: REG_SZ:\\CHARON\home\user_name\Windows Config\Favorites

Further Reading

The in the documentation for NewSID at http://www.sysinternals.com there are some interesting notes on HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList which contains the list of unloaded profile hives.

The Configuration for The User Session

To be independant from an initial profile we developed userinit. This scipt configures a users session when he logs in for the first time. userinit is started due to an entry in the registry in ntuser.dat inclued in the default user profile:

[HKEY_USERS\defaultuser\Software\Microsoft\Windows\CurrentVersion\Policies\System]
 "RunLogonScriptSync"=dword:00000001
[HKEY_USERS\defaultuser\Software\Microsoft\Windows\CurrentVersion\RunOnce]
 "RunUserinit"="c:\perl\bin\perl.exe \\winpack.ee.ethz.ch.\isgtc\bin\win32-userinit"

In addition userinit is started by loginmgr as a login script to be sure, that userinit is executed in every case.

The userinit script patches the user registry, copies the profile, and sets environment variables.

How To Creat a Roaming Profile?

Creating a Roaming User Profile

Creating a roaming user profile is a two-step process. First you create a test user profile, and then you copy the test user profile to a network server.

Create a Test Profile

To create a test profile for the roaming user, follow these steps:

1.

Log on as Administrator.

2.

Click Start, point to Administrative Tools, and then click Computer Management.

3.

In the console tree, expand Local Users and Groups, and then click Users.

4.

Right-click Users, and then click New User.

5.

Type a name and password for the user.

6.

Click to clear User must change password at next logon.

7.

Click Create, and then click Close.

8.

Quit the Computer Management snap-in.

9.

Log off the computer.

10.

Log on as the test user account that you created in step 7.

A user profile is automatically created on the local computer in the drive:\Documents and Settings\username folder (where drive is the drive on which Windows is installed).

11.

Configure the desktop environment, including appearance, shortcuts, and Start menu options.

12.

Log off, and then log on as Administrator.

Copy the Test Profile

To copy the test profile to a network server, follow these steps:

1.

Create a folder on a network drive in which you can store network profiles. For example:

\\server_name\Profiles\user_name

2.

Click Start, point to Control Panel, and then click System.

3.

Click the Advanced tab, and then click Settings in the User Profiles section of the System Properties dialog box.

4.

Under Profiles Stored On This Computer, click the profile for the user that you created in the "Create a Test Profile" section of this article, and then click Copy To.

5.

In the Copy Profile To dialog box, type the network path to the folder.

6.

Under Permitted to Use, click Change.

7.

Type the name of the user account that you created in the "Create a Test Profile" section, and then click OK.

8.

Click OK three times.

9.

Click Start, point to Administrative Tools, and then click Computer Management.

10.

In the console tree, expand Local Users and Groups, and then double-click Users.

11.

Double-click the user account that you created in the "Create a Test Profile" section.

12.

Click the Profile tab. In the Profile path box, type the path to the network profile folder. For example, type \\server_name\Profiles\user_name.

13.

Click OK.

14.

Quit the Computer Management snap-in.

NOTE: To make this profile mandatory, rename the Ntuser.dat file as Ntuser.man in the user's