S
systinte5
I have a weird problem. I have created a PRF file using Custom Maintenance
Wizard from Office Resource Kit 2003. I have placed the outlook.prf file in a
share where everyone has read permissions. I have set up a login script GPO
on the users OU under User Configuration. I have done gpupdate /force. When
users login, the GPO should result in the outlook.exe /importprf
\\sharename\folder\outlook.prf command to execute and configure the outlook.
I found out it works well only if the login user is a local administrator on
the PC. The GPO does not appear to execute at all for others (non local
admin). I do not see the Outlook come up at all for these users who are in
the same OU and I do see the gpresult showing the GPO took effect for these
users! Any ideas?
Someone suggested I try runas to run the command as an administrator. While
I am confident that would solve my problem, unfortunately runas does not have
a switch for password. It only has a /user switch for specifying a user, but
it prompts for the password during execution. That obviously will not work
for me in a login script.
Any pointers will be appreciated. Thanks.
Wizard from Office Resource Kit 2003. I have placed the outlook.prf file in a
share where everyone has read permissions. I have set up a login script GPO
on the users OU under User Configuration. I have done gpupdate /force. When
users login, the GPO should result in the outlook.exe /importprf
\\sharename\folder\outlook.prf command to execute and configure the outlook.
I found out it works well only if the login user is a local administrator on
the PC. The GPO does not appear to execute at all for others (non local
admin). I do not see the Outlook come up at all for these users who are in
the same OU and I do see the gpresult showing the GPO took effect for these
users! Any ideas?
Someone suggested I try runas to run the command as an administrator. While
I am confident that would solve my problem, unfortunately runas does not have
a switch for password. It only has a /user switch for specifying a user, but
it prompts for the password during execution. That obviously will not work
for me in a login script.
Any pointers will be appreciated. Thanks.