Need to exclude Server CIs from being created/updated from SCCM Imports
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
So we have a situation where servers are being cloned. Against the advise given we are told they can't use syspred prior to cloning them.
This of course as cause us issues with CI's being updated incorrectly because both the old and the new cloned server have information in the registry like Serial Number that link them to the wrong CI.
Professional Services decided that as they were helping with a project that included setting up the AWS Service Graph connector that the solution was to go to the the SCCM Service Graph Connector and add the following to the Computer Identity data source:
"WHERE v_GS_SYSTEM.SystemRole0 = 'workstation'
I am just wonder if maybe someone here has a better solution. It just seems a little odd to me that they suggested adding this to only that one data source.
We are now having issues with a lot of partial payloads and having to reinstall and reconfigure SCCM so it is a good time to revisit this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday - last edited Tuesday
It seems this change has been planed from this community post: Azure Virtual Desktops (AVD) discovering as Server class in SG-SCCM
"We have separate SCCM Site servers for Servers and Workstations. So, in the Data Source for importing from the Workstation SCCM Site server we just hardcoded the role assignment in the SQL statement.
This line in the SQL Statement:
v_GS_SYSTEM.SystemRole0 as SystemRole"
