Unsolved
1 Rookie
•
2 Posts
0
51
January 16th, 2025 15:29
Wyse WMS Groups - RDS 2019 and Published RemoteApp Autoconnect does not work
Hello!
We are using WMS 4.4
Wyse Thin Clients are placed in the correct WMS Group using DHCP Scope Options.
We are now in a project to migrate many old ThinOS 8 clients from WS2012 R2 RDS to WS219 RDS.
They are currently using old style "mac.ini" files with all configurations set.
Autoconnect option works flawlessly in WS2012 R2 RDS environment with below Brokersettings
VDIBroker=https://rdwa.domain.com AutoConnectList="App1"
ConnectionBroker=Microsoft
SignOn=Yes
DomainList="domainname"
We have published a remote app in the new RDS Collection and set the options to autoconnect in the new WMS Group Policy.
Microsoft Broker
Broker Server = https://rdwa.domain.com
Sessions to connect automatically = RDSCollection
Advanced Settings:
AutoConnectList=msedge
However when we logon to the client we only get the RemoteApp listed on the Sidebar.
It does not autoconnect no matter how we try.
Any solution suggestions ?
Br / Tony
fahlis64
1 Rookie
•
2 Posts
0
January 16th, 2025 18:16
One thing I did noticed.
When using admin mode in the thin client (5010) and going to settings-properties for the remoteapp the is an option "Auto-connect on start-up" which is not marked. When I activate it and logoff-logon or reboot-logon as a user it does not stick. I do believe it will auto-connect the RemoteApp if I can get it to stick after a reboot.
In the WMS Groups Policy it's set to auto connect from what I can tell.
How can I solve that ?