SCCM 2007 Package can’t reassigned to DP’s and BDP’s

Package deployed to DP and BDP’s so many packages are not installed on BDP,s it shows Install Pending in long time .

Site server Distmgr.log shows try to copy are failed and PeerDPagent.log says hash Mismatch failed are content download failed.

As above error We removed package failed BDP’s and wait till removing and again assigned to package to BDP,s but not assigned.

SQL Management run below Query

 

 select * from pkgservers where NALPath Like '%BDP name%' and pkgID = 'PKg ID'

 

Delete from pkgservers where NALPath Like '%BDP name%' and pkgID = 'PKG ID'

Content Download Failed: Content mismatch

Content Download Failed: Content mismatch

When I deploy the package I am getting Content Download Failed: Content Mismatch.

I checked failed Client CAS.log it shows like below.( HashMismatch)

CAS Log..

Download started for content ISC00130.1             ContentAccess  7/19/2013 2:47:21 PM    3132 (0x0C3C)

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistDownloadStartedEvent

{

                ClientID = "GUID:959ACA07-67C8-4C0A-AC9B-094800CF1EA0";

                DateTime = "20130719091721.312000+000";

                MachineName = "ACER-6DBE1475F3";

                PackageId = "ISC00130";

                PackageName = "ISC00130";

                PackageVersion = "1";

                ProcessID = 1040;

                SiteCode = "SITECODE";

                ThreadID = 3132;

};

                ContentAccess  7/19/2013 2:47:21 PM    3132 (0x0C3C)

Download completed for content ISC00130.1 under context System        ContentAccess  7/19/2013 2:47:47 PM    256 (0x0100)

Cannot open source file c:\windows\system32\ccm\cache\isc00130.1.system\Package,

 Win32 Error = 32              ContentAccess  7/19/2013 2:48:20 PM    256 (0x0100)

Failed to hash file, Win32 error = 32         ContentAccess  7/19/2013 2:48:20 PM    256 (0x0100)

Failed to hash on directory C:\WINDOWS\system32\CCM\Cache\ISC00130.1.System, 32               ContentAccess  7/19/2013 2:48:20 PM          256 (0x0100)

Hash matching failed.     ContentAccess  7/19/2013 2:48:20 PM    256 (0x0100)

Download failed for content ISC00130.1 under context System, error 0x80091007             ContentAccess  7/19/2013 2:48:20 PM         256 (0x0100)

Download failed for download request {55D3C5E1-F471-4857-B3FE-87F7D2090F27}          ContentAccess  7/19/2013 2:48:20 PM         256 (0x0100)

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistHashMismatchEvent

{

                ClientID = "GUID:959ACA07-67C8-4C0A-AC9B-094800CF1EA0";

                DateTime = "20130719091821.344000+000";

                MachineName = "ACER-6DBE1475F3";

                PackageId = "ISC00130";

                PackageName = "ISC00130";

                PackageVersion = "1";

                ProcessID = 1040;

                SiteCode = "ISC";

                ThreadID = 256;

};

                ContentAccess  7/19/2013 2:48:21 PM    256 (0x0100)

Successfully raised SoftDistHashMismatchEvent event. ContentAccess  7/19/2013 2:48:22 PM    256 (0x0100)

Releasing content request {55D3C5E1-F471-4857-B3FE-87F7D2090F27}   ContentAccess  7/19/2013 2:48:30 PM    256 (0x0100)

Resolution

Remove the Package on catch and rerun the Advertisement.

Exclusion for Antivirus for CCM Folder and Ccmsetup

Distribution Manager in System Center Configuration Manager 2007 is blocked by checking distribution points and packages

Distribution Manager in System Center Configuration Manager 2007 is blocked by checking distribution points and packages

After you do a site reset by using System Center Configuration Manager (ConfigMgr) set up or you do a hotfix installation with a site reset, Distribution Manager needs hours to check following things if the sites have many distribution points and thousands of packages on the distribution points.

Cause

Cause 1

Setting SigURL / Setting HTTPUrl for every package on every distribution point.

 

