Jamie's Blog

SCCM 2012 R2 OSD Deployment Run Task Sequence From Distribution Point

Problem
Unable to switch the deployment option to run from local distribution point

Solution

All the software included in the task sequence need to have the option enabled “copy the content in this package to a package share on distribution points”
an easy way to find which packages do not have this enabled is the SQL query below:

1. Find your PackageID number for the task squence

2. Login to sql and run the query against the sccm db

Declare @TaskSequenceID char(8); set @TaskSequenceID = '000CB'

and (128 & P.PkgFlags) <> 128 --the bitmask for the "Copy the content... option in the Package Data Access properties"

3. Enable the option: Copy the content in this package to a package share on distribution points

SCCM 2007 – Server 2012 and Windows 8 Support

Problem:
SCCM 2007 SP2 is not showing any Windows 8 or Windows Server 2012 updates in Software Updates.

Solution:

There are two fixes that need to be installed on the server:
http://www.microsoft.com/en-us/download/details.aspx?id=30747
http://support.microsoft.com/kb/2750782

Windows XP SATA ACHI Drivers For SCCM

Elitebook 8470p
Intel 7 Series Chipset Family SATA ACHI Controller
QUERY:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Elitebook%8470p%"

Elitebook 8460p

SCCM Use HTA To Set Task Sequence Variables

Problem:

I configured a task sequence to begin deployment of Windows 7 via USB thumb drives which are given to the techs. I wanted them to be able to install optional software at the time of deployment.

Solution:

UPDATED HTA FILE TO LATEST VERSION

Using Groups within the Task Sequences assigned variables gave me the best method of doing so. I created a front end HTA to allow the techs 1. set the PC name 2. add any additional software that the user might have had on their XP or replaced PC.

1.Mount current boot.wim file and then add HTA packages (if you dont already have HTA support)

Dism /image:c:\mountedwim /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\%Architecture%\WinPE_FPs\winpe-hta.cab”
Dism /image:c:\mountedwim /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\%Architecture%\WinPE_FPs\en-us\winpe-hta_en-us.cab”

2. Refresh/update boot image in SCCM

3. Configure Task Sequences to launch HTA

4. Configure groups with Task Sequence Variables

5. Configure HTA file
SCCMDeployments.hta.txt
(right click and save-as a text file and then rename to .hta once downloaded)
modify it to match your task sequence variables and the correct value it should be.
Keep in mind this will throw an error when not in the WinPE environment.

6. Deploy Image to USB Drive
No need to set variables on the Task sequence itself. When the image boots up and begins task sequence the HTA will run and prompt for check boxes and computer name value.

SCCM Resources

Guides:
http://ccmexec.com

Hotfixes:
http://www.mskbarticles.com/index.php?product=12769

SCCM Client Troubleshooter

This tool is extremely helpful for mass management of clients.

http://myitforum.com/cs2/blogs/gramsey/archive/2008/05/19/introducing-the-configmgr-client-troubleshooter.aspx

SMS_SITE_SQL_BACKUP Error – component SMS_SITE_COMPONENT_MANAGER on computer ‘SERVER’ reported: SMS Site Component Manager failed to reinstall this component on this site system

 Problem:

SCCM SP2 R3 was installed on a Server 2008 R2 box with its SQL 2008 R2 database on Server 2008 R2. Backups worked fine for a little while and then started to error out. The logs did not explain much.  I was getting the following in the event logs and in the SMS_SITE_SQL_BACKUP component:

“component SMS_SITE_COMPONENT_MANAGER on computer ‘SERVER’ reported:  SMS Site Component Manager failed to reinstall this component on this site system.”

 Resolution:

After doing some research it appears that after installing SP2 something gets messed up in the .\Microsoft Configuration Manager\install.map file.   We need to add the additional srvboot.exe line to the file. Please update the “333664” to match the byte size of your version.

BEGIN_COMPONENT_FILELIST
    <SMS_SITE_SQL_BACKUP>
    <1193>
    BEGIN_DIRECTORY
        <bin\i386>
        <9><X86><>
        FILE <smssqlbkup.exe><1><765280>
       FILE <srvboot.exe><0><333664>
    END_DIRECTORY
    BEGIN_DIRECTORY
        <bin\x64>
        <17><AMD64><>
        FILE <smssqlbkup.exe><1><1544048>
    END_DIRECTORY
    UNIT <SMS>
END_COMPONENT_FILELIST

Windows 7 Image Deployment with SCCM SP2 R2

1. Create Windows 7 Gold Image to your liking, installing all applications

2. Create unattend.xml file for initial audit phase using WAIK. The only setting I like to apply here is the CopyProfile=TRUE. This will enable whatever user’s profile that runs sysprep.exe to be copied to the Default User profile.

3. After configuring initial unattend file copy it to c:\windows\system32\sysprep\ folder and load up a command prompt. After the file has been placed there boot sysprep into audit mode with the generalize command. Without the generalize command the current user’s profile will not be copied to the default profile.

4. After it boots up into audit mode install any additional software, clean up temporary files, customize any other settings needed.

5. Once additional customizations are complete put sysprep into oobe mode. delete the orginal unattend.xml file as the new one will be pushed down with SMS. then run sysprep with sysprep.exe /oobe /generalize /shutdown. This will cause the system to shutdown after the sysprep is complete and then your ready to capture the image.

— WORK IN PROGRESS

Refresh All SCCM DPs With Latest Package

Refresh all Packages on a SCCM DP
I used this successfully in an environment with a primary and multiple secondaries.  Below are the instructions how it works and a few things that you will likely want to change to customize it.
 
Overview:
This is to be saved as a HTA file.  There are 3 fields for you to fill in:
 
SCCM Primary Site Code
SCCM Primary Server Name
SCCM Site Code (to Refresh)
These variables get passed to enable the connection to the primary and ultimatly the DP refresh.  The “SCCM Site Code” is the code for the site you wish to refresh.  For example if your primary is ABC and a secondary is 123 – ABC is the “SCCM Primary Site Code” and 123 would be the “SCCM Site Code”.  If 123 has multiple DP’s in the infrastructure design all of them will have their packages refreshed.

Customizations:
Replace LOGO.gif with your company’s logo
I use an images folder for LOGO.gif and winicon.ico

Refresh SCCM DPs

Thanks to Joshua Smueller of http://joshuasmueller.spaces.live.com/default.aspx for this HTA script.

Delete Orphaned Distribution Points From SCCM Packages

1. Backup the database.

2. Find the entries for the DP package share:

Select * from pkgservers where NALpath like ‘%\\Server%’
Select * from pkgstatus where pkgserver like ‘%\\Server%’
Select * from contentdpmap where serverpath like ‘%\\Server%’
Select * from DPinfo where servername like ‘%Server%’
3. Delete any entries from any of the above tables that point to the nonexistent share:

Delete from pkgservers where NALpath like ‘%COMPUTERNAME’ 
Delete from pkgstatus where pkgserver like ‘%Server%’
Delete from contentdpmap where serverpath like ‘%Server%’ 
Delete from DPinfo where servername like ‘%Server%’