Search This Blog

Monday, July 28, 2014

Speed up loading the PXE boot image on SCCM 2012 R2

When loading the WINPE boot image with PXE from your distribution point, you might be able to speed up the boot time by increasing the TFTP block size.

In my test scenario the boot time was one minute faster after the change, and this is often a part of the OSD installation where we are actively waiting, so faster boot time are more than welcome.

On the Distribution point with PXE support find the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

Create a new DWORD value RamDiskTFTPBlockSize and use the values 4096, 8192 or 16384 depending on what gives you the best performance in tests.

Start with the value 16384 decimal.

image

image

After changing/adding the value restart Windows Deployment Services Server.

image

And then test to see if the boot time is faster.

image

Please note that you might find older hardware that wont work with larger TFTP block sizes, so test carefully.

Tuesday, July 22, 2014

.Net framework 4.5.2 installation fails

When running a silent installation of Microsoft .Net framework 4.5.2 in a SCCM 2012 R2 task sequence you might see the installation fail when using the application model.

The following is my silent installation command line "NDP452-KB2901907-x86-x64-AllOS-ENU.exe" /q /norestart and in my test scenario this is done on a Windows 2008 R2 server.

smsts.log include this information:

Install Static Applications failed, hr=0x80004005 InstallApplication 12-06-2014 10:14:53 1928 (0x0788)
Process completed with exit code 2147500037 TSManager 12-06-2014 10:14:53 1580 (0x062C)
Failed to run the action: Install .Net 4.5.2.
Unspecified error (Error: 80004005; Source: Windows) TSManager 12-06-2014 10:14:53 1580 (0x062C)

image

The log file "C:\Windows\Temp\dd_NDP452-KB2901907-x86-x64-AllOS-ENU_decompression_log.txt" gave this messages

[6/12/2014, 10:14:53] Error 0x80004005: Failed to extract all files out of box container #0.
[6/12/2014, 10:14:53] Error 0x80004005: Failed to extract
[6/12/2014, 10:14:53] Exiting with result code: 0x80004005

image

In this thread I found a possible solution, edit the properties of the Deployment Type and enabled “Run installation and uninstall program as 32-bit process on 64-bit clients.”

http://social.technet.microsoft.com/Forums/en-US/4808233e-1410-4305-a8d1-0e88f3a6fdc8/net-451-install-only-works-when-running-on-a-ui-session?forum=configmanagerapps

Setting this as shown allowed the installation to complete.

image

Tuesday, July 15, 2014

Start a scheduled SCCM 2012 site backup job manually

You might want to start a scheduled SCCM 2012 site backup job manually.

off course the Site Maintenance task Backup Site Server must be enabled and a valid backup path must be selected (UNC or local drive).

image

image

 

To start the scheduled backup job outside the scheduled time start services.msc 

image

 

And then start the service SMS_SITE_BACKUP

image

 

You are also able to start the task inside the console by using Monitoring tab > System Status > Component Status > Ribbon > Start > Configuration Manager Service Manager

image

Drill down to SMS_SITE_BACKUP and query the component.

image

Then start the component.

image

 

Regardless of the method you use, you can follow the backup in the log file smsbkup.log

image

Monday, July 7, 2014

MDT 2012 Boot Images fails after upgrading to SCCM 2012 R2

When you have task sequences that uses MDT 2012 boot images they will no longer work after upgrading SCCM to 2012 R2.

The boot image will boot as expected but the task sequence ends unexpectedly at Setup Windows and ConfigMgr.

In the SMSTS.log you might see the error:

Failed to resume task sequence (0x800700EA)

image

You will need to use the default boot images or create new MDT 2013 boot images, so that they are updated to version 6.3.9600.16384 (ADK 8.1).