W
William P
Guest
Situation
---------
Sever Farm containing W2K3SP1 servers
Users accessing WebInterface (WI) for applications
VBS logon script for printers, redirection and mapped drives setting
environment, Local
policy also.
Currently users using local profiles. Every night profiles are deleted ->
users lose customized settings.
I would like to switch to Mandatory policies and also use Flex profiles.
Restrictions:
-----------
NOT allowed to use use 'Terminal profile settings path' in the properties
for the user accounts.
What I have done so far:
Implemented local policy setting 'Set TS Roaming Profile path' to point to
another server.
Copied 'Default profile' from Ts to each user's TS roaming profile on the
other server.
Renamed NTUSER.DAT to NTUSER.MAN
Issue at stake:
--------------
I created a logon.cmd file and logoff.cmd file and set the Logon/Logoff
settings in the local policy on the servers in the farm. These scripts
restore and save changes made to an OPS file, first written localy then
copied back to the user's roaming profile.
When user starts WI, starts an application, say MS WORD, the local policy is
applied, the VBS script runs, and very quickly the logon.cmd file window
appears --> nothing happens.
As for the logoff.cmd script, it doesn't even run. --> I have no idea why!!
If I change the profile to "Roaming" instead of "Mandatory", both scripts run.
Does anyone have a clue as to why this is occurring?
I noticed that if I use the 'Terminal profile settings path' in the user
account properties, everything works fine.
i would appreciate any insight on my problem.
---------
Sever Farm containing W2K3SP1 servers
Users accessing WebInterface (WI) for applications
VBS logon script for printers, redirection and mapped drives setting
environment, Local
policy also.
Currently users using local profiles. Every night profiles are deleted ->
users lose customized settings.
I would like to switch to Mandatory policies and also use Flex profiles.
Restrictions:
-----------
NOT allowed to use use 'Terminal profile settings path' in the properties
for the user accounts.
What I have done so far:
Implemented local policy setting 'Set TS Roaming Profile path' to point to
another server.
Copied 'Default profile' from Ts to each user's TS roaming profile on the
other server.
Renamed NTUSER.DAT to NTUSER.MAN
Issue at stake:
--------------
I created a logon.cmd file and logoff.cmd file and set the Logon/Logoff
settings in the local policy on the servers in the farm. These scripts
restore and save changes made to an OPS file, first written localy then
copied back to the user's roaming profile.
When user starts WI, starts an application, say MS WORD, the local policy is
applied, the VBS script runs, and very quickly the logon.cmd file window
appears --> nothing happens.
As for the logoff.cmd script, it doesn't even run. --> I have no idea why!!
If I change the profile to "Roaming" instead of "Mandatory", both scripts run.
Does anyone have a clue as to why this is occurring?
I noticed that if I use the 'Terminal profile settings path' in the user
account properties, everything works fine.
i would appreciate any insight on my problem.