Skip to main content

Enterprise deployment of Windows 10 Deployment via System Center configuration Manager and Office 365

By
Enterprise deployment of Windows 10 Deployment via System Center configuration Manager and Office 365

In this blog I will discuss Windows 10 deployment as well as what has changed in System Center Configuration Manager. In addition servicing models for Windows 10, SCCM, and Office 365.

The latest version of SCCM has re-branded itself without a year designation i.e. SCCM 2012 R2.  It has rather adopted the SaaS model of Windows 10 and updates will flow down more frequently rendering the year in the title obselete. The new name is System Center Configuration Manager 1511 (current branch).  The 1511 designation implies that the the current branch is 2015 November.

Within the Configuration Manager console updates synchronise when the 'Service Connection Point' role is configured.  This role supports In-console updates for Configuration Manager infrastructure and clients, and replaces the following separate update methods previously understood within SCCM:
Service packs
Cumulative updates
Extensions for Microsoft Intune
Individual fixes

Office 365 servicing model is similar to Windows 10 in the fact that there is a Current Branch and Current Branch for Business release of updates.  Within SCCM it is possible to deploy these branches via SCCM + WSUS as a normal Windows update deployment package, making use of Distribution Points rather than clients directly connecting to the Internet.  Unfortunately the process to synchronize the update with WSUS is manual however, the effort is minimal. The link referenced below refers to the Technical release however,




References
Finding documentation is now a little harder since the year has been dropped. Please see useful links below.

ConfigMgr 1511 Supported Configurations
https://technet.microsoft.com/en-us/library/mt589499.aspx

Supported client counts and site system scale
https://technet.microsoft.com/en-us/library/mt589738.aspx

SQL requirements (CU requirements, collation requirements, etc)
https://technet.microsoft.com/en-us/library/mt589592.aspx

Recommended hardware specs for ConfigMgr
https://technet.microsoft.com/en-us/library/mt589500.aspx

SCCM 1511 – Step by Step Installation Guide
http://sccmentor.com/2015/12/27/sccm-1511-step-by-step-installation-guide/

Upgrade to Windows 10 with System Center Configuration Manager
https://technet.microsoft.com/en-us/library/mt426642(v=vs.85).aspx

Manage Office 365 client updates with System Center Configuration Manager
https://technet.microsoft.com/library/mt628083.aspx#BKMK_ImportUpdates


Labels:

Comments

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

By
Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...
161 comments
Read more

Windows 7 Offline files will not go Online when connected to network

By
Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...
151 comments
Read more

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

By
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...
4 comments
Read more