System Center

Microsoft Endpoint Manager: Bringing together SCCM and Intune capabilities

See the evolution of device management, with the new Microsoft Endpoint Manager. Microsoft Endpoint Manager brings together Configuration Manager and Intune in one unified, web-based experience. You’ll also see the evolution of our compatibility tools and services to ensure your devices, apps, add-ins and sites are always ready. Plus you’ll see new security baselines and Threat and Vulnerability Management to help bring IT and security teams together.

Announcing Microsoft Endpoint Manager

Learn more about how we’re integrating Microsoft Intune, Configuration Manager, and more into a single solution called Microsoft Endpoint Manager. In this video, Brad Anderson walks through the details on what Microsoft Endpoint Manager is, and why Microsoft is moving towards an integrated management solution.

Microsoft Eliminates SCCM and Intune, Combines Management Tools into Microsoft Endpoint Manager

Microsoft today at Ignite has renamed and combined all of its management tools into a single set of tools with a more modern name. Gone is the name SCCM and Intune. Instead…meet Microsoft Endpoint Manager. One big announcement was bringing together all of the Microsoft management solutions under a common brand – Microsoft Endpoint Manager.  Microsoft Endpoint Manager is the single management solution to manage and empower your users across all of their devices.  ConfigMgr, Intune, Desktop Analytics, Co-Management, Device Management Admin Console, … now are Microsoft Endpoint Manager.  For many of you, your destination may be all-cloud.  For many others of you, your destination may be ConfigMgr and Intune working together in co-management.  Both are destinations and will be full...

Hydration Kit For Windows Server 2019, SQL Server 2017 and ConfigMgr Current Branch Now Available

Johan has done it again, delivering the next revision of his famous hydration kit for System Center Configuration Manager. Delivered over the weekend, this latest release supports Windows Server 2019, SQL Server 2017 and ConfigMgr Current Branch. This kit builds a complete ConfigMgr Current Branch infrastructure running on Windows Server 2019 and SQL Server 2017. This kit is tested on both Hyper-V and VMware virtual platforms, but should really work on any virtualization platform that can boot from an ISO. Read more about it: Hydration Kit For Windows Server 2019, SQL Server 2017 and ConfigMgr Current Branch Direct download: http://bit.ly/HydrationCMWS2019

Pre-release Builds of Windows 10 Coming to Configuration Manager Once a Month Starting with 1909

Microsoft today has announced a new opportunity for IT administrators to get access to pre-release features of Windows 10 prior to public delivery. Today, in response to your feedback, we will begin making pre-release Windows 10 feature updates available to IT administrators using Windows Server Update Service (WSUS). This is the next step in our efforts to provide your organization with the ability to validate line-of-business (LOB) applications, business-critical functionality, and policies, as well as evaluate new business features, prior to an update’s official release. Beginning with Windows 10, version 1909, we will aim to release pre-release builds to Configuration Manager on a monthly cadence. Beyond that release, we will aim to release these types of builds in line with the ...

Tip: Locating SCCM Log Files

  Configuration Manager and dependent components store log files in various locations. These locations depend on the process that creates the log file and the configuration of your environment. The following locations are the defaults. If you customized the installation directories in your environment, the actual paths may vary. Client: C:\Windows\CCM\logs Server: C:\Program Files\Microsoft Configuration Manager\Logs Management point: C:\SMS_CCM\Logs Configuration Manager console: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog IIS: C:\inetpub\logs\logfiles\w3svc1 Task sequence log locations The location of the task sequence log file smsts.log varies depending upon the phase of the task sequence: In Windows PE before Format and Partition Disk step: X:\Wi...

BranchCache – Part 3 Caching! Understanding the Options

This session focuses on the Configuration Manager integration with Windows BranchCache. The discussion includes details about how to configure BranchCache in a Configuration Manager environment and the flow when BranchCache is used. The demonstrations walk through in detail the process of using BranchCache, how to track it and how to confirm it has been used for content download.

Tip: Troubleshoot Update Rejections by Exposing the Applicability Rules

Available from GitHub, @MrWyss has delivered a tool that allows administrators to troubleshoot why an update was rejected based on the supplied rules. Windows Updates have Applicability Rules, that decide whether an update is installable or is installed. This information can be very useful in Troubleshooting cases and to understand why a updates report back installed or why a updates is not installing. These Rules are defined in the Update.xml per Update. The Update.xml is stored in the WSUS Update Database in the RootElementXmlCompressed filed of the table tbxml. An update can be bundled. Therefore the bundled update xml needs to be looked at. Show-ApplicabilityRule.ps1 will help you to extract the Applicability Rule. Download: Show Update Applicabilty Rule

Peer Caching and OSD – Part 2 Caching! Understanding the Options

This session focuses on peer cache functionality build into ConfigMgr and specifically details how peer caching works in Operating System Deployment scenarios. The discussion includes details and demonstrations of using the Download Package Content task sequence option, the pre-download image deployment option, the use of the variables available or required to enable peer caching and more.

Peer Caching – Part 1 Caching! Understanding the options

The session focuses on the peer cache functionality built into Configuration Manager and details how it works and how to configure it. It includes a demonstration of using peer cache along with details about WMI, associated log files and the content location request process.

Changes You are Required to Make to Enable ConfigMgr and WSUS to Deploy Windows 10 1903

After Microsoft began making Windows 10 1903 available publicly this week, the company announced some changes in how its Configuration Manager and WSUS environments handle this update. The changes require that administrators of these systems make some quick changes. For Configuration Manager: In order to deploy feature and quality updates to devices running Windows 10, version 1903 or Windows Server, version 1903 (and later), you will need to ensure that you are running the current branch of System Center Configuration Manager, which is version 1902. Then, in the Configuration Manager console, enable the Software Update point to download updates for Windows 10, version 1903 and later and/or Windows Server, version 1903 and later. For WSUS:  If you are using Windows Server Update Services (...

Microsoft Adding MBAM Features to ConfigMgr and Intune

Announced at MMS 2019 at the Mall of America, System Center Configuration Manager and Intune will be getting MBAM features. #MMSMOA announcement: MBAM features will be added to #ConfigMgr and #Intune pic.twitter.com/kyAw7ms6PV — Octavian @ MMSMOA (@octav_cm) May 6, 2019 Microsoft BitLocker Administration and Monitoring (MBAM) 2.5 provides a simplified administrative interface for BitLocker Drive Encryption. BitLocker offers enhanced protection against data theft or data exposure for computers that are lost or stolen. BitLocker encrypts all data that is stored on the Windows operating system volumes and drives and configured data drives.