syswow64 blog

What Are Server Groups? Within SCCM Assets and Compliance you can create a collection containing Server Client membership. Once the 'Server Group' feature is enabled the properties of the collection will contain an additional option to declare that all members of the collection are part of a server group.   This means SCCM knows that the servers within this collection must be treated with specific logic and settings. In the example below the collection contains three nodes of a cluster and only one node may be Software Updated at a time. Once policy is received for the Software Update Group deployment an election is held in which one of the nodes will engage a lock state forcing the other nodes to wait until it has been released. The UpdatesDeployment.log details the 'Lock State'. Once the node has taken the lock (Lock State: 1) the server will then run the 'Node Drain Script' and continue if the script has an exit code of 0 zero or if the script times out (600 ...

Scenario: A two node cluster required new and old software updates to bring it up to compliance. The installation of KB3000850 was failing to install either manually or via SCCM deployment on one node  but not the other. WUAHandler.log Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001 CBS.log  Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] CBS    Store corruption, manifest missing for package: Package_33_for_KB3081320~31bf3856ad364e35~amd64~~6.3.1.1 CBS    Mark store corruption flag because of package: Package_33_for_KB3081320~31bf3856ad364e35~amd64~~6.3.1.1. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]  Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION] WER: Generating failure report for package: Package_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8, status: 0x800f0831, failure source: Execute, start state: Staged, target state: Inst...

Scenario: The client has pretty standard ConfigMgr setup to manage there primary and dev systems. The clients communicate to Distribution and Management Points however, the PORT 8530 from the Software update Point ( SRVSUP01 ) can not be opened to clients in the dev vlan. Without getting into the technical architecture of the configured firewall rules a second Software update Point would be required to over come this architectural design. However, the Dev client would not switch over to the new SUP ( SRVSUP02) . Upon opening a Browser window from a Dev client it was possible to navigate to the addresses below thus confirming the availability of the new SUP. http:// SRVSUP02 .Contoso.local :8530/SimpleAuthWebService/SimpleAuth.asmx   http:// SRVSUP02 .Contoso.local :8530/ClientWebService/wusserverversion.xml   http:// SRVSUP02 .Contoso.local :8530/Selfupdate/wuident.cab The WUAHandler.log was reporting a scan failure error code: 0x8024401c. Implying the Scan agent was not ...

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...

All New posts are placed on: http://www.SystemCenterBlog.co.uk

Windows 10 - UE-V Deployment Guide UE-V in Windows 10 is setup pretty quickly but the documentation for Group Policy and expected outcomes is all over the place.  In order to help other IT Pro's navigate their UE-V implementation I have documented my configuration with observations. Folder and Executable Reference Table Templates folder                    = C:\ProgramData\Microsoft\UEV\Templates InboxTemplates folder           = C:\ProgramData\Microsoft\UEV\InboxTemplates Scripts Folder                         = C:\ProgramData\Microsoft\UEV\Scripts SettingsStoragePath                = Central UNC Share i.e \\ServerName\UEVData\%UserName% SettingsTemplateCatalogPath = Central UNC Share i.e \\ServerName\UEVCatalogPath UEVAppMonitor.exe                  ...

Software Updates - Feature Upgrade - Windows 10 Software updates within an Enterprise organisation has been fairly straight forward until you attempt to use it for Feature Upgrades of Windows 10.  SCCM is very reliable at delivering the updates (Rollups, Updates, Upgrades) and as i have previously proved is UWF aware in Windows 10. However, the Feature Upgrade does require a bit of prep work if you do not want the new Appx Applications installed as part of the Upgrade. Moving between the 1507-1703 branches each Feature upgrade would reinstall the Appx Applications that you previously removed. Microsoft has addressed this in the 1703 - 1709 feature upgrade and if you removed an application it will not come back.  However, if the new branch has a new application this will get installed. Uninstalled in-box apps no longer automatically reinstall Starting with Windows 10, version 1703, in-box apps that were uninstalled by the user won't automatically reinstall as part of the featur...