syswow64 blog

Windows Management User Group Special thanks to the WMUG team for allowing me to speak on the Topic " Keeping up -to-date with Windows 10 Servicing"; Key words 'Keeping Up' For those of you who asked for my slide deck please see the OneDrive link here . Hope see you at the next Meetup. https://www.meetup.com/en-AU/WMUGUK/events/calendar/

Removing the Application Catalog Role within ConfigMgr was not as straight forward as i was hoping ! Like many SCCM admins historically the Application Catalog Web service Point and Website point were installed in order to deploy applications to Users.   However, this feature is now depreciated and User deployments can be deployed without this role as the client will query a management point instead for all deployments (user and device). ( https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures ) I decided that this role should be removed as we were on 1810 Hotfix2 and colleagues had stated the transition was near seamless (see below regarding a reported BUG and quick fix to modify any Client setting). The procedure to remove the App Catalog role is straight forward: 1. Remove references to App Catalog website within Client Settings. 2. Remove the Roles within the SCCM console. See Adam Gross blog   In our case the removal of the webs

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 feature upd

Creating Global Conditions in System Center configuration Manager for Office 365 deployments Firstly I would recommend reading the Microsoft docs article below. https://docs.microsoft.com/en-us/sccm/apps/deploy-use/create-global-conditions Software Library  >  Application Management  >  Global Conditions . Scenario: I have an AD group " SD-LSG-Comp-Microsoft Project ClickToRun"  with computer objects that should install Office 365 -  ProjectProXVolume edition. I wanted to create one application with multiple deployment types depending on their AD membership. For example if the computer is only a members of the  " SD-LSG-Comp-Microsoft Project ClickToRun" AD group then the deployment should only run the deployment Type " Office 365 Default Deployment Type-Install_InstallProject.cmd ".   This deplyoment Type calls the Office 365 setup.exe with a configuration xml detailing the  <Product ID="ProjectProXVolume">. (For a detailed understa

Scenario: I wanted to package the Office 365 Activation Troubleshooter ( Officeact.diagcab ) for Office 365 users with activation issues. I needed to find out the commands to use as well as the appropriate Detection Method. 1. Download: Officeact.diagcab https://aka.ms/diag_officeact 2. Create a PowerShell (Diagnostics.Office365.ps1) script to call the officeact.diagcab file. See example below 3. Create an SCCM Script application calling the Diagnostics.Office365.ps1 script powershell -ExecutionPolicy Bypass .\Diagnostics.Office365.ps1 Select the Detection Method tab and select radial next to "Use a custom script to detect the presence of the this deployment type". Select the Edit option on the right and set the script type to PowerShell and the script content as appropriate to the application. The script below will look at all running processes and filter out all processes that equal msdt; if a process matching this string is found the client will return an exit code of 0

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