https://community.cisco.com/t5/network-access-control/device-profiled-as-microsoft-workstation-instead-of-more/m-p/3897804#M471054 <P>I have created sub-policy to Microsoft-Workstation that looks for the same attributes, but adds in DHCP host-name. The devices are still getting profiled as Microsoft-Workstation instead of 'SJ-Desktop' even though they clearly meet the host-name criteria. I've attached the profile, but I've tried to make sure the certain factor is greater than what the deviec is getting from the Microsoft-Workstation profile.&nbsp;</P><P>&nbsp;<span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.PNG" style="width: 341px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41917i87EFBBC4E20439DC/image-size/large?v=v2&amp;px=999" role="button" title="1.PNG" alt="1.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.PNG" style="width: 999px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41919i2D173E031B708C98/image-size/large?v=v2&amp;px=999" role="button" title="2.PNG" alt="2.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3.PNG" style="width: 929px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41918i6A32AB2C2FAF5FC4/image-size/large?v=v2&amp;px=999" role="button" title="3.PNG" alt="3.PNG" /></span></P> Thu, 25 Jul 2019 18:34:41 GMT Josh Morris 2019-07-25T18:34:41Z https://community.cisco.com/t5/network-access-control/device-profiled-as-microsoft-workstation-instead-of-more/m-p/3897804#M471054 <P>I have created sub-policy to Microsoft-Workstation that looks for the same attributes, but adds in DHCP host-name. The devices are still getting profiled as Microsoft-Workstation instead of 'SJ-Desktop' even though they clearly meet the host-name criteria. I've attached the profile, but I've tried to make sure the certain factor is greater than what the deviec is getting from the Microsoft-Workstation profile.&nbsp;</P><P>&nbsp;<span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1.PNG" style="width: 341px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41917i87EFBBC4E20439DC/image-size/large?v=v2&amp;px=999" role="button" title="1.PNG" alt="1.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2.PNG" style="width: 999px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41919i2D173E031B708C98/image-size/large?v=v2&amp;px=999" role="button" title="2.PNG" alt="2.PNG" /></span><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3.PNG" style="width: 929px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/41918i6A32AB2C2FAF5FC4/image-size/large?v=v2&amp;px=999" role="button" title="3.PNG" alt="3.PNG" /></span></P> Thu, 25 Jul 2019 18:34:41 GMT https://community.cisco.com/t5/network-access-control/device-profiled-as-microsoft-workstation-instead-of-more/m-p/3897804#M471054 Josh Morris 2019-07-25T18:34:41Z https://community.cisco.com/t5/network-access-control/device-profiled-as-microsoft-workstation-instead-of-more/m-p/3897929#M471055 A few things to consider/keep in mind when attempting to use profiling to your advantage are:<BR />-Some will say to not use the Cisco defaults and to create your own.<BR />-If creating your own increase your MCF to something higher than some of the other default ones. Without looking I am assuming the default policy MCF is higher than the one you are trying to create.<BR />-A device can get re-profiled and cause no harm unless you are pushing policy based on profiled endpoint groups<BR />My recommendation would be to ditch the Cisco default as your parent and start focusing on your own parent policy with child policies. Good luck &amp; HTH! Thu, 25 Jul 2019 23:23:36 GMT https://community.cisco.com/t5/network-access-control/device-profiled-as-microsoft-workstation-instead-of-more/m-p/3897929#M471055 Mike.Cifelli 2019-07-25T23:23:36Z