Kinom

Take a look at the SMSTS.log

Take a look at this post http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/

Quiestion Why capture a complete OS with all the drivers and progs? You can create a WIM file with only the OS and put the rest in a task sequence. That’s much easier, If you have to change a program or driver, you can do it in the task sequence. Otherwise you have to create a new complete OS and capture again. cheers

Hi, Are you trying to take an image of the ideal computer? Why? Chreers

Hallo, Take a look at this post http://blogs.technet.com/smsandmom/archive/2008/10/23/configmgr-2007-osd-task-sequence-fails-with-the-error-an-error-occurred-while-retrieving-policy-for-this-computer-0x80004005.aspx I hoop it helps you

Hi, I se 2 problems 1) The command line has to start with cmd.exe /c The /c is for the silent istall after that you can try to add the rest of the command. 2) Leave the Start in empty, this is not necessary and this is also the problem of the following error 0x00000001. It means that SCCM can’t find the pad specified. For example you can try the next line. cmd.exe /c net user RMA local_x /ADD timeout /t1 net user …… Sometimes is it better to use multiple command line task sequences. I hope that this helps you

Anyweb, Do you have any idea?

Task sequence: 1 Capture network settings Migrate Domain and workgroup membership (selected) Migrate Network adapter configuration (selected) 2 capture Windows settings Migrate computer name (selected) Migrate registered user and organization names (selected) Migrate timezone (selected) 3 OSDStateStorePath Value --> %_SMSTSUserStatePath% 4 OSDMigrateAdditionalCaptureOptions Value --> /nocompress /hardlink 5 Capture User State Customize how user profiles are captured Files: MigApp.xml, MigDocs.xml and MigUser.xml 6 Restart in winPE 7 Apply operating system 8 Apply windows settings 9 Join domain 10 Apply device drivers 11 setup configMgr 12 OSDMigrateAdditionalRestoreOptions Value --> /nocompress /hardlink 13 Restore User State Customize how user profiles are captured Files: MigApp.xml, MigDocs.xml and MigUser.xml Restore local computer user profile (selected) Set a password Continue if some files cannot be restored (selected) The USMT package is pointed to the X86 folder The computer is an existing Vista with 2 partitions C and D drive.

Hi All Can someone help me? I managed to do the USMT capture. I check on the C drive if the hardklink is there and all the files, it is. Now when the task sequence reboots the computer it does something strange. De hardlink on the C drive is gone and I see the hardlink on the D drive but I dont see the files. It deploys Win7 and if it starts with the restore of the user data I receave an error (0x8007001c). Is it possible to configure that the hardlink has to stay on the C drive? Logs from the SCCM Console: dstate.log" /progress:"C:\Windows\system32\CCM\Logs\SMSTSLog\loadstateprogress.log" /i:"D:\_SMSTaskSequence\Packages\F010013C\x86\MigApp.xml" /i:"D:\_SMSTaskSequence\Packages\F010013C\x86\MigDocs.xml" /i:"D:\_SMSTaskSequence\Packages\F010013C\x86\MigUserxml" /nocompress /hardlink Connection request for "D:\_SMSTaskSequence\UserState" Path is not a UNC Path. Trying it as a local path. Succeeded loading resource DLL 'C:\Windows\system32\CCM\1033\TSRES.DLL' Executing command line: "D:\_SMSTaskSequence\Packages\F010013C\loadstate.exe" "D:\_SMSTaskSequence\UserState" /c /lae /lac:*** /l:"C:\Windows\system32\CCM\Logs\SMSTSLog\loadstate.log" /progress:"C:\Windows\system32\CCM\Logs\SMSTSLog\loadstateprogress.log" /i:"D:\_SMSTaskSequence\Packages\F010013C\86\MigApp.xml" /i:"D:\_SMSTaskSequence\Packages\F010013C\x86\MigDocs.xml" /i:"D:\_SMSTaskSequence\Packages\F010013C\x86\MigUser.xml" /nocompress /hardlink USMT returned exit code (0x0000001c). Look USMT log file loadstate.log for detail error message. Scanstate Log: 2009-12-10 16:51:01, Info [0x000000] USMT Started at 2009/12/10:16:51:01.661 2009-12-10 16:51:01, Info [0x000000] Command line: D:\_SMSTaskSequence\Packages\F010013C\scanstate.exe D:\_SMSTaskSequence\UserState /o /localonly /c /efs:copyraw /l:C:\Windows\system32\CCM\Logs\SMSTSLog\scanstate.log /progress:C:\Windows\system32\CCM\Logs\SMSTSLog\scanstateprogress.log /i:D:\_SMSTaskSequence\Packages\F010013C\MigApp.xml /i:D:\_SMSTaskSequence\Packages\F010013C\MigDocs.xml /i:D:\_SMSTaskSequence\Packages\F010013C\MigUser.xml /nocompress /hardlink 2009-12-10 16:51:01, Info [0x000000] Script file specified: D:\_SMSTaskSequence\Packages\F010013C\MigApp.xml[gle=0x00000002] 2009-12-10 16:51:01, Info [0x000000] Script file specified: D:\_SMSTaskSequence\Packages\F010013C\MigDocs.xml[gle=0x00000002] 2009-12-10 16:51:01, Info [0x000000] Script file specified: D:\_SMSTaskSequence\Packages\F010013C\MigUser.xml[gle=0x00000002] 2009-12-10 16:51:01, Info [0x000000] Starting the migration process[gle=0x00000006] 2009-12-10 16:51:02, Warning [0x080462] CListSysFileFilter::BuildTree: could not create FileList object for D:\_SMSTaskSequence\Packages\F010013C\SFLISTLH.DAT: Win32Exception: \\?\D:\_SMSTaskSequence\Packages\F010013C\SFLISTLH.DAT: The system cannot find the file specified. [0x00000002] __thiscall UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long) 2009-12-10 16:51:02, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Windows Live Mail [store Root] is considered invalid in the current context 2009-12-10 16:51:02, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Works\9.0\Common\Templates [TemplateDirectory] is considered invalid in the current context 2009-12-10 16:51:09, Info [0x000000] System information: Computer name: LPT00223 Machine SID: S-1-5-21-2548410259-1414263244-2658524999 OS version: 6.0.6002.Service Pack 2 Language: en-US Architecture: 32-bit Drives: C: Type: Fixed, Bus type: ATA, Hotplug: No D: Type: Fixed, Bus type: ATA, Hotplug: No E: Type: CD/DVD Users: FCSNTDOMAIN\xxx_INSTALL, administrator: No, interactive: Yes, logged on: No, has profile: Yes FCSNTDOMAIN\xxxxxx, administrator: No, interactive: Yes, logged on: No, has profile: Yes LPT00223\xxx, administrator: Yes, interactive: Yes, logged on: No, has profile: Yes LPT00223\Guest, administrator: No, interactive: Yes, logged on: No, has profile: No LPT00223\Administrator, administrator: Yes, interactive: Yes, logged on: No, has profile: No 2009-12-10 16:51:09, Info [0x000000] Processing the settings store[gle=0x00000006] 2009-12-10 16:51:09, Info [0x000000] Examining the system to discover the migration units [gle=0x00000006] 2009-12-10 16:51:20, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Windows Live Mail [store Root] is considered invalid in the current context 2009-12-10 16:51:20, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Works\9.0\Common\Templates [TemplateDirectory] is considered invalid in the current context 2009-12-10 16:51:21, Info [0x000000] Selecting migration units [gle=0x00000006] 2009-12-10 16:51:21, Info [0x000000] Estimating total file size for the progress log[gle=0x00000006] 2009-12-10 16:51:23, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Windows Live Mail [store Root] is considered invalid in the current context 2009-12-10 16:51:23, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Works\9.0\Common\Templates [TemplateDirectory] is considered invalid in the current context 2009-12-10 16:51:37, Info [0x000000] Gathering data [gle=0x00000006] 2009-12-10 16:51:40, Error [0x0808fe] Plugin {0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}: CscMig: CscMigrationPlugin::raw_Gather(693):Fatal error gather information from CSC cache, status = 0xc0000035 2009-12-10 16:51:40, Error [0x080389] Failure while calling IDiscovery->Gather for Plugin={ServerPath="%SYSTEM32%\CscMig.dll", CLSID={0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}, ThreadingModel=Apartment}. Error: 0xD0000035 2009-12-10 16:51:56, Error [0x0808fe] Plugin {0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}: CscMig: CscMigrationPlugin::raw_Gather(693):Fatal error gather information from CSC cache, status = 0xc0000035 2009-12-10 16:51:56, Error [0x080389] Failure while calling IDiscovery->Gather for Plugin={ServerPath="%SYSTEM32%\CscMig.dll", CLSID={0db12ccb-7cfd-46b6-b4d1-daa6ff0fbcf7}, ThreadingModel=Apartment}. Error: 0xD0000035 2009-12-10 16:51:59, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Windows Live Mail [store Root] is considered invalid in the current context 2009-12-10 16:51:59, Warning [0x0803ec] Registry location HKCU\Software\Microsoft\Works\9.0\Common\Templates [TemplateDirectory] is considered invalid in the current context 2009-12-10 16:52:31, Info [0x000000] Success.[gle=0x00000006] 2009-12-10 16:52:31, Info [0x000000] USMT Completed at 2009/12/10:16:52:31.933[gle=0x00000006]

Ok hire it comes. What I have done is: Copy past the USMT folder from the Program files of a XP computer to a server share and created a package pointed to the X86 folder and distributed to the DPs (No program). You can use this also C:\Program Files\Windows AIK\Tools\USMT I added into the task sequence and specify the files just like you told me. It is strange because on my virtual environment I dont have to do these steps, pointing to the X86 file and add the files. Migrate XP to Win7 no problem Now I am testing to migrate a vista to win7 but I have to configure the MigUser.xml and I dont know what to change

I deed what you told and it works I will let you know if it is complete.

I will give it a try

Ho all, I have a problem using USMT 4.0 in SCCM On my virtual environment it works fine , now I am trying to implement it on our existing infrastructure and I receive the following error 80070002. 0, HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,95) VerifyIfPreLonghornBinary(sUsmtBinary, m_bUSMTPreLonghorn), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,523) SetUSMTBinary(), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,955) usmAction.Init(::GetCommandLineW()), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\main.cpp,235) Invoking ReleaseSource on USMTPackagePath D:\_SMSTaskSequence\Packages\F010013C Entering ReleaseSource() for D:\_SMSTaskSequence\Packages\F010013C reference count 1 for the source D:\_SMSTaskSequence\Packages\F010013C before releasing Delete source directory D:\_SMSTaskSequence\Packages\F010013C IsUsmtPreLonghorn failed (0x80070002). UserStateMigrationAction::GetUSMTBinary failed (0x80070002). Failed to initlialize, (0x80070002) Released the resolved source D:\_SMSTaskSequence\Packages\F010013C OSDMigrateUserState finished: 0x80070002 I deed already what Peter told me but it wont work. What am Im doing wrong?

I have been looking on the internet and someone mention something about a log file mpfdm.log I attach it, maybe it will help :-) mpfdm.log

Any idea

Thats strange. I check the folders to see how big the files are and all the folders are empty.

Hi all, I updated SCCM to SP2 and I have a small problem After the upgrade I receive the following warnings MP File Dispatch Manager cannot copy files from "F:\SMS\MP\OUTBOXES\sinv.box" to "\\server\SMS_123\inboxes\auth\sinv.box” Before the upgrade I didn’t have any problem with this. Has someone experience on this? Thanks

Hi, Thanks, I will check it out.

Any news?

I deed, but I don't see anything special Here is the recent log files, maybe you can. smspxe.zip

no MDT integrated

Hi Anyweb, Thanks for all the support that you give and the other guys to, I just want to mention that Its a great forum; it solves a lot of my problems in the past 6 months that I work with sccm The server is a windows server 2008 and since 1week it is SCCM2007 SP2. The errors are there now for more than 1 month and it repeats every hour.

Yes. The funny thing is that everything works fine

Hi all, At one of my customers I have the following issue. Every hour I see the following error. Status Message in SMS_PXE_SERVICE_POINT component log: PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389. I check with other configurations and there I don’t see this. Has some one any idée where to look. Thanks

that is also a possability But I had the same problem ones and it was not expired and then I solved it like that. strange I know