Monday, August 14, 2017

SCCM Software Update Deployment Package Distribution Error | Content/Package does no exist

Hold on there! Don’t take the step to create a new package and re-download all the content into new package yet!

My customer has a 10GB software update deployment package. It will cost a lot of replication traffic if he create a new package and re-download the entire package.

Copy the SQL query from this blog, https://blogs.technet.microsoft.com/ken_brumfield/2013/01/10/troubleshooting-sccm-software-update-deployment-package-distribution-due-to-missing-directories/

  1. Copy the SQL query and replace @missingSourceDirectory and @PackageIdimage
  2. Execute the query and this should give you the KB Article and the Software Update Name
  3. Open the Software Update Deployment Package, and search for that KB Article
  4. Delete it from the deployment package
  5. Back to the Content Status monitoring, and check the status.
  6. Repeat the steps above if you see a new GUID error

SQL Query:

DECLARE
@MissingSourceDirectory
NVARCHAR(512)
DECLARE
@PackageId
NVARCHAR(8)
SET
@MissingSourceDirectory =
'c34e2458-681f-4a8b-8941-a460c2de314a'
SET
@PackageId
= '0020000D'

SELECT
CASE
         WHEN
ci.BulletinID LIKE
''
OR ci.BulletinID IS
NULL
THEN
'Non Security Update'
         ELSE ci.BulletinID
         END
As
BulletinID
     , ci.ArticleID
     , loc.DisplayName
     , loc.Description
     , ci.IsExpired
     , ci.DatePosted
     , ci.DateRevised
     , ci.Severity
     , ci.RevisionNumber
     , ci.CI_ID
FROM dbo.v_UpdateCIs
AS
ci
LEFT
OUTER
JOIN dbo.v_LocalizedCIProperties_SiteLoc
AS
loc
ON
loc.CI_ID = ci.CI_ID
WHERE ci.CI_ID IN
(
     SELECT [FromCI_ID]
     FROM
[dbo].[CI_ConfigurationItemRelations]
cir
     INNER
JOIN [dbo].[CI_RelationTypes]
rt
ON
cir.RelationType = rt.RelationType
     WHERE
cir.ToCI_ID IN
     (
         SELECT
CI_ID
         FROM
[dbo].[CI_ContentPackages]
cp
         INNER
JOIN [dbo].[CI_ConfigurationItemContents]
cic
ON
cp.Content_ID = cic.Content_ID
         WHERE
cp.ContentSubFolder = @MissingSourceDirectory AND cp.PkgID = @PackageId
     )
)

Tuesday, August 8, 2017

WSUS 3.0 SP2 Re-installation Failure due to .NET Framework and Update Services Folder

I’ve just resolved this issue half an hour ago. Customer uninstalled WSUS 3.0 SP2 but failed to reinstall it back later.

The WSUSSetup.log under %temp% showed Error 0x80070643

2017-08-07 11:14:36  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
2017-08-07 11:14:36  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
2017-08-07 11:14:36  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2017-08-07 11:14:40  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

From the event viewer, Event ID 11722 showed that the installation is failed with Error 1722.

image

I came across Anoop Blog and resolve the installation issue. In short, WSUS 3.0 SP2 doesn’t like .NET Framework 4.6 or later very much, WSUS cannot detect those newer version. Here are some official article/blog from Microsoft regarding that, https://support.microsoft.com/en-us/help/3045727/cannot-install-wsus-3-2-on-a-server-with-the-net-framework-4-6-or-late and https://blogs.technet.microsoft.com/wsus/2017/06/12/microsoft-net-framework-4-7-coming-to-wsus/ 

The resolution is to uninstall .NET Framework 4.6 or later before the WSUS 3.0 SP2 installation. You can install the .NET Framework after the WSUS 3.0 SP2 completed.

The WSUS finally installed!
BUT more errors pops out from the event viewer.
Event ID 7053, 12022, 12032, 12012, 12002

image

image

I have tried a lot of things that people suggested like delete the wsus MMC profile under %appdata%\Microsoft\MMC, change the WsusPool Identity and Manage Pipeline, remove then re-add the Windows Process Activation Services from Server Manager, verify the permission on all the required folder, and SQL permission.

None of the above resolve my issue until I perform the steps below:

  1. Uninstall WSUS 3.0 SP2 from program and features
  2. Verify SQL SUSDB has been deleted, D:\WSUS content has been deleted.
  3. Manually delete C:\Program Files\Update Services folder. This is the step that resolve the issue. There will be some leftover files after the WSUS uninstalled, which will not be replaced even after the WSUS re-installation
  4. Delete the MMC profile under %appdata%\Microsoft\MMC
  5. Reboot the server
  6. Run the WSUS 3.0 SP2 setup.
  7. You should be able to see the WSUS Wizard prompt. This mean that the installation is successful!
  8. Close the Wizard, do not configure, let SUP do the configuration later.
  9. Install the WSUS latest patch. I installed KB2938066
  10. Install the SCCM SUP role

For your reference:
WSUS 3.0 (SP2):     Build 3.2.7600.226
WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
WSUS 3.0 (SP2) + KB2938066:     Build 3.2.7600.274

Monday, March 6, 2017

Windows 10, v1507 End of Servicing?

Windows 10 has already with us for some time, coming to 2 years in July 2017. There are 3 build/version since Windows 10 released, v1507, v1511, v1607. Many people asked which build/version should I install? I would answer the latest. That is not because the latest has improvement or new feature set. It is simply because I want to ensure that the Windows keeps receiving its security and critical patches. If you interested on what’s new on every new Windows 10 release.

Yes, according to this site, Windows 10, v1507 end of servicing will be occur in May 2017. End of servicing simply means that Microsoft will not provide security and critical patches to Windows 10, v1507 from May 2017 onwards.

Plan now and move forward with SCCM!!!

WIndows 10 Servicing