You are browsing the archive for OSD.

Lenovo X1 not PXE booting in Configmgr 2012 SP1 ?

10:51 am in ConfigMgr 2012, ConfigMgr 2012 SP1, Deployment, lenovo, Operating System Deployment, OSD, SCCM 2012, SCCM 2012 SP1, windows 8 by Kenny Buntinx [MVP]

 

Customer does zero-touch Windows 8 deployments on all computers , but when I tried it on the Lenovo Carbon X1 with the USB Ethernet dongle (P/N: 0A36322 or 0B67708) that Lenovo sells , it didn’t work.

However PXE boot works and I get an IP to begin the WinPE x64 download but once we get in the WinPE 4.0 stack , the Ethernet lights turns off and the machine reboots.To troubleshoot, I pressed F8 to bring up the CMD and IPCONFIG /all doesn’t list the NIC. Strange .

What if PXE boot does not work at all ? You need to do this first :

  • In the BIOS, under STARTUP, change the UEFI/Legacy Boot to "Legacy Only"
  • In the BIOS, under RESTART, change the OS Optimized Defaults to "Disabled", then choose "Load Setup Defaults".

On Configmgr 2012 sp1 ,  I imported the x64 drivers both from Lenovo the Ethernet dongle and then redeployed the boot images but no luck each time.

So hold on a minute .. does that X1 only have USB 3 ports ? Yes it has .

Solution : Download the USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family here : https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21129 . Make sure you have version 1.0.8.251 as older versions do not work with WINPE 4.0 .

Import the drivers in ConfigMgr 2012 SP1 and add them to your boot image . Now it will work !

Note : Other systems that exhibit this same behavior are the ASUS Zenbook UX31, Apple MacBook Air plus and I expect most of the new Ultrabook form factor systems that only have USB 3.0 ports and no built-in ethernet port will have this same problem.

Hope it Helps ,

Kenny Buntinx

Enterprise Client Management MVP

Do you need driver packs for deploying Fujitsu Systems ?

12:10 pm in Fujitsu, Operating System Deployment, OSD by Kenny Buntinx [MVP]

 

I’ve also found that Fujitsu also provided a SCCM driver cab download for their enterprise models. Get the supported model list and driver link here :

http://support.ts.fujitsu.com/content/sccm.asp?LNG=EN&LNID=1

image

Hope it helps ,

Kenny Buntinx

Configmgr 2012 RTM/SP1 and Riverbed Appliances not a good marriage: “Application fails during OSD Task sequence with exit code 16389 (RequestContent from CAS failed. Error = 0x87d01202)” and “Apply driver Package does not apply the NIC driver”

3:12 pm in ConfigMgr 2012, ConfigMgr 2012 SP1, OSD, riverbed, sccm, SCCM 2012, SCCM 2012 SP1, sccm RTM by Kenny Buntinx [MVP]

 

Environment : SCCM2012 SP1 (W2K8 R2 sp1) and the SQL2K8 R2 SP2 that is hosting the database is running on a separate VM. Our source files are stored on a CIFS share.

We experienced a strange behavior when using a task sequence to deploy an OS together with .Net framework (4.5) application after the upgrade to SP1 and our OSD task sequence wouldn’t apply any driver anymore. This looked suspicious , but finally it had nothing to do with the upgrade to sp1 , but with riverbed appliances for WAN traffic optimization.

For the driver packages, the data source folder is created successfully and contains all the subfolders (i.e.0EC7ACC5-0776-4676-B90B-967D7769C185) with the driver files. The problem is that when we distribute the content to our DP’s, it indicates everything is successfully distributed on all DP’s, but when our OSD wants to use those drivers package it says no files found.

Problem 1 : The application wouldn’t install anymore and fail .

Once that the step kicks in to install the application we get the following error:

"The task sequence failed to install application Microsoft .NET Framework 4.5(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6) for action (Install Application .NET) in the group () with exit code 16389."

Extract from CITaskMgr.log
Initiating task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 (WKS_CORP_.NET Framework 4.5_EN_64) for target: , consumer: {B351446F-8FDF-4DD9-AE75-F9E818E79D25}    CITaskMgr    1/29/2013 5:53:51 PM    1036 (0x040C)
Initiating content download : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
RequestContent from CAS failed. Error = 0x87d01202    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
Binary content download failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
State transition to (Failure), Error(0x87d01202) : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
State transition to (Failure), Param(-2016407038) : CTaskConsumer(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2.{4FFAD6D2-6F40-4870-96F5-B49B091CA9D2})    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
ResumeTask failed. Error = 0x87d01202 : CITask(ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2..Install.ContentDownload)    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
CCITaskMgr::InitiateTask failed. Error =0x87d01202    CITaskMgr    1/29/2013 5:53:52 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e.2 for target: , consumer {B351446F-8FDF-4DD9-AE75-F9E818E79D25}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6.2 for target: , consumer {EE171CEB-C12F-47FD-8564-57CB90B02641}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)
Release task ContentDownload for CI ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 for target: , consumer {544D045C-A3DE-4B93-8C8C-B68B0DE703B6}    CITaskMgr    1/29/2013 5:53:53 PM    1036 (0x040C)

Extract from SMSTS.log
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
Passed in version 2 for ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 = DownloadFailed    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
NotifyProgress received: 24 (Application download failed )    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
GetAppMgmtSDKInterface successful    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
Passed in version 2 for ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6.2 = DownloadFailed    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)
GetAppMgmtSDKInterface successful    InstallApplication    1/29/2013 5:53:53 PM    2120 (0x0848)
CAppMgmtSDK::GetEvaluationState ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/RequiredApplication_0e53477f-e752-4d52-b9b2-db24e27961b6    DCMAgent    1/29/2013 5:53:53 PM    2120 (0x0848)

Extract from CIDownloader.log
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:51 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:53 PM    2036 (0x07F4)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6/2/MANIFEST    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/Application_0e53477f-e752-4d52-b9b2-db24e27961b6/2/PROPERTIES    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
GetInstanceFromLantern failed (0x80041002).    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
DCM::LanternUtils::CheckCIExists – Wmi Instance: PolicyPlatform_Policy.Name="ScopeId_59BCBA4C_DFF4_4108_922A_B0F379D9AC3A_Application_0e53477f_e752_4d52_b9b2_db24e27961b6_Platform_PolicyDocument",Authority="System Center Configuration Manager",Revision=2 not found in namespace: root\microsoft\policyplatform\Documents\Local. CI not found.    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e/2/MANIFEST    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
VerifyCIDocumentHash – Preparing to verify hash for CI document ScopeId_59BCBA4C-DFF4-4108-922A-B0F379D9AC3A/DeploymentType_ad388e96-a3ce-4fc8-9c56-75d3dc5c116e/2/PROPERTIES    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
GetInstanceFromLantern failed (0x80041002).    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)
DCM::LanternUtils::CheckCIExists – Wmi Instance: PolicyPlatform_Policy.Name="ScopeId_59BCBA4C_DFF4_4108_922A_B0F379D9AC3A_DeploymentType_ad388e96_a3ce_4fc8_9c56_75d3dc5c116e_Discovery_PolicyDocument",Authority="System Center Configuration Manager",Revision=2 not found in namespace: root\microsoft\policyplatform\Documents\Local. CI not found.    CIDownloader    1/29/2013 5:53:55 PM    1036 (0x040C)

Problem 2 : The apply driver package did not apply any driver :

In fact, ALL the other driver packages we have made till now have the same settings, but those have well a size between 80 – 600 MB.

The distmgr.log (the driver package with 0 size is EUA00060)

Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:49:06 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:44 AM    3476 (0x0D94)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:49 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:49 AM    3476 (0x0D94)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:54 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:54 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x1204 (4612)    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:55.383 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Start adding package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
The Package Action is 2, the Update Mask is 0 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2300    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Taking package snapshot for package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
The content package does not contain any contents.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2376    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Adding these contents to the package EUA00060 version 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:55.554 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:55 AM    4612 (0x1204)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
A program for package EUA00060 has been added or removed, therefore it needs to be replicated to all child sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Adding these contents to the package EUA00060 version 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4612 GMTDATE=Mon Jan 28 08:57:56.760 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:56 AM    4612 (0x1204)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:57:59 AM    3476 (0x0D94)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:00 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:00 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:05 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:05 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:10 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 9:58:10 AM    3268 (0x0CC4)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:14 AM    3476 (0x0D94)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:19 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:24 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:24 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0xA68 (2664)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:25.352 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Start updating the package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
The Package Action is 1, the Update Mask is 18 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:25.425 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Set share security on share \\TGDAMSA01.tgtest.com\SCCMContentLib$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:25 AM    2664 (0x0A68)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2664 GMTDATE=Mon Jan 28 09:01:26.028 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:26 AM    2664 (0x0A68)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:01:26 AM    2664 (0x0A68)
Found package properties updated notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:02:59 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:04 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:04 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x1248 (4680)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:05.353 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Start updating the package EUA00060…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
The Package Action is 1, the Update Mask is 264192 and UpdateMaskEx is 0.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Successfully created/updated the package EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:05.420 2013 ISTR0="EUA00060" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Set share security on share \\TGDAMSA01.tgtest.com\SCCMContentLib$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Created policy provider trigger for ID EUA00060    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Package EUA00060 does not have a preferred sender.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
Package EUA00060 is new or has changed, replicating to all applicable sites.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=EUA00060, Version=1, Status=2301    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
StoredPkgVersion (1) of package EUA00060. StoredPkgVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
SourceVersion (1) of package EUA00060. SourceVersion in database is 1.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:05 AM    4680 (0x1248)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=4680 GMTDATE=Mon Jan 28 09:03:06.014 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:06 AM    4680 (0x1248)
Exiting package processing thread.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:06 AM    4680 (0x1248)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:09 AM    3476 (0x0D94)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:10 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:10 AM    3268 (0x0CC4)
Found notification for package ‘EUA00060’    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Used 0 out of 7 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Starting package processing thread, thread ID = 0x99C (2460)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
Sleep 3600 seconds…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    3268 (0x0CC4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2460 GMTDATE=Mon Jan 28 09:03:20.901 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="EUA00060" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="EUA00060"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    2460 (0x099C)
No action specified for the package EUA00060.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:20 AM    2460 (0x099C)
Start adding package to server ["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=2760 GMTDATE=Mon Jan 28 09:03:21.473 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
Start adding package to server ["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    5004 (0x138C)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=5004 GMTDATE=Mon Jan 28 09:03:21.986 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\BEBRMSA02V.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA02V.tgtest.com\"    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    5004 (0x138C)
The current user context will be used for connecting to ["Display=\\TGDAMSA03.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\TGDAMSA03.tgtest.com\.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
Successfully made a network connection to \\TGDAMSA03.tgtest.com\ADMIN$.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:21 AM    2760 (0x0AC8)
CreateSignatureShare, connecting to DP    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Signature share exists on distribution point path \\TGDAMSA03.tgtest.com\SMSSIG$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Set share security on share \\TGDAMSA03.tgtest.com\SMSSIG$    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Ignoring drive \\TGDAMSA03.tgtest.com\C$\.  File \\TGDAMSA03.tgtest.com\C$\NO_SMS_ON_DRIVE.SMS exists.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (TGDAMSA01.tgtest.com) is submitting SDK changes from site(EUA)    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2760 (0x0AC8)
Start adding package to server ["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.com\…    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Will wait for 3 threads to end.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Thread Handle = 0000000000001F04    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    2460 (0x099C)
Attempting to add or update a package on a distribution point.    SMS_DISTRIBUTION_MANAGER    1/28/2013 10:03:22 AM    540 (0x021C)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=TGDAMSA01.tgtest.com SITE=EUA PID=1880 TID=540 GMTDATE=Mon Jan 28 09:03:22.488 2013 ISTR0="DELL E6230 WIN7 x64" ISTR1="["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="EUA00060" AID1=404 AVAL1="["Display=\\BEBRMSA01.tgtest.com\"]MSWNET:["SMS_SITE=EUA"]\\BEBRMSA01.tgtest.

Solution :

After further investigations and testing, we found the source of our problems: Riverbed Appliances at  www.riverbed.com !

In there infrastructure, there are RIVERBED appliances between our Datacenter (where the CIFS is located) and remote locations (where DP’s resides) and after we bypass the traffic optimization for the IP’s concerned (CIFS + SCCM servers), a simple "Update Content" on affected packages results immediately in a (re-)provisionning of the content library on the DP’s.

This wasn’t a Configmgr SP1 related issue , but keep in mind when you implement WAN optimization solutions after you have implemented your configmgr 2012 environment.

I have investigated with Vincent Devos (enigineer from the company) . In the meantime we where out of ideas and therefore posted the 2 original forum questions to get additional help . You will find them here :

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/b5373b31-e594-4e1b-b6b9-ffecea05531e

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/a19a37ce-ffa5-41eb-b6f7-dba6f50894dc?prof=required

Hope it Helps ,

Kenny Buntinx

System Center Configuration Manager MVP

ConfigMgr 2012 SP1 : The 8dot3name settings are disabled on the volumes upon partitioning and formatting of the local disk.

8:59 am in adk, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, OSD, sccm, SCCM 2012, SCCM 2012 SP1, sccm RTM, WAIK by Kenny Buntinx [MVP]

 

Ever since we’ve been capturing our images with ConfigMgr 2012 SP1 we’ve noticed that 8dot3name creation is disabled on all volumes on the hard drive on the volume level when installing a machine with the same installation source as before (Windows 7 Enterprise SP1 x64). In our environment, we need this to be enabled for certain applications to work properly. ( Almost all Legacy XP Apps that work on Win7) . Nowhere is this change documented .

This wasn’t the case with ConfigMgr 2012 RTM , the difference there was that we where using WAIK instead of ADK.

I’ve been in discussions with the System Center Configuration Manager product team and received a response from them late yesterday.  They did, in fact, change the default behavior of the formatting tools in Windows 8. (ADK) 

They are working with them (ADK Team)  to figure out where/how this change was communicated, and to see how they can best communicate it more broadly.  In the meantime, They’ll continue working with them to figure out what our options are for resolving/working around this issue in Configmgr 2012 SP1.

Workarounds :

One option would be to create your own partitioning and formatting script and use that as a Run Command Line action instead of using there built-in Format and Partition Disk action.  I know that’s not elegant, but may be your best bet for now.

Here’s what the Windows imaging team had to say (with some additions/clarifications from me)…

Windows 8 does have 8.3 disabled on non-OS drives by default.  ImageX (and other Windows imaging tools) does preserve the same when capturing the image, and will apply as how the image was captured.  In the case where files with short file names are in a captured image, but the volume where the image will be applied has 8.3 disabled, WIMGAPI will enable 8.3 on the volume and set the short file names accordingly when the image is applied.

If they formatted a data volume using a Windows 8 format utility, short names would be disabled by default on the volume.  This is the default way format behaves.

How short names get enabled on the system volume is that setup explicitly turns them back on after formatting the system volume.  (i.e. if you’re applying an image and not running Setup, they won’t be turned back on automatically)

They can override this on the format command line with the following switch:  format x: /s:enable (where x: is the drive letter to format)  Unfortunately, you can’t add your own command line switches when using our built-in Format and Partition Disk action.

To manually enable 8.3 naming after formatting, you can use fsutil.exe from the command line:

                fsutil 8dot3name set x: 0 (where x: is the drive letter to enable 8.3 naming on)

This will enable short names on the given volume and it takes effect immediately.  (and yes, 0 does enable short names).  Unfortunately, fsutil.exe is not included in Windows PE, so you would have to copy it over to your boot media and run it with a Run Command Line action.

Hope it Helps,

Kenny Buntinx

MVP System Center Configuration Manager

How to create an application for deploying the App-V 5.0 Client with Configmgr 2012

9:09 pm in App-V, App-V 5.0, Application Model, AppV, CM12, ConfigMgr 2012 SP1, Deployment, deployment types, detection methods, Operating System Deployment, OSD, sccm, SCCM 2012 SP1, vbscript by Kenny Buntinx [MVP]

 

In this blog post we will show you how to create the application for deploying the App-V 5.0 client which is part of the MDOP ( Microsoft Desktop Optimization Pack )suite.

App-V 5.0 client is supported on the following platforms (As you can see , there is NO XP support) :

image

First we need to have a look on the exact prerequisites needed to run the App-V 5.0 client . You will find that kind of information here : http://technet.microsoft.com/en-us/library/jj713458.aspx

However the information on what version you need on the Microsoft Visual C++ is vague. We will clarify that below :

  1. Microsoft Windows .NET Framework 4 (Full Package) (http://www.microsoft.com/en-us/download/details.aspx?id=17718)
  2. Windows PowerShell 3.0 (http://www.microsoft.com/en-us/download/details.aspx?id=34595)
  3. Download and install KB2533623 (http://www.microsoft.com/en-us/download/details.aspx?id=26746)
  4. The Microsoft Visual C++ 2010 SP1 x64 Redistributable –> v10.0.40219 (http://go.microsoft.com/fwlink/?LinkId=268896)

image

  1. The Microsoft Visual C++ 2005 SP1 x86 Redistributable –> v8.0.61001 http://www.microsoft.com/en-us/download/details.aspx?id=26347

image

Now we need to create for each component an application . Lets start :

Windows .NET Framework 4 (Full Package)

Knipsel

Knipsel2

Knipsel3

Full installation code : dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT

Knipsel4

Create 2 detection methods as shown below

Knipsel5

Detection Method 1 : {8E34682C-8118-31F1-BC4C-98CD9675E1C2}

Knipsel6

Detection Method 2 : {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}

Windows PowerShell 3.0

31

Full installation code : c:\windows\System32\wusa.exe "Windows6.1-KB2506143-x64.msu" /quiet /norestart

32

Use a script as detection method :

33

Full detection script :

KB2533623 –> Apply hotfix in your base image or use CBS updates with offline updates

Microsoft Visual C++ 2010 SP1 –> Use download link specified above and use MSI detection methods

Microsoft Visual C++ 2005 SP1 –> Use download link specified above and use MSI detection methods

App-V 5.0 Client itself

When done , we going to create the App-V 5.0 Client Application . Deploy one of the following Windows Installer files to the target computer. The Windows Installer file you specify must match the configuration of the target computer.

  • If the target computer is running a 32-bit Microsoft Windows operating system, deploy the appv_client_MSI_x86.msi.
  • If the target computer is running a 64-bit Microsoft Windows operating system, deploy the appv_client_MSI_x64.msi.
  • If you are deploying the App-V 5.0 Remote Desktop Services client, deploy the appv_client_rds_MSI_x64.msi.

14

Create your application.

10

Create 2 deployment types : x64 and x86

11

For the X64 deployment type

13

Use the regular msi install parameters

15

Use the regular msi detection method

16

Now you must create dependencies . Make sure you select AUTO Install !

17

First create the Visual C++ 2005 SP1 x86 and select the deployment type you created earlier .

18

Then create a WMF 3.0 one and select the deployment type you created earlier .

19

Then create the Visual C++ 2010 SP1 x86 and select the deployment type you created earlier .

20

Then as the last one , create the Visual C++ 2010 SP1 x64 and select the deployment type you created earlier .

21

 

Your al set , your App-V 5.0 install is ready to be used .

Hope it Helps ,

Kenny Buntinx

Configmgr SP1 : Windows 7 deployment is not supported anymore from the setup.exe

8:10 pm in CM12, ConfigMgr 2012, ConfigMgr 2012 SP1, Operating System Deployment, OSD, SCCM 2012, SCCM 2012 SP1, System Center by Kenny Buntinx [MVP]

 

Windows 7 Setup.exe install is not supported ( but also VISTA , Windows Server 2008 / 2008 R2 )on ConfigMgr 2012 SP1.  With SP1, you need to use a WIM installation unless you’re installing Windows 8.  It was mentioned here :

http://technet.microsoft.com/en-us/library/jj591552.aspx#BKMK_WhatsNewSP1_Software

The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor.

If you want to use the Windows 7 install.wim, find some instructions here to make sure the OS ends up on drive C:

When doing build and capture for Windows 7, you will need to first import the Windows 7 install.wim, which can be found in the sources folder on the Windows 7 installation media.

clip_image001

Once you have imported the install.wim as an available Operating System Image package, then you can update the build and capture task sequence to use the image instead of Setup (in my screenshot, I’m using the Windows 8 install.wim, but Windows 7 works the same way).

clip_image002

Now with Windows 7, there are some additional considerations required to ensure the installed/captured image ends up on drive C: (because the Windows 7 install.wim was captured using drive D: originally).  You must add a Set Task Sequence Variable step before the Apply Operating System step that sets OSDPreserveDriveLetter=False.

clip_image003

Finally, you need to make sure that any partitions that come before the Windows partition are configured to not assign a drive letter.

clip_image004

This will ensure the Windows partition is assigned the first drive letter (C:) when the OS is booted.  Once the image has been captured, it will already have the Windows partition captured as drive C:, so none of these additional steps are needed when actually deploying the image.

Hope it Helps ,

Kenny Buntinx

Deploying a Windows 7 MUI machine based on a "Hybrid MUI image" within Configmgr 2012

7:48 am in ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr V.next, Deployment, deployment types, detection methods, MUI, OSD, sccm, SCCM 2012, SCCM 2012 SP1, SCCM v.Next, Windows 7, Windows 7 SP1, Windows7 by Kenny Buntinx [MVP]

 
This post and subsequent posts will be a step by step on how to build a Hybrid base Windows 7 ( yes , I know that everyone should rollout the new fancy Win 8 Winking smile ) image in Configmgr 2012 and use that image as a base to deploy it in your company. I will be outlining not necessarily pointing out every click. Hopefully others will find this helpful. This assumes an understanding of Configmgr 2012 and uses what is referred to as a “Hybrid Image Strategy”.

 

In this post I’m going to outline how to handle multiple languages in a Windows 7 Enterprise deployment. Windows 7 Enterprise comes natively as a MultiLanguage User Interface type OS to which you can add on Language Packs. A language pack allows user to change the interface display language of Windows’ dialog boxes, menus and other text to the selected language. You can download/install them in a few different ways.

They take a long time to install and in our scenario it’s better to integrate them into your hybrid base .WIM image.

For this example, we’re going to configure and capture an OS image with the Dutch language pack installed. The reason why we use the Windows 7 base OS in English is :

  • Scripting in native English language. This means creating one script for all workstations in the enterprise .
  • One Worldwide image per platform (x64 or x86) , otherwise we would deploy a windows 7 professional English , Dutch and French as a native OS , meaning 1 image per language
  • Windows security updates Patching could be limited to English , which will reduce time and effort to test/build everything .

    The first step is build the hybrid image and to get a copy of the Language pack you need; these are a little hard to get a hold of but it’s because of the licensing requirement. You can get  a copy of the language pack :

  • Through your Microsoft support via MVLS
  • The Windows 7 language packs are available via Windows Update as optional update.
  • Windows 7 SP1 MUI language packs are released as KB2483139. All language packs (MUI) of Windows 7 SP1 in DVD ISO format from MSDN and TechNet Subscriber Downloads.
  • For people who wants to download the MUI language packs for Windows 7 SP1 only from official source, here’s the direct download links for most of both 32-bit (x86) and 64-bit (x64) Windows 7 SP1 MUI language packs from Microsoft’s Windows Update server.

    Download Official 32-bit (x86) Windows 7 SP1 MUI Language Packs

    Arabic: windows6.1-kb2483139-x86-ar-sa_5add6e4a36127029d431ba98d99708c44ef9b53f.exe
    Bulgarian: windows6.1-kb2483139-x86-bg-bg_a8a5013e477366119cfdc5fbda43b904755db450.exe
    Chinese (Simplified): windows6.1-kb2483139-x86-zh-cn_ae61ea226215f96fc95be33201ffc96755ac7eb5.exe
    Chinese (Traditional): windows6.1-kb2483139-x86-zh-hk_411a6bb68728f12f5ced712d9a33fee9ebe0b0b3.exe
    Danish: windows6.1-kb2483139-x86-da-dk_67fecaab0a940e2e537bc8dcd8a9ebb8ab4ed102.exe
    Dutch: windows6.1-kb2483139-x86-nl-nl_b7e1c3046b218fb45a665ab5f5ed8a5ea8125760.exe
    English: windows6.1-kb2483139-x86-en-us_783d6dd59e2ec8fb0995a059c9c121795bde46c8.exe
    Finnish: windows6.1-kb2483139-x86-fi-fi_5259ca6a22a981dbdee352dde5b8e65c2fddd407.exe
    French: windows6.1-kb2483139-x86-fr-fr_f57427487dfc2f49da67cac22480ab1f48983d22.exe
    German: windows6.1-kb2483139-x86-de-de_acb9b88b96d432749ab63bd93423af054d23bf81.exe
    Italian: windows6.1-kb2483139-x86-it-it_1d54a8d0047674fc1b5b6f41292a0074d9fe3cc5.exe
    Japanese: windows6.1-kb2483139-x86-ja-jp_bc46078938ae9129c7ce86a9c176fa517e4c0a3d.exe
    Korean: windows6.1-kb2483139-x86-ko-kr_18f213428cc6fde96d8c76c6dd91446348e86ce6.exe
    Norwegian: windows6.1-kb2483139-x86-nb-no_5bd6fc76ad54b7a232d4ceb4a5f5c7c366bf90b6.exe
    Polish: windows6.1-kb2483139-x86-pl-pl_c460a8c1392d7f3d35d1c0b37e56017d3552d245.exe
    Portuguese (Brazil): windows6.1-kb2483139-x86-pt-br_6e1d337b2fd56669d461e82601aa51004fecbd24.exe
    Portuguese (Portugal): windows6.1-kb2483139-x86-pt-pt_5cc92ef98ed177b2f6bbae3a0420ee2f12764fab.exe
    Russian: windows6.1-kb2483139-x86-ru-ru_6532a8f36ad7d15277d5d60da92555f0fbee4daa.exe
    Spanish: windows6.1-kb2483139-x86-es-es_6aef75f7d83edaabc2a921a6b157cc7005628286.exe
    Swedish: windows6.1-kb2483139-x86-sv-se_bd65af75e8995bd865d93c8d8c8a35091499083f.exe

    Download Official 64-bit (x64) Windows 7 SP1 MUI Language Packs

    Arabic: windows6.1-kb2483139-x64-ar-sa_f07f2cc7b55b17076eebceea2c2c2826b08b8f63.exe
    Chinese (Simplified): windows6.1-kb2483139-x64-zh-cn_2c1884b4fdf6c8e91986369d88bbcaae01c6f187.exe
    Chinese (Traditional): windows6.1-kb2483139-x64-zh-hk_285282b1e2f750eeed91466918443b657968d977.exe
    Danish: windows6.1-kb2483139-x64-da-dk_d753d19cc1a0fe95aef21548193393c04a6a8024.exe
    Dutch: windows6.1-kb2483139-x64-nl-nl_12c90c70d408b08f51f500d6e974878a5d662398.exe
    English: windows6.1-kb2483139-x64-en-us_9b9c8a867baff2920507fbf1e1b4a158572b9b87.exe
    Finnish: windows6.1-kb2483139-x64-fi-fi_223465e1b382484d1d82f8f2ccfcd9ed2f902c76.exe
    French: windows6.1-kb2483139-x64-fr-fr_0f18e2a244dd9ff04664112a82776d2bd2177798.exe
    German: windows6.1-kb2483139-x64-de-de_4f4ce6bd38530b4a02199172863b21a0cba13773.exe
    Italian: windows6.1-kb2483139-x64-it-it_6d8223c065d6974d833d0eaa162f3ceb7680850f.exe
    Japanese: windows6.1-kb2483139-x64-ja-jp_aeaf7e9b0b6c2173bf757330017a7f655f1f8715.exe
    Korean: windows6.1-kb2483139-x64-ko-kr_0ea76f748e3d5309d568147ad1337b2664090944.exe
    Norwegian: windows6.1-kb2483139-x64-nb-no_78df68604970041a6337b4058a3e5339f79e50b4.exe
    Polish: windows6.1-kb2483139-x64-pl-pl_24d00a966a7a75132c3af5627634483d3e2d01e7.exe
    Portuguese (Brazil): windows6.1-kb2483139-x64-pt-br_f8035731c55d774c95c7c673aedfd42d52479294.exe
    Portuguese (Portugal): windows6.1-kb2483139-x64-pt-pt_78485491088298110a3e78b7a5f95e55ff7808df.exe
    Russian: windows6.1-kb2483139-x64-ru-ru_0587eb296a2f04e0d3699650d39b53ee18b97a79.exe
    Spanish: windows6.1-kb2483139-x64-es-es_fdbdf4061b960324efb9eedf7106df543ed8ce33.exe
    Swedish: windows6.1-kb2483139-x64-sv-se_81051fe3083afdb4f2d1d23752c587de9bb35025.exe

    With those language packs downloaded , we going to create a “Hybrid Base OS” task sequence which will build and capture a VM (Vmware, Xen or Hyper-V –> HAL independent) from a setup.exe Windows 7 SP1 enterprise setup files, and add the following components:

  • Create a great unattended xml file to automate . –> See also http://scug.be/sccm/2010/02/02/sccm-windows-7-deployments-amp-unattended-xml/
  • Create a few Task sequence variables to identify the machine and do some branding.
  • My MUI packs I want to integrate. I add my Dutch Language pack install. That will produce a hybrid .WIM with the language pack integrated.
  • Latest .NET Framework 3.5 SP1 and 4.0 . If you really want , .NET 4.5 should work as well
  • Windows Management Framework 3.0  = KB2506146 or KB2506143 ( Attention : There are few code defects but a toxic issue with using ConfigMgr 2012 RTM  – It is FIXED with ConfigMgr 2012 SP1 –> Only install if you have SP1 !! )
  • All the various Visual C++ Runtime Libraries (2005 SP1 , 2008 SP1, 2010 SP1 )
  • All the various Visual C++ Report Viewers (2005 SP1 , 2008 SP1, 2010 SP1 )
  • Internet explorer 9 ( or 10 when it releases for Windows 7 )
  • All current Patches
  • Optional : Office 2007 / 2010 / 2013 MUI . My advise is only to incorporate Office x if you only have one version of Office thru your Enterprise . Meaning Office ProPlus for everyone and no mix !

    The Task Sequence itself will look like this :

    1 (2)

  • 1) Import Windows 7 SP1 x64 enterprise as an Operating System Install Package and add it to a Distribution point.
  • 2) Create a Windows 7 SP1 x64 Unattend.xml package in Configmgr ( yes a package as there is no way to handle it as an application ) and add it to a Distribution point. An example of a good unattend.xml file could be found here : http://scug.be/sccm/2010/02/02/sccm-windows-7-deployments-amp-unattended-xml/

    Make sure you have the following lines adapted as shown below . It will help you later to build a great machine that will meet your language criteria .

  • 3) Create a package and Program for your Windows 7 SP1 MUI language packs. Create one for X64 and one for X86 (if you need to support 2 HW platforms). An example of a how to build the Windows 7 SP1 MUI language packs package could be found here :

     

  • 4) Create four (4) OSD collections and set your collection variables accordingly :

    200

    Define the following variables accordingly :

  • OSDInputLocale = EN-US
  • OSDSystemLocale = EN-US
  • OSDUILanguage = EN-US
  • OSDUILanguageFallback = EN-US
  • OSDUserLocale = EN-US
  • Capture = YES
  • OfficePreinstall = YES
  •  

    201image

     image image

     

  • 4) Create a “Build and capture” task sequence :

     

        • Name the task sequence something appropriate like “Build & Capture Windows 7 SP1 X64 Hybrid Image”
        • Select the x64 boot image
        • Create a “Disk Format and Partition” step and choose properties on the Default (Primary) partition and check the “Quick Format” option
        • Select the Operating System Package you created in step 1 and specify your unattend.xml file you created in step 2
        • Set the local admin password to blank ( needed for sysprep to work )
        • Join a Domain and use a domain join account for security reasons. An example of a how to create a domain join account could be found here : http://scug.be/sccm/2008/10/20/configmanager-osd-joining-machines-to-a-domain-and-its-security/
        • Select the ConfigMgr 2012 client that is already available in Configmgr 2012
        • Create a few Task sequence variables to identify the machine and do some branding. We will use that later to create our automatic  naming when we are capturing the image.
          • Set “OSDModel for VMware" when the following query is true “select * from Win32_ComputerSystem WHERE model like ‘%VMware%’ “

          300

          • Set OSDARCHITECTURE=”X64"

          302

          • Set OSDVERSION=”Windows 7"
          • Set OSDREVISION=”SP1

     

    2 (2)

     

        • Windows Management Framework 3.0  = KB2506146 or KB2506143 ( Attention : There are few code defects but a toxic issue with using ConfigMgr 2012 RTM  – It is FIXED with ConfigMgr 2012 SP1 –> Only install if you have SP1 !! )
        • All the various Visual C++ Runtime Libraries (2005 SP1 , 2008 SP1, 2010 SP1 )

    4

    3 (2)

     

        • Optional : Office 2007 / 2010 / 2013 MUI (Remember the task sequence variable we have set at collection level !)

    303

        • All current Patches –> setup SU
        • Set your image properties and Capture settings
        • Select a location to save the image and make sure you include the full path including the .wim extension

    Capture Without Office : (Remember the task sequence variable we have set at collection level !)

    304

    image

    Capture With Office : (Remember the task sequence variable we have set at collection level !)

    306

    image

        • Enter an account with rights to write to the share
        • Finish up

    5) Deploy your “Build and capture” task sequence to a VMware , XEN or Hyper-V VM : Look here how to do it for VMware : http://scug.be/sccm/2010/02/03/sccm-deploying-windows-7-on-a-vmware-esx-environment-howto/

    Create your deployments (advertisements) accordingly :

    402

     

    Stay tuned for Part 2 , where we will deploy the Hybrid image ( that we just created)  for full deployment..

    Hope it Helps

    Kenny Buntinx

    How to Install Windows 7 Language packs online during OSD Task Sequence (or in your Hybrid base image)

    7:27 am in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, language Packs, MUI, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, SCCM 2012 SP1, sccm2007, Task Sequence, Windows 7, Windows 7 SP1, Windows7 by Kenny Buntinx [MVP]

     

    Windows 7 language pack setup, lpksetup, includes parameters to support a managed installation.  I successfully tested the following from the command prompt:

    lpksetup.exe /i nl-NL /p . /r /s

    I created and advertised a program with this command line, but it quickly failed on a windows7 x64. 

    1

    The test system returned an error status message, ID 10003: “An error occurred while preparing to run the program for advertisement….  The operating system reported error 2147942402: The system cannot find the file specified.”

    Execmgr.log contained the following:

    File C:\Windows\SysWOW64\CCM\Cache\…\lpksetup.exe is not a valid executable file
    Invalid executable file lpksetup.exe

    It turns out that lpksetup.exe on Windows 7 64-bit is a 64-bit-only process so with WOW file redirection in a 32-bit process C:\Windows\System32 redirects to C:\Windows\SysWOW64, which does not contain lpksetup.exe.  So I altered the ConfigMgr program command line to:

    %WinDir%\SysNative\lpksetup.exe /i nl-NL /p . /r /s

    3

    Using the SysNative alias allowed the language pack to be successfully installed on Windows 7 64-bit from a ConfigMgr advertised program or Task Sequence.

    The Language Packs are installed successfully as i can choose the installed languages after the installation.

    I have got this valuable information from Aaron Czechhowski at http://blogs.technet.com/b/aaronczechowski/archive/2011/12/18/deploying-windows-7-language-packs-via-configmgr.aspx

    Hope it Helps ,

    Kenny Buntinx

    ConfigMgr 2012 SP1 Beta : Skipping Client prerequisites in the OSD “Setup windows and install Configmgr client” step.

    6:22 pm in CM12, ConfigMgr 2012, ConfigMgr 2012 SP1, Operating System Deployment, OSD, SCCM 2012, SCCM 2012 SP1, System Center, WES, WES 2009, WES2009 by Kenny Buntinx [MVP]

     

    Hi guys ,

    Working for a customer on managing WES 2009 Clients with Configmgr 2012 sp1 in TAP. On of the requirements by the customer was not to install Silverlight 5.0 or .net 4.0 onto the WES2009 Device as they did not manage or support their core image.

    The client prerequisites documentation can be found here on technet http://technet.microsoft.com/en-us/library/gg682042.aspx .

    Silverlight is not required, Software Center and Software Catalog are the only things that need it.  You can specify a commandline switch on ccmsetup to not install Silverlight.  Example: CCMSetup.exe /skipprereq: silverlight.exe but that only works to client push or manual install in RTM

    If my base image has .net 2.x installed and I don’t want install .net 3.0/3.5/4.0 because of lack of disk space – (image being build by another company and no possibility to adjust ) and app compatibility on the embedded, how can I use the */skipprereq* on the OSD “Setup windows and install Configmgr client” step ?

    GOOD NEWS ! They fixed that in SP1 . Now you are able to pass that “/SKIPPREREQ” parameter in your  OSD “Setup windows and install Configmgr client” step .

    Hope it Helps ,

    Kenny Buntinx

    Configuration Manager 2012: Select a Preferred Deployment when deploying via unknown computer support

    1:16 pm in CM12, ConfigMgr 2012, ConfigMgr V.next, OSD, PXE, sccm, SCCM 2012, SCCM v.Next, System Center, Task Sequence, V.next, Windows 7 by Kenny Buntinx [MVP]

    Hi there ,

    Today a customer requested an interesting scenario about selecting a preferred deployment when deploying multiple TS to a single collection:

    Scenario:

    You have made a few task sequences available thru PXE boot and enabled unknown computer support . You set all your deployments to available , not required.
    When you start your OSD deployment , you will see the few task sequences sitting there and waiting . This is a correct behavior.

    The customer likes to see the following behavior:

    – one of the task sequences made available will be started automatically after 30 seconds  if none of the other TS are selected.

    This will help them to avoid the import computer information part as they stage thousands of machines over one weekend and there process is that the computer name is generated from their CMDB tool after the mac address and serial number is scanned. Then we extract that information and push it into TS variables.

    Solution:

    You can define a deployment in a prestart command that overrides existing deployments to the destination computer. Use the SMSTSPreferredAdvertID task sequence variable to configure the task sequence to use the specific Offer ID that defines the conditions for the deployment.

    More interesting info on John Vintzels blog at http://blogs.technet.com/b/inside_osd/archive/2010/06/07/v-next-beta-1-feature-select-preferred-deployment-from-pre-execution-hook.aspx

    Hope it Helps ,

    Kenny Buntinx