Hi Vera or Whoever Responds -

We are a library. We have Terminal Services installed and we support
about 80 Wyse Thin Clients. We are using a batch file to erase
history, cookies, passwords etc. We want to use mandatory profiles
because the patrons leave data on the desktops. All the clients can
look identical.

Can you give me a step by step. I have tried this over and over.
When I choose properties for the client and then add a profile path,
the client always says it can't find it and then displays the usual
profile. We are confused about this and could use a step-by-step for
windows 2003 terminal server or something.

Thanks
David

I'm not sure what exactly you are trying to do.
What do you mean with "properties for the client"? Do you mean the
"Terminal Services Profile" tab in the AD user account properties?

You can configure the accounts that way (you need to enter
\\my_server\my_TS_profile_share as the path), but it's easier with
a GPO. Then you need this hotfix first:

You cannot use a Group Policy setting to set the same mandatory
profile for all the Terminal Services users in Windows Server 2003
http://support.microsoft.com/kb/908011/en-us

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

alamedalibit RemoveThis @gmail.com wrote on 08 apr 2009 in alt.os.citrix:

> Hi Vera or Whoever Responds -
>
> We are a library. We have Terminal Services installed and we
> support about 80 Wyse Thin Clients. We are using a batch file
> to erase history, cookies, passwords etc. We want to use
> mandatory profiles because the patrons leave data on the
> desktops. All the clients can look identical.
>
> Can you give me a step by step. I have tried this over and
> over. When I choose properties for the client and then add a
> profile path, the client always says it can't find it and then
> displays the usual profile. We are confused about this and
> could use a step-by-step for windows 2003 terminal server or
> something.
>
> Thanks
> David