SCCM 2012 Client Upgrade Package Distribution Failed

Whenever you setup a new distribution point, the system will automatically distribute 2 packages to the distribution point.

          1. Configuration Manager Client Package

          2. Configuration Manager Client Upgrade Package

But somehow the Configuration Manager Client Upgrade Package failed to distribute to the distribution point. The upgrade package is hidden, hence unable to redistribute the upgrade package like normal package. Therefore, we have to trick the system to redistribute the packages.

Resolution:-

1. Open an empty notepad and save it as client.acu

2. Copy the client.acu to the inboxes\hman.box folder at the top-level site

3. Monitor the hman.log to check whether the Client Upgrade package gets updated

WDS and DHCP are running in the same SCCM Server

WDS service will not start, since DHCP and WDS both will use the same port 67 by default.

To get around this the following registry change needs to be made (UseDHCPPorts = 0)

Monitored PXEControl.log to ensure PXE was responding to tests

         
 If PXE boot still didn't work run the below command
Initialize the WDSServer (wdsutil /initialize-server /reminst:G:\RemoteInstall) 
NOTE: Adjust the G:\remoteinstall location to reality in your environment

Next you need to run the following command for the registry change made in above step
 to take affect

SCCM 2007 - Task Sequence Error 0x80004005 & NO MP Certificates

When you get the below error it might be a problem with the boot image (If you were using a boot CD for image deployment) or problem with the Management Point

It’s very advisable to investigate the smsts.log files to troubleshoot task sequence errors. The log file is located on different locations depending on the task sequence process. My reference machine rebooted even before format so I needed to get my log file from the Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log. You need to press F8 during WINPE to get command line abilities and copy your log file to another destination.  Make sure that “Enable command support” is enabled in your boot image properties ( Operating system deployment – Boot images – right click your boot image – properties –  WINPE tab)

Solution - Create a new boot image & if still No MP Certificates error occurs re-install the Management Point

Supported Client Version of App-v in SCCM 2012

Before the migration of SCCM 2012 you should check the App-v client version on your environment, below are the App-v version details

App-v Client Version	Support Details
4.5.0.15341 (App-V 4.5 HF03 Jan 2009)	Not Supported in SCCM 2012
4.6.0.1523 (App-V 4.6 RTM)	Not Supported in SCCM 2012
4.6.0.20200 (App-V 4.6 All Languages)	Not Supported in SCCM 2012
4.6.1.20870 (App-V 4.6 SP1)	Not Supported in SCCM 2012
4.6.2.24020 (App-V 4.6 SP2)	Supported in SCCM 2012
4.6.2.30111 (App-V 4.6 SP2 HF03)	Supported in SCCM 2012
4.6.3.24870 (App-V 4.6 SP3)	Supported in SCCM 2012
4.6.3.25111 (APP-V 4.6 SP3 HF01)	Supported in SCCM 2012

The below SQL query will help you to find the App-v version details on your site

SELECT     dbo.v_R_System.Netbios_Name0, dbo.v_R_System.User_Name0, dbo.v_R_System.AD_Site_Name0, dbo.v_GS_OPERATING_SYSTEM.Caption0,

                      dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0,dbo.v_GS_ADD_REMOVE_PROGRAMS.Version0

FROM         dbo.v_R_System INNER JOIN

                      dbo.v_GS_OPERATING_SYSTEM ON dbo.v_R_System.ResourceID = dbo.v_GS_OPERATING_SYSTEM.ResourceID INNER JOIN

                      dbo.v_GS_ADD_REMOVE_PROGRAMS ON dbo.v_R_System.ResourceID = dbo.v_GS_ADD_REMOVE_PROGRAMS.ResourceID

                      where

                   

                      dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 like 'Microsoft Application Virtualization Desktop Client'

If the client App-v is not upgraded, you will receive the below error on ccmsetup.log

SQL Report – Detailed Advertisement Report

