lnk files there and deletes unnecessary ones. For each given user on the target machine prepares the "C:\Users\\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch" folder and places necessary.The rest is easy, write a batch file that does the following: Export HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop key from the registry into the.This is critically important - if you do not log out or if you kill Explorer, it will not commit your new toolbar settings to the registry. Log out from your account on test machine and log right back in.Adjust the Quick Launch the way you desire (title, text, position, width, icon order).This makes the blob re-usable for any user I want to deploy the Quick Launch toolbar to. When you do that, Explorer will create a blob where the current user name is not hard-coded, and instead the environment variable %USERPROFILE% name is placed in the blob. On a clean test machine manually create a Quick Launch toolbar using the mouse, but, when asked to specify the path to the toolbar folder, instead of navigating step-by-step to C:\Users\\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch, which would commit a fixed username into the blob as part of the path, you need to specify "%USERPROFILE%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch" in Select Folder dialog as one line (the starting location for the Select Folder dialog is not important in this case).And I did not have to reverse-engineer the blob format for that (although I have started that fun process and managed to learn a few things about its internal structure). So, after all updates, I have quite opposite situation: I no longer have issues with item 3, but I do need to know the format of the blob stored in registry HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop key, TaskbarWinXP value. Update 2: As I have mentioned in the update 1, the reason I don't see any registry traffic when I am manually creating the toolbar is because Explorer postpones registry commit until normal shutdown. But Explorer has to store these changing settings somewhere. Process monitor does not detect any meaningful and relevant activities with either registry or files during such manual manipulations, only a bunch of background noise. I also tried spying on the system using SysInternals procmon64 while I perform these three actions manually with a mouse. If you terminate Explorer by killtask, it won't commit these changes. It seems like Explorer holds these values in RAM and only commits them to registry when it terminates normally, e.g. Update 1: I was wrong, these values are stored in the blob, but they are not committed to the registry right away by Windows Explorer. These settings are not stored in the HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop key, TaskbarWinXP value blob, I did binary comparisons of different versions of this blob before and after manual change, they are identical.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |