Packages are not distributed to Child Sites

This behavior can occur because the Sms\Inboxes\Schedule.box\Uid folder is empty or does not exist or incorrect files in the \SMS\inboxes\schedule.box\UID folder can stop or inhibit communications

To resolve this behavior, you must open the Sms\Inboxes\Schedule.box\Uid folder and create two empty text files called nnnnnnnn.job and nnnnnnnn.req, where nnnnnnnn is the number in the filename, which is greater than any of the files' names that were already found in the directory SMS\Inboxes\Schedule.box (Guess what could be the greater name???? it took for me some time but finally the file name should be… ZZZZZZZZ …..I have mentioned below the process for how to do it)

How to do it:-

Stop the SMS Executive Service.

Verify that the \SMS\inboxes\schedule.box\UID folder exists. Create it if it does not.

Place two files in this folder. Because the scheduler processes jobs in a sequential fashion, you will want to create files that are at the end of the processing cycle. Name the first one ZZZZZZZZ.JOB and the other ZZZZZZZZ.REQ. 

Start the SMS Executive Service.

In some cases communications will be in stopped state, but there are two files already in the UID directory, Just delete them and adding the "Z" files.

Note:- Make sure there are 8 "Z"'s in the file name

~~~~~~~~~~

Enjoy

Delete all packages from Distrubution Point

Did you get ever a situation to delete all the Packages from one Specific DP ?

There are few tools/Scripts are available

-          ConfigMgr 2007 Distribution Point Package Utility

o   Can be downloaded from http://www.myitforum.com/inc/arts/12171Setup.zip

-          Vbscript I like this tool as it is very quick

o   http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-00-54-13-12/DPClean.zip

For SCCM 2012 http://gallery.technet.microsoft.com/scriptcenter/Remove-Packages-from-5031a1b5

'Rslaten 03/2005
'http://blogs.msdn.com/b/rslaten/archive/2006/03/01/removing-a-retired-dp-from-all-your-packages.aspx  
On Error Resume Next

WScript.Echo ""
WScript.Echo "SMSDPClean v1.3"
WScript.Echo "Usage: cscript.exe SMSDPClean  "
WScript.Echo "Example: cscript.exe SMSDPClean.vbs myCentralSiteServer myDistributionPoint"
WScript.Echo ""

Dim SMSSiteServer, SMSNameSpace, oLocator, oServices, bDone

'Get Args, add error checking here if needed
SMSSiteServer = WScript.Arguments(0)
DP = WScript.Arguments(1)

'Get SMS namespace
SMSNameSpace = GetSMSNameSpace(SMSSiteServer)

'Connect to SMS namespace
Set oLocator = CreateObject("WbemScripting.SWbemLocator")
Set oServices = oLocator.ConnectServer(SMSSiteServer, SMSNameSpace,,,,,128)
If Err.number <> 0 Then
    WScript.Echo "Error connecting to " &SMSNameSpace& " on " &SMSSiteServer& ": " &Err.Number
    Set oLocator = Nothing
    Set oServices = Nothing
    WScript.Quit
End If

'Call main procedure
PackageLoop

'Loop until async task is done
Do While not bDone
    WScript.Sleep 1000
Loop

Set oLocator = Nothing
Set oServices = Nothing
WScript.Quit


'Functions
'''''''''''''''''''''''''''''''''''''''''
'
'GetSMSNameSpace Function
'
'''''''''''''''''''''''''''''''''''''''''
Function GetSMSNameSpace(SiteServer)
    On Error Resume Next
    Dim colNameSpaceQuery, refitem, refWMI
    Set refWMI = GetObject("winMgmts:\\" &SiteServer&"\root\sms")
    If Err.number <> 0 Then
        WScript.Echo "Error connecting to SMS namespace on " &SiteServer
        WScript.Quit
    End If
    Set colNameSpaceQuery = refWMI.ExecQuery("select * from SMS_ProviderLocation")
    For Each refitem in colNameSpaceQuery
        GetSMSNameSpace = refitem.NamespacePath
    Next
    Set colNameSpaceQuery = Nothing
    Set refitem = Nothing
    Set refWMI = Nothing
End Function

'''''''''''''''''''''''''''''''''''''''''
'
'ValidDP Function
'
'''''''''''''''''''''''''''''''''''''''''
Function ValidDP(DP, SiteCode)
    On Error Resume Next
    Dim SysRes, start, finish, tempDP
    ValidDP = False
    Set SysRes = oServices.ExecQuery("select * from sms_sci_sysresuse where SiteCode = '" &SiteCode& "'")
    For each res in SysRes
        start = InStr(res.NALPath,"=\\") + 3
        finish = InStr(res.NALPath,"]MSWNET") - 2
        tempDP = mid(res.NALPath,start,finish-start)
        If (UCase(tempDP) = UCase(DP)) and (res.RoleName = "SMS Distribution Point") Then
            Set SysRes = Nothing
            ValidDP = True
            Exit Function
        End If
    Next
    Set SysRes = Nothing
End Function

