- This topic has 4 replies, 2 voices, and was last updated 2 years ago by
.
-
Posts
-
Dear all,
Need some help. I’ve built a parallel WMS 3.7 servers and DHCP/DNS discovery points to it. I’ve upgraded all of my Win10 IoT clients to WDA 14.6 latest (as of writing).
If I go onto a client, and unregister it or clean the management state, and hit register the auto registration works great. However, I can’t seem to get this to occur automatically. E.g. if I leave it for days, it won’t do anything, until I click autodiscover.
Is there anything I am missing? Is there a command line to trigger WDA server discovery? How best I am to get my clients to bulk migrate from old server to new server? The old and new WMS are completely separate configs, e.g. no backup and restore of the DB.
Thanks!
A reboot will trigger a discovery. If you reboot, will your device register? Also, UWF is enabled?
A reboot doesn’t seem to do it, which is the frustrating problem.
UWF is currently enabled. From what I can tell, the UWF excludes the WDA configuration folders so I don’t believe this is a problem? I could be wrong.
I’ve got auto discovery in DHCP and DNS. DHCP was already present, but I added DNS to see if it would help, but it hasn’t. I saw a previous comment saying you should not have both. Is one more reliable than the other?
What is the best way to force? Do I need to unregister my hosts from the old WMS server, force a reboot and it should just automatically work?
Think I understand the issue now. The group configuration in DHCP was done by another admin, and they matched what WMS says, which is defaGROUPNAME.
However, this seems to be the problem, as it should be defa-GROUPNAME as per what WDA shows. Does this seem correct?
- You must be logged in to reply to this topic.