You are browsing the archive for 2013 January.

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 : PowerShell Script to repair “Broken Applications after upgrading them from RTM”

7:52 pm in Application Model, applications, CM12, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, Deployment, deployment types, SCCM 2012, SCCM 2012 SP1, upgrade by Kenny Buntinx [MVP]

 

Upgrading a Configmgr 2012 RTM environment to a new SP1 environment . After the upgrade was successfully performed , suddenly all applications within my OSD task sequence start failing as described in my previous blog post here : http://scug.be/sccm/2013/01/08/configmgr-2012-sp1-broken-applications-after-upgrading-from-rtm/

Finally we have found some other errors as well , they are listed here :

  • The task sequence failed to install application Intel Management Engine 6.0.40.1215(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_2071f753-7604-42a5-b6be-b1b45c3c1f0a) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 615. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
  • The task sequence failed to install application NVIDIA Quadro/NVS Mobile Drivers 305.93(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_17e0153e-3d4f-467b-a2b3-68491516b0e1) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 580. The operating system reported error 580: An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.
  • The task sequence failed to install application Synaptics Touch Pad Driver(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_a0628bfc-3f06-4096-a001-c1a6c92675ea) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 16389. The operating system reported error 2: The system cannot find the file specified.

We found a workaround, you have simply to add a comment to each DT and it will update the content ID. Nevertheless, the change means that a redistribution of your application on all your DP’s.

BUT , that is all manual work , and we hate that , don’t we Smile with tongue out . Luckily we have an excellent PowerShell scripter in our team and all credits for creating this script goes to  Bart Serneels. He has written a PowerShell script to do all the work . He was happy to share this with you guys.

Here is the script : (replace VVM with your “Site Code” )

 

What the script will do is :

  1. Look for any application that has no deployment attached to it
  2. Opens the application deployment type(s) and looks for a description .
  3. If the description field is empty , it will update that field with the deployment type name.
  4. If the description field exists , it will make a backup , adapt it with the deployment type name , save it , reopen and revert to the backup descriptions and save it once more .

Again  , this is a workaround that helped us fixing our issues and no guarantee it will work for you .

Hope it Helps ,

Kenny Buntinx

MVP ConfigMgr

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

CM2012 SP1 – No default boot images available / "Only finalized boot images are supported"

7:57 am in adk, CM12, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, mcaffee, SCCM 2012, SCCM 2012 SP1, WAIK by Kenny Buntinx [MVP]

 

Issue : When you do a fresh install or you do an upgrade from Configmgr 2012 RTM to SP1 , you will see your install/upgrade failing with “No default boot images available” or "Only finalized boot images are supported" . The Configmgr setup log file will confirm that the migration/creation of boot images did not succeed.

Adding the boot images manual isn’t working neither. You will see the following error message :

clip_image001

 

Reason :  You have the following components running in your environment :

  • McAfee VirusScan Enterprise (VSE) 8.8 Patch 2
  • Microsoft Windows Assessment and Installation Kit (WAIK)
  • ADK (Assessment and Deployment Kit)
  • Microsoft Deployment Toolkit (MDT) 2012 / SP1
  • Microsoft Configuration Manager 2012 RTM / SP1

Solution :

Issue during upgrade from RTM to SP1 : If you find yourself in this situation where boot images didn’t get updated during site upgrade, you can manually update the boot images using the following instructions:

    1. Rename the boot.wim and the default boot wims in each architecture folder of the <smsinstall>OSD\boot\ folder – both the i386 and x64 to <wim>.bak
    2. Starting with the i386 folder first…Find the install folder of the ADK, which should be here if you installed with the defaults: “C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim”. You will need to copy the winpe.wim to the <smsinstall>OSD\boot\i386 folder. Rename it to boot.wim.
    3. You will also need to copy it again, but this time rename it so it matches the name of the default boot wim for the site – so it should look like boot.<packageid>.wim
    4. Update default boot image.
    5. Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID="<Image ID you see in the Console e.g. POL00001>" -> UpdateDefaultImage
    6. You will need to do this for the x64 folder as well. Do not do this for any custom boot images – this is just to update the default boot wims installed during setup of the site.

Before full install or upgrade :

Folders to exclude from AV scanning:

· Temporary folder for these cases is C:\Windows\TEMP\BootImages\{GUID}.  Exclude C:\Windows\TEMP\BootImages and subfolders.

· Temporary folder for offline servicing is <X:>\ConfigMgr_OfflineImageServicing and several subfolders used for different purposes – staging files, mounting OS, etc. – where <X:> is the StagingDrive value from the Offline Servicing Manager section of the site control file.  If this value is missing, we use the drive where the site is installed.  Exclude <X:>\ConfigMgr_OfflineImageServicing and subfolders.

Information from Mcaffee : KB: https://kc.mcafee.com/corporate/index?page=content&id=KB76867&actp=search&viewlocale=en_US&searchid=1357907921573

Product team Blog :

http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx

Hope it Helps ,

Kenny Buntinx

MVP System Center Configuration Manager 2012

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

Scug.be and MEET Belgium will be visiting the Microsoft Datacenter in Dublin

7:54 pm in dublin, MEET, msft by Kenny Buntinx [MVP]

 

Packing bags for the first time in 2013. Destination will be the Microsoft Datacenter in Dublin. Looking forward to it with some members of SCUG.be and MEET ( Check out http://microsoft.be/meet )

clip_image001

Fast facts about Microsoft’s Online, Live Services and Cloud Services:

  • Bing supports over 2 billion queries/month; Microsoft Business Productivity Online Suite hosts one million+ people on e-mail; and Windows Live ID processes more than 1 billion authentications per day.

Fast facts about the Dublin data centre:

  • The data centre – one of the largest construction projects in the Republic of Ireland over last 12 months – has taken approximately one million man-hours to complete and involved a workforce close to 2,100 at peak. The facility covers 303,000 square feet and can generate up to 5.4 megawatts of critical power, with the potential to expand to a total of 22.2 megawatts of critical power.
  • Making use of the low ambient air temperatures in Ireland, the facility uses ‘free air’ cooling almost exclusively. This means the operating environment can be maintained without mechanical or refrigerated cooling systems for over 95% of the time. Mechanical cooling typically represents ~38% of the power consumed in traditional data centres.
  • This cooling system eliminates the necessity for chilled water cooling systems, used in traditional data centres. This saves ~18 million litres of water each month.
  • The facility uses latest generation IT hardware, designed through tight collaboration with manufacturers to deliver the highest performance, lowest power consumption and least heat generation. These systems are shipped to the data centre preinstalled into server racks, resulting in substantial reductions in transportation and packaging overheads.

01_Microsoft%20Dublin%20Data%20Centre%20Entrance 

02_MicrosoftDublinDataCentreAerialView

 

Hope it Helps ,

Kenny Buntinx

How to sequence the Microsoft System Center 2012 Configuration Manager Admin Console with Microsoft App-V

6:28 am in App-V, App-V 5.0, AppV, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, SCCM 2012, SCCM 2012 SP1 by Kenny Buntinx [MVP]

 
Did you ever felt like sequencing your Configmgr 2012 console with App-V ? Somaning Turwale , a Support Engineer from Management and Security Division has written these steps on how to do this :

 

1. Follow the best practices for the Microsoft Application Virtualization Sequencer:

http://technet.microsoft.com/en-us/library/dd351420.aspx

2. Build your clean sequencing system with the 64-bit version of Windows 7 Service Pack 1 and join it to the domain. 

3. Install .NET 4 full version on the Sequencer machine (http://www.microsoft.com/en-us/download/details.aspx?id=17851).

4. Copy the Tools folder from your ConfigMgr 2012 central site server to the sequencing machine and place it in the following path:

C:\Program files\Microsoft Configuration Manager\Tools

NOTE This is used for sequencing ConfigMgr 2012 Version 5.00.7711.0000 and build 7711

5. Install the App-V 4.6 SP1 Sequencer with Hotfix 8 (http://support.microsoft.com/kb/2761558)

6. Launch the Microsoft Application Virtualization Sequencer and select Create New Virtual Application Package.

7. Select the Create Package (Default) option and click Next.  Note that Prepare the Computer for Creating a Virtual Package may give the Warning “Windows Defender is active”.  If so, launch the Services.msc snap-in and stop the Windows Defender service.  After doing so, click Refresh and then click Next.

7. Select the Standard Application (default) option and click Next.

8. On the Select Installer screen, browse to the Tools folder and select ConsoleSetup.exe, then click Next.

9. Name the package ConfigMgr2012Console, leave other options as the defaults and click Next.

10. Once the ConfigMgr installation screen appears, click Install Configuration Manager 2012 and click Next.

11. Type the FQDN of the Central Site server name and click Next.

12. Leave the Destination Folder as the default (e.g. C:\Program Files(x86)\Microsoft Configuration Manager Console\) and click Next.

13. Click Install and wait for the installation to complete, then click Finish.

14. Now the ConfigMgr 2012 console will launch. Verify that everything functions properly and exit from the console.

15. Select the I am finished installing option and click Next.

16. Select the ConfigMgr console and run it. After launching the console close it.  Click Next to review the installation report and click Next when you’re done.

17. Select the Customize option and click Next.

18. If you would like to remove the "Remote Control View" then right-click and remove it.

19. Click Next and then Run All. Once the console launches completely, verify the settings and exit the console.

20. Select the Target OS, click Next and then select Create the Package. The package will be saved as ConfigMgr2012Console.

21. Copy the package to the App-V management content share.

22. Follow the normal procedure to import the package into your App-V Management server.

23. Verify that the console is published to the App-V users.

24. Ensure that the .NET 4 full version is installed on the App-V clients as it is a prerequisite for console.

25. Make sure that the App-V clients have the latest hotfix installed (e.g. 4.6.1.30151).

26. Ensure that you have the required permissions and connectivity to the Site server.

If all steps are followed correctly then the client should be able to launch the Configuration Manager console successfully.

For the full article on how to sequence the console , please visit http://blogs.technet.com/b/appv/archive/2013/01/08/how-to-sequence-the-microsoft-system-center-2012-configuration-manager-admin-console-with-microsoft-app-v.aspx

Hope it Helps ,

Kenny Buntinx

Configmgr 2012 SP1 : Broken Applications after upgrading from RTM

10:45 am in a, Application Model, applications, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, SCCM 2012, SCCM 2012 SP1, upgrade by Kenny Buntinx [MVP]

Scenario : Upgrading a Configmgr 2012 RTM environment to a new SP1 environment . It was a standalone primary site RTM Build without any CU (5.00.7711.0000).

Issue : After the upgrade was successfully performed , suddenly all applications within my OSD task sequence start failing with the following error code :

The task sequence failed to install application Intel Management Engine 6.0.40.1215(ScopeId_67A221E3-64F0-47D4-AA5A-BB3729EC221F/Application_2071f753-7604-42a5-b6be-b1b45c3c1f0a) for action (Install HW Driver Applications for HP8540P) in the group () with exit code 615. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.

Identifying the cause:  After some checks, I saw that it concerned only applications and I discovered that had no ContentID associated to each Deployment Type. In other words, all the applications created and that are embedded in a TS with no direct deployments attached to the Application.  It appears that the upgrade process broke all applications.

Workaround :

We found a workaround, you have simply to add a comment to each DT and it will update the content ID. Nevertheless, the change means that a redistribution of your application on all your DP’s.

Hope it Helps ,

Kenny Buntinx

KB2688247: SQL Server cumulative updates must be manually installed on secondary System Center 2012 Configuration Manager sites that use SQL Server Express

10:21 am in ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr V.next, SCCM 2012, SCCM 2012 SP1, SQL, SQL Cluster, SQL Reporting services by Kenny Buntinx [MVP]

 

System Center 2012 Configuration Manager: The original RTM version of Microsoft System Center 2012 Configuration Manager installs Microsoft SQL Server Express 2008 R2 Service Pack 1 (SP1) when you deploy a new secondary site. The minimum supported SQL Server version is Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1 (SP1).

System Center 2012 Configuration Manager Service Pack 1:  System Center 2012 Configuration Manager SP1 requires Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1 (or SQL Server 2008 R2 SP2).

You must manually install the Cumulative Update for SQL Server 2008 R2 SP1 on the new secondary site after the site is installed. More information here : http://support.microsoft.com/kb/2688247

Hope it Helps ,

Kenny Buntinx