1. Terminal Server Profiles in WIN2003 Terminal Server...moving to WIN2008 Terminal Server
Good morning! Just a simple, basic question! Have a client with two WIN2003 Terminal Servers. I have the TS Lockdown thing going (via GPO and loopback processing). Additionally, we have folder redirection for My Documents and for Desktop (can not do App Data for really stupid reasons). Also - and here is part of the question - about to implement the Terminal Server specific profile. Client is going to be moving to two WIN2008 Terminal Servers in the near future. Question: Assuming that I move forward with creating the Terminal Server-specific profile this week, how is the Terminal Server specific profile going to be affected when we move to the two WIN2008 TS Boxes? Am I going to see \\servername\tsprofiles$\username.v2? Read: like when we move clients that have roaming profiles (not Terminal Server....just "normal" roaming profiles) from Windows XP to Windows Vista or, now, Windows 7? This 'username.v2' folder is an entirely new profile......which normally is not an issue. However, in the case of this particular client there are some things that we need to do to each profile for things to work (Scanners that are attached to the desktop....I believe that RemoteScan is the software used....have to copy some files and folders specific to that scanning software up to the WINDOWS directory in each user's profile). I am thinking that it would be better to set up the TS specific profiles once the new TS boxes are in place. Has anyone done this yet? And can share the experience. Thanks, Cary
2. Mapping my Terminal Services User Profile to my Terminal Services Home Folder
3. Move Terminal Services Profiles to another Volume
When my Terminal Server was intially setup the users were set with roaming profiles being stored on the c volume of the terminal server. I am running out of space on that server and would like to change the path to save the profiles on the d volume of the terminal server. I can't seem to find where I would change this and can't find any articles on how to do this. Can anyone point me to information or give me an idea on how I can do this? Thanks, Chris
4. Terminal Services Local Profile relocate or move
5. Prevent Roaming Profile changes from propagating to the server - Terminal Services Profiles
Hi, saqib ali schrieb: > When I set the > Group Policy Object Editor -> Local Computer Policy -> Computer > Configuration -> Administrative Templates -> System -> User Profiles -> > Prevent Roaming Profile changes from propagating to the server TO > "Disabled" > Does this applies to the Terminal Services Roaming Profiles as well? Nothing easier, than trying ... Mark -- Mark Heitbrink - MVP Windows Server Homepage: www.gruppenrichtlinien.de extend GPO: www.desktopstandard.com PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
6. Prevent Roaming Profile changes from propagating to the server - Terminal Services Profiles
7. Terminal Services Profile and Profiles
Hi, In our organization we have various windows 2000 sp4 terminal servers. We are using Active Directory and use the userprofile path so the users can signon onto numerous machines. They have a separate profile path to a different server under the terminal services path. The problem is when they sign onto the terminal server it copies over the user profile path. This creates a problem since the users get confused on where they are sign on and the terminal services profile it getting large which increases the time to log on and off again. We would like to keep these two separate. Is this possible? Any help will be nice.
8. Prevent Roaming Profile changes from propagating to the server - Terminal Services Profiles