STOP COPY of ROAMING PROFILES?

[scanjam]

Anyone know if we can we setup the roaming profiles to be access directly on another server SHARE, but NOT copied to the M:\docs and settings directory? although the users profiles are only 50mb ish, why waste time copying?

This is the area that we experience the most most pain,. its the slow logins, slow login scripts.

ALso any suggestions for login script replacement? Its typically only for the mapped drives but here we have tried a number of groups policy template "hacks" that connect drive4s, but dont reconnect on login etc...

Any suggestions or assistance would be fantastic.
Cheers

Scanjam

 

[patrickrouse]

Profiles MUST load locally at logon, as that's how Windows works. Are you redirecting My Documents to the user's network Home Folder and Deleting the Local Profile at logoff via DeleteRoamingCache?

Patrick Rouse
Microsoft MVP - Terminal Server

http://www.sessioncomputing.com

 

[scanjam]

My Docs is redirected, but we are not deleting after logoff because its "seems" to gretly increase the login time (would i be correct) as it needs to copy over their entire profile again?

It has been reccomended to do this, but I dont really understand the benefits of deleting the cached copies.

Sorry for the ignorant questions.. and thanks for your quick reply!

SCANJAM

 

[patrickrouse]

No problem with questions. The advantage of deleting local profiles is that it positively wipes the temp & IE Cache folders at logoff, which often get bloated. In addition to this it seems to reduce the frequency of profile corruption.

It's true that it the system must copy the entire profile at logon, so it's imporatant to:

1. Keep the profile small
2. Keep the profile to as few a number of files as possible
3. Have a 1GB link between the profile server and TS.

If you have a multi-server TS Farm, the chances of the profile needing to be copied to the local computer at logon are high when you don't delete the local cache, as this will happen any time a user logs onto a TS that's different from their last logon.

The type of profiles you use is your choice, i.e. there is no right or wrong way, so use whichever you prefer.

Patrick Rouse
Microsoft MVP - Terminal Server

http://www.sessioncomputing.com

 

[scanjam]

We store our roaming profiles on a DFS share which is actually located on one of the TS servers itself would i be right in assuming then that the slow log off could be related to the profiles copying "INTERNALLY" on the server from "n:\DFSSHARE" to m":\doc and settings"

Is there a Group Policy to only allow like 1 MB of temp and temp IE cache? Maybe even in ie 7?

 

[patrickrouse]

The GPO setting exists w/ IE 6 and 2003 SP1 to delete the IE Cache. Policies exist in 2000 and 2003 to restrict the IE Cache size.

I would only expect this to slow down logon/logoff if the local disk is very busy, however I've never stored roaming profiles on the same server.




Patrick Rouse
Microsoft MVP - Terminal Server

http://www.sessioncomputing.com