Azure Virtual Desktops (AVD) discovering as Server class in SG-SCCM

[garyminnick]

We have some VM's which are Azure Virtual Desktops (AVD) and they are a multisession VM. They are based on a multisession Windows OS image that does have server elements because it can allow multiple user sessions per VM but is still a client OS. The System Role that SCCM pulls from these are the 'Server' role. As I understand it from our AVD support team, that is how Microsoft defines these systems in regard to System Role and have no plans to change that. Because of this, when SG-SCCM imports these computers, they will be put in the Server class because from what I can tell SG-SCCM uses System Role to determine the class. Is anyone else running into this issue and have a solution?

[mamtameshra]

Hi,

We too faced the same issue. 

As this is from manufacturer, its comes as product type 3 (which is same as server), it creates in Server class.

We wrote rule to classify them as Computer.

[abdelkader1971]

Hi,

We are having the same behaviour.

How did you do the configuration is ServiceNow to classify them as workstation?

Many thanks

[garyminnick]

Here is what we wound up doing.

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

Can be changed to

"Workstation" as SystemRole

This only worked because we have different Site servers between workstation and servers.