Task Sequence reports exit error code 183

Every (mostly even) task sequence reports exit error code 183 if you advertise several task sequences to a SMS/SCCM client machine in Configuration Manager 2007.

The error normally appears in SCCM when you perform the below tasks:

1. You create several task sequences in SCCM 2007.
2. You advertise these task sequences to a SMS/SCCM clients. All advertisements are mandatory.
3. All advertisements are scheduled to run at the same time.
4. User notification is disabled in the properties of the advertised programs client agent.

Note that this problem does not occur when user notification is enabled.

When this problem occurs, information that resembles the following is logged in the execmgr.log file as:
1600 (0x0640) 19.12.2007 13:31:34 Program exit code 183
1600 (0x0640) 19.12.2007 13:31:34 Script for Package:J1000014, Program: * failed with exit code 183
1600 (0x0640) 19.12.2007 13:31:34 Execution is complete for program *. The exit code is 183, the execution status is FailureNonRetry 

Microsoft has confirmed that this is a problem in SCCM 2007, and the Article ID 946519 explains the scenario with a Hotfix and Workaround steps.

Hotfix:

You can download the hotfix @ http://support.microsoft.com/kb/946519

Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described above. Apply this hotfix only to systems that are experiencing this specific problem.

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart the computer after you apply this hotfix.

WORKAROUND-1

Enable user notification in the properties of the advertised programs client agent. To do this, follow these steps:

1. Open the Configuration Manager console.
2. In the console tree, expand Site Management, expand the node that corresponds to the current site, expand Site Settings, and then click Client Agents.
3. In the details pane, right-click Advertised Programs Client Agent, and then click Properties.
4. On the Notification tab, click to select Provide a countdown, and then click OK.

 

WORKAROUND-2

Use only one task sequence at a time :)

Ref.: http://support.microsoft.com/kb/946519

System Center Configuration Manager 2007 Toolkit V2

The Configuration Manager 2007 Toolkit V2 contains 11 downloadable tools to help you manage and troubleshoot Configuration Manager 2007. Click the below link to download the Toolkit.

ConfigMgrTool.msi - http://download.microsoft.com/download/5/5/0/55078AC4-3D15-407B-948E-CEB72A0A5A50/ConfigMgrTools.msi

1. Trace32 - A log viewer that provides a way to easily view and monitor log files created and updated by Configuration Manager 2007 clients and servers.
2. Client Spy -A tool that helps you troubleshoot issues related to software distribution, inventory, and software metering on Configuration Manager 2007 clients.
3. Delete Group Class Tool - A tool used to remove inventory group definitions along with history data, tables, views and stored procedures for the group.
4. Desired Configuration Management Migration Tool - A tool used to migrate from the DCM Solution for SMS 2003 to DCM in ConfigMgr 2007.
5. Desired Configuration Management Model Verification Tool - A tool used by desired configuration management content administrators for the validation and testing of configuration items and baselines authored externally from the Configuration Manager console.
6. Desired Configuration Management Substitution Variable Tool - A tool used by desired configuration management content administrators for authoring desired configuration management configuration items that use chained setting and object discovery.
7. Management Point Troubleshooter Tool - A tool that checks a computer system before and after a management point installation to ensure that the installation meets the requirements for management points.
8. Policy Spy - A policy viewer that helps you review and troubleshoot the policy system on Configuration Manager 2007 clients.
9. Preload Package Tool - A tool used to manually install compressed copies of package source files on Configuration Manager 2007 sites.
10. Security Configuration Wizard Template for Configuration Manager 2007 - The Security Configuration Wizard (SCW) is an attack-surface reduction tool for the Microsoft Windows Server 2008 R2 operating system. Security Configuration Wizard determines the minimum functionality required for a server's role or roles, and disables functionality that is not required. The Configuration Manager 2007 Service Pack 2 Security Configuration Wizard template supports new site system definitions and enables the required services and ports.
11. Send Schedule Tool - A tool used to trigger a schedule on a Client or trigger the evaluation of a specified DCM Baseline. You can trigger a schedule either locally or remotely.

 Ref: http://www.microsoft.com/en-us/download/details.aspx?id=9257 

Backup the SCCM Backup with AfterBackup.bat

It's always better and a preventive thought to Backup the Daily SMS/SCCM Backup, (keeping a daily copy on the server & mirroring the backups to an alternate server). I have seen people trying to add custom scripts in Scheduled tasks to copy/move the Backup data to a Remote server. But in the process of SCCM's daily backup (visible in smsbkup.log), there's an 'AfterBackup.bat' file used to perform post-backup actions automatically after the Backup Site Server maintenance task runs successfully. By default, the AfterBackup.bat batch file does not exist. To use it, you must first create the batch file and add commands.

To create the AfterBackup.bat batch file:

1. Prepare an ASCII file with commands that archive your backup snapshot, run a third-party archive tool, or perform any other post-backup tasks your site requires.
2. Name the file AfterBackup.bat, and save it in the *ConfigMgrInstallPath*\inboxes\smsbkup.box folder

Here is a simple script for 'AfterBackup.bat' written by 'Garth Jones', which saves 7 days backup to a folder named the day of the week, and also deletes/overwrites the older ones.

************************************************************************************************** 
REM @echo off

Setlocal enabledelayedexpansion

Set target=\\Destination_Servername\E$\Primary_SCCM_Backup\%date:~0,3%

If not exist %target% goto datacopy

RD %target% /s /q

:datacopy

xcopy "\\Source_Servername\SCCM_BackupPath\*" "%target%\" /E /-Y

***************************************************************************************************
where, *Source_Server is the Primary Server from which the backup has to be copied,
and *Destination_Server is the Remote Server where you want to copy the SiteBackup.

* You can also replace the word 'copy' to 'move' if you want to move the files instead of copy.
* You can also remove the part "\%date:~0,3%" from the script if you only require present day's backup. In my case we were running out of space on one backup server to save 7 days stuff, hence i removed that date part on the script.

[Although the intended use of AfterBackup.bat is to archive SMS backup snapshots, you can use that file for other tasks that you need to perform at the end of every back up operation, such as: 

• Run a SQL Server DBCC test to verify that there are no integrity problems with the SMS site database.
• Run a site health tool, or other health tools.]

Update: I have created a simple document with snapshots on how to implement the AfterBackup.bat script in your SCCM infrastructure. Click the below link to download the document for reference.

Backing up SCCM Backup - Download Link - https://sites.google.com/site/ucrajee/welcome/attachments/Backing%20up%20SCCM%20Backup.pdf?attredirects=0&d=1

Process Ref: http://technet.microsoft.com/en-us/library/cc180424.aspx
Script Ref: http://smsug.ca/blogs/garth_jones/archive/2011/01/13/afterbackup-bat.aspx

ConfigMgr 2012 Notes - Updated

Refer the below Links:

ConfigMgr (SCCM) 2012 – Starter kit: 
http://anoopmannur.wordpress.com/2011/08/10/configmgr-sccm-2012-starter-kit-very-useful-links/

What’s New in Configuration Manager:
http://technet.microsoft.com/en-us/library/gg699359.aspx
 
Frequently Asked Questions for Configuration Manager:

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

OS Deployment Guide for ConfigMgr 2007

  Here is a 160 pages of step-by-step instructions on how to successfully deploy Operating Systems with SCCM. Nico does a brilliant job of augmenting MS documentation, as well as clarifying all the acronyms associated with the product.

Dowload Link here - http://cid-18bc7bd65ad851b6.skydrive.live.com/self.aspx/Public/OSD%20in%20SCCM.pdf

Windows 7 Tips&Tricks

  I found this .pdf document which is created by 'Vasu Jain' on a google search, and would like to share the same with you all. This document has few tips & tricks that has not been told in any other documents i visited.

Thanks for the same Vasu.

http://windowsvj.com/wpblog/downloads/Windows 7 Tips & Trics [Vasu Jain].pdf

Ref: http://windowsvj.com/wpblog/downloads

ConfigMgr Patch Installer Tool/Script

   The ConfigMgr Patch Installer is a tool (vbscript) which can be used for installing updates which are advertised from SCCM. If the updates are advertised without a deadline. Especially it is useful for Windows Server 2008 Core edition as they do not have a GUI and so the updates can't be installed. This tool will query SCCM for each Update which is advertised to the System and will install it. The result can be displayed in a output logfile.

The Tool can be downloaded at:

• systemcentercentral.com - http://www.systemcentercentral.com/tabid/144/indexId/64192/Default.aspx

• winoneclick.com - http://www.winoneclick.com/

Ref: http://pleasepressanykey.blogspot.com/2010/08/configmgr-patch-installer.html