Roaming Profile Problem

[Tony]

Hi:

Hopefully someone has seen this problem, before.

I've got a Windows 2003 server domain environment using roaming
profiles.

A user is happily using his computer with only has user rights on his
computer.

Now it's time for him to get a new XP Pro system. So he logs into the
new computer, and he can't run Outlook (just bombs with a helpful
message like, "Outlook cannot be Run"
And Outlook Express won't allow you to create profiles.
And, all the icons on the left side of the Start popup menu don't
appear.

If I give him administrator rigthts to the machine, everything works
fine. But as a normal user, the above problems exist.

The worse part is that it doesn't happen all the time.

It's a bummer, since until I can figure this out, all my nice, locked
down users are getting admin rights to their machines?

Any ideas?

Thanks,

Tony
Saga Communications
(e-mail address removed)

 

[Lanwench [MVP - Exchange]]

Hi:

Hopefully someone has seen this problem, before.

I've got a Windows 2003 server domain environment using roaming
profiles.

A user is happily using his computer with only has user rights on his
computer.

Now it's time for him to get a new XP Pro system. So he logs into the
new computer, and he can't run Outlook (just bombs with a helpful
message like, "Outlook cannot be Run"
And Outlook Express won't allow you to create profiles.
And, all the icons on the left side of the Start popup menu don't
appear.

If I give him administrator rigthts to the machine, everything works
fine. But as a normal user, the above problems exist.

The worse part is that it doesn't happen all the time.

It's a bummer, since until I can figure this out, all my nice, locked
down users are getting admin rights to their machines?

Any ideas?

Thanks,

Tony
Saga Communications
(e-mail address removed)

Hi - I seem to recall replying to your nearly identical post (in another
group, maybe?) not long ago....

 

[Lanwench [MVP - Exchange]]

In Lanwench [MVP - Exchange]

Hi - I seem to recall replying to your nearly identical post (in
another group, maybe?) not long ago....

microsoft.public.win2000.networking, as it turns out.