Hi guys, i need help with SCCM 2007 R2. I am about to create our new task sequences for x86 and x64 architecture. I set up a build and capture TS for x86 and after the step "Setup windows and ConfigMgr" i added a "install software" with this program from my langpack package: DISM /Online /Add-Package /PackagePath:"x86\de-de\lp.cab" <- this is working fine! But when it comes to the x64 task sequence i added a programm to the langpack package with this command: DISM /Online /Add-Package /PackagePath:"x64\de-de\lp.cab" <- but this isn working in the x64 TS! Following error message is shown: Severity Type Site code Date / Time System Component Message ID Description Error Milestone xxx 28.06.2011 15:04:47 xxxxxxxx Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Install "Windows 7 LanguagePacks-OSD Win7 LangPack DEU") in the group (Win7 LangPacks) with the error code 2147942411 Action output: Pack DEU x64'='{FD19396E-179E-4E78-89C6-C6A13C72636F}' Waiting for installation job to complete.. CompleteExecution received Received job completion notification from Execution Manager Installation completed with exit code 0x8007000b Setting TSEnv variable 'SMSTSInstallSoftwareJobID_AZL000BE_AZL2012D_OSD Win7 LangPack DEU x64'='' CompleteExecution processed GetExecRequestMgrInterface successful Releasing job request, jobID='{FD19396E-179E-4E78-89C6-C6A13C72636F}' Releasing of Job Request successful CompleteJob successful Entering ReleaseSource() for \\Distributionshare\xxx000BEreference count 1 for the source \\Distributionshare\xxx000BE\ before releasing Released the resolved source \\Distributionshare\xxx000BEpInstall->Install(sPackageID, sProgramName), HRESULT=8007000b (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) Installation failed with error (0x8007000b) Install Software failed, hr=0x8007000b. The operating system reported error 2147942411: An attempt was made to load a program with an incorrect format. Could you please help me with this error? Or tell me what other methods are available for installing language packs in a build and capture TS? kind regards Peter Weiger

Have you disabled X64 redirect?? You could also install from WinPE using MDT integration.Michael Petersen My Deployment Blog - http://blog.coretech.dk/mip

We dont use MDT right now. Where can i disable x64 redirect?

on the run command line step where you run the dism command! its a check box just under the command field! And you should really consider using MDT integration, it will give you all kinds of nice stuff! Michael Petersen My Deployment Blog - http://blog.coretech.dk/mip

i found the option... But like i wrote, this is not a "run command line" step. It is a "install software" step. I created a package with the langpacks inside and for each langpack there is a programm with the DISM command.

then try and run C:\windows\system32\DISM /Online /Add-Package /PackagePath:"x64\de-de\lp.cabMichael Petersen My Deployment Blog - http://blog.coretech.dk/mip

or create a package with the content of "C:\Program Files\Windows AIK\Tools\x86\Servicing" and the LP.cab, and then run cmd.exe /c DISM.exe /offline /Add-Package /PackagePath:lp.cab" from within WinPE using that package from a run commandline stepMichael Petersen My Deployment Blog - http://blog.coretech.dk/mip

i tried your frist solution -> same error. To your second solution... that would mean, that i have to create one package for every languagepack? and why do i have to use the /Offline switch? i thought /offline only works with already created images. is there no standard way for adding language packs?

i finally installed MDT 2010. But now i have a task sequence which looks a little bit confusing to me... i think, i don't need the state capture and state restore group or am i wrong? I just want a simple build and capture TS, like it was befor without MDT 2010. Last and most important question for me. Where do i have to put in the install language pack step?

sorry for the /offline switch, had a lot to do and i obviously forgot the syntax!! While ruining dism from WinPE you are actually running in offline mode, so you can use dism as if it was a mounted image.. so lets say you applied the image to c:\, then you can add the LP using this command line cmd.exe /c DISM.exe /Image:c\ /Add-Package /PackagePath:lp.cab If you put all your LanguagePacks in folders in the DISM package you should be able to use cmd.exe /c DISM.exe /Image:c\ /Add-Package /PackagePath:de-de\lp.cab (for German) and so on. About the TS, then you do not need to use the MDT wizard build TS, you can just open your current TS, and the add the "Apply language pack offline" step that can now be found in the MDT menu in your TS editor (remember that it must be in WinPE). There is even a step to apply language on line (full OS) so you decide for you self)Michael Petersen My Deployment Blog - http://blog.coretech.dk/mip

Ok now, finally i got it working. I added the "install language pack offline" task before the "configure windows and configmgr" task. It seems like there is no way to add language pack in a x64 windows 7 without MDT2010 Thanks for your help Michael !

This can be done without MDT integration. Here is how I do it: 1) Create a package and copy each lp.cab file into the root (Just rename each cab so they can all exist in the same folder e.g. de-de.cab for German etc...) 2) In your task sequence, after the Setup windows and ConfigMgr step and before you apply any updates (important) add a Run command line step with the following properties: a. Package: The package from step 1 b. Disable 64-bit file system redirection: Enabled c. Command Line: cmd.exe /c dism.exe /online /add-package /PackagePath:"%CD%" This will add all language packs that exist in the package directory to the installed OS. If you need to add more languages later, just drop a CAB file in the package and update it the command line stays the same. This also has the added benefit of only downloading the package once to install all the required languages. If you specify multiple tasks to do this in the task sequence it has to download each one separately which can add some additionall overhead to the time to install.