@Dashrender I'm a 3rd party to the end customer here. Acting as the middle man as the customer's IT department wanted to engage outside support to try and vet different products.
I candidly told the customer that while this product will work, it won't work with all of the features they want without some substantial changes to their infrastructure and that the support (at least from this vendor) is pretty awful.
The simple approach here is to not integrate RFID/HID's to the system and simply use the AD Integration with the built-in QR codes that each member is assigned.
Just because something may be supported, doesn't imply that it is support.
Except in this case the vendor very clearly has stated they support you adding custom attributes within AD.
@travisdh1 Yeah I'm thinking what happened is someone setup a Unifi Controller on windows at some point, then they engaged us and said yeah we don't have access to the AP's but its all still working. So they were sold a physical cloud key, and still the AP's weren't adopted.
Assuming you're at an MSP now, do you host a controller that you could just build a new site for and adopt the APs too?
By default, installing MicroSIP using Chocolatey causes the install to go to an inappropriate data folder location and is only available for the admin installing user, rather than for the end users of the Windows system. Does anyone have any experience or ideas in changing the installation location so that system users can actually use MicroSIP when installed and maintained using choco?