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

SQL Joins - INNER, OUTER, LEFT and RIGHT

Here is a simple post from Eswar explaining why and where to use SQL join. Please check the below link to view the post:

Writing SCCM Reports using SQL Joins

http://eskonr.com/2012/08/writing-sccm-reports-using-sql-joins/

For more detailed information on SQL joins, Check the below post by Suresh Dasari:

Joins in sql server, Inner Join, Cross Join, Left Outer Join, Equi join, Right Outer Join, Full Outer Join

http://www.aspdotnet-suresh.com/2011/12/different-types-of-joins-in-sql-server.html

Software Distribution is currently paused on this computer

   Today I came across a new issue while working on SCCM Task Sequence. The deployed softwares are not being received by the SCCM Client machine. My analysis on the issue and the solution with ref. links are given below for your reference.

The ConfigMgr Status Message Viewer showed the error stated below:

Message ID : 10038
System      : "MachineName"
Source       : SMS Client
Component : Software Distribution  Description: "The program for advertisement "ABCxxxxx" has not been run yet ("ABCyyyyy" - "App - Install"). Software Distribution is currently paused on this computer, and it has to be resumed before this program can begin."

Execmgr.log says "This program cannot run because a reboot is in progress or software distribution is paused."

RESOLUTION 1:
If Task Manager does not un-pause (resume) Software Distribution, then it will eventually get itself out of the paused state after 24 hours (probably it should).

RESOLUTION 2: 
Check the below snapshot and the registry keys:

For X86 machines: 

• HKEY_Local_Machine\Software\Microsoft\SMS\Mobile Client\Software Distribution\State\Pause

For X64 Machines:

• HKEY_Local_Machine\Software\Wow6432Node\Microsoft\SMS\Mobile Client\Software Distribution\State\Pause 

• HKLM\SOFTWARE\Microsoft\SMS\Task Sequence

On the right pane of the registry path, there might be some values that were not set to 0 again. Change the DWORD values for "Paused" and "Paused Cookie" from '1' to '0' and if possible restart the client.

You can try to stop/start the SMS Task Sequence Agent and then restart the SMS Agent Host, wait a couple of minutes and the Software Distribution will resume its process.

Please note that the task sequence resumed on the second snapshot but the detail states that it is failed which is due to a different error '183'. The discussion about the exit error code 183 is detailed here in my next post --> http://scorpits.blogspot.in/2013/01/task-sequence-reports-exit-error-code.html.

Ref.: http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/42114c0f-9de8-4a2c-9dac-1bac842b1d8a/

SCCM Client installation Troubleshooting steps Check list

We can find most of the SCCM value information on Eswar Koneti's blog.

A link to one such valuable post that helped me in maintaining a checklist for SCCM Client troubleshooting is given below. Please click the link to view the post.

SCCM Client installation Troubleshooting steps Check list
http://eskonr.com/2010/11/sccm-client-installation-troubleshooting-steps-check-list/

Scripting with Windows PowerShell

Want to learn about the Windows PowerShell command line and scripting environment? 

Microsoft Script Center focuses on teaching people on how to use Windows PowerShell and VBScript to reduce time spent performing mundane tasks.

Click on the below topics, and you will find training Videos, Guides, Wiki articles, and more that will help you learn Windows PowerShell.

• Script Center -- http://technet.microsoft.com/en-us/scriptcenter
• Webcasts from the Scripting Guys -- http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx

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 

Unable to create collection on SCCM 2007 / Logs not updating

Would like to share one of the weird issues we faced in our SCCM infra and their technet forum links with solution. Hope you all SCCM Folks will find it useful..

Unable to create any new collection on SCCM 2007
-- http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/1b38b94a-db80-4e48-bda1-94af825eb78e
 
One fine day at my office, ConfigMgr 2007 reported an error while trying to create any new collection.

Error Detail: “Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling ShowDialog.”

Click the below forum link for more details and resolution: 
http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/1b38b94a-db80-4e48-bda1-94af825eb78e
...
...
Troubleshooting the SCCM'07 Collections issue lead to a new problem due to a regedit step which was not reverted back after testing.