'''''''''''''''''''''''''''''''''''''''''
'
'PackageLoop SubRoutine
'
'''''''''''''''''''''''''''''''''''''''''
Sub PackageLoop
    On Error Resume Next
    Dim sinkcol, retValuecol
    bDone = False
    Set sinkcol = wscript.CreateObject("WbemScripting.SWbemSink","SINKCOL_")
    retValuecol = oServices.ExecQueryAsync(sinkcol,"SELECT * FROM SMS_DistributionPoint")
    If Err.Number <> 0 Then
        WScript.Echo "Error running query:" &err.description
        WScript.Quit
    End If
End Sub
Sub SINKCOL_OnObjectReady(objDP, objAsyncContext)
    On Error Resume Next
    Dim start, finish, tempDP
    start = InStr(objDP.ServerNALPath,"=\\") + 3
    finish = InStr(objDP.ServerNALPath,"]MSWNET") - 2
    tempDP = mid(objDP.ServerNALPath,start,finish-start)
    If UCase(tempDP) = UCase(DP) Then
        WScript.Echo "Found " &DP& " on "& objDP.SiteCode& " linked to package " &objDP.PackageID
        If ValidDP(DP, objDP.SiteCode) Then
            WScript.Echo "Validated " &DP& " for site " &objDP.SiteCode
            objDP.Delete_()
            If Err.number <> 0 Then
                WScript.Echo "Failed to delete " &DP& " from package " &objDP.PackageID& " on site " &objDP.SiteCode
                WScript.Echo "Error = " &Err.number& " - " &Err.Description
            Else
                WScript.Echo "Successfully deleted " &DP& " from package " &objDP.PackageID& " on site " &objDP.SiteCode
            End If
        Else
            WScript.Echo DP& " is not specified as a distribution point on site " &objDP.SiteCode
        End If
    End If
End Sub
Sub SINKCOL_OnCompleted(iHResult, objErrorObject, objAsyncContext)
    bDone = True
End Sub

For a specific Advertisement status for last 3 Days…

---for a specific Advertisement status for last 3 Days… if we include the Set   @AdvName = '%' line then and remove the above line in red color will show for all advertisements with last 3 days status

-- To include all we need to give % in SQL this is a tip

Declare     @AdvName Varchar(256)
Set   @AdvName = 'Lync_2010_Full_Install'

---Set   @AdvName = '%'  
Select      adv.AdvertisementName
,    adv.AdvertisementID
,    s.Host
,    LastAcceptanceMessageIDName
,    LastAcceptanceStateName
,    LastAcceptanceStatusTime
,    LastStatusMessageIDName
,    LastStateName
,    LastStatusTime
,    LastExecutionResult
From  (
      Select      AdvertisementName
      ,    AdvertisementID
      From  dbo.v_AdvertisementInfo
      Where AdvertisementName Like @AdvName
      ) As  adv
Join  (
      Select      AdvertisementID
      ,    ResourceID
      ,    LastAcceptanceMessageIDName
      ,    LastAcceptanceStateName
      ,    LastAcceptanceStatusTime
      ,    LastStatusMessageIDName
      ,    LastStateName
      ,    LastStatusTime
      ,    LastExecutionResult
      From  dbo.v_ClientAdvertisementStatus
      Where LastStatusTime >= DateAdd(d,-3,GetDate())
      ) As  cas
On    adv.AdvertisementID = cas.AdvertisementID
Join  (
      Select      ResourceID
      ,    Netbios_Name0 As Host
      From  dbo.v_R_System
      Where Client0 = 1
      And  Active0 = 1
      And  Obsolete0 = 0   
      ) As  s
On    cas.ResourceID = s.ResourceID
Order By
      AdvertisementName
,    Host

To get ride of IIS Webdav issue

Most of the time some or other application extension would be blocked because of IIS Webdav Settings issue, to stop filtering in IIS Webdav we can change the

setting at the site level, i.e., open inetmgr/ IIS Console and chose the server name and in the right side we need to choose the “WebDav Authoring Rules” and in actions you will see “WebDAV  settings” click on the  button and you need to configure you Request filtering Behavior as below.

 

 

Okey, we may read in the blogs as we need to change in the applicationHost.config file.. if we do above settings it must be appear in the file… okey if you want to see the file how it looks like ……..

