Today's useful geek tool.

[theweaselking]

This is the ForensiT User Profile Wizard.

It handles all the SID-fuckery and ACL-wanking required to tell any domain account to use any profile folder. So, for example, if you have your profile set up just the way you want it and then you have to join a domain, or if IT accidentally the sysvol of the primary domain controller[1] so the machine has to be removed and re-added? Or maybe you're just having one of those days when Windows decides it can't read your profile and so makes a new one for you and you want the old one back? Just run this as a local Administrator. It wil prompt you for the Domain and the username you want, and then do all the lookups and permissions changes and registry hooks required to make sure that your chosen account does, in fact, have the rights and the settings to use the profile that was set up the way you liked it.

You CAN do all of this with Explorer and Regedit, but with this tool, *you don't have to*.

It is smurfy. And has saved me a number of headaches, today.

[1]: Let Me Tell You About My Day.

Comments

[skiriki.livejournal.com]

Cool, thanks! I'm gonna pass this one onward to a friend of mine, who has use for such tool.

[theweaselking.livejournal.com]

If the old profile was made "private" in Windows, you will lose saved passwords in IE and stored personal certificates, for the record. But you should already know to have those double-backed-up.

[youwantitwhen.livejournal.com]

I don't know why I do this, but figured you'd appreciate

http://motherjones.com/politics/2011/01/republican-plan-redefine-rape-abortion

[krinndnz.livejournal.com]

That looks highly useful. Cheers.

[ardys-the-ghoul.livejournal.com]

Can't say I've ever had that problem, but this does sound useful.

Then again, I'm only marginally computer literate, so I probably wouldn't know I had that problem if it happened.

[theweaselking.livejournal.com]

The main symptom of the problem is that you log in and none of your settings are there. The machines looks exactly like you'd just logged in to the first time to a fresh installation.

This tool will allow you to fix the problem.

This is, outside a corporate environment, a rare problem. Inside, it's a rare-but-predictable problem, where it won't show up often but when it does, the techies will be all going "Yeah, I knew that was going to happen"