Re: Terminal Server profile group policy not working

I figured it out. The TS servers are 2003 but they were not in the GPO where
I was applying it to. I thought if I was applying it to the OU where the
users were located, it would affect all the users in that OU.

But I ended up applying the gpo to the TS servers OU and that worked (since
anybody logging in to that OU would have those policies applied to them.)


"Mathieu CHATEAU" wrote:

Hello,

stupid question, but this gpo is a computer based. Is the TS Server also in
the TESTOU ?

This GPO is for at least Windows XP. Your TS is not a windows 2000, isn't it
?

You shouldn't add the username, just the share. It will create a sub folder
which has the username as name:

To use this setting, type the path to the network share in the form
\\Computername\Sharename. Do not specify a placeholder for user alias,
because Terminal Services automatically appends this at logon. If the
specified network share does not exist, Terminal Services displays an error
message at the server and stores the user profiles locally. If the status
is set to Enabled, Terminal Services uses the specified path as the root
directory for all user profiles. The profiles themselves are contained in
subdirectories named for the alias of each user. If the status is set to
Disabled or Not Configured, user profiles are stored locally on the server,
unless specified otherwise by the server administrator. Note: The roaming
profiles specified with this setting apply to Terminal Services connections
only; a user might also have a Windows roaming profile, in which case the
Terminal Services roaming profile always takes precedence in a Terminal
Services session.

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Gilbert" <Gilbert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2EF34A63-960B-44E1-92FD-D571473CEE74@xxxxxxxxxxxxxxxx
I'm using Group Policy and I'm trying to apply a Terminal services Profile
path to users in an OU. It doesn't appear to be working. I used the
following Microsoft document to setup profile paths thru Group Policy.

http://technet2.microsoft.com/windowsserver/en/library/af49a8bc-9fa0-48c3-a5cf-0ff77e698fd01033.mspx?mfr=true

Local Computer Policy/Computer Configuration/Administrative
Templates/Windows Components/Terminal Services

-->Set path for TS Roaming Profiles

My AD setup:

Domain
TESTOU

I applied the group policy to the OU. (both computer and users are
located
in the same OU). I have checked to make sure no policy from the domain is
over-riding my TS policy. I also ran GPUpdate on the local computer and
also
replicated all the Active Directory DCs.

I setup the path as \\server\tsusers\%username%

On that server, there's a folder called tsusers that's shared and
everybody
has Full Share permissions.

I am a member of the Domain Admins.

A folder doesn't get created in that directory with that user name as I
would expect. I also tried just typing in \\server\tsusers without the
%username% and it doesn't work.

If I manually put in the profile path in the Properties of the user, then
it
works just fine.


.

Relevant Pages

  • Re: Terminal Server profile group policy not working
    ... If the specified network share does not exist, Terminal Services displays an error message at the server and stores the user profiles locally. ... I applied the group policy to the OU. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Move Documents and Settings to new drive
    ... We have a few users who want to log on using Terminal Services and ... Windows Server 2003, roaming profiles, users ... Rather than moving the entire documents & settings folders elsewhere, ...
    (microsoft.public.windows.server.general)
  • Re: Group Policy By User
    ... If you still will do it create an OU and move the normal users to it, then configure your GPO and link it to the OU, so it will only effect this OU nothing else. ... Active Directory setup as well as Terminal Services. ... I am only using the server for Terminal Services and email. ...
    (microsoft.public.windows.server.general)
  • Re: Terminal Services GPO
    ... I am trying this on a upgraded (from Windows 2000 Advanced ... Server) Windows Server 2003 Enterprise edition domain ... I have another GPO that I am able to see the ... >> when I go back into the GPO the terminal services object ...
    (microsoft.public.win2000.group_policy)
  • Re: Color Depth Wont Apply
    ... You can configure the max color depth either in TS Configuration, ... In both cases, the setting is applied to the server, ... means that the GPO that is applied last wins. ... I do understand the Terminal services configuration is server ...
    (microsoft.public.windows.terminal_services)
Loading