Monthly Email Newsletter curated by our Top Editors
Hi everyone! Many organizations want to be sure corporate devices to meet requirements to protect access to corporate network or company data only for compliant devices. By using the Intune Compliance Policies, you can create and assign access on corporate devices or personal devices, then you can alert your users, or you can block access to corporate resources with Azure AD Conditional Access.
There are two parts of Intune compliance policies:
- Policies which define criteria and rules we can configure and deploy on devices;
- Settings which define actions for noncompliant devices and determine how compliance policies will interact with user devices.
Introduction
Here we are again with a brand new series. I have made some articles and blogs in the past around this area but they were in several pieces, so I’m not only going to consolidate some of that information but also provide a basis on an end to end strategy which will indeed cover everything talked about within this series.
As we all know patching is a very fundamental element in order to keep our environments healthy. But sometimes demands can either make us develop a strategy on impulse, quick fix solutions and many other areas which can get ignored. And one of them in my honest opinion is the foundational state of your WSUS servers. This first part we will cover the basis on how we can keep these areas healthy and regularly maintained as these can have a guaranteed knock on affect to everything within MECM.
Worth noting that this series is going to cover everything from MECM and Intune for all patching areas so we can get things right.
Introduction
The next area we want to look into is now how we construct our collections for patching. Now many can utilise pre-existing collections which is fine if you are doing more of a generalist type of patch approach to hit all machines, but there are various areas of why you may not want to do that.
Therefore it can be more beneficial to split these apart so there is no specific overlapping of any policies put in place. This then allows for workflows to remain in place to handle their respective tasks whilst software patching will maintain its own realm.
In this article I will show how to perform Windows 11 22H2 upgrade using SCCM. This is the latest version of windows 11. It is released on September 20, 2022.Here user can use windows servicing plans to keep windows 11 updated and secured. users who are running with windows 11 21h2, can upgrade with Windows 11 22H2 using windows update. ConfigMgr Servicing Plans are also used to learn how to upgrade to Windows 11 version 22H2. Widows 11 feature update release cycles are now set to one per year.so you have to perform Windows 11 upgrades once a year.
Introducing the Microsoft Intune product family
Microsoft is noticing IT leaders and administrators using Microsoft Intune to power productive and secure at work and the number of windows, android & IOS devices managed by Intune grew up 60%. Nearly 80% of windows 11 endpoints managed by Intune and 50% of Microsoft managed endpoints are cloud managed, compared to less than 20% in 2020. Microsoft is investing more in Microsoft Intune to enhance features, performance, and integration with Microsoft 365. Microsoft Intune will be the name of product family for endpoint management.
Microsoft is building suite of advanced endpoint management solutions in the cloud which comes under the Intune product family. Microsoft configuration manager will remain part of Intune product family and using co-management capabilities, it will migrate workload to the cloud.