The following is an example from DistMgr.LOG file:

 

1/27/2009 14:52:58          Setting HTTPUrl to http://JENSGOPALSRV001/SMS_DP_SMSPKGC$/HP100005/ for package HP100005 on DP \\JENSGOPALSRV001\SMSPKGC$           628 (0x0274)

1/27/2009 14:52:58          Setting SigURL to http://jensgopalsrv001/SMS_DP_SMSSIG$/HP100005.2.tar for package HP100005 on DP \\jensgopalsrv001\SMSSIG$          628 (0x0274)

1/27/2009 14:52:58          Setting HTTPUrl to http://JENSGOPALSRV001/SMS_DP_SMSPKGC$/HP100009/ for package HP100009 on DP \\JENSGOPALSRV001\SMSPKGC$           628 (0x0274)

1/27/2009 14:52:58          Setting SigURL to http://jensgopalsrv001/SMS_DP_SMSSIG$/HP100009.2.tar for package HP100009 on DP \\jensgopalsrv001\SMSSIG$          628 (0x0274)

 

Cause 2 

SMS_Site_Component_Manager creates a RESETISAPI.TRN in the INBOXES\DistMgr.BOX directory if a real site reset is initialized by ConfigMgr Setup / Hotfix Installation / "PREINST /StopSite" or a site upgrade happens.

 

Note Site Reset is initiated by via SHUTDOWN.TRN created in directory INBOXES\SiteComp.BOX, a Site Upgrade via RESETALL.TRN.

 

The following is an example of the DistMgr.LOG file:

 

1/27/2009 14:58:40          Found file resetisapi.trn, will try to upgrade SMS hidden file ISAPI on all BITS enabled Distribution Points   2892 (0x0B4C)

