Her er en spiseseddel!
Linket:
http://support.novell.com/cgi-bin/search/search.pl?database_name=kb&type=HTML&docid=%03fF221929%3a966887370%3a%20%28%202000%20AND%20profiles%20%29%20%20AND%20%28%20productClass%20%3d%20%28%22NetWare%22%29%20%29%20%20AND%20%28%20docGroup%20%3d%20%280%29%20%29%20%20%07%01%00&byte_count=10191Og siden:
Windows NT Roaming Profiles & the NT Client (Last modified: 05APR2000)
This document (10050571) is provided subject to the disclaimer at the end of this document.
Printer friendly version of this document
Forward this document to a colleague
Provide feedback about this document to Novell
--------------------------------------------------------------------------------
Fact
Novell Client 4.x for Windows NT
Microsoft Windows NT
Formerly TID 2939923
--------------------------------------------------------------------------------
Symptom
Windows NT Roaming Profiles & the NT Client
--------------------------------------------------------------------------------
Fix
Microsoft Windows NT allows users to customize their desktop and to have that custom configuration follow
them throughout the network, this is referred to as a roaming profile. The IntranetWare Client for Windows NT
4.11a and the Novell Client for Windows NT 4.30 extend the capability of roaming profiles so that they can be
stored on a NetWare file server. The following details information on known issues, troubleshooting, and
configuring roaming profiles using the Novell clients.
Configuring Roaming Profiles
1. If the 4.11a client is installed, roaming profiles stored on Netware servers can be enabled via the client control
panel on the advanced login tab. To do this select enable IntranetWare storage of roaming profiles and then
choose the location to store the profile. Under most cases the \"Relative to Home Directory\" should be used.
However, in the event that a mandatory profiles is desired then the option for \"Relative to Home Directory\" should
be unmarked and a UNC path should entered into the field for IntranetWare File System.
2. If the 4.30 client is installed, roaming profiles can only be enabled by creating a Z.E.N.works NT User Policy
Package, enabling NT Desktop Preferences policy and selecting the \"Roaming Profiles\" tab. This page is the
same as was previously in the client control panel. At this point set the appropriate storage location for the
roaming profile.
3. If the 4.30 client is installed, the workstation manager service must also be installed in order to read the
ZENworks policies to enable roaming profiles.
Known Issues
1. If a user runs out of disk space on the network storage point the profile will not be written to the network, in
most cases this results in the roaming profile being corrupted. This issue occurs in both the 4.11a client as well
as the 4.30.
2. With the 4.11a client there appears to have been a problem with the NTUSER.DAT not always being closed
on logout. This would result in the NTUSER.DAT not being able to be read on subsequent warm logins. The
result is the creation of a local profile named user.00x. This issue appears to have been corrected in the Novell
Client for Windows NT 4.30.
3. In the 4.11a client there was a problem where the local profile could not be read by the client. This would
result in an access denied message when viewed with a debugger and would create a default user profile for the
user. This was corrected in the NT411P1.EXE patch for the 4.11a client. This fix was rolled into the 4.30 client
prior to it\'s release.
4. Microsoft policies can cause the loss of profiles through the setting of Custom Folders in an NT User or
Group Policy. This is also true of the corresponding ZENworks policies. See TID 2940740.
Troubleshooting
1. Verify that roaming profiles have been correctly enabled either in the client with 4.11a or by correctly
associating the user with a Z.E.N.works NT User Policy Package.
2. Verify that the user has sufficient space on the network storage point to store the profile.
3. Ensure that OS/2 namespace (3.1x, 4.10) or LONG namespace (4.11) has been loaded for the network
volume. When storing a roaming profile, it will create the \"Windows NT 4.0 Workstation Profile\" directory to
store it in. If the NetWare file server does not support LFN (Long FileName) Directories, then it will not be able to
save the profile to the NetWare server.
4. Ensure that the DeleteRoamingCache setting in the registry at HKLM/Software/Microsoft/Windows
NT/CurrentVersion/Winlogon key is set to the appropriate setting for your environment.
Note: DeleteRoamingCache will delete the user\'s local copy of the roaming profile during logout. This can be a
problem if there is a problem writing the profile to the network and there will be no local profile to fall back on, in
this case the profile would have to be re-created. Furthermore, if at a later time the roaming profiles were turned
off for the user the result would be a lost profile.
5. Verify that you are not encountering the issue described in TID 2939925. This document describes a problem
with losing the profile if using Workstation Manager 1.0 to upgrade from the 4.11a to the 4.3 client.
6. Disable virus scanning software and other service which may be locking the registry.
7. Try troubleshooting the Microsoft\'s environment as described in MS Technical Documents: Q174520,
Q177662, and Q154120. .
--------------------------------------------------------------------------------
Please select if this document solved your problem.
--------------------------------------------------------------------------------
Document Title: Windows NT Roaming Profiles & the NT Client
Document ID: 10050571
Solution ID: NOVL1639
Creation Date: 20MAR2000
Modified Date: 05APR2000
Novell Product Class: NetWare
Novell Product and Version: Novell Clients
/TWM
Ny bruger
Nybegynder
Opret
Preview
