Cool Solutions

Using Profiles on Terminal Servers

coolguys

By:

July 25, 2006 12:00 am

Reads: 4281

Comments:0

Score:0

ENVIRONMENT: NetWare 6.5 SP5
ZENworks 7
Windows 2003 Terminal Server SP1

When you are working with ZENworks DLU, terminal server and server-based user profiles, you can have problems with saving these profiles to a NetWare volume. All settings get lost when the user logs off. The problem is a security setting from Microsoft which checks if the user is the owner from this profile. But ZENworks gives the user at every login a new SID so the user will never be the owner for the Microsoft System and so the terminal server will never save the profile.

Solution

You can implement a computer policy via ZENworks or by setting a Registry Key.

Policy:

Deactivate checks for existing roaming user profile folders

Computerconfiguration\Administrative Template\System\Userprofile\

Registry:

Set the following keys:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]
"CompatibleRUPSecurity"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon]
"CompatibleRUPSecurity"=dword:00000001

After that, restart your terminal server and your profiles should be saved.

You can check it when you look at the last modified date from the ntuser.dat in the roaming profile.

For more information, see this TID.

If you have any questions you may contact Bjoern at bjoern.schoenhoff@capgemini.com

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS