Mike S

After much headache, I was finally able to gain some headway with OS deployment in SCCM 2007 and SMP. I am able to run a task sequence against a source PC to capture the user profile and store it in the state store location (I think). When I run the second task sequence on the target PC, the OS loads, but the profile restore TS fails. (see error below) The task sequence execution engine failed executing the action (Request State Store) in the group (Restore User State) with the error code 16389 Action output: /Property></Hook2></Hooks><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> CLibSMSMessageWinHttpTransport::Send: URL: SRV253.REVENUE.WI.GOV:80 CCM_POST /ccm_system/request The request has succeeded. 200 OK migInfoRequestMessage.DoRequest (m_sResponse,true), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1142) pClientRequestToMP->DoRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2787) ExecuteRestoreRequestToMP(migInfoFromMP), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2899) ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,80) OSDSMPClient finished: 0x00004005 reply from server is 'NoReply' ClientRequestToMP::DoRequest failed (0x80004005). ExecuteRestoreRequestToMP failed (0x80004005). ExecuteRestoreRequest failed (0x80004005).. I have attached the .xml file of my test TS. If anyone has some ideas as to what I am doing wrong, I would really like to hear them. Thanks, Mike XP to W7 SMP Test.xml

I have figured out how to implement hardlinking using the .xml examples provided in this forum. Hardlinking works great for in-place upgrades. As we begin to replace devices, I plan on implementing SMP to tranfer profiles from the old PC to the new one. This is where my problems begin. I have been trying to import the SMP .xml example from this forum into SCCM 2007 to use it as a point of reference. The problem is that when I import the file, nothing happens. I can import every other .xml file into my task sequence location. Finding information on what to set up in SCCM2007 is very difficult. Even the books I have are less that informative. Does anyone know where I can find a guide on SMP implementation that actually outlines the steps needed to properly configure and execute SMP profile migration? Right now, I am manually copying profiles created with a hardlink TS to a shared server, running a O/S install TS, copying the profile to the new PC and running a USMT restore TS. There really has to be an easier way to do this. Thanks for any help in this matter. Mike

I know this an older thread, but hopefully I can get a solution. I have been trying in vain to import the "XP to W7 Demo - X86 using SMP.xml" example into a test folder in SCCM. No matter what I try, it will not import. I was able to import the hardlinking example without any problems. Does anyone have any ideas why this particular .xml file will not import? Thanks in advance, Mike

I am having difficulty pinpointing why I cannot run a command line task sequence. I am running the following command: cmd /c "setup.exe -quiet -wait -responsefile \\srv252\SAS Software Depot 9.2\responsefiles\onlyEG.properties" Not matter how I change the command line, the install always returns the following error: (Error: 8007010B; Source:Windows) Install Software failed to run command line, hr=0x8007010b. The operating system reported error 2147942667: The directory name is invalid. I have disabled 64-bit redirection, stripped down the command line to only run "setup.exe", Mapped a network drive before running the command line (I changed the path to match the mapped drive, Used the "Start In" field, etc. I know the command line works, I have ran it successfully from the "run" field. Why won't it work in SCCM 2007? I am pulling my already scarce hair out trying to figure this one out. Thanks, Mike

I see you have the same error I did..."The printer is out of paper". Try updating your distribution point for the USMT 4 package. I had made changes to my USMT .xml files and forgot to update the distribution points. Also, according to Microsoft, you should not use migdocs.xml in conjunction with miguser.xml. Hope this helps Mike

I have resolved this problem. It turns out, there is truth to computers doing exactly what they are told. Once I updated my USMT package at the distribution point, the task sequence worked perfectly. Which leads me to my next question... How do I exclude the All Users profile from being migrated? The Hard-link scan parameters are: /hardlink /nocompress /uel:15 (This excludes logins older than 15 days) The Hard-link load parameters are: /Hardlink /nocompress /ue:%computername%\* (This excludes all local accounts) The All Users profile was transferred, which doubled up many desktop icons among other things. I do not want this to happen. Is it possible for me to insert a task sequence before the Restore which will delete the All Users folder from the Local State Location without disrupting the restore task sequence? Is there a simpler method perhaps? Thanks again for any insight to this problem. Mike

I have finally managed to create a working task sequence that will migrate an XP machine to Windows 7 that will also include only domain user profiles from the last 15 days. Unfortunately, some unwanted baggage is also restored. I have a custom.xml file that takes care of this I wish to incorporate into my task sequence. I know the custom.xml file works, because we can run it manually without any errors. When I add the custom.xml file to the list of files used during the load state task, I get an interesting error in the advertisement.... The task sequence execution engine failed executing the action (Restore User Files and Settings) in the group (Restore User Files and Settings) with the error code 2147942428 Action output: ing user defined params successful Building USMT command successful Securing store .. Executing command line: "C:\_SMSTaskSequence\Packages\MAD0019C\amd64\loadstate.exe" "C:\UserState" /c /lae /lac:*** /v:5 /l:"C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\loadstate.log" /progress:"C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\loadstateprogress.log" /i:"C:\_SMSTaskSequence\Packages\MAD0019C\amd64\migapp.xml" /i:"C:\_SMSTaskSequence\Packages\MAD0019C\amd64\miguser.xml" /i:"C:\_SMSTaskSequence\Packages\MAD0019C\amd64\cstom.xml" /Hardlink /nocompress /ue:RVPC5762\* Log messages are being sent to 'C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\loadstate.log' Script file is not present: 'C:\_SMSTaskSequence\Packages\MAD0019C\amd64\custom.xml' Failed. An error occurred processing the command line. Unable to find a script file specified by /i LoadState return code: 28 USMT returned exit code (0x0000001c). Look USMT log file loadstate.log for detail error message. POSDMigrateUserState finished: 0x8007001c. The operating system reported error 2147942428: The printer is out of paper. The loadstate.log shows the following error.... [0x000000] Script file is not present: 'C:\_SMSTaskSequence\Packages\MAD0019C\amd64\custom.xml'[gle=0x00000006] I am trying to incorporate the custom.xml in the restore user step. When I remove the custom.xml file, the problem goes away. How can I use the custom.xml file properly? Thanks in advance, Mike

Yes. The complete task sequence is for a Windows 7 x64 deployment. Prior to running the VS2008 task, I run Document Explorer, Web Designer Tools and the appropriate 64-bit prerequisites. The three prerequisite tasks run without any problems. Once the VS2008 task finishes downloading the source files locally, it runs for about 10 seconds then moves on to the next task (VS2008 SP1) which then fails upon execution. The logfiles report that VS 2008 has installed correctly...so I have no clue where to look anymore. I do not wrap the prerequisites into a script (not much of a programmer), I use separate task sequences for each one. Judging by your reply, I can assume you have figured out how to make VS 2008 install using a customized .ini file. I am very confused as to why the program will not install with SCCM 2007 but will install manually using the very same command line configured in the task sequence. Your help is greatly appreciated. Mike

I have created several packages for installing Visual Studio 2008. These packages, when executed manually from the source directory, have run successfully. The problem is when I deploy the packages using SCCM 2007, they bomb. I am using the setup.exe /unattendfile vs2008.ini command to customize the install. During the install process, the prerequisite software is installed correctly. When the Visual Studio 2008 install downloads to the local PC, the install starts, then breaks. I have to manually go to the downloaded files in the cache folder and run the command line described above to run the install. The rest of the task sequence breaks and has to be manually continued as well. My initial thoughts were permission related, but when I created a separate task sequence to be executed while I was logged in, it bombed as well. My question: What am I missing? It really seems silly that a Microsoft product will not install using Microsoft's own management tool. I will gladly answer any and all requests for additional information pertaining to this problem. Thanks, Mike

I have resolved the problem. I had to manually edit the configuration file to point to the PCU folder (used in slip-streaming the SP). After much irritation, I noticed that I had forgotten to put a "." in front of the folder location. Funny how a "." is powerful enough to bring down an entire package. Lesson learned I guess.

The package is run using a command line entry to incorporate a customized install (setup.exe /ConfigurationFile=sql2008_x86.ini). Basically, I am running the install as it appears in the installation DVD. Snapshot attached. When I run the installation manually, everything works perfectly. The errors (4 errors) are as follows: Error ID: 10006 The program for advertisement "MAD20060" failed ("MAD00077" - "MS SQL 2008 Workstation"). A failure exit code of -2068578304 was returned. Error ID: 11135 The task sequence execution engine failed executing the action (SQL Server 2008) in the group (Install Software) with the error code 2226388992 Error ID: 11141 The task sequence execution engine failed execution of a task sequence. Error ID: 11170 The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. Hope this info helps, if you need more, let me know. Thanks for your assistance. Mike

I am trying to deploy SQL Server 2008 R2 with SP1 slip-streamed using SCCM2007 (Version: 4.00.6487.2000)to a Windows 7 32-bit box and am having absolutely no luck. I have tested the install for functionality and correctly created a package in SCCM. Everything looks correct. The problem is; when I run the advertisement it bombs out. I noticed that the cache size was too small, so I fixed that...still no luck. Thinking I would be slick, I created a completely new O/S install package to include SQL 2008. The new installation worked great...until it was trying to install SQL 2008. Again, SQL bombed. I know I am missing something, but I cannot for the life of me figure out what it is. Any insight to this irritating problem is greatly appreciated. If more info is needed, please ask and I will give what knowledge I have. Thanks