S
SilkBC
I have an odd permissions-related issue.
We have a Client who is running a Terminal Server with local account
logins. Everything is working fine.
We recently installed a Windows 2003 Small Business Server to put them
on a domain with Exchange, etc.
For each "local" user, a "domain" user also exists. I logged in to
each user's "domain" account to create a new profile, and everything
still works OK.
When I copy a user's "local" profile to their "domain" profile (to
keep settings, customizations, etc.) I don't get the full profile
settings (primarily background), and when I open Outlook 2002 I gett a
popup with the following error:
"Cannot start Microsoft Outlook"
No other error information comes up. If I right-click on
"outlook.exe" and choose run it as "Administrator", it opens no
problem.
If I add the "domain" user to the local "Administrators" group on the
Terminal server then log in as the user, everything once again works
perfectly.
I know it is a permissions issue, but am not sure what permissions are
wrong.
Any help you might be able to provide in this would be greatly
appreciated.
Thanks, in advance!![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Sincerely,
Alan Murrell
We have a Client who is running a Terminal Server with local account
logins. Everything is working fine.
We recently installed a Windows 2003 Small Business Server to put them
on a domain with Exchange, etc.
For each "local" user, a "domain" user also exists. I logged in to
each user's "domain" account to create a new profile, and everything
still works OK.
When I copy a user's "local" profile to their "domain" profile (to
keep settings, customizations, etc.) I don't get the full profile
settings (primarily background), and when I open Outlook 2002 I gett a
popup with the following error:
"Cannot start Microsoft Outlook"
No other error information comes up. If I right-click on
"outlook.exe" and choose run it as "Administrator", it opens no
problem.
If I add the "domain" user to the local "Administrators" group on the
Terminal server then log in as the user, everything once again works
perfectly.
I know it is a permissions issue, but am not sure what permissions are
wrong.
Any help you might be able to provide in this would be greatly
appreciated.
Thanks, in advance!
Sincerely,
Alan Murrell