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...
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.
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
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.
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.
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 (...
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.
This session focuses on Autopilot and walks through in detail what autopilot is, how to configure it and demonstrates four key autopilot scenarios.
This session focuses on Upgrade Readiness. We describe how to configure Upgrade Readiness and then shift to discussing how to connect ConfigMgr to Upgrade Readiness and the benefits of doing so. Troubleshooting options are also reviewed.
This session centers around the benefits, requirements, and usage of the Microsoft Store for Business and focuses on the integration between the Microsoft Store for Business and Configuration Manager.
Still struggling to maintain Configuration Manager 2007 and Forefront Endpoint Protection 2010? Believe it or not, despite all the advances in Configuration Manager…some are. Well, here’s the best reason to move forward. As of July 9, 2019, Configuration Manager 2007 and Forefront Endpoint Protection will no longer receive updates of any kind (security, non-security) and support options (both paid and free) will no longer be available. Additionally, definition, engine, and platform updates for FEP will cease. Time to take the leap of faith and move on.
This session focuses on Device Health Attestation and the options to use ConfigMgr as a management source for Device Health Attestation data. We also discuss troubleshooting.