I did some lab work to try and reproduce the issue. I don't have an Asustek Ethernet adapter - but I used my raspberry pi connected to a Cisco C9300 switch running device-sensor.
I changed the MAC address of the raspi to look like an Asustek
root@raspberrypi:/home/admin# macchanger --mac=00:0C:6E:01:02:03 eth0
Current MAC: b8:27:eb:2c:50:0c (Raspberry Pi Foundation)
Permanent MAC: b8:27:eb:2c:50:0c (Raspberry Pi Foundation)
New MAC: 00:0c:6e:01:02:03 (ASUSTEK COMPUTER INC.)
And I also created a DHCP request that looks like a Windows DHCP request.
/etc/dhcp/dhclient.conf
send host-name DESKTOP-YT66D2F;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
send vendor-class-identifier "MSFT 5.0";
send dhcp-client-identifier 1:00:0c:6e:01:02:03;
The result is that my IE 3.2 p2 deployment correctly profiles the device as a Microsoft-Workstation. Since I don't have an AD, I can't profile my endpoint more accurately (e.g. Windows10) - but at least it's not stuck on Asus-Device.
CORE01#show device-sensor cache interface gi 1/0/22
Device: 000c.6e01.0203 on port GigabitEthernet1/0/22
----------------------------------------------------------------------------
Proto Type:Name Len Value Text
DHCP 61:client-identifier 9 3D 07 01 00 0C 6E 01 02 03 =....n...
DHCP 60:class-identifier 10 3C 08 4D 53 46 54 20 35 2E <.MSFT 5.
30 0
DHCP 50:requested-address 6 32 04 AC 16 80 B2 2.,.^@2
DHCP 12:host-name 17 0C 0F 44 45 53 4B 54 4F 50 ..DESKTOP
2D 59 54 36 36 44 32 46 -YT66D2F
And the Endpoint in ISE
AAA-Server labise02
AllowedProtocolMatchedRule Default
AuthenticationIdentityStore Internal Endpoints
AuthenticationMethod Lookup
AuthenticationStatus AuthenticationPassed
AuthorizationPolicyMatchedRule Default
BYODRegistration Unknown
Called-Station-ID F8-B7-E2-4F-57-16
Calling-Station-ID 00-0C-6E-01-02-03
ClientLatency 0
DTLSSupport Unknown
DestinationIPAddress 172.22.137.12
DestinationPort 1812
Device IP Address 172.22.136.1
Device Type Device Type#All Device Types#SWITCH
DeviceRegistrationStatus NotRegistered
ElapsedDays 0
EndPointMACAddress 00-0C-6E-01-02-03
EndPointPolicy Microsoft-Workstation
EndPointProfilerServer labise02.rnlab.local
EndPointSource RADIUS Probe
EndPointVersion 196
FQDN raspberrypi.rnlab.local.
FailureReason -
Framed-IP-Address 172.22.128.178
Framed-IPv6-Address fe80::1d20:83:6e62:a123
IPSEC IPSEC#Is IPSEC Device#No
IdentityGroup Workstation
IdentityPolicyMatchedRule Default
IdentitySelectionMatchedRule Default
InactiveDays 0
IsThirdPartyDeviceFlow false
Location Location#All Locations
MACAddress 00:0C:6E:01:02:03
MatchedPolicy Microsoft-Workstation
MessageCode 3002
NAS-IP-Address 172.22.136.1
NAS-Identifier CORE01
NAS-Port 50122
NAS-Port-Id GigabitEthernet1/0/22
NAS-Port-Type Ethernet
Name Endpoint Identity Groups:Profiled
Network Device Profile Cisco
NetworkDeviceGroups Device Type#All Device Types#SWITCH, IPSEC#Is IPSEC Device#No, Location#All Locations
NetworkDeviceName CORE01
NetworkDeviceProfileId b0699505-3150-4215-a80e-6753d45bf56c
NetworkDeviceProfileName Cisco
OUI ASUSTek COMPUTER INC.
OriginalUserName 000c6e010203
PolicyVersion 17
PostureApplicable Yes
PostureAssessmentStatus NotApplicable
PreviousMACAddress 00:0C:6E:01:02:03
RadiusFlowType WiredMAB
SSID F8-B7-E2-4F-57-16
SelectedAccessService MAB
SelectedAuthenticationIdentityStores Internal Endpoints
SelectedAuthorizationProfiles MAB_PERMIT_ALL
Service-Type Call Check
StaticAssignment false
StaticGroupAssignment false
StepData 5= Normalised Radius.RadiusFlowType, 7=Internal Endpoints, 12= EndPoints.EndPointPolicy
Total Certainty Factor 30
TotalAuthenLatency 1
UseCase Host Lookup
User-AD-Last-Fetch-Time 1685107210384
User-Fetch-User-Name 00-0C-6E-01-02-03
User-Name 00-0C-6E-01-02-03
UserType Host
allowEasyWiredSession false
chaddr 00:0c:6e:01:02:03
ciaddr 0.0.0.0
dhcp-class-identifier MSFT 5.0
dhcp-client-identifier 01:00:0c:6e:01:02:03
dhcp-message-type DHCPREQUEST
dhcp-parameter-request-list 1, 28, 2, 3, 15, 6, 119, 12, 44, 47, 26, 121, 42
dhcp-requested-address 172.22.128.178
epid epid:248796463613620224
flags 0x0000
giaddr 172.22.128.1
hlen 6
host-name DESKTOP-YT66D2F
htype Ethernet (10Mb)
ip 172.22.128.178
op BOOTREQUEST
yiaddr 0.0.0.0
Maybe you can share some of your endpoint data and profiling information - to compare notes.
