Re: (Remote) Batch Writing/Execution
I'm stuck at batch, VBS, and psexec (as mentioned by niemir). I know we can pull the information remotely in batch, which would provide the information, but we still would need to run the batch on the target machine with the information grabbed remotely to pull the information from the HKU registry tree
So, here's a simple breakdown of what this is meant to help with. On our network, profile corruption is a common thing (700,000+ users makes it hard to avoid). As such, there are four things we are required to support recovery for: Network Drive Mappings, Network Printer Mappings, PST Mappings, and Profile Files (Desktop, Documents, and Favorites). This is universal requirements between XP and 7. Most complex part of these differences is that Windows 7 splits the My Documents into all the individual directories.
The issue we have is that most of our agents don't do the remappings because it hurts their numbers to stay on a call longer just to restore them when the user actually still has access (but doesn't know they do).
For Windows XP, the profile rebuild process is fairly easy, back-up the mappings, rename the user corrupted profle, and restore mappings and files to newly created local profile (after Cx logs in to regenerate the local profile from the network profile).
In Windows 7, Microsoft made this method a little harder for us to do. Now we have to remove the registry key from HKLM\SOFWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, which is also SID-based (just like the network drive mappings), when we rename the corrupted profile. Otherwise, same process.
I know the we can't do the PSTs locations back-up/restore via batch, but the rest can be done from the target machine in batch, I know, I've made it work. The issue comes with grabbing the right information to remove the human error involved in getting the right SID and/or making the process work remotely (HKU registry tree).
Now, I'm no beginner to this entire thing and now that it will have to be broken into, at least, two scripts. The first being for while the customer is logged in and/or out for renaming, and the second for after their profile has been rebuilt. Not a big deal. I actually expect it to be three so three's no issue with pulling the current user information and then running the renaming/registry editing after they log out.
So, that's the basic rundown of what my end-game is, but I'm not looking for a 1-stop fix all for it. I think that's a bit much to ask for. All I'm looking for is a means to remove the human error in backing-up the mappings, preferrably without having to remote into the machine. Restoration is a lot easier when you know where everything is.
Also, as a note, any scripts I use, though will be noted for credit to the authors, would be claimed by HP. So, if that's a problem for you, please let me know and I'd be more than happy with tutorials on how to do these tasks (expect questions). I'm hoping for some time this weekend to study up on VBS, but I also have a computer to break down, test, and rebuild for my brother. ^^'