Policies
We have:
PDC
BDC
2 Terminal Servers
All NT 4.0
The policies do not appear to take affect on the Terminal Servers. What could be the possible reasons?
Windows Forum
We have:
PDC
BDC
2 Terminal Servers
All NT 4.0
The policies do not appear to take affect on the Terminal Servers. What could be the possible reasons?
by devaraj1975
In some cases, users may have already been assigned Windows NT profiles. It may be desirable to assign Terminal Server?specific profiles to users whenever the user gains access to Terminal Server across the WAN or if the administrator wants to present a session to the user that is different from the user's own desktop.
Whenever a user logs on to a server running Terminal Server, the server will first search for the Terminal Server?specific profile. If Terminal Server cannot locate this profile, it will attempt to load the user's Windows NT profile. This may not be an ideal solution for users who gain access to Terminal Server over a slow WAN link because the Windows NT profile must be transferred across the slow link when the user logson.
Roaming profiles allow the user to move between different computers and maintain the same environment and preference settings. When a user logs on to Terminal Server, the system checks for the presence of a Terminal Server?specific roaming profile. If one is not found, it uses the Windows NT roaming profile instead.
There are two types of roaming profiles, mandatory and personal. A roaming mandatory user profile is a preconfigured user profile that the user cannot change. One mandatory profile can be assigned to many users. By changing one profile, the administrator can change several desktop environments. You should use this type of profile to assign common settings for all users who require identical desktop configurations.
A roaming personal user profile is a user profile that a user can change. This means that when the user logs off, the user profile is updated to include any changes the user made. When the same user logs on again, the profile is loaded as it was last saved.
by bill.beckett
by steve penn
If you are talking policies rather than profiles the answer is this.
You must also write a TS policy. Open policy editor then hit connect and enter the server name. You will then see a list of users currently logged on. Double click to edit theirTS policy.
OR
If you want blanket policies edit the registry.
HKLM\SYSTEM\CONTOL\CURRENT CONTROL SET\SYSTEM\UPDATE - I THINK.
Add a value called NetworkPath and enter the string as the path of a server where an NTConfig.pol file is.
Set the update to 2 - which sets it to manually pull a policy from the above path.
To edit the policy just open the NTConfig.POL from policy editor.
hope this helps
Steve
This discussion is closed to new replies.
Sort by Trending