I have generated a config.xml and turned off the: <component displayname="Taskbar and Start Menu" migrate="no" ID="appearance_and_display\taskbar_and_start_menu">
Inside the xml file as I noticed this was happening way back with USMT4. I was getting all the Windows XP start menu shortcuts and folders on my completed Windows 7 upgrades. Very annoying! Also make sure you are using the \targetwindows7 switch in your USMT command line otherwise wallpaper and a few other things will not be migrated properly. I have a step in my TS under CM 2012 SP1 which sets additional migration commands including this one for my Windows XP - Windows 7 migrations. /uel:90 /config:"%_SMSTSMDataPath%\Packages\%_OSDMigrateUsmtPackageID%\%PROCESSOR_ARCHITECTURE%\config.xml" /targetwindows7 From: [email protected] [mailto:[email protected]] On Behalf Of Hyatt, Dewayne - Data Center Operations Sent: Tuesday, 25 June 2013 10:55 PM To: [email protected] Subject: [mssms] USMT - Orphaned shortcuts Hey everyone, I've been working on refreshing a lot of our machines from XP to W7. I have a couple thousand teacher machines that I am using hardlinking on to preserve their data. Everything is working great except I am apparently migrating dead/orphaned desktop shortcuts and start menu objects. It was my understanding that loadstate would not migrate a shortcut if the target file didn't exist on the system. Not sure how I managed to break that.... Am I missing something or is this normal behavior that I need to clean up? I'm on SCCM 2012 SP1 using USMT 5.0 Thanks, Dewayne ________________________________ [Florida has a very broad Public Records Law. All correspondence sent to or from this entity is subject to the Public Records Law of Florida. Email communication may be subject to public and media disclosure upon request. Under Florida Law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public-records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.] ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
