Jump to content


jering

Established Members
  • Posts

    4
  • Joined

  • Last visited

jering's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Yes, the computer are joined to the domain. However, the SCCM-client are installed, but not configured properly. I`ll resolve that problem first to see if the restore process also are resolved afterwards. Update: The SCCM-client issue are now resolved. I tried a new offline migration from XP to Win 7, but still the same thing happens. No data restored. When I access the C:\USMTOffline folder I get an "You need permissions on this folder to continue" message. When I press Continue I can see the contents, but I guess I`m then taking ownership. Could permissions be the issue regarding the USMT restore process? Update #2: FYI I created a thread regarding the issue here: http://social.technet.microsoft.com/Forums/en/configmgrosd/thread/d4fdfb19-1c24-417b-8b33-0d64af72dda4
  2. Will do First I need to get the XP to Win7-migration work newdomain->newdomain before I test olddomain->newdomain. As I mentioned the scanstate now runs successfully and Win7 installs successfully. At the first boot after completion it complains about wrong password when automatically logging on as administrator. I type the password manually and it logs on but no restore sequence kicks off. I can see the USMT-folder in C:\USMTOffline, so the data are present. It`s supposed to auto-logon the local administrator-account, perform the Restore (loadstate) and then log off?
  3. I`m sorry, I did a mistake and chose the "USMT - both" package where I should have chosen the "USMT - x86 only". Fixed that and now it works as expected. Thanks for your quick reply! The scenario where I`m planning to use this: New domain with a new installation of SCCM 2007 R2 with SP2 and MDT 2010-integration Old domain with Windows XP client computers Users migrated from old domain to new domain using Active Directory Migration Tool (with SID History and passwords). What we want to accomplish is to migrate the client computers to Windows 7 and join them directly to the new domain. I guess that local profiles can be retained by using the /md:OldDomain:NewDomain switch on the loadstate.exe. Anyone tried this?
  4. Nice work! I`ve imported the task sequence and set up the cmd-file as a package and assigned the right packages and a Win7 OS image. However, when I run the task sequence on a computer running Windows XP it fails on "do x86 scanstate" with the error 0x00000001. I can see that the C:\USMTOffline and C:\USMTbits are created and that the cmd-file and the USMT-files are there. Any ideas?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.