<requestFiltering>

                <fileExtensions allowUnlisted="true" applyToWebDAV="false">

                    <add fileExtension=".asa" allowed="true" />

                    <add fileExtension=".asax" allowed="true" />

                    <add fileExtension=".ascx" allowed="true" />

                    <add fileExtension=".master" allowed="true" />

                    <add fileExtension=".skin" allowed="true" />

                    <add fileExtension=".browser" allowed="true" />

                    <add fileExtension=".sitemap" allowed="true" />

                    <add fileExtension=".config" allowed="true" />

                    <add fileExtension=".cs" allowed="true" />

                    <add fileExtension=".csproj" allowed="true" />

                    <add fileExtension=".vb" allowed="true" />

                    <add fileExtension=".vbproj" allowed="true" />

                    <add fileExtension=".webinfo" allowed="true" />

                    <add fileExtension=".licx" allowed="true" />

                    <add fileExtension=".resx" allowed="true" />

                    <add fileExtension=".resources" allowed="true" />

                    <add fileExtension=".mdb" allowed="true" />

                    <add fileExtension=".vjsproj" allowed="true" />

                    <add fileExtension=".java" allowed="true" />

                    <add fileExtension=".jsl" allowed="true" />

                    <add fileExtension=".ldb" allowed="true" />

                    <add fileExtension=".dsdgm" allowed="true" />

                    <add fileExtension=".ssdgm" allowed="true" />

                    <add fileExtension=".lsad" allowed="true" />

                    <add fileExtension=".ssmap" allowed="true" />

                    <add fileExtension=".cd" allowed="true" />

                    <add fileExtension=".dsprototype" allowed="true" />

                    <add fileExtension=".lsaprototype" allowed="true" />

                    <add fileExtension=".sdm" allowed="true" />

                    <add fileExtension=".sdmDocument" allowed="true" />

                    <add fileExtension=".mdf" allowed="true" />

                    <add fileExtension=".ldf" allowed="true" />

                    <add fileExtension=".ad" allowed="true" />

                    <add fileExtension=".dd" allowed="true" />

                    <add fileExtension=".ldd" allowed="true" />

                    <add fileExtension=".sd" allowed="true" />

                    <add fileExtension=".adprototype" allowed="true" />

                    <add fileExtension=".lddprototype" allowed="true" />

                    <add fileExtension=".exclude" allowed="true" />

                    <add fileExtension=".refresh" allowed="true" />

                    <add fileExtension=".compiled" allowed="true" />

                    <add fileExtension=".msgx" allowed="true" />

                    <add fileExtension=".vsdisco" allowed="true" />

                    <add fileExtension=".exe" allowed="true" />

                    <add fileExtension=".vbs" allowed="true" />

                </fileExtensions>

                <verbs allowUnlisted="true" applyToWebDAV="false" />

                <hiddenSegments applyToWebDAV="false">

                    <add segment="web.config" />

                    <add segment="bin" />

                    <add segment="App_code" />

                    <add segment="App_GlobalResources" />

                    <add segment="App_LocalResources" />

                    <add segment="App_WebReferences" />

                    <add segment="App_Data" />

                    <add segment="App_Browsers" />

                </hiddenSegments>

            </requestFiltering>

"+" In AutoCAD files not able to Download at client side

This can be fixed with……….

 

investigated this and turns out this is an IIS request filtering issue with urls containing "+" character. Basically you get a 404.11 error since the url is double encoded. The following KB article presents a workaround to set "allowDoubleEscaping" to true. Note that by default this is disabled and you need to set this explicitly.

http://support.microsoft.com/default.aspx/kb/942076

After I enabled this I was able to download files from directories containing "+" character. Can you try this out and let me know if it resolves you issue.

 

To resolve this problem, follow these steps.
Note After you follow these steps, the security level of the server that is running IIS may be reduced. Therefore, before you set the allowDoubleEscaping property to True, consider the risk that is involved.

1. Click Start, type Notepad in the Start Search box, right-click Notepad in the Programs list, and then clickRun as administrator. If you are prompted for an administrator password or for a confirmation, type your password, or click Continue.
2. On the File menu, click Open, type %windir%\System32\inetsrv\config\applicationHost.config in the File name box, and then click Open.
3. In the ApplicationHost.config file, locate the requestFiltering XML element.
4. Change the value of the allowDoubleEscaping property to True. To do this, use code that resembles the following example code.

   <requestFiltering allowDoubleEscaping="true">
   

   
   
5. On the File menu, click Save.
   
6. Exit Notepad.

Important When you enable double escaped sequences, the security level of the server that is running IIS may be decreased.
The previous steps will directly edit the applicationHost.config file and configure this setting at the server level. You can also use the Appcmd command to configure this setting. To do this, follow these steps:

1. Click Start, click Run, and then type cmd in the Open box.
   
2. Type the following command, and then press ENTER:
   

   C: CD %windir%\system32\inetsrv

   
   
3. Run one of the following commands:
   
   
   
   • 
     

     Appcmd set config "Default Web Site" /section:system.webServer/Security/requestFiltering -allowDoubleEscaping:True

     
     

     Note This will configure this setting only for the "Default Web Site" by creating or editing the Web.config file in the root folder of the "Default Web Site."

     
     
   • 
     

     appcmd set config "Default Web Site" /section:system.webServer/Security/requestFiltering -allowDoubleEscaping:True /commit:appHost

     
     

     Note This will configure this setting only for the "Default Web Site" in the applicationHost.config file by using a location tag.

Pop-up to Postpone the advertisement or allow user to interact with advertisement

there was good Script from Jörgen Nilsson for Pop-up to Postpone the advertisement or allow user to interact with advertisement

http://ccmexec.com/2011/09/allow-the-user-to-postpone-installation-in-sccm/

Screenshots of how it will look at the client:

If the user press Cancel:

If the Process specified is running:

Usage:

• Download the script: http://ccmexec.com/wp-content/uploads/2011/09/Prerun1.txt
• Create a Package in SCCM containing the prerun1.vbs file
• Create a Program with a command line for executing the script, for example:
  “wscript.exe prerun1.vbs Excel Excel.exe”

Distribution Point Update Vs Refresh

Choose Between Updating and Refreshing a Package

Applies To: System Center Configuration Manager 2007 only

Updating and refreshing Microsoft System Center Configuration Manager 2007 packages are two different operations. Use the following table to help decide when to update and when to refresh a package.

 

