you dont usually mix workstations and servers in one collection. this is unusual. you should have two different collection then use two deployments in which you have different configurations.How does the Device Restart Behavior in a Deployment know if a machine is a Workstation or Server?
I can't seem to find where to set Device Type that correlates with these two options.
This is not what I am asking. I am trying to understand what settings Device Restart Behavior uses to determine if a machine is a "Server" or "Workstation." Please see the screenshot attached.you dont usually mix workstations and servers in one collection. this is unusual. you should have two different collection then use two deployments in which you have different configurations.
I would think it was based on the OS as the OS will tell you if it is a workstation or server.This is not what I am asking. I am trying to understand what settings Device Restart Behavior uses to determine if a machine is a "Server" or "Workstation." Please see the screenshot attached.
I thought this too, however my none of my Servers were suppressed. I looked through Microsoft documents and didn't see any mention as to how this exactly works.I would think it was based on the OS as the OS will tell you if it is a workstation or server.
My guess is there are two deployments to the client then and the one that doesn't block the reboot is happening. I'm guessing of course but the logs would tell you for sure.I thought this too, however my none of my Servers were suppressed. I looked through Microsoft documents and didn't see any mention as to how this exactly works.
Thank you, I will check. Which logs cover this?My guess is there are two deployments to the client then and the one that doesn't block the reboot is happening. I'm guessing of course but the logs would tell you for sure.
Thank you for thisHere is the list of log and what each of them do.
![]()
Log file reference - Configuration Manager
A reference of all log files for Configuration Manager client, server, and dependent components.learn.microsoft.com