![]() ![]() Run this and Windows will continue installation and now stores profiles in D:\Users instead of C:\Users. In a command prompt enter this command C:\Windows\system32\sysprep\sysprep.exe /oobe /reboot /unattend:d:\relocate_profiles.xmlĪssuming the xml file is on D: but it can be anywhere even on the installation medium. Now you are logged on a temporary Administrator. Step twoĪfter the reboot close (cancel) System Preparation Tool. ![]() Prepare a relocate_profiles.xml response file with this contents Īt the moment just after reboot at the language select dialog hit Ctrl+ Shift+ F3. Lets say you plan to run Windows off a DOM (Device or Disk on a Module) but want to use for instance a RAID set on another device (D:) for (pro)file storage.Īfter installation of Windows core finalizes and it reboots to the OOBE (Out Of Box Experience) is the moment to change the profiles from in our case C:\Users to D:\Users. Just for those who prepare for the profiles on a second drive before installing Windows 10. The profile should now be recreated in the correct location. Switch accounts and log in with your domain user. That way, if something went wrong, you still have one account that's working I recommend using Switch Accounts rather than logging out of the temporary account. Log out of your account and log into the temporary admin user.įind Advanced System Settings (for example through Start | Run and typing sysdm.cpl) and select Settings from the User Profile section.įind the username of your domain user and click the Delete button This is needed to remove your domain user profile so it can be recreated. This will only come into effect for new profilesĬreate a temporary user with admin rights on the local computer. Modify the registry value of ProfilesDirectory under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to point to your new directory. ![]() Move files that you want to keep from your profile somewhere independent, for example directly on the C: or D: drive I messed up once and had to do a restore myself! Obviously everybody is different, so I'm hoping for some discussion.WARNING: Create a backup and a restore point before you try this. I'd really love some ideas on how I should start organizing these things before I start. bat file type things in it really quickly, or you can be building libraries and sophisticated services with it. But PowerShell seems to be very different. bat files which are usually standalone or piled in a heap in some folder. And at the other extreme I've done a lot of crappy. Where do you all put your PowerShell scripts and how do you organize them? I've got a lot of experience making C# and C++ tools and know what to name them and where to put them. Does it go in a PSMODULEPATH? What kind of stuff goes there anyway? Does it look recursively or is it just like the normal PATH?.So where should it go and how do I call it from a Posh command line? I plan to write more! Where should they go? ![]() ps1 and not one of those fancy advanced functions that take params and such. I'll give it a verb-noun type name, but for now it's a simple. I want to be able to call it from the Posh command line. I just wrote my first serious PowerShell script, and I'm really happy with it. (I can't believe I'm actually asking this, but I am out of brainpower for the day.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |