Article

coolguys's picture
article
Reads:

4065

Score:
0
0
 
Comments:

0

Using Profiles on Terminal Servers

Author Info

24 July 2006 - 11:00pm
Submitted by: coolguys

Author Blog
Author Profile

Tags

Tags Map

(View Disclaimer)

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


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

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, test, test before you do anything drastic with it.



Related Articles


User Comments

© 2013 Novell