Oh, and the folder structure seems to restore between OS versions and architecture (x86 vs x64). I often use Fabs to backup from an XP machine and restore to a fresh Win7 x64 machine with no troubles. That's the killer feature for me (not sure how DataGrab handles that situation).
Never noted any differences in x86 vs x64. For XP to Vista/7, no problem - see same question/answer below.
Does your process of maintaining the entire directory structure work between Windows versions (for instance XP to 7)? XP has Application Data folder where 7 uses AppData. Fab's works great when backing up and restoring between different versions. Sorry of this question was already answered in the spreadsheet.
Yes, actually the differences between XP's Application Data and Vista/7's AppData structure, or XP's My Documents structure vs. Vista/7's, all of that is actually taken care of not by DataGrab (and probably not by Fab's either) but by Windows Vista/7 itself when you copy the files back over. It's actually a neat and little realized feature of Windows thanks to junctions and redirection points for backwards compatibility.
Example, I can backup an XP box and have all my user profiles in the backup location\Documents and Settings. When I migrate that to a Vista/7 box, I just select all the user profiles in Documents and Settings from the backup loc, and copy. Then paste to the \Users folder on the fresh install of Vista/7.
During the file copy, Windows itself will automatically move "\My Documents" to "\Documents", it will also prompt you to move "My Documents\My Pictures" to "..\Pictures", etc. etc. for the folders inside My Documents now stored in the root of the user profile, and it will also automatically move Application Data folders to their respective locations inside AppData.
So even when migrating data to a newer version of Windows, it's still as simple as copy/paste the user folders and you're done. Windows takes care of all of that for you.
Fixed, thanks!
Quicklaunch: Yes for many of my end users this is necessary as they utilize this heavily (note: can't restore quicklaunch to Win7 since it doesn't use quicklaunch)
But... what shortcut in quicklaunch that you backup/restore actually works until you install the app - which would install the quicklaunch shortcut anyway?! I'm sorry, I fail to see the point in backing that up... EDIT: Note I can just imagine that yes it would be useful if someone say, had manually placed a shortcut in there to something like a frequently used excel file, or similar, but in all my years I don't think I've ever seen an end user do that lol. I've only ever seen quicklaunch shortcuts be placed there by app installs...
The item listed as and other such things are just reported right? Might want to make that clear since there can be no restoration of such data automatically. IIRC, Fabs doesn't do any reporting of information that it cannot restore.
Yes I noticed Fab's doesn't do that... Yes, the list of installed apps is merely that, a list. This was actually a user-requested feature and I feel it is important to have a full list of applications that the system had installed, so you can look it over and re-install what is necessary (if you go that extra mile for the client.) I do go that extra mile - granted I don't look at the list and install every little thing on it (toolbars LOL), but it's nice to browse it and pick out the key/important apps that you know your client will miss, so you can go ahead and reinstall them for the client.
Just my opinion, but it's also useful as I've had clients try to tell me they had office installed previously when they in fact did NOT. (in some cases it wasn't MICROSOFT office but OpenOffice or even Microsoft WORKS they were talking about; without that list I would have no way of knowing what they were talking about or proving otherwise should I need to.)