Criterion	Package Update	Package Refresh
Use when	You make a modification to the package source, such as adding, changing, or deleting a file or folder.	You need to repair a package at a specific distribution point.
What it does	Builds a new, complete, compressed package file and a delta compressed package file from the updated package source files. The delta file is passed to all distribution points.	Recopies the compressed package from the local site server to the distribution point but does not copy files from the package source.
Resets access control list (ACL)?	No.	Yes, if you have made changes to the Package Access Accounts.
Resets the Virtual Directory?	Yes, if you have enabled or disabled BITS on the distribution point since the last package update.	Yes, if you have enabled or disabled BITS on the distribution point since the last package refresh.
Updates the package source version?	Yes.	No.
Increments package version in client policy?	Yes.	No.

Manage DP wizard ==>using Refresh the package?--Delete and recreate the package ,does not change source version.

right click Update ==>Distribution Point -Change source version and copy the changed source.(Delta change)

 

 

more ==>http://technet.microsoft.com/en-us/library/bb892806.aspx

SCCM: Content Download to Cache Issues – 2008 / 2008 r2 / IIS 7 and IIS 7.5 and Webdav Issues

Issue

The issue that was reported to me was that the content was not downloading. My datatransferservice.log, my CAS.log, and ContentTransferManager.log all looked good. The client found a local DP to download the content from. However when I looked at my cache folder, I saw that only a couple of MB of data was downloaded and it never increased in size.

 

BITS was the culprit here !!!

 

In order to see what jobs are currently downloading, type in:

bitsadmin /list /allusers

This will give you output similar to the following:

BITSADMIN version 3.0 [ 7.5.7600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

{19A1D938-E1E9-437F-882E-1BFAABB707CB} ‘CCMDTS Job’ ERROR 146 / 3805 4752558 / UNKNOWN
Listed 1 job(s).

Notice how in this picture I have the following line:

{19A1D938-E1E9-437F-882E-1BFAABB707CB} ‘CCMDTS Job’ ERROR 146 / 3805 4752558 / UNKNOWN

This is no good. This basically means there’s an error somewhere in the transfer job.

Before we get into the next step of the solution, you must first understand what an SCCM distribution point is. An SCCM DP is simply a glorified web server. If you look at the Datatransferservice.log file on any of your SCCM clients, you’ll see a lot of URLs that look like the following:

http://DOMAIN:80/SMS_DP_SMSPKGF$/CEN00119/System32/Redist/MS/System/msvcrt.dll

What your client is basically doing is grabbing the files from these URLs and storing them into your local cache directory underneath the package ID.

So back to BITS. Since we saw an error in our bitsadmin /list /allusers, we need to find out exactly what that error is. The following command will show just that:

bitsadmin /info {19A1D938-E1E9-437F-882E-1BFAABB707CB} /verbose > c:bits2.txt

So what this command is doing is giving us the information about the failed BITS job that we saw before. The verbose command gives us the status of each file in the job. We then pipe this out to a file. Inside of that file, we see the following:

BITSADMIN version 3.0 [ 7.5.7600 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.

BITSAdmin is deprecated and is not guaranteed to be available in future versions of Windows.
Administrative tools for the BITS service are now provided by BITS PowerShell cmdlets.

GUID: {19A1D938-E1E9-437F-882E-1BFAABB707CB} DISPLAY: ‘CCMDTS Job’
TYPE: DOWNLOAD STATE: ERROR OWNER: NT AUTHORITYSYSTEM
PRIORITY: LOW FILES: 146 / 3805 BYTES: 4752558 / UNKNOWN
CREATION TIME: 5/12/2010 11:31:04 AM MODIFICATION TIME: 5/12/2010 11:33:18 AM
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: REGISTERED NOTIFICATION FLAGS: 11
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 2419200 ERROR COUNT: 147
PROXY USAGE: NO_PROXY PROXY LIST: NULL PROXY BYPASS LIST: NULL
ERROR FILE:    http://DOMAIN:80/SMS_DP_SMSPKGF$/CEN00119/Program Files/Hummingbird/Connectivity/9.00/HostExplorer/SDK/Samples/OHIO/Visual C++ Samples/HEOhioSample/MyTabCtrl.cpp -> C:Windowssystem32CCMCacheCEN00119.1.SystemProgram Files/Hummingbird/Connectivity/9.00/HostExplorer/SDK/Samples/OHIO/Visual C++ Samples/HEOhioSample/MyTabCtrl.cpp
ERROR CODE:    0×80190194 – HTTP status 404: The requested URL does not exist on the server.

ERROR CONTEXT: 0×00000005 – The error occurred while the remote file was being processed.

DESCRIPTION:
JOB FILES:

 

also check for Client side BITS Policy settings

Advertisement status tracking

How to read the advertisement reports:-

Accepted – Software can be installed in few mins, as it will start downloading the software from remote /local system

No Status - Systems are not online or has issue with SMS Agent, or not received the policy, if the system is online then this status must change in one hour time (if the status not changed then you may

     Suspect the issue with SMS / SCCM agent )

Accepted - No Further Status – Back end installation may be running and need to wait for some time to get the actual status

Failed – Software installation failed, you need to re push once again this advertisement.

Succeeded – Software installed successfully without any issues

Package not downloading due to some IIS File filtering blocking issue

Check with these commands

 

 

BITSADMIN /LIST /ALLUSERS

 

C:\>BITSADMIN /geterror {7D46DE5B-3911-40B1-A72B-607737DB06F9}

BITSADMIN version 2.0 [ 6.6.3790.3959 ]
BITS administration utility.
(C) Copyright 2000-2004 Microsoft Corp.

ERROR FILE:    http://sccmserver.mydomain:80/SMS_DP_SMSPKGD$/SMSPKG/HCC00
05F/AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm -> C:\WINDOWS\system32\CCM\Cache\HCC0005F.1.System\AdminImage/x86/en-us/acad/Acad/Program Files/Root/HelpHtml/contexthelp/+CONSTRAINTSETTINGS.htm
ERROR CODE:    0x80190194 - The requested URL is not found on this server.
ERROR CONTEXT: 0x00000005 - When processing the remote file error has occurred

/LISTFILES job                     Lists the files in the job
/SUSPEND job                       Suspends the job
/RESUME job                        Resumes the job
/CANCEL job                        Cancels the job
/COMPLETE job                      Completes the job

 

BITSADMIN /INFO job [/VERBOSE]

BITSADMIN /geterror {B2826EF6-C78B-4D1C-A386-94D0D36DC107}

BITSADMIN /LIST /ALLUSERS

 

Where job =

{B2826EF6-C78B-4D1C-A386-94D0D36DC107}

Software Distribution Flow

Software Distribution Flowcharts

Software Distribution Flowcharts

Software distribution is the SMS feature that you use to automate software installation in your site. You can also use software distribution to open applications or run commands on targeted clients.

Several steps are required to distribute software. You must create packages and then target those packages to client computers in your site. You target and schedule the packages by using advertisements. Several SMS components assist in the software distribution process. Two components that work exclusively with software distribution are Distribution Manager and Courier Sender.

This chapter contains the site server software distribution flowcharts and includes two process flowcharts and two component flowcharts as follows:

· Advertisements 

· Package Creation and Distribution 

· Distribution Manager 

· Courier Sender 

Advertisements

The Advertisements flowchart illustrates the processing that occurs when an administrator uses the SMS Administrator console to create an advertisement for software distribution. This processing includes preparing the advertisement, lookup, and installation files, placing these files in the appropriate inbox directories on the site server, and copying the advertisement files to the appropriate CAPs.

If the advertisement is targeted to a child site, the processing also involves creating the outbound advertisement file, which is then processed as described in the Package Creation and Distribution flowchart.

The activity illustrated in this flowchart takes place on the site server.

Tracing Information

You can trace the activity that occurs in this flowchart by studying the status messages and optional log files for the server components listed in the following table. You can view status messages, or you can enable the log files for the server components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about how to access status messages for a specific component and how to enable logging,

Table Status Message Components and Log Files for Advertisements

Server components	Log files
SMS Provider	SMS\Logs\SMSprov.log
Offer Manager	SMS\Logs\Offermgr.log
SMS SQL Monitor	SMS\Logs\SMSdbmon.log
Distribution Manager	SMS\Logs\Distmgr.log
Inbox Manager	SMS\Logs\Inboxmgr.log

Note The term "offer" in the component name Offer Manager and in the directory name Offerinf.box refers to advertisements.

Troubleshooting Tips

If advertisement status shows that no advertisement has been sent to clients:

· Verify that the target collection you specified for the advertisement contains clients. Until valid clients are present in the target collection, no client instruction files for the advertisement are written to the client access point (CAP). 

· Check to see if the package associated with the advertisement contains source files. If it does, examine the package status to determine if the package has been installed on its specified distribution points. The package will not be advertised until the files are available on at least one distribution point within the site. 

If the package source files have not been installed on the distribution points:

· Verify that at least one distribution point has been specified for the advertised program. At least one distribution point must be specified for each site in which clients will receive the advertisement.

· Check the Inboxmgr.log file to determine whether Inbox Manager can connect to all of the CAPs and copy the advertisement, package, and program files. Inbox Manager must have access to the CAP in order to replicate the information from the site server. Clients access the CAP to check for advertisements. 

·

If the advertisement has not been made available to Inbox Manager:

· Check for the existence of the <ObjectID>.ofr file in the SMS\Inboxes\Offerinf.box directory on the site server.

· Verify that the <ObjectID>.ins file and several lookup (.lkp) files have been created in the SMS\Inboxes\Offerinf.box directory on the site server. Inbox Manager begins its part of the process when these files appear in the Offerinf.box. 

If a program you have advertised is not installed on the target clients:

· Check the status reported for the advertisement in Advertisement Status under System Status in the SMS Administrator console.

Package Creation and Distribution

The Package Creation and Distribution flowchart illustrates the processing that occurs when an administrator creates a package for software distribution. This processing includes creating required files (including compressed source files, if compression is specified in the package definition), and placing them in the appropriate directories on the site server, distribution points, and CAPs.

If the package is targeted to a child site, Package Creation and Distribution also includes additional tasks. These include replicating the package files to the child site, decompressing them, and copying them to the appropriate locations on the child site.

The activity illustrated in this flowchart takes place on the site servers at the originating site and the child site.

Tracing Information

You can trace the activity that occurs in this flowchart by studying the status messages and optional log files for the server components listed in the following tables. You can view status messages or you can enable the log files for the server components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about how to access status messages for a specific component and how to enable logging, see "Status Messages Versus Logging" in Chapter 16, "Introducing the SMS 2.0 Flowcharts."

Table 21.2 Status Message Components and Log Files at Originating Site Server for Package Creation and Distribution

Server components	Log files
SMS Administrator via SMS Provider	SMS\Logs\SMSprov.log
SMS SQL Monitor	SMS\Logs\SMSdbmon.log
Distribution Manager	SMS\Logs\Distmgr.log
Inbox Manager	SMS\Logs\Inboxmgr.log
Replication Manager	SMS\Logs\Replmgr.log
Scheduler	SMS\Logs\Sched.log
Sender	SMS\Logs\Sender.log

Table 21.3 Status Message Components and Log Files at Child Site Server for Package Creation and Distribution

Server components	Log files
Despooler	SMS\Logs\Despool.log
Distribution Manager	SMS\Logs\Distmgr.log
Replication Manager	SMS\Logs\Replmgr.log
Inbox Manager	SMS\Logs\Inboxmgr.log

You can view status messages generated during the steps in this flowchart using the SMS Administrator console. To view these messages, navigate to Component Status for the individual component.

Systems Management Server

· Site Database (site code - site name)

· System Status

· Site Status

· site code - site name

· Component Status

You can also view status messages that are generated in the installation, update, and removal of packages on distribution points in the SMS Administrator console. To view these messages, navigate to Package Status.

Systems Management Server

· Site Database (site code - site name)

· System Status

· Package Status

Troubleshooting Tips

If a package created at a parent site does not appear at child sites:

· Check the Distribution Manager status messages or the Distmgr.log file to determine whether Distribution Manager was able to retrieve the source files and successfully compress them.

· Verify that the package's *.rpt files have been placed in the SMS\Inboxes\Replmgr.box\Outbound\<SiteCode> directory. 

· Verify that Replication Manager created a mini-job to send the compressed package to the destination child site. The mini-job should appear in the SMS\Inboxes\Schedule.box directory. 

Also, check whether Replication Manager has files queued to send to the destination child site. If it has, the package mini-job will be appended to the queue. The priority of the entire queue is set at the priority (high, medium, or low) of the item in the queue that has the highest priority. 

· If the package contains source files, verify that at least one distribution point in the child site is specified. 

· Verify that Sender has renamed the *.srq (send request file) to an *.srs file and moved it to the SMS\Inboxes\Despoolr\Receive directory on the child site. If this has not occurred, verify the file permissions at the destination site for the SMS Service Account. Also verify the network connectivity between the two sites. 

· Verify that Distribution Manager on the child site successfully copied all of the files to the appropriate distribution points. 

If the package has arrived at the child site but is not available for advertisements:

· Verify that Replication Manager has successfully moved the package files to the SMS\Inboxes\Distmgr\Incoming directory on the child site. 

· Verify that Despooler could read the package instruction file and decompress the package source files. You can find this information in the Despool.log file. 

· Verify that the decompressed versions of the source files (*.rpl, *.rpt, and *.pkg) are on the SMSpkgx directory of the child site server. 

· Verify that Distribution Manager on the child site updated the SMS site database (if the child site is a primary site) and placed the package objects in the correct inboxes (SMS\Inboxes\Offerinf.box and SMS\Inboxes\Pkginfo.box) for Inbox Manager to distribute. 

Distribution Manager

Distribution Manager is an SMS thread component that facilitates software distribution by compressing and decompressing package source files, placing packages on distribution points, and directing Inbox Manager to copy program definitions and current server lists to CAPs. Distribution Manager also manages the replication of package definition files and package source files to child sites.

The activity illustrated in this flowchart takes place on the site server as Distribution Manager performs these tasks.

Tracing Information

You can trace the activity that occurs in this flowchart by studying the status messages and optional log files for the server components listed in the following table. You can view the status messages or you can enable the log files for the server components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about how to access status messages for a specific component and how to enable logging, see "Status Messages Versus Logging" in Chapter 16, "Introducing the SMS 2.0 Flowcharts."

Table 21.4 Status Message Components and Log Files for Distribution Manager

Server components	Log files
Despooler	SMS\Logs\Despool.log
Distribution Manager	SMS\Logs\Distmgr.log
Replication Manager	SMS\Logs\Replmgr.log
Inbox Manager	SMS\Logs\Inboxmgr.log

Troubleshooting Tips

If a package created in the SMS Administrator console does not appear at the client access point (CAP):

· Verify that the SMS SQL Monitor service is running and has access to the SMS site database. When a package is created in the SMS Administrator console, it must be written to the SMS site database before it can be distributed. 

· Verify that a directory change notification file has been written to the Distribution Manager Inbox in the \\<SiteServer>\SMS\Inboxes\Distmgr.box directory. After the package has been written to the SMS site database, the SMS SQL Monitor service must generate the directory change notification file and place it in this directory so that Distribution Manager can process the package. 

· If the package uses source files, verify that Distribution Manager can connect to the source directory.

· If the package does not use source files, verify that Distribution Manager has written the package files (*.pkg, *.nal, and *.ico) to the \\<SiteServer>\SMS\Inboxes\Pkginfo.Box directory. 

If a package that is configured to use and compress source files fails to appear at the CAP:

· Verify that Distribution Manager has compressed the package and written the compressed file to the \\<SiteServer>\SMS\Inboxes\Pkginfo.box directory. Distribution Manager writes files to the TMP directory that it creates on the site server and compression can fail if there is insufficient disk space. 

· Verify that the \\<SiteServer>\SMSpkg<DriveLetter>$\PackageIDnumber directory exists and that it contains the compressed package files.

If the package is configured for distribution to the site at which it was generated:

· Verify that Distribution Manager was able to decompress the files and place them on the distribution points. 

· Determine which distribution points the package source files were copied to by viewing Package Status in the SMS Administrator console.

· Verify that the \\<DistributionPoint>\SMSpkg<DriveLetter>$\PackageIDnumber directory exists and contains the decompressed source files at each distribution point. If a particular share has been specified as a distribution point for the package, verify that Distribution Manager has copied the package source files to that share. 

· Verify that Inbox Manager copied the package files (*.pkg, *.nal and *.ico) to the \\<CAP>\CAP_<SiteCode>\Pkginfo.box directory.

If the package is configured for distribution to a child site, at the parent site:

· Verify that Distribution Manager has created the package replication files and placed them in the \\<SiteServer>\SMS\Inboxes\Replmgr.box\Outbound directory. 

· Verify that Replication Manager has created a mini-job for Scheduler to schedule the transfer of the package and package files to each destination child site and a mini-job for Sender to send the files. 

· Verify that Scheduler has created a job to send the package to the child site if the \\<SiteServer>\SMSpkg<DriveLetter>$\PackageIDnumber directory exists and contains the compressed package files. Refer to Figure 17.12, "Scheduler and Sender," for additional troubleshooting tips. 

· Verify that Sender was able to connect to the site server at the destination child site and transfer the package and package instruction files. Refer to Figure 17.12, "Scheduler and Sender," for additional troubleshooting tips. 

If the package is configured for distribution to a child site, at the child site:

· Verify that Despooler has decompressed the package and instructions. 

· Verify that Despooler has instructed Distribution Manager to distribute the package. 

 

Courier Sender

Courier Sender is an SMS thread component that writes SMS software distribution packages and data on physical media such as compact discs, floppy disks, or tapes to be sent to SMS sites when only very limited bandwidth is available. This flowchart documents the activity that takes when an SMS administrator at a sending site chooses Courier Sender as the preferred sender for a package and, after Distribution Manager has sent a request to distribute the package, uses the Courier Sender Outgoing Parcel Wizard to create the parcel. This flowchart also documents the activity that takes when an SMS administrator at a destination site opens and decompresses the parcel.

You enable Courier Sender by using the SMS Administrator console to create a Courier Sender address. Click on Addresses under Site Settings. Use Courier Sender to distribute packages to a child site that is connected only via a slow, unreliable, or intermittent link.

The activity illustrated in this flowchart takes place on both the sending site server and the destination site server.

Tracing Information

You can trace the activity that occurs in this flowchart by studying the status messages and optional log files for the server components listed in the following table. You can view status messages, or you can enable the log files for server components. You can then study the log files and status messages associated with these components to trace the activity that is actually occurring on your SMS system and compare it to the activity described in the flowchart. For more information about how to access status messages for a specific component and how to enable logging, see "Status Messages Versus Logging" in Chapter 16, "Introducing the SMS 2.0 Flowcharts."

Table 21.5 Status Message Components and Log Files for Courier Sender

Server components	Log files
Courier Sender	SMS\Logs\Coursend.log
Distribution Manager	SMS\Logs\Distmgr.log

Troubleshooting Tips

If a package you are sending via Courier Sender does not appear on the media you plan to ship to the remote site, do the following:

· Verify that you have specified Courier Sender as the preferred Sender in the Package Properties dialog box for the package. Distribution Manager creates a request for this package to use Courier Sender. 

· Verify that you have created a parcel that includes the package. To do this, you use the Courier Sender Manager interface, which is separate from the SMS Administrator console. You can also use the Courier Sender Manager interface to assign optional information such as the tracking number and how the package was sent.

To open Courier Sender Manager, select it from the Start menu on the primary site server. 

· Verify that parcel status was manually set to Sent in the Courier Sender Manager interface after package files were transferred to the specified media. Courier Sender does not change the parcel status when files are written to the media you specify. 

To change the parcel status, select the parcel, click Properties, and then click Change Status. 

If the package you sent via Courier Sender does not appear at the destination site:

· Verify that the destination site has received the parcel and package.

· Verify that an administrator at the destination site has used Courier Sender Manager to receive and process the incoming parcel.

· Check the Coursend.log file at the destination site to determine whether errors occurred when the incoming package was processed. 

Deploy Office 2007 with SCCM

Office 2007 Dump Looks Like this….

Go to command prompt and change the working directory to office dump folder and type "setup.exe" /admin

then you will see similar to below wizard

enter the values or choose the option that you want to customized then click on file and save now it will save as a FILE.MSP

Now lets try out our saved .MSP file and see if it works correctly before proceeding further

Now let's open CMD.
browse to your install and enter the following switch: "setup.exe" /adminfile file.msp

If this works create an Package and advertisement and push to the systems

Preload Package Tool for Configuration Manager 2007

http://download.microsoft.com/download/d/e/d/ded78c6e-59a4-43ee-b601-6527be7bd881/PreloadPkgOnSite.exe 

Overview

The Preload Package Tool (PreloadPkgOnSite.exe) is used to manually install compressed copies of software distribution package source files on Configuration Manager 2007 sites. After package source files are installed, a status message is sent up the site hierarchy indicating the presence of the new package source files. This avoids sites higher in the hierarchy from copying package source files over the network when distribution points at child site are selected to host software distribution package content that has already been preloaded on them.
The following feature enhancements have been made to the tool since it was released in the SMS 2003 Toolkit:

• SQL Server named instance support
• Administrator specified StoredPkgVersion value support

 

Problem Scenarios:

1. When software distribution packages are created, information about them is sent to child sites in the hierarchy. If a child site has a distribution point installed that is listed in the package properties to host the content, the content is transferred over the network and uses available network bandwidth sending compressed copies of all required package source files. To avoid using network bandwidth, the Preload Package Tool can be used to copy compressed software distribution package source files to the remote child site before assigning the child site distribution point to host the package source files.
2. If a child site fails that has a distribution point that is assigned to host software distribution package source files for a package created at a site higher in the hierarchy, all package source files will be resent over the network when the site is rebuilt and rejoined to the site hierarchy. To avoid this, the Preload Package Tool can be used to restore backed up compressed software distribution package source (.pck) files to the distribution point before rejoining the site to the hierarchy so they will already be present.

Instructions:

1. Copy PreloadPkgOnSite.exe file to the .\program files installation directory\bin\i386 directory on the child site that you wish to preload compressed software distribution package source (.pck) files.
2. Copy the applicable .pck files from the parent site or from a backup location to the distribution point share on the child site manually. After manually copying the files, ensure that the read-only NTFS file attribute for the .pck file is set.
3. From a command prompt, run the tool using the following syntax: PreloadPkgOnSite.exe PkgID StoredPkgVersion.
4. Running this command will update necessary software distribution package source location information for the site and forward this information up the hierarchy.
5. After the package source file location information is sent up the hierarchy, the distribution point hosting the manually copied .pck files can be added to software distribution package source locations at without the need to transfer package source files over the network.

Checks:

1. The command line usage is: PreloadPkgOnSite.exe PkgID StoredPkgVersion
2. If software package information already exists for a package at the site where the tool is used, the tool cannot be used.
3. This tool is meant only for child sites and cannot be used to preload packages that were created at the child site where the tool is run.
4. The PkgID.pck file must exist at the child site before the tool is run.

Precautions:

• When run, this tool modifies site database information at all sites higher in the hierarchy. This tool should only be run on fully functioning child sites and only when necessary.
• If the Configuration Manager 2007 distribution manager process has already started processing software distribution package information to be preloaded, there is no need to run the tool

How To Check If A BITS Enabled Distribution Point Is Up And Running like how we check MP

To check if a Management Point is up and running we have the mplist and mpcert http URLs that we can open in Internet Explorer.  We don’t have such URLs to test if a Distribution Point (DP) is up. Management Point and Distribution Point servers are very different roles.  The Management Point is a conduit for the clients to get information from the SQL database i.e. their cert, their machine policy, etc.  That is why there is a way to use an http link to get that information from SQL through the MP.  A DP is nothing but a server share.  To use BITS for downloads, we expose that share through a virtual IIS directory.

There is no http link with a cert on a DP that we can query on, but you can create a package just to test the DP health.  Here is how:

1. Create a text file and write in it whatever you want to see when you use the http URL to test the DP.

2. Rename that file and change the txt extension to html.

3. Create a package that only contains that file and add your distribution points to the package.

4. Get the package ID and then go to the IIS Manager console and find the name of the DP virtual directory and make sure there is a folder for your DP health package.

5. Use IE and type the URL for the server, the virtual IIS directory, the package ID folder, and then your html file.  In my case it looks like this:

http://sccm/sms_dp_smspkge$/zzz0002e/dphealth.html

6. You should get back the content of the text file you created on step one:

If you get the content of your html file back, your BITS enabled DP is up.

Deploy Office 2007 SP2 with ConfigMgr 2007

As Microsoft recently released Service Pack 2 for Office 2007 suite, it is a good idea to add the update files to the package so it it can be deploy during the installation.

So, first of all we have to download the SP2 executable file from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en (see additional information bellow).

Then, using a command prompt window, extract the content of the package to a folder you can browse to.

Accept EULA and click Continue.

Select a folder to extract the files to.

When the extraction is complete, you should have the following files:

At this point, you can delete the office2007sp2-kb953195-fullfile-en-us.exe file. Copy the other 9 files to “Updates” folder from your Office 2007 source folder.

Now you only have to update the distribution point/s and the next time Office 2007 will install, it will apply the SP2 update during Office 2007 installation.

The same steps are valid for Visio and Project 2007.

Microsoft Office Visio 2007 Service Pack 2 (SP2) can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?familyid=78E36742-8BDA-471E-88E6-9B561BB06258&displaylang=en.
Microsoft Office Project 2007 Service Pack 2 (SP2) can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c126fa4a-b43f-4f7e-a9d4-522e92a6cfee.

Install software using Task Sequence

The TS Looks like this… to install software using a TS, is to have only Install Software steps. This way, you can install multiple software products using one advertisement instead of advertising every package. I use this only when I have an OS installed and I want to install software on it.

This is how such a TS looks like: