You are browsing the archive for sccm RTM.

Detect, Inventory and report about the encryption method used by Bitlocker thru ConfigMgr

6:54 pm in bitlocker, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr 2012, configmgr 2012 R2, ConfigMgr 2012 R2 SP1, ConfigMgr 2012 SP1, ConfigMgr Dashboards, ConfigMgr SP2, Encryption, Inventory, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, sccm 2012 R2, SCCM 2012 R2, SCCM 2012 R2 SP1, SCCM 2012 SP1, SCCM Dashboards, sccm RTM, SCCM v.Next, sccm2007 by Kenny Buntinx [MVP]

 

Recently at a client, we needed to provide a report that was listing what Bitlocker Encryption strength method was used. That information had to be fed into the CMDB to make sure we had ‘256AES with Diffuser’ enabled.

Unfortunately, Configmgr 2012 does deliver out-of-the-box a way to determine what Bitlocker Encryption strength method, and that means the information is not in the registry or WMI.

Dependencies :

Well I tried to find an easy way , and the customer required a solution that was :

– Flexible and dynamic as they where constantly migrating from Mcafee Disk Encryption to Bitlocker and the CMDB had to be dynamically updated.

– Centrally managed code , meaning that if we needed to change anything to the code , it had to be intelligent enough to update it auto magically to all clients.

– Had to be reliable .

The solution :

– was to use a kind of detection powershell script for the Bitlocker Encryption strength using the standard powershell commandlet ‘Manage-bde’ .

– The script was to be used with a “compliance Item” and deployed thru a “Baseline” as one of my colleagues Henrik Hoe explains here :  http://blog.coretech.dk/heh/configuration-items-and-baselines-using-scripts-powershell-example/ . By using a CI , you will meet the centrally managed code part , but also the automatically way of updating the detection logic to all clients.

Forget about the old package/program way and then a way to execute the script on regular basis ( That can all be done thru the Baseline deployment)

– The script will be executed and will write a registry value BitlockerEncryptionStrenght = “TheActualValue”  and the baseline will report complaint when it has the ‘256AES with Diffuser’ detected. When the machine is not bitlockered at all , we will write a value  BitlockerEncryptionStrenght = “None”

$ErrorActionPreference="silentlycontinue" $StrBEncryption = "" $objBEncryption = "" $objBEncryption=manage-bde.exe -status |Where-Object{$_ -like "*encryption method*"} $arrBEncryption=$objBEncryption.Split(":") $StrBEncryption=$arrBEncryption[1].Trim() If ($StrBEncryption.Contains("AES")) { New-ItemProperty -Path HKLM:\SYSTEM\ABPosdInstall -Name BitlockerEncryptionStrenght -Value $StrBEncryption -Property String -Force -ErrorAction SilentlyContinue | Out-Null if ($StrBEncryption -eq "AES 256 with Diffuser") { return 1 } } Else { New-ItemProperty -Path HKLM:\SYSTEM\ABPosdInstall -Name BitlockerEncryptionStrenght -Value "None" -Property String -Force -ErrorAction SilentlyContinue | Out-Null Return 0 }

– We will pick the value up later with a custom registry key hardware inventory extension and use that in our reporting later on. For more details on how to do it : https://technet.microsoft.com/en-us/library/gg712290.aspx

Hope it Helps ,

Kenny Buntinx

Enterprise Client Management MVP

Configuration Manager 2012 OSD : Only import the Intel chipset drivers you really need for your brand/model !

6:31 pm in ConfigMgr 2007 R2, ConfigMgr 2012, configmgr 2012 R2, ConfigMgr 2012 SP1, ConfigMgr SP2, configmgr2007, Deployment, Drivers, Operating System Deployment, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, sccm 2012 R2, SCCM 2012 R2, SCCM 2012 SP1, sccm RTM, sccm2007 by Kenny Buntinx [MVP]

 

Yesterday I wrote a blogpost about the reason to keep your “Driver DB” and “driver packages” as clean as possible and that you do not need to import all the junk they provide in those so called “enterprise driver packages” for multiple models.

As a first tip for helping you accomplish that , we show you in this blog post how we can limit the number of *.inf files we need to import from Intel(R) Chipset Device Software . When downloading and extracting that Intel(R) Chipset Device Software package you will see that originally there are about  98 inf files present :

image

Now reduce the number of INF files :

Two override command switches for setup.exe from Intel(R) Chipset Device Software that will help us to reduce the *.inf files we need to import into our “Driver Package” :

-AONLY Extracts the needed INF files to install on the current system. If the install has been run once successfully, ‘-AONLY’ will not return any INFs when used in conjunction with ‘-OVERALL’ switch, all the needed INFs for the system will be extracted.

-P <Installation Path> Specifies the hard disk location to which the INF program files are copied. If this flag is not specified at the command line, the <Installation Path> directory is as follows: C:\Program Files\Intel\INFInst .

If this flag is used without the ‘-A’ option, only the Readme will be copied to <Installation Path>. The directory name can include spaces, but then a pair of double quotes (") must enclose the directory name. There should not be any space between the switch ‘-p’ and the directory name. This flag works in either Silent Mode or Interactive Mode.

Lets execute on the local brand/model that contains an intel chipset :

The result of running the setup with those parameters:

And then the result after running the tool on your local brand/model , you will see that the number of *.inf files are reduced to five (5) items ! isn’t that great ? Now copy those drivers to your regular driver import process and you reduced the number of bloat in your ConfigMgr driver database by 80% at least !

 

image

 

Hope it Helps ,

Kenny Buntinx

MVP enterprise Client Management

Configuration Manager 2012 and the need of keeping your Driver database lean and clean !

8:03 pm in CM12, CM12 R2, CM12 SP1, Deployment, Drivers, OSD, sccm, SCCM 2012, sccm 2012 R2, SCCM 2012 R2, SCCM 2012 SP1, sccm RTM, Task Sequence by Kenny Buntinx [MVP]

 

Hi ,

Lately we had an issue on a CM2012 R2  production environment when exporting a “task sequence” from our Acceptance environment and importing that exported “task sequence” into production , and ran into an error where our task sequence import would fail with out of memory message.

The exact message was : “System.OutOfMemoryException , Exception of type ‘System.OutOfMemoryException’ was thrown” as shown in the picture below:

clip_image002

Several people recommended me to increase the WMI memory allocation by doing this : http://anoopcnair.com/2011/05/06/configmgr-sccm-how-to-increase-wmi-default-memory-allocation/ . Anoop links to the “_providerhostquotaconfiguration” class in his article. Anoop’s advice is not uncommon, although supportability of the matter is questionable without PSS/CSS support , it’s a common test/fix giving on PSS/CSS calls related to slow or underperforming console issues.

My advice : DON’T DO THIS BLINDLY or without PSS/CSS support . You’d be crazy doing anything to WMI on a ConfigMgr production environment that you don’t understand the impact off. And if it’s to a component as critical as WMI is to ConfigMgr than you’d better do your homework before implementing it in production.

And this blog post explains what the impact is: http://blogs.technet.com/b/askperf/archive/2008/09/16/memory-and-handle-quotas-in-the-wmi-provider-service.aspx

We increased the WMI memory allocation with PSS support until 8Gb memory (Server having 16 Gb physical memory) , but no luck at all.

A little recap and issue definition:

  1. 1. We created a OSD Task sequence deployment in our acceptance environment.
    2. Once validated , we exported the TS without content (Content is located on a shared UNC storage path) but with dependencies.
    3. We tried to import the exported TS into production, the import fails both trough the GUI and via the powershell cmdlts. The import in production of the exported tasksequence fails with an out of memory error as shown in the screenshot above
    4. We tested both on the Primary site server itself as via remote console –> same result
    5. We have sufficient memory available on the server. I saw that the PowerShell session on the primary site server used up to 1.5Gb ram during the import. (memory was not maxed out (74% used))

Further investigation leads us to the size of the exported Task Sequence , which was about 235 Mb ( without content , go figure ! ) . Probably you would say : “What the hell did you put into that task sequence ????? ”. Well , the customer needs to support 55 different hardware models because of the way they need to buy there hardware. Crazy , I know and the fact is that they know that as well , however they can’t change this purchase behavior.

That being said , they have 55 HW driver packs and they have around 4800 drivers imported in there CM12 Driver DB .

After testing , we discovered that if the imported task sequence is more or less bigger then 135Mb in size , it will fail to import with the error displayed above. Once we lowered the number of drivers being referenced in the driver packages and therefore also in the CM12 driver database itself and the exported TS would be below 135mb in size , the import succeeded. However we could never pinpoint the exact size of the task sequence when it would fail as this was between 135 and 145 Mb.

What I recommend you to do:

  • One of the biggest mistakes customers make is to go the manufacturer website and grab every driver with those so called “enterprise driver packs” that contain drivers for multiple models…. Hell no , mostly the drivers are out dated, full of additional crap…
  • Use common sense and  only import drivers that are applicable to machines in your environment. I do not recommend that drivers are blindly imported into ConfigMgr where there is no actual benefit. This will just cause the database to bloat and the task sequences to become unwieldy. I recommend that any unused drivers/driver packages are removed from ConfigMgr
  • If you have a large number of Manufacturers and models or you run into conflicts, you can apply the driver package based on category or apply a specific package, especially when exporting / importing task sequences .
  • Typically graphic cards , Intel Vpro , Soundcard drivers or custom “hotkey” drivers are “bad” drivers. Those should be installed with applications from the setup.exe or msi.

To give you an idea , we went for a Lenovo C30 desktop model from +_ 400 drivers to 22 drivers. Keep it clean and tight . It will cost you more energy in the beginning , but will save you a lot of time when you need to debug. That’s the message I am trying to give you !

Hope it helps ,

Kenny Buntinx

MVP Enterprise Client Management

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