Link to home
Start Free TrialLog in
Avatar of Mfinch
MfinchFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Server 2008 Roaming Profile cache data

I am setting up a Server 2008 Terminal Server farm and have a question relating to the roaming profile cache data location on server 2008 and how to change it properly. The attachment shows Microsoft's recommendations for limiting the size of the cache but also mentions that best practice is to cache the profile data on a separate drive. I am confused if this is just referring to the location of the roaming user profiles or the actual local location of the roaming profile cache data. If it refers to local cache data, how do I change the location from the default %systemroot%\users to a separate, faster local drive on each session host?

I hope this makes sense :)


raoming-profile-cache.docx
SOLUTION
Avatar of itsmein
itsmein
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Avatar of Cláudio Rodrigues
Cláudio Rodrigues
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Mfinch

ASKER

Hi

It never occurred to me that the local cache for roaming profiles was actually the local profile, d'uh!

I have configured folder redirection so only minimal changes will be copied back at logoff and I also configured background refresh so as the users will not often log out. The reason for that being that this is for 2 Server 2008 session hosts (Terminal servers) accessible only via rdweb.

As this is critical to users and I will have people logging in to the UK (head office) from both Australia and Canada, I didn't want profiles to be a bottleneck for users so adding a high performance disk for this purpose is something I am willing to do.

Tsmvp, thanks for the link on how to change the profile path but it doesn't seem very stable to me and as this would have to be performed on 2 critical Terminal servers, it's probably not the best idea.....

Thanks for the input anyway guys and I will share the points (more to tsmvp for the attempt at providing a solution)

Cheers
Avatar of Mfinch

ASKER

Grade B as the solution was not really suitable, more advice than a solution.