ConfigMgr 2007 Logs not updating
-- http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c9d2a699-e822-4249-b317-8873d7b56e9b
 
Site Reset and Site Repair did not help, and finally found that the Tracing was disabled in registry.

Check the below forum link for more details and resolution: 
http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c9d2a699-e822-4249-b317-8873d7b56e9b

Ref: http://social.technet.microsoft.com/Forums/en-US/user/threads?user=ucrajee

sms_def.mof

   In SMS/SCCM, we always hear about sms_def.mof and mof modifications. What really is that? Few days before, I googled on how to edit a .mof file and then found this article by Jeff Gilbert which i added to my bookmark. Hopefully this article will shine a little light on what the sms_def.mof file is and all the wondrous things it can do for you if you aren’t afraid to modify it. Here i reshare it:

   MOF stands for Management Object Format (MOF). The MOF standard defines how text files can be used to represent computer management information, objects that define computer management information, and related structures. SMS uses a file named sms_def.mof to coordinate client hardware inventory information queried from SMS clients. In other words, the sms_def.mof is a text file that tells SMS what computer information you’re looking for when you run a hardware inventory on a client. The file is stored in the \SMS\Inboxes\Clifiles.src\Hinv folder on the SMS site server.

   Out of the box SMS hardware inventory collects a lot of information about your client computers. Because it is really just a text file, you can edit the sms_def.mof using a text file editor like notepad. By reading through it you can see what is being collected and either increase or decrease the amount of information you would like to receive from your clients.

   The sms_def.mof starts with the definition of namespaces, base classes, and providers that are needed by the Hardware Inventory Agent and WMI. The rest of the file defines the classes that the Hardware Inventory Agent can collect data about. Each property and class has an SMS_Report flag. To include a property or class in the hardware inventory just set the report flag to true, to exclude a property or class form the inventory just set the flag to false. Be careful not to enable too much for SMS to inventory every time hardware inventory is run. Each time you modify the sms_def.mof you must first consider the impact on system and network performance.

   If the standard sms_def.mof doesn’t meet your reporting needs, you can also extend the SMS hardware inventory by defining additional classes for WMI to collect by adding new classes to the sms_def.mof file. Extending the sms_def.mof beyond the standard sms_def.mof shipped with SMS is beyond the scope of this article.

   Advanced Clients download new hardware inventory rules when Advanced Client policy is refreshed. By default, this is once per hour. Legacy Clients download new hardware inventory rules when their client refresh cycle is run. By default, this is once every 25 hours. When the clients have the new hardware inventory rules, the next hardware inventory is collected according to the modified sms_def.mof file, as long as it is syntactically correct. Otherwise, the previous version of sms_def.mof is used.

   So now you know the mystery of the sms_def.mof file everyone is always talking about. Once you’re comfortable modifying the standard sms_def.mof file, maybe even adding additional classes to inventory, you’ll be ready to tackle any reporting request your boss can throw at you— until then just tell them that you’re currently exploring the possibility of extending the WMI CIMv2\SMS namespace to include the Win32_LogEvent and evaluating the possible network and system performance impact that will cause...that usually sends them packing for a while.

Ref: http://www.myitforum.com/articles/1/view.asp?id=8629 - by Jeff Gilbert

For more information about the sms_def.mof file and how to modify it see the links below:

Customizing with MOF Files from the SMS 2003 Operations Guide:

http://www.microsoft.com/resources/documentation/sms/2003/all/opsguide/en-us/ops_6ewj.mspx
or                                                                            

For detailed information on “everything .mof” see Michael Schultz’s, MOF Editing Guide at:

http://myitforum.techtarget.com/articles/1/view.asp?id=2169

How to Assign Security Rights on SCCM

Today when i had to check and assign security rights for one of the user at my client place, i thought it would be better to share this on my blog. This has been explained well in technet under the title:

How to Assign Rights for Objects to Users and Groups - http://technet.microsoft.com/en-us/library/bb680648.aspx

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