I need to remove roaming profiles from one of my Terminal Servers.
There are two terminal servers in the domain and are located in their own
OU. That OU had a Group Policy associated with it that set the Roaming
Profile path. I disabled that GPO but the profiles were still loading from
the server location. I then stopped sharing the server profile location and
as expected got the profile cannot be found error when a user logged in.
I then deleted the GPO link to the OU. But still get the Server Profile
Location error when logging in.
Anyone have any ideas? I want the users to use new local profiles when
logging into the 2nd terminal sever.
Mike (NLX) <nlx.bay@gmail.com> wrote:
> I need to remove roaming profiles from one of my Terminal Servers.
>
> There are two terminal servers in the domain and are located in their
> own OU. That OU had a Group Policy associated with it that set the
> Roaming Profile path. I disabled that GPO but the profiles were
> still loading from the server location. I then stopped sharing the
> server profile location and as expected got the profile cannot be
> found error when a user logged in.
> I then deleted the GPO link to the OU. But still get the Server
> Profile Location error when logging in.
>
> Anyone have any ideas? I want the users to use new local profiles
> when logging into the 2nd terminal sever.
>
> thanks,
> -mike
Run gpupdate /force - then review your event logs & rsop.msc for errors.
PS: you want to avoid the phrase "roaming profiles" when referring to TS
profiles - TS profiles *do* roam but the former phrase is generally taken to
mean "profiles used by my desktop users in the domain'
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:eq9KOJEtIHA.4528@TK2MSFTNGP03.phx.gbl...
> Mike (NLX) <nlx.bay@gmail.com> wrote:
>> I need to remove roaming profiles from one of my Terminal Servers.
>>
>> There are two terminal servers in the domain and are located in their
>> own OU. That OU had a Group Policy associated with it that set the
>> Roaming Profile path. I disabled that GPO but the profiles were
>> still loading from the server location. I then stopped sharing the
>> server profile location and as expected got the profile cannot be
>> found error when a user logged in.
>> I then deleted the GPO link to the OU. But still get the Server
>> Profile Location error when logging in.
>>
>> Anyone have any ideas? I want the users to use new local profiles
>> when logging into the 2nd terminal sever.
>>
>> thanks,
>> -mike
>
> Run gpupdate /force - then review your event logs & rsop.msc for errors.
>
> PS: you want to avoid the phrase "roaming profiles" when referring to TS
> profiles - TS profiles *do* roam but the former phrase is generally taken
> to mean "profiles used by my desktop users in the domain'
>
thanks for the gpupdate command. I rebooted several times to no avail, but
then went back several hours later and the policy had now taken. The manual
command you sent is what I'll use next time.
Mike (NLX) <nlx.bay@gmail.com> wrote:
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in
> message news:eq9KOJEtIHA.4528@TK2MSFTNGP03.phx.gbl...
>> Mike (NLX) <nlx.bay@gmail.com> wrote:
>>> I need to remove roaming profiles from one of my Terminal Servers.
>>>
>>> There are two terminal servers in the domain and are located in
>>> their own OU. That OU had a Group Policy associated with it that
>>> set the Roaming Profile path. I disabled that GPO but the profiles
>>> were still loading from the server location. I then stopped
>>> sharing the server profile location and as expected got the profile
>>> cannot be found error when a user logged in.
>>> I then deleted the GPO link to the OU. But still get the Server
>>> Profile Location error when logging in.
>>>
>>> Anyone have any ideas? I want the users to use new local profiles
>>> when logging into the 2nd terminal sever.
>>>
>>> thanks,
>>> -mike
>>
>> Run gpupdate /force - then review your event logs & rsop.msc for
>> errors. PS: you want to avoid the phrase "roaming profiles" when
>> referring
>> to TS profiles - TS profiles *do* roam but the former phrase is
>> generally taken to mean "profiles used by my desktop users in the
>> domain'
>
> thanks for the gpupdate command. I rebooted several times to no
> avail, but then went back several hours later and the policy had now
> taken. The manual command you sent is what I'll use next time.
Glad to hear it's working.
>
> Also, thanks for the terminology correction.
No worries - just helps to keep things clear for everyone!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.