Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've recently changed following registry key:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
Default=D:\Users

In order to ensure that all new profiles will be created on D drive, I've also successfully re-created some bulky profiles which were already created on C drive (by backing up all data, then deleting profiles through Windows GUI and letting them to be re-created on D).

Shortly afterwards I've noticed that some users whose profiles which already existed on C drive prior to that change start logging on with temp profiles. Just wondering if there any connection between change I made & this. And in general is it safe to just change this setting on Windows Server 2008 R2 with RDS role installed (if all I want is to have new profiles created on D drive) or some other registry changes required? Any negative consequences for existing profiles?

P.S. The server in question is AD DS member server with some corporate customizations (I'm not fully aware about all of them) - that's why I have extra concerns about possible conflicts of my change with some other settings/customizations.

share|improve this question
    
Can I ask why you're separating things out across the drives? –  Dan Jan 14 at 14:00
    
Just trying to avoid running out of space on C drive, as some profiles are too bulky for standard C drive size in my environment... –  Mikhail Jan 14 at 15:02
    
I know sometimes you can't, but I just recommend large single partitions with TS/RDS/Citrix boxes now. –  Dan Jan 14 at 16:21

2 Answers 2

up vote 1 down vote accepted

A host with the RDSH role installed will not behave all that differently than one without - at least in this respect.

When the User Profile service is about to load a user's local profile, it first checks HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList for a key named after the logging-on-user's SID. If it is present, the profile storage directory is determined by looking up the ProfileImagePath value inside this key. If you have deleted the storage directory but have left the corresponding key/value in ProfileList in place, you will see profile loading errors in the event log and have users logged on with a temporary profile.

After you have changed the default storage directory, you will not necessarily have to touch all profiles already present on your system and move them over. Leaving "old" profiles in the C:\Users directory and setting new profiles to be created in D:\Users would work quite fine.

share|improve this answer

It is most likely due to the registry entries for the old profiles. Have a look in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\<User SID>\

You should see a registry entry for ProfileImagePath. You can modify that to the correct location and it should work as expected. If you currently logged in as one of the users having the issue you will need to logout and back in.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.