SELECT dbo.v_R_System.Netbios_Name0 AS Name,

 dbo.v_ClientAdvertisementStatus.ResourceID,

 dbo.v_ClientAdvertisementStatus.LastStateName AS [Status],

 dbo.v_ClientAdvertisementStatus.LastStatusMessageIDName AS [Status Detail],

 CONVERT(datetime,

            SWITCHOFFSET(

                CONVERT(datetimeoffset,

                    dbo.v_ClientAdvertisementStatus.LastStatusTime),

  DATENAME(TzOffset, SYSDATETIMEOFFSET()))) AS StatusTime,

 dbo.v_GS_OPERATING_SYSTEM.Caption0 AS OSName,

 dbo.v_GS_OPERATING_SYSTEM.CSDVersion0 AS SP,

 dbo.v_R_System.AD_Site_Name0 AS SiteName

FROM dbo.v_ClientAdvertisementStatus LEFT OUTER JOIN

 dbo.v_GS_OPERATING_SYSTEM ON dbo.v_ClientAdvertisementStatus.ResourceID =

 dbo.v_GS_OPERATING_SYSTEM.ResourceID LEFT OUTER JOIN

 dbo.v_R_System ON dbo.v_ClientAdvertisementStatus.ResourceID = dbo.v_R_System.ResourceID

WHERE (dbo.v_ClientAdvertisementStatus.AdvertisementID = '2D020081')

ORDER BY Name

SQL Report - Package not used recently

SELECT   

      A.AdvertisementName AS [Advertisement Name],

      A.PresentTime AS Created,

      MAX(CAS.LastStatusTime) AS [Last Time Used],

      p.packageID,

      A.ProgramName,

      A.CollectionID,

      P.PkgSourcePath,

            (SELECT COUNT(PkgID) FROM vPkgStatusSummaryDistPts WHERE PkgID = p.PackageID) AS [No of DP]

FROM

      v_Package P

      INNER JOIN v_Advertisement A ON P.PackageID = A.PackageID

      INNER JOIN v_ClientAdvertisementStatus CAS ON A.AdvertisementID = CAS.AdvertisementID

WHERE

      (CAS.LastStateName != 'Accepted - No Further Status')AND

      p.PackageID NOT IN (SELECT ReferencePackageID FROM v_TaskSequenceReferencesInfo) and p.Packagetype=0

GROUP BY

      A.AdvertisementName,

      A.PresentTime,

      A.CollectionID,

      P.PkgSourcePath,

      P.Name,

      P.PackageID,

      A.ProgramName,

    P.Description

HAVING

      (MAX(CAS.LastStatusTime) IS NOT NULL)

      AND datediff(mm,MAX(CAS.LastStatusTime),getdate()-365) > 0

ORDER BY

      A.AdvertisementName,

      A.PresentTime

SUP unable to Sync with upstream Server

When you configure a Software Update Point (SUP) role on a Secondary Site/Primary Site you receive an error in the WCM.log and the SUP on secondary site is not functional.  The errors are similar to the following

From the WCM.log:

  Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = Unspecified error~ 

From the WSUSctrl.log:

 Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = Unspecified error~

               Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes

To resolve this issue re-register the wsusmsp.dll and the wsyncact.dll files.  To do this follow these steps: 

  1.       Open a CMD window and navigate to c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\.

 2.       Run the following command lines in the order listed:

 •         RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsyncact.dll /unregister

•         RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsyncact.dll

•         c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll /unregister

•         c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll

 The above commands register the Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction  class  and the Microsoft.SystemsManagementServer.WSUS.WSUSServer class successfully.

3.       Run regedit.exe and verify that the following registry keys exist:

HKEY_CLASSES_ROOT\Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction

•         HKEY_CLASSES_ROOT\CLSID\{E5272449-2083-4020-ACEE-18A145F79A75}

4.       Wait for the next Sync status to see if the sync is working now.

Note Uninstalling and reinstalling the SUP will not resolve this issue.

Source - http://support.microsoft.com/kb/962224