My Citrix Server (W2K Server / Citrix XPs) has a 4GB boot partition on one local disk (M and a 15GB shared partition on a second local disk (O
My M: has 550MB of free space and dwindling. I have 100 users with published desktops that have growing temporary interenet files, documents, ect expanding their profile folder sizes everyday.
Time to move the Profiles to the 15gb drive and free up space on my boot partition.
I think I know how to do this, (and I'll find out tommorow morning ;-) ) But can anybody verify that this is correct.
First, I will move the "Documents and Settings" folder from my M: to my O: and make sure users have the appropriate rights to it. Next, I'm thinking I need to go into the Registry and modify HKLM\SOFTWARE\Microsoft\Windows NT\CurentVersion\ProfileList and modify the deafult key to change the profile path setting from %systemroot%\documents and settings to O:\documents and settings
For the existing users, I suppose I'll also have to go to each individual key designated by SID and update their profile paths as well... Not looking forward to that but shouldn't take more than a half hour...
Anyway, I'm thinking that should do it and keep additional profiles from being created on M: each time a user authenticates...
Am I missing anything?
My M: has 550MB of free space and dwindling. I have 100 users with published desktops that have growing temporary interenet files, documents, ect expanding their profile folder sizes everyday.
Time to move the Profiles to the 15gb drive and free up space on my boot partition.
I think I know how to do this, (and I'll find out tommorow morning ;-) ) But can anybody verify that this is correct.
First, I will move the "Documents and Settings" folder from my M: to my O: and make sure users have the appropriate rights to it. Next, I'm thinking I need to go into the Registry and modify HKLM\SOFTWARE\Microsoft\Windows NT\CurentVersion\ProfileList and modify the deafult key to change the profile path setting from %systemroot%\documents and settings to O:\documents and settings
For the existing users, I suppose I'll also have to go to each individual key designated by SID and update their profile paths as well... Not looking forward to that but shouldn't take more than a half hour...
Anyway, I'm thinking that should do it and keep additional profiles from being created on M: each time a user authenticates...
Am I missing anything?