In my house I have 2 computers which I use to manage the Admin Console, the behavior of which is different on each. Both computers show the same Java Version, Update, and Build. If I use my desktop (which Control Panel shows I am using the 32 bit Java), when I start IoX, I have 2 entries each of which is slightly different for the same eisy. If I select the one identified as Local, I get asked to sign in with the eisy password. On my Laptop (which Control Panel shows I am using the straight Java), when I start IoX, I have only 1 entry from which to select. If I select that one, I get asked to sign in with the ISY Portal credentials. Both computers are running Windows 11 Pro.

Can anyone help me understand what is going on?

If you want to log in with the eisy password on both, add a new entry in IoX finder on the laptop. Just click on "Add" and enter the URL identical to the one you use on desktop. The difference is that the entry using the eisy password will have port number 8443 as part of the URL.

@GreyFox My launcher consistently does not have the correct paths showing up.

I have two work arounds that save me a bundle of effort:

1) When local, I connect directly to the EISY w/o using the launcher. To set this up, go to http://<your eisy IP>:8080/admin.jnlp . This will automatically download a shortcut called admin.jnlp. Move this to your desktop. Single click on it will take you immediately to the sign in screen for your local admin / password. This is the ONLY way I sign in when local. Skips the whole clunky Finder step

2) When I am remote, I have to use the Finder, but it doesnt populate consistently or fully. So I manually added every URL that I have to connect to the Eisy, then hit SAVE. I saved this file in an easy location so that each time I open the Start.jnlp finder file, I then hit LOAD and navigate to the file I previously saved. It then "thinks" for about 15-30 seconds and then all my connection options load.

Hope this helps!

@GreyFox there is probably a different value stored in the .state files that UD uses in the temp area on the computer.

Check this part of the wiki: https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored

I think @Guy Lavoie and @dbwarner5 have offered valid suggestions for making them work similarly. If both computers are always local to the system then I would probably lean more toward the direct login as @dbwarner5 outlines.

I've got Win10 and Win11 laptops and use admin console on my local eisy, but also a remote eisy system sometimes. It gets tricky if/when I'm traveling to the remote location as it will find it, but still list the home device (sometimes). There seems to be a real disconnect in IoX Finder window if/when the computer is not on the same network as it will keep some of the cache info, but other times it is blank and/or just finds/lits the local system. I suspect the valuse stored in one of the UD*.state files (probably: udi_launcher.state) is what keeps the addresses stored locally. Since it's in a "temp" file that Windows controls there's no telling when they'll get wiped out.

Saving the list that includes all systems that I might randomly connect to is simple to load if/when the finder comes up without all the options.

Perhaps the one thing I do look forward to with eisy_ui is the lack of unpredectibility of how you'll log in. I just hope remote access is as easy as it has been wirh the java admin console.