OK, thanks for that but that doesn’t address my question. There are several problems with that approach.
1. Removing “Device Security” also removes positive management control of the device until it “phones home” and sees that the WDM server has removed Device Security. We do not wish to lose positive control.
2. It is my understanding that doing this results in a system reboot on the device and this cannot be managed by device, subnet, or IP-range so we’d have literally thousands of devices randomly rebooting at some point within a certain period of time after Device Security is removed.
3. We are replacing WDM management software with a system wide package that will manage all end-units in the WAN. Therefore purchasing a new Enterprise WDM license for a very short period of time is not a financially advantageous move.
What the hope was is to deploy numerous workgroup versions of WDM and manage the network so that only certain V90s can see certain WDM servers so the 750 device limit of the workgroup edition is not exceeded. This would allow us the ability to manage the devices if we needed to during the very short interval between insourcing the management of our network and the full deployment of the new management software.
So ultimately, we need to be able to disable “Device Security” on the V90 device without doing it from the WDM server that is currently managing that device. Otherwise, this approach as a failover Plan B is dead in the water and certain management level decisions will have to be made.
@ConfGen wrote:
You have to do the following:
– Disable device security on the 3rd party WDM
– Move the device to your WDM server
– Enable device security on both WDM servers againCG