Re: using Roaming Profiles...
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Apr 2006 11:12:57 -0400
In news:AA2E463A-BC70-40F3-960E-76BB3ECDE88C@xxxxxxxxxxxxx,
Dhow <Dhow@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Owen,
Who is Owen?
I've tried what you've suggested but it still fail.
Perhaps it's has something to do with GPO priority list in Domain
Controller GPO?
?
Which the GPO that I create for roaming users is located at the most
bottom from all SBS' other GPOs (GPOs that are created automatically
from SBS 2003). The whole settings still won't follow as I've
instructed in GPO I created and linked in that particular OU...
What OU? And what is in this GPO, and why?
It really seems that you are making life unneccessarily complicated for
yourself, and I think you're confused as to what roaming profiles do, as
opposed to Group Policy. The two are not really related at all.
I suggest you put all the users back in the default SBS OU and unlink your
GPO. This is not a group policy thing. Get your profiles working properly
first and then worry about GP -
Make sure the user objects have \\server\profiles$\%username% in their
properties in ADUC. Make sure that share is set up properly, with the right
permissions.
How about if I wish to make a roaming profiles for Terminal
Service/Server users that connected to the SBS 2003? So every users
that are going to user TS will have the same roaming profiles?
Same deal. You just specify a *different* path in the user's ADUC
properties. Such as \\server\tsprofiles$\%username%.
Thanks!
"Lanwench [MVP - Exchange]" wrote:
Plus I've set
other settings such as : Control Panel to show certain options only.
But it doesn't work, and I don't know how to fix this. Perhaps you
can help me out?
Or perhaps I should post in another thread?
First, open GPMC on the server and check the settings in there. Is
this linked to the appropriate OU? Remember that some things are
*computer* and some things are *user* - and that's why it really
matters where you link the policies.
Then run gpupdate /force on the server, in a command line.
Then run gpupdate /force on a workstation, in a command line.
Then run gpresult >x:\myfilename.txt in a commandline on the
workstation, wherever you choose x:\myfilename.txt to go. Read the
output.
You can also go to start | run, type rsop.msc <enter> and look
therein.
.
- Follow-Ups:
- Re: using Roaming Profiles...
- From: Dhow
- Re: using Roaming Profiles...
- References:
- Re: using Roaming Profiles...
- From: Lanwench [MVP - Exchange]
- Re: using Roaming Profiles...
- From: Lanwench [MVP - Exchange]
- Re: using Roaming Profiles...
- From: Lanwench [MVP - Exchange]
- Re: using Roaming Profiles...
- From: Dhow
- Re: using Roaming Profiles...
- From: Lanwench [MVP - Exchange]
- Re: using Roaming Profiles...
- Prev by Date: Re: ISA 2004 fails - starts to block HTTPS for no reason.....
- Next by Date: Re: Group Policy and enforcing a common wallpaper.
- Previous by thread: Re: using Roaming Profiles...
- Next by thread: Re: using Roaming Profiles...
- Index(es):
Relevant Pages
|