1/27/2009 14:58:40          for ["Display=\\jensgopalsrv001\"]MSWNET:["SMS_SITE=HP1"]\\jensgopalsrv001\, machine account is to be used     2892 (0x0B4C)

1/27/2009 14:58:40          target processor architecture is x86         2892 (0x0B4C)

1/27/2009 14:58:40          for ["Display=\\jensgopalsrv001\"]MSWNET:["SMS_SITE=HP1"]\\jensgopalsrv001\, machine account is to be used     2892 (0x0B4C)

1/27/2009 14:58:40          IISPortsList in the SCF is "80".      2892 (0x0B4C)

1/27/2009 14:58:40          IISSSLPortsList in the SCF is "443".             2892 (0x0B4C)

1/27/2009 14:58:40          IISWebSiteName in the SCF is "".              2892 (0x0B4C)

1/27/2009 14:58:40          IISSSLState in the SCF is 0.            2892 (0x0B4C)

1/27/2009 14:58:40          Virtual Directory SMS_DP_SMSPKGC$ for the physical path C:\SMSPKGC$ already exists.             2892 (0x0B4C)

1/27/2009 14:58:40          As this is an upgrade Virtual Directory SMS_DP_SMSPKGC$ will be updated with new properties.                2892 (0x0B4C)

1/27/2009 14:58:40          target processor architecture is x86         2892 (0x0B4C)

1/27/2009 14:58:41          Successfully created the virtual directory SMS_DP_SMSPKGC$ for the physical path C:\SMSPKGC$.                2892 (0x0B4C)

1/27/2009 14:58:41          Successfully added file extension C:\WINDOWS\system32\inetsrv\smsfileisapi.dll.          2892 (0x0B4C)

1/27/2009 14:58:41          for ["Display=\\jensgopalsrv001\"]MSWNET:["SMS_SITE=HP1"]\\jensgopalsrv001\, machine account is to be used     2892 (0x0B4C)

1/27/2009 14:58:41          IISPortsList in the SCF is "80".      2892 (0x0B4C)

1/27/2009 14:58:41          IISSSLPortsList in the SCF is "443".             2892 (0x0B4C)

1/27/2009 14:58:41          IISWebSiteName in the SCF is "".              2892 (0x0B4C)

1/27/2009 14:58:41          IISSSLState in the SCF is 0.            2892 (0x0B4C)

1/27/2009 14:58:41          CWmi::GetObject(): GetObject() failed. - 0x80070003     2892 (0x0B4C)

1/27/2009 14:58:41          Setting HTTPUrl to http://JENSGOPALSRV001/SMS_DP_SMSPKGC$/HP100005/ for package HP100005 on DP \\JENSGOPALSRV001\SMSPKGC$           2892 (0x0B4C)

1/27/2009 14:58:41          target processor architecture is x86         2892 (0x0B4C)

1/27/2009 14:58:41          for ["Display=\\jensgopalsrv001\"]MSWNET:["SMS_SITE=HP1"]\\jensgopalsrv001\, machine account is to be used     2892 (0x0B4C)

1/27/2009 14:58:41          IISPortsList in the SCF is "80".      2892 (0x0B4C)

1/27/2009 14:58:41          IISSSLPortsList in the SCF is "443".             2892 (0x0B4C)

1/27/2009 14:58:41          IISWebSiteName in the SCF is "".              2892 (0x0B4C)

1/27/2009 14:58:41          IISSSLState in the SCF is 0.            2892 (0x0B4C)

1/27/2009 14:58:41          Virtual Directory SMS_DP_SMSSIG$ for the physical path C:\SMSSIG$ already exists.      2892 (0x0B4C)

1/27/2009 14:58:41          As this is an upgrade Virtual Directory SMS_DP_SMSSIG$ will be updated with new properties. 2892 (0x0B4C)

1/27/2009 14:58:41          target processor architecture is x86         2892 (0x0B4C)

1/27/2009 14:58:41          Successfully created the virtual directory SMS_DP_SMSSIG$ for the physical path C:\SMSSIG$.  2892 (0x0B4C)

1/27/2009 14:58:41          Successfully added file extension C:\WINDOWS\system32\inetsrv\smsfileisapi.dll.          2892 (0x0B4C)

1/27/2009 14:58:41          for ["Display=\\jensgopalsrv001\"]MSWNET:["SMS_SITE=HP1"]\\jensgopalsrv001\, machine account is to be used     2892 (0x0B4C)

 

Note In both causes, the SMS_Site_Component_Manager creates a RESETISAPI.TRN.

 

Resolution

Resolution for Cause 1

This issue is addressed by hotfix KB956194. For more information about hotfix KB956194, see the following article in the Microsoft Knowledge Base:

 

956194 Distribution Manager in System Center Configuration Manager 2007 Service Pack 1 may require several hours after startup before it begins to process packages

 

Additionally, registry changes are necessary to disable the verification that Distribution Manager runs on distribution point properties at startup.

 

HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER 

 

Create the following new value:

 

Name : DoNotVerifyDPPropertiesOnStartUp

Type : REG_DWORD

Value : 1

 

Note This will disable the verification that Distribution Manager runs on distribution point properties at startup.



 

If the DoNotVerifyDPPropertiesOnStartUp item does not exist or if its value is set to 0, Distribution Manager will verify distribution point properties during the startup process. If the value of the DoNotVerifyDPPropertiesOnStartUp item is set to 1, this verification behavior is  disabled.

 

With hotfix KB956194 and the registry changes completed, you should find only following line in the DistMGR.LOG file:

 

1/27/2009 14:57:43          Skip DP Properties Verification. 2892 (0x0B4C)

Resolution for Cause 2

You can prevent such a scan if you delete RESETISAPI.TRN before SMS_Distribution_Manager can pickup the file - rename distmgr.dll to distmgr.org before the site reset happens.

 

If the site reset finished by SMS_Site_Component_Manager and you have delete the TRN, rename back the DLL and restart SMS_EXECUTIVE.

 

Note You can upgrade SMS hidden file ISAPI on all BITS enabled distribution points for example over night by creating RESETISAPI.TRN in INBOXES\DistMgr.BOX directory.

Choose Between Primary Sites, Secondary Sites, and Branch Distribution Points

3 out of 6 rated this helpful - Rate this topic

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
Primary sites are used in Configuration Manager 2007 site hierarchies to manage clients located within the boundaries of the primary site and any of its child secondary sites.
Secondary sites are used in Configuration Manager 2007 site hierarchies to lessen the processing load on primary site systems and to ease client administration and network bandwidth usage to more efficiently manage Configuration Manager clients at remote locations. In general, secondary sites are used to control network bandwidth utilization across slow links for client information generated by clients and to support software distribution operations across slow network links.
In some cases, branch distribution points can be used instead of creating additional sites. Branch distribution points can help reduce network utilization for package downloads; however, they do not manage other types of client traffic, such as inventory, policy downloads, and status messages.
When choosing between primary sites, secondary sites, and branch distribution points, you should consider the amount of network traffic that the planned and future site clients will generate. It might be beneficial to install a secondary site if the amount of network traffic generated by clients across a slow link would be greater than the site-to-site communication traffic generated by a secondary site. Clients generate uncompressed network traffic when they request policies and send information—such as inventory, discovery, and status message information—to their management point based on the policy polling interval and client agents settings you define in the primary site's Configuration Manager console. Site-to-site communication between primary and secondary sites is compressed and can be scheduled and throttled by configuring site address settings.

Note

If a proxy management point is installed at a secondary site, the clients located within the boundaries assigned to the secondary site will request policies from the proxy management point. When the proxy management point receives a client request for a policy, it requests any new policies from the default management point for the primary site that the client is assigned to and returns the policy body to the requesting client. To conserve network bandwidth, the policy body returned by the default management point is cached on the proxy management point and returned to other clients at the secondary site when the same policy version is requested. For more information, see About Client Policy in Configuration Manager.

When supporting many clients at remote locations across slow network links, it might be beneficial to install a secondary site and configure distribution site systems that are local to clients within the secondary site's boundaries. When distribution points are installed within secondary sites, package source files are sent only once across the slow link from the primary site to secondary site distribution points instead of each time a client within the secondary site's boundaries requests software distribution package content. However, branch distribution points might also be beneficial in this scenario.

Other Secondary Site Deployment Planning Considerations

The following table lists additional pros and cons to consider when determining whether to install a primary or secondary site.

 

Pro

Con

Secondary sites do not require additional Configuration Manager 2007 server licenses. Secondary sites do not require an additional SQL Server database at the secondary site. Clients can be managed across a slow network connection link, such as a wide area network (WAN) connection between sites, without the need to configure client agent settings. Secondary sites can have management points (called proxy management points) to help prevent client reporting information, such as inventory reports and status messages, from traversing slow network connections to the primary site. Remote sites can be managed centrally from a parent primary site without the need for an on-site administrator at the secondary site.

Parent sites for secondary sites cannot be changed without uninstalling them and installing a new secondary site. Secondary sites cannot be upgraded to primary sites. To replace a secondary site with a primary site, you must uninstall the secondary site and install a primary site. Because Configuration Manager clients are always assigned to primary sites, client agent settings cannot be configured differently from the secondary site's parent site for clients located within the boundaries of secondary sites.

Considerations for Using a Branch Distribution Point Instead of a Site

If you have a location that is so small that it does not have a server, you should at least install a branch distribution point to provide a local package source.
If the location is large enough to have a server or if there are several users, consider the pros and cons listed in the following table when deciding whether to use a branch distribution point instead of creating a new site.

 

Pro

Con

Reduces site hierarchy complexity. Allows package to be copied out of band to a distribution point within the site. Does not require a server operating system. Provides on-demand package distribution, in which packages are downloaded to the branch distribution point only when specifically requested by a client computer. Branch distribution points download content from standard distribution points using BITS (Background Intelligent Transfer Service). Supports all packages, including software update packages and operating system deployment packages.

Does not manage traffic uploaded from clients to management points. Does not manage traffic when downloading policies from management points to clients. Does not provide a local software update point to scan for software updates. Does not provide precise time and bandwidth controls between sites, as a Sender does. Restricts available connections to 10 or fewer if using a client operating system.