Tuesday, 28 November 2023

Intune Scope Tags - In Detailed

Scope tags determine which objects admins can see; Intune scope tags allow you to manage a large organizations IT infrastructure while giving each department/region/sub company/… the flexibility to configure their own settings. Scope tags in Microsoft Intune allow administrators to divide devices in their organization into logical groups. These groups, also known as tags, can be used to make certain settings, applications, and policies available only to specific users or devices. By using Intune scope tags, you can streamline your IT infrastructure, improve security, and make your life easier.

Intune scope tags

What’s an Intune scope tag?

A scope tag assigns an Intune configuration (e.g. device configuration, compliance policy, mobile app or managed device) to one or more specific management scope(s)

Create Scope Tag

First of all, we have to create one or more scope tag. Go to Intune → Roles → Scope Tags. There you can create custom Scope Tags.

Use Roles

What is a role? Roles are a bunch of settings to allow administrators very specific tasks to do in Intune. A role has two sections. Permissions and Assignments

Within the permissions you can – how obviously – define which permissions you want to delegate

Within the Assignment you’ll have three sections:

• Members: Who will get the new permission

• Scope (Groups): Which groups should be managed. This can be a device and/or user group

• Scope (Tags): Which tag will apply.

You can have multiple assignments in one Role. But let’s keep it simple and use only one assignment

Let’s create a new Role. Go to Intune → Roles → All Roles and add a new role

You will first have to define what permissions you want to delegate to them. Please select all your required permissions and click create. If you want to can also Scope that role. Don’t let the wizard upset you. This scope is not relevant for the delegated admin at this point.
Now it’s getting interesting. Go into your new role, and create a new assignment.

• Members, please use a group where your admins are in who want to delegate permission to.
• Scope (Group): This is a list of target groups where your delegated admin can have permissions to.
• Scope (Tags): A list of Tags this assignment is relevant to

Things to keep in mind:

• To be assigned an intune role, the user must have an intune license.
• When an admin creates an object in Intune, all scope tags assigned to that admin will be                           automatically assigned to the new object.
• Intune RBAC doesn’t apply to Azure Active Directory roles. So, the Intune Service Admins and              Global Admins roles have full admin access to Intune no matter what scope tags they have.
• Admins with scope tags can see policies with NO scope tag and policies with scope tags assigned          to him
• Newly created items always inherit all of his scope tags
• Change items with no scope tag will then require a scope tag
• Admins can only target groups that are listed in the scope (Group) of his assignment
• New created or changed items by an admin need at least one scope tag





Monday, 13 November 2023

Migrate SCCM to Intune Using Co-Management

Cloud attach allows organizations to use MECM to manage devices that are enrolled in Microsoft Intune, without the need to install the MECM client on the device. This allows organizations to take advantage of the advanced management capabilities of MECM, while still using Intune for device enrollment and basic management tasks

Co-management, on the other hand, allows organizations to use both MECM and Intune to manage the same set of devices. With co-management, organizations can use MECM for traditional device management tasks, such as deploying software and updates, while using Intune for modern management tasks, such as mobile device management and conditional access.




Pre-requisites

• Azure Active Directory Premium

• An Azure Account that is global admin and has got a Microsoft Intune subscription.

• Configure a hybrid Azure AD join using Azure AD Connect

• Configure Client Settings to direct clients to register with Azure AD

• Configure auto-enrollment of devices to Intune.

• Setting up Co-management in MECM


Configure a hybrid Azure AD join using Azure AD Connect

•Use Client Settings to configure Configuration Manager clients to automatically register with Azure AD

•Open the Configuration Manager console and go to: \Administration\Overview\Client Settings.

•Edit the default Client settings and select Cloud Services, set Automatically register new Windows 10 domain joined devices with Azure Active Directory to = Yes. Select OK.

Configure auto-enrollment of devices to Intune.

With automatic enrollment, devices you manage with Configuration Manager automatically enroll with Intune.

Automatic enrollment also lets users enroll their Windows 10 devices to Intune. Devices enroll when a user adds their work account to their personally owned device, or when a corporate-owned device is joined to Azure Active Directory

Sign in to the Azure portal and select Azure Active Directory > Mobility (MDM and MAM) > Microsoft Intune.

Configure MDM user scope. Specify one of the following to configure which users’ devices are managed by Microsoft Intune and accept the defaults for the URL values.

     •Some: Select the Groups that can automatically enroll their Windows 10 devices

     •All: All users can automatically enroll their Windows 10 devices

     •None: Disable MDM automatic enrollment

