Archive | Configuration Manager 2012/2012R2 RSS for this section

SCCM 2012R2 Distribution Point Transfer/Setup Error: 0x80040154

While troubleshooting package transfer failures for a Distribution Point in a customer’s SCCM 2012R2 environment, I came across the following errors:

ExecStaticMethod failed (80040154) SMS_DistributionPoint, AddFile SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)
CSendFileAction::AddFile failed; 0x80040154 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)
Failed to add the file in content SKI00003.4. Error 0x80040154 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)
CSendFileAction::AddFileMetaData failed; 0x80040154 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)
CSendFileAction::SendFiles failed; 0x80040154 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)
CSendFileAction::SendContent failed; 0x80040154 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 2:18:13 a.m. 12632 (0x3158)


After researching the issues and checking installed components on the Distribution Point, I noticed that IIS had been manually configured and the RDC (Remote Differential Compression) feature wasn’t added to the server.


After installing this and triggering a distribution to this DP everything kicked into life.



Prepopulate Office 365 servers for Lync/Skype for Business Client

I’m currently working through a Lync cut-over for a customer to Office 365.  As they are moving from a single on-premise Lync 2010 server and didn’t wish to go the hybrid route, we are running through a cut-over process for users.  Ideally we would like to do this with no interruption to existing users (ie, updating DNS settings for all).  As such, would like to manually configure the test users to point directly to Office 365 Lync Online/Skype for Business – preferably with as little hands on as possible.  Thankfully, these settings can be configured in the registry.  These registry keys to set can be found:
under HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync.

2-10-2015 11-49-58 a-m- 2-10-2015 11-53-12 a-m- 2-10-2015 12-00-59 p-m- 2-10-2015 12-03-07 p-m-

I am packaging these settings into the installer for SCCM deployment but this could easily be adjust using a GPO, script, etc.

Remove “Unknown” computer from System Center Configuration 2012 R2 Manager PowerShell

Recently while testing out some task sequences with non-domain systems, I ended up with a bunch of “Unknown” computers in the Devices list in SCCM.  While I could filter this and remove it easily from the console, I wanted to set a task sequence to continually run through process while testing.

First, open PowerShell from Configuration Manager (to easily load the SCCM PowerShell Modules)

#Define your 3 character site code with this variable, in my example “ABC.”  I have defined the Site Code as I didn’t want the inherent x64 & x86 Unknown Computer Devices to be filtered from my results.  You could replace Unknown with another computer name, import a list via CSV, etc.

$sitecode = “ABC”
$devicename = “Unknown”
Get-CMDevice | Where-Object { ($_.SiteCode -ne $sitecode) -and ($_.Name -eq $devicename) } | Remove-CMDevice -force -confirm:$false


Note:  Please do this at your own risk – I’d suggest lab testing this first. 😉

Windows Deployment Services service will not start (Error 0x2740 )

Starting Windows Deployment Services on a recently assigned Distribution Point for System Center Configuration Manager, I received the following error in the Application Event log on the DP:

An error occurred while trying to create the UDP endpoint for WDSPXE provider on interface x.x.x.x:67. This can happen if the network interface was disabled or changed, or some other application is already using the port. The provider  will not be able to receive requests on this interface.

Error Information: 0x2740

This was because the DP was setup as a DHCP server and for WDS.  Unfortunately WDSUTIL /set-server /UseDHCPPorts:No did not work. The fix was to perform the following registry change:

Set the registry value to: UseDHCPPorts = 0

The service then started without any issues.

Note: Another thing to remember, is that if you are running your WDS server on your DHCP server, you will need to set the 060 option in your DHCP Server Options. From a command prompt run the following command:WDSUTIL /set-server /DHCPOption60:yes


System Center PXE/WDS “Processor Architecture Boot Image (0) not found”

When setting up a new System Center Distribution Point recently, I received the following error in the SMSPXE.log:

Warning: Matching Processor Architecture Boot Image (0) not found
This is because, even if you only using the x64 WinPE image, SCCM/WDS requires that both x64 & x86 to be present.  Simply distribute your x86 image from SCCM and restart the Windows Deployment Service on your Distribution Point.




WMI Model Query for System Center or MDT Task Sequence

In order to specify device driver install package for a specific model during your SCCM or MDT task sequence, you can create a WMI Query for the specific models covered by your driver pack. ie.
Select * From Win32_ComputerSystem WHERE Model LIKE “%HP%%600” or LIKE “%HP%%800”

To find the WMI specific model info, open command prompt and run the following commands:

In the above example, as I am running an HP Zbook 15, it would be Select * From Win32_ComputerSystem WHERE Model LIKE “%HP%%Zbook”

Offline Servicing DISM/WIM – SCCM PXE Deployment

Recently while testing an System Center Configuration Manager 2012 R2 PXE Deployment on a new HP Elitebook 840 or 850, I received the following error:
“Windows could not configure one or more system components.  To install Windows, restart the computer and then restart the installation.”
The reason for this is that the new hardware requires a later version of the Kernel Mode Driver Framework than is included with the Windows 7 install media.  The easiest fix for that is to download a copy of the updated Framework:  From there we can perform an offline servicing of the WIM image using the DISM command.

Dism /Get-WIMInfo /WimFile:D:\Software\OSImages\Windows_7_Ent_SP1_X64-KMDF1.11\Win7x64entSP1.wim
Dism /Mount-WIM /WimFile:D:\Software\OSImages\Windows_7_Ent_SP1_X64-KMDF1.11\Win7x64entSP1.wim /index:1 /MountDir:D:\Temp\offline
Dism /image:D:\Temp\offline /Add-Package /PackagePath:D:\Software\Patches\kmdf-1.11-Win-6.1-x64\
Finally: Dism /Unmount-WIM /MountDir:D:\Temp\offline /Commit.  Update your distribution points with updated WIM and re-run deployment to resolve.