The Programdata directory on my Win7 machine is 4GB. That is more than i want to commit to my SSD unless I absolutely have to. Also. much of that data is accessed fairly frequently. Moving it to a spinner will increase the life of my SSD, which I bought solely for the OS and one specific database program that needs lightning-fast access.
Besides, i think an earlier post in this thread described how to roll back, and then forward again. That would eliminate or mitigate any alleged update/SP problem.
I have corrected the link in the original post. Sorry, I didn't realize it was pointing to the wrong place. Here you go ProgramData It's not an evidence, though, it's just a warning.
Technically, ProgramData is moved exactly the same way as ProfilesDirectory. Just add one node to the answer file and you're all set. Example is in the link above. It's supported, but not recommended.
Anyway, what highlander58 method are you referring to exactly?
>Anyway, what highlander58 method are you referring to exactly?
Posts 229-232 in this thread (around page 23) are what got my hopes up.
Your corrected link, however does put a damper on things :-(
Well, that's exactly what's not supported here - messing with the registry and taking ownership over some system keys I don't recommend this even if it worked for someone.
Let me suggest a different approach to your problem your formulated as follows:
First, I don't think there's a lot of writes to ProgramData, given a single DB program operating on a PC. How did you determine this? Off the top of my head, I can only think of monitoring typical activity with Windows Performance Recorder from ADK and analyzing a trace with WPA. For example, this is what actually gets written during boot. Peanuts.The Programdata directory on my Win7 machine is 4GB. That is more than i want to commit to my SSD unless I absolutely have to. Also. much of that data is accessed fairly frequently. Moving it to a spinner will increase the life of my SSD, which I bought solely for the OS and one specific database program that needs lightning-fast access.
You may find out that there's no real need to move anything because of "excessive writes".
Second, you can use Process Monitor to identify the processes that write to this folder. That will give you an idea of what's really going on and prepare to the third point
Third, you can move only certain subfolders using symbolic links (mklink /?), judging by the folder purpose from the name and the space it occupies. For example, I have TechSmith and Skype folders, and this is third party software that can't affect my system stability and serviceability.
Also, I've got a bunch of installation packages (MSI, CAB) in the Package Cache folder, because I have installed ADK, SDK and similar specific products from Microsoft. It's still third party software to Windows, so I'd say this can be moved without much harm to the operating system, and it's easy to undo if you run into software installation problem.
I emphasize this is still unsupported. But by analyzing the folder content and making informed decisions you can mitigate or avoid harm to the system and get what you want.
But if 4GB of space in ProgramData make you uneasy about disk space, it really sounds like you've got an SSD a little too small for your needs. What did you get?
Very good post Vadikan.
In the original version of this tutorial I had included also the ProgramData, how to relocate it. However, I had a red warning box in the beginning of the tut telling that relocating ProgramData can only be recommended for those hardcore geeks who are absolutely sure they will not use any Windows Apps, do not need Windows Store.
Really, going through all the trouble it involves only to get rid of 4 GB makes no sense.
I decided to add a video to my quick and easy instruction on moving profiles during install. I had made it for my blog post anyway, so I just changed the text callouts from Russian to English.
P.S. Thanks, Kari, that's exactly my point. But I can imagine that it could be tight on a 64GB SSD with x64 installed and the DB files taking lots of space. But then again, space considerations should done in advance.
I am having the sysprep problem of not being able to find the relocate.xml. The error says it can't deserialize the file:
2013-05-28 14:46:47, Error [sysprep.exe] UnattendFindAnswerFile: Unable to deserialize explicitly provided unattend file [E:\relocate.xml]; status = 0x80070246, hrResult = 0x0.
2013-05-28 14:46:47, Error [0x0f009e] SYSPRP SysprepSearchForUnattend: Failed while searching for unattend file; hr = 0x80070246
2013-05-28 14:46:47, Error [0x0f00a5] SYSPRP WinMain:Encountered error while searching for unattend file; hr = 0x80070246
I have followed all of the suggestions on this and other forums and still get the error. Can someone help me?
Hi Gassman, welcome to the Eight Forums.
Your error messages are all telling about one of two possible reasons:
- Syntax error in answer file
- Answer file not found
For the first one, check the spelling, check that all paths are correct, bit architecture (x86 / amd64) is correct, Windows version is correct.
For the second possible reason, check that the drive which contains the answer file keeps the same drive letter when rebooted. It happens quite easily that the answer file is stored for example on USB stick which had let's say letter F: while in Audit Mode but after reboot going to OOBE mode the stick is E:.
Thanks for the quick response. I was going to try vadiken's method and in doing so I noticed a dash in <ProfilesDirectory>. I copied and pasted the answer file, but it added some extraneous hyphens. I thought I had cleaned all of them out. I am starting over, reinstalling and will let you know.