We can select All or specific the group where the devices are part of cloud attach or co-management collection

Setting up Co-management in MECM

Open your MECM console and go to: \Administration\Overview\Cloud Services\Co-management and click on Configure co-management.

Click Sign In.

Sign in with the Intune organizational account (this account has got to have a Enterprise Mobility + Security (EMS) Subscription). It also must have Global Administrator Rights in Azure AD tenant.

Click Yes to accept the Create AAD Application notification.

Select All my devices managed by MECM or select a specific collection. And check Enable Endpoint Analytics for devices uploaded to MECM. Click Next >.

Now select how you want to automatic enroll your devices in Intune:

1.None of your devices.

2.Pilot a collection of devices, In the case of Pilot, you can select which collections to add from your list

3.All of the devices that are managed by MECM.

Now lets select what workloads we want Intune to manage instead of MECM. Slide al of the workloads to the Pilot Intune, so we can assign each workload to different collections. 

Once the workload is applied, you can verify it through Microsoft Endpoint Manager admin center, and navigate to Devices > Windows > Windows devices. Click on the device and we can see the information under Co-management.


Tuesday, 31 October 2023

SCCM Replication Troubleshooting

 

To replicate the data between configmgr sites, Configuration Manager uses Database Replication Service (DRS). The DRS intern uses SQL Server Service Broker (SSB) to replicate data between the sites

We can troubleshoot SQL replication issue by following below approach.
1. Replication Link Analyzer.
2. Investigating Log files.
3. Performing SQL queries
4. Re-initiating replication.

The Replication Link Analyzer can find and fix most but not all database replication problems
rcmctrl.log
replmgr.log

Run the spDiagDRS script. The resulting output contains useful information about the general status of the database replication, the current replication link status, and the last sync time for each replication group

Examine the vLogs view. These logs show more detailed information about the process. For example, when the database replication checks for changes, when it receives the BCP (bulk copy data) from the publisher, when it ProcessSyncDataXml, and when a specific table is updated.

Check the SSB log found at: C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\ErrorLog.

Manual Sync

To re-initiate the global data, run the following SQL command:
EXEC spDrsSendSubscriptionInvalid ‘SiteCode’, ‘SiteCode’, ‘Configuration Data’

Create a .PUB file in rcm inbox folder on primary site for failed global data group

The Replication Link Analyzer works by examining both sites and checking whether:
The SMS service is running
The SMS Replication Configuration Monitor component is running
The ports required for SQL replication are enabled
The SQL version is supported
The network is available between the two sites
There is enough space for the SQL database
The SSB service configuration exists
The SSB service certificate exists
There are any known errors in SQL log files
There are any replication queues disabled
Time is in sync
The transmission of data is stuck
A key conflict exists

Monday, 9 March 2020

SCCM SQL Qury - SCCM Client Distribution Point

SCCM SQL Qury - SCCM Client Distribution Point

This Query will help to identify SCCM client DP details, if you want to know from which DP you client download the content, Use the below SQL query



select
rsys.Name0 as 'Client Name',
"Content Source Type" = CASE cdh.DistributionPointType
WHEN 1 THEN 'Cloud DP (Distribution Point)'
WHEN 2 THEN 'Management Point'
WHEN 3 THEN 'Peer Cache'
WHEN 4 THEN 'DP (Distribution Point)'
WHEN 5 THEN 'BranchCache'
END
,
cdh.HostName as 'Content Source Host Name',
pkg.Name as'Content Name',
cdh.ContentID,
cdh.BytesDownloaded
from
v_R_System as rsys
join v_ClientDownloadHistoryDP_BG as cdh on rsys.ResourceID = cdh.ClientId
join v_Content as con on con.Content_UniqueID = cdh.ContentID
join v_Package as pkg on con.PkgID = pkg.PackageID
where pkg.name = <your package, application, update name>

SCCM - SQL Query SUP WSUS Syncronization Custom Report

SCCM - SQL Query SUP WSUS Syncronization Custom Report


SELECT SiteCode, WSUSServerName, WSUSSourceServer, SyncCatalogVersion, LastSuccessfulSyncTime,
CASE [LastSyncState]
WHEN 6700 THEN 'WSUS Sync Manager Error'
WHEN 6701 THEN 'WSUS Synchronization Started'
WHEN 6702 THEN 'WSUS Synchronization Done'
WHEN 6703 THEN 'WSUS Synchronization Failed'
WHEN 6704 THEN 'WSUS Synchronization In Progress Phase Synchronizing WSUS Server'
WHEN 6705 THEN 'WSUS Synchronization In Progress Phase Synchronizing SMS Database'
WHEN 6706 THEN 'WSUS Synchronization In Progress Phase Synchronizing Internet facing WSUS Server'
WHEN 6707 THEN 'Content of WSUS Server is out of sync with upstream server'
WHEN 6709 THEN 'SMS Legacy Update Synchronization started'
WHEN 6710 THEN 'SMS Legacy Update Synchronization done'
WHEN 6711 THEN 'SMS Legacy Update Synchronization failed'
END AS 'Last Sync State', LastSyncStateTime, (Datediff(d,LastSyncStateTime,GETDATE())) as 'DateDiff'

FROM vSMS_SUPSyncStatus

Thursday, 2 January 2020

SCCM - SQL Query Machine without boundaries

SCCM - SQL Query Machine without boundaries 

SELECT DISTINCT

v_R_System.Name0,

v_R_System.Client0,

v_RA_System_IPAddresses.IP_Addresses0,

v_RA_System_IPSubnets.IP_Subnets0,

v_RA_System_SMSAssignedSites.SMS_Assigned_Sites0

FROM v_R_System LEFT OUTER JOIN

v_RA_System_IPSubnets ON v_R_System.ResourceID = v_RA_System_IPSubnets.ResourceID LEFT OUTER JOIN

v_RA_System_IPAddresses ON v_R_System.ResourceID = v_RA_System_IPAddresses.ResourceID LEFT OUTER JOIN

v_RA_System_SMSAssignedSites ON v_R_System.ResourceID = v_RA_System_SMSAssignedSites.ResourceID

WHERE (v_RA_System_SMSAssignedSites.SMS_Assigned_Sites0 IS NULL)

AND (NOT (v_RA_System_IPAddresses.IP_Addresses0 IS NULL))

AND (v_R_System.Client0 IS NULL)

AND (NOT (v_RA_System_IPSubnets.IP_Subnets0 IS NULL))


order by v_RA_System_IPSubnets.IP_Subnets0

SCCM - SQL Query Boundary / Boundary Group with Site System Details

SCCM - SQL Query Boundary / Boundary Group with Site System Details


SELECT BG.GROUPID,
       B.BOUNDARYID,
       B.BOUNDARYTYPE,
       BG.NAME [BOUNDARY GROUP NAME],
       B.DISPLAYNAME [BOUNDARY NAME],
       B.VALUE,
       CASE B.BOUNDARYTYPE
           WHEN '1' THEN 'AD Site'
           WHEN '0' THEN 'IP Subnet'
           WHEN '3' THEN 'IP Range'
       END AS 'Type',
       SUBSTRING(BGS.SERVERNALPATH, CHARINDEX('\\', BGS.SERVERNALPATH)+2,(CHARINDEX('"]', BGS.SERVERNALPATH) - CHARINDEX('\\', BGS.SERVERNALPATH))-3) AS 'Site System'
FROM VSMS_BOUNDARY B
INNER JOIN VSMS_BOUNDARYGROUPMEMBERS BGM ON B.BOUNDARYID = BGM.BOUNDARYID
INNER JOIN VSMS_BOUNDARYGROUP BG ON BG.GROUPID = BGM.GROUPID
INNER JOIN VSMS_BOUNDARYGROUPSITESYSTEMS BGS ON BGS.GROUPID = BGM.GROUPID

ORDER BY BG.GROUPID ASC


---------********--------------

SELECT DISTINCT BG.GROUPID,
BG.NAME [BOUNDARY GROUP NAME],
SUBSTRING(BGS.SERVERNALPATH, CHARINDEX('\\', BGS.SERVERNALPATH)+2,(CHARINDEX('"]', BGS.SERVERNALPATH) - CHARINDEX('\\', BGS.SERVERNALPATH))-3) AS 'Site System'
FROM VSMS_BOUNDARY B
INNER JOIN VSMS_BOUNDARYGROUPMEMBERS BGM ON B.BOUNDARYID = BGM.BOUNDARYID
INNER JOIN VSMS_BOUNDARYGROUP BG ON BG.GROUPID = BGM.GROUPID
INNER JOIN VSMS_BOUNDARYGROUPSITESYSTEMS BGS ON BGS.GROUPID = BGM.GROUPID
ORDER BY BG.GROUPID ASC

🔍SCCM (MECM) RAS Assessment

  SCCM (MECM) RAS Assessment – Comprehensive Checklist 1️⃣ Site Infrastructure & Core Health ✔ Site Server Component Status Site c...