setup executable lite touch

[labch]

Hi guys.. I'm a real newbie here so. first off HI

I'm a tier 2 desktop support specialist for a small 300+ user organization. I am not the only tech guy at the office, but i am actively trying to make things easier for all of us by automating some of the tasks we use daily. I am constantly reimaging pc's, etc etc.. the next few months however, I will be upgrading all of our users to Windows 7 (from xp), and that means doing a LOT of copy/paste/settings, etc.

 

now.. being in the low end of the "technical" world at our place, I don't get access to the servers ( i basically do just the grunt work), so SCCM is kind of out of the question for me :/, AND it is extremely unlikely I would get any of the top technicians to implement a solution that would make them do any thing that would add to their work (why would they)...

 

I have come to read about using USMT, and it sounds exactly like the tool i would use to accomplish this .. If i could only automate it in some way. ( too many switches, commands, etc). I have found a tool called USMT XML Builder that I could use to build a self extracting executable file that would run and copy a set of predetermined settings, but I have been unable to make it work.

this sounds PErfet.. if i could go to the winxp machine.. run the executable.. let it do its thing (backup).. and go back to the win7 and run the restore executable,, THAt right there would save me TONS of time.. that is.. if it worked :/ so far, I have not been able to make it work .. and i think the answer lies in the HTML

 

this are the things I am trying to accomplish:

 

*copy the entire "My documents" folder

*copy the "favorites folder

*copy the "desktop" folder"

*copy all the *.pst files in the outlook folder

*copy attached network printers

*copy attached network drives

 

sounds pretty straight forward.. I don't need any other settings.. just file backup.

 

Now, my question to you all is

a) could I setup a pseudo-server in my existing network to install sccm and automate this task ?

(i should mention the switches here are configured manually and they DO not allow multicasting)

 

could someone help me build an html that would work for USMT to do the tasks i mentioned earlier?

 

If someone could help me get this going, I would be forever in your debt.. at the moment, I am just going into each machine and copying manually all those files, and there have been times were I miss the outlook files (thank god those machines were not wiped)

 

I am willing to work for this help, but i think i'm out of my league trying to figure this out. Please be kind to respond, and thank you for your time.

 

ps: i would donate a few pp bucks if need be

[anyweb]

read the below first (from http://technet.microsoft.com/en-us/library/dd560792%28v=ws.10%29.aspx)

 

does it answer your questions above ?

 

User Data

 

 

This section describes the user data that USMT migrates by default, using the MigUser.xml file. It also defines how to migrate access control lists (ACLs).

• Folders from each user profile. When you specify the MigUser.xml file, USMT migrates everything in a user’s profiles including the following:
   
  My Documents, My Video, My Music, My Pictures, desktop files, Start menu, Quick Launch settings, and Favorites.
  
• Folders from the All Users and Public profiles. When you specify the MigUser.xml file, USMT also migrates the following from the All Users profile in Windows® XP, or the Public profile in Windows Vista® or Windows® 7:
   
  Shared Documents, Shared Video, Shared Music, Shared desktop files, Shared Pictures, Shared Start menu, and Shared Favorites.
  
• File types. When you specify the MigUser.xml file, the ScanState tool searches the fixed drives, collects and migrates files that have any of the following file name extensions:
   
  .accdb, .ch3, .csv, .dif, .doc*, .dot*, .dqy, .iqy, .mcw, .mdb*, .mpp, .one*, .oqy, .or6, .pot*, .ppa, .pps*, .ppt*, .pre, .pst, .pub, .qdf, .qel, .qph, .qsd, .rqy, .rtf, .scd, .sh3, .slk, .txt, .vl*, .vsd, .wk*, .wpd, .wps, .wq1, .wri, .xl*, .xla, .xlb, .xls*.
   
   
  Note The asterisk (*) represents zero or more characters.
  
• Access control lists. USMT 4.0 migrates access control lists (ACLs) for specified files and folders from computers that are running both Windows® XP and Windows Vista. For example, if you migrate a file that is named File1.txt that is read-only for User1 and read/write for User2, these settings will still apply on the destination computer after the migration.
  

Important To migrate ACLs, you must specify the directory to migrate in the MigUser.xml file. Using file patterns like *.doc will not migrate a directory. The source ACL information is migrated only when you explicitly specify the directory. For example, <pattern type="File">c:\test docs</pattern>.

 

Operating-System Components

 

 

USMT migrates operating-system components to a destination computer that is running Windows 7 from computers that are running Windows XP, Windows Vista, or Windows 7.

Note If you are using USMT 4.0 to migrate a user state to Windows Vista instead of to Windows 7, use the /targetvista option with the ScanState tool. Without the /targetvista command-line option, some operating-system settings can be lost during the migration. For more information, see ScanState Syntax.

 

The following components are migrated by default using the manifest files:

• Accessibility settings
  
• Address book
  
• Command-prompt settings
  
• *Desktop wallpaper
  
• EFS files
  
• Favorites
  
• Folder options
  
• Fonts
  
• Group membership. For example, right-click My Computer, and then click Manage. USMT migrates the groups under Local Users and Groups for the users who are included in the migration.
  
• *Windows Internet Explorer® settings
  
• Microsoft® Open Database Connectivity (ODBC) settings
  
• Mouse and keyboard settings
  
• Network drive mapping
  
• *Network printer mapping
  
• *Offline files
  
• *Phone and modem options
  
• RAS connection and phone book (.pbk) files
  
• *Regional settings
  
• Remote Access
  
• *Taskbar settings
  
• Windows Mail. Microsoft Outlook® Express Mail (.dbx) files are migrated from Windows XP.
  
• *Windows Media® Player
  
• Windows Rights Management
  

* These settings are not available for an offline migration. For more information, see Offline Migration.

Important This list may not be complete. There may be additional components that are migrated.

 

Note Some settings, such as fonts, are not applied by the LoadState tool until after the destination computer has been restarted. For this reason, restart the destination computer after you run the LoadState tool.

 

Supported Applications

 

 

Although it is not required for all applications, it is good practice to install all applications on the destination computer before you restore the user state. This makes sure that migrated settings are preserved.

Note The versions of installed applications must match on the source and destination computers. USMT does not support migrating the settings of an earlier version of an application to a later version, except for Microsoft Office.

 

Note USMT migrates only the settings that have been used or modified by the user. If there is an application setting on the source computer that was not touched by the user, the setting may not migrate.

 

When you specify the MigApp.xml file, USMT 4.0 migrates the settings for the following applications:

 

Product Version

Adobe Acrobat Reader

9

AOL Instant Messenger

6.8

Apple iTunes

7, 8

Apple QuickTime Player

7

Apple Safari

3.1.2

Google Chrome

beta

Google Picasa

3

Google Talk

beta

IBM Lotus 1-2-3

9.8

IBM Lotus Notes

8

IBM Lotus Organizer

9.8

IBM Lotus WordPro

9.8

Intuit Quicken

2009

Money Plus Business

2008

Money Plus Home

2008

Mozilla Firefox

3

Microsoft Office Access®

2003, 2007, 2010*

Microsoft Office Excel®

2003, 2007, 2010*

Microsoft Office FrontPage®

2003, 2007, 2010*

Microsoft Office OneNote®

2003, 2007, 2010*

Microsoft Office Outlook®

2003, 2007, 2010*

Microsoft Office PowerPoint®

2003, 2007, 2010*

Microsoft Office Publisher

2003, 2007, 2010*

Microsoft Office Word

2003, 2007, 2010*

Opera Software Opera

9.5

Microsoft Outlook Express

(only mailbox file)

Microsoft Project

2003, 2007

Microsoft Office Visio®

2003, 2007

RealPlayer Basic

11

Sage Peachtree

2009

Skype

3.8

Windows Live® Mail

12, 14

Windows Live Messenger

8.5, 14

Windows Live MovieMaker

14

Windows Live Photo Gallery

12, 14

Windows Live Writer

12, 14

Windows Mail

(only shipped with Windows Vista®)

Microsoft Works

9

Yahoo Messenger

9

Zune™

3

* A hotfix is available to support migrating Office 2010 settings. You should install this hotfix before you use USMT, when either the source or destination computer has Office 2010 installed. For more information, see Information about the User State Migration Tool (USMT) 4.0 update.

What USMT Does Not Migrate

 

The following is a list of the settings that USMT does not migrate. If you have a problem that is not listed here, see Common Issues.

Application Settings

<p class="subSection">

USMT 4.0 does not migrate the following application settings:

• Settings from earlier versions of an application. The versions of each application must match on the source and destination computers. This is because USMT does not support migrating the settings of an earlier version of an application to a later version, except for Microsoft Office, which USMT can migrate from an earlier version to a later version.
  
• Application settings and some operating-system settings when a local account is created. For example, if you run /lac to create a local account on the destination computer, USMT will migrate the user data, but only some of the operating-system settings, such as wallpaper and screensaver settings, and no application settings will migrate.
  
• Microsoft Project settings, when migrating from Office 2003 to Office 2007 system.
  
• ICQ Pro settings, if ICQ Pro is installed in a different location on the destination computer. To successfully migrate the settings of ICQ Pro, you must install ICQ Pro in the same location on the destination computer as it was on the source computer. Otherwise, after you run the LoadState tool, the application will not start. You may encounter problems when:
  • You change the default installation location on 32-bit destination computers.
    
  • You attempt to migrate from a 32-bit computer to a 64-bit computer. This is because the ICQ Pro default installation directory is different on the two types of computers. When you install ICQ Pro on a 32-bit computer, the default location is "C:\Program Files\...". The ICQ Pro default installation directory on an x64-based computer, however, is “C:\Program Files (x86)\...”.
    

Operating-System Settings

 

USMT 4.0 does not migrate the following operating-system settings.

• Local printers, hardware-related settings, drivers, passwords, application binary files, synchronization files, DLL files, or other executable files.
  
• Permissions for shared folders. After migration, you must manually re-share any folders that were shared on the source computer.
  
• Files and settings migrating between operating systems with different languages. The operating system of the source computer must match the language of the operating system on the destination computer.
  
• Customized icons for shortcuts may not migrate.
  
• Taskbar settings, when the source computer is running Windows XP.
  
• The following firewall settings when the source computer is running Windows XP.
  • The Internet Connection Sharing setting is not migrated because it can make the network less secure if it is migrated to the destination computer.
    
  • The firewall advanced-configuration settings are not migrated because of increased security risks.
    
  • The Network Connections user interface will not completely refresh until you log off or press F5.
    
  • Bridge settings are not migrated; for example, bridging a virtual private network to a second network adapter.
    

You should also note the following:

• You should run USMT from an account that has administrative credentials. Otherwise, some data will not migrate. When running the ScanState and LoadState tools on Windows Vista and Windows 7, you must run the tools in Administrator mode from an account that has administrative credentials. If you do not run USMT in Administrator mode, only the user profile that is logged on will be included in the migration. In addition, you must run the ScanState tool on Windows XP from an account with administrative credentials. Otherwise, some operating-system settings will not migrate. To run in Administrator mode, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  
• You can use the /localonly option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /localonly, see ScanState Syntax.
  

[labch]

i've been trough that documentation.. but it seems like it backs up a lot of other things i really don't need. :/