- This topic has 2 replies, 2 voices, and was last updated 4 years ago by
.
-
Posts
-
I have a Microsoft RD collection of virtual desktops. I am able to connect to the VDI broker and it locates the correct collection Win10_Desktops. When logging into the thin client however the connection does not auto launch. The user logs in, it authenticates, creates the RDP icon for the Win10_Desktops on the thin client desktop and then stops, making the user have to double click the RDP icon. If i open up the RDP icon properties I can set it to auto connect on sign in but then when the thin client is rebooted that config gets cleared. Is there any way to auto launch the RDP connection when configuring a VDI network connection in the .ini file? I know if i just set up an RDP connection i can configure it to auto launch but when the configuration is VDI and it creates its own RDP i dont see any option to have it auto launch that connection. Below is my .ini for reference with redacted domain info.
VDIBroker=https://access.Domain.org AutoConnectList=Win10_Desktops
ConnectionBroker=Microsoft RDCollections=Win10_Desktops
SignOn=Yes
Domainlist=”Domain”
AddCertificate=RDPcertificate.cer
Addcertificate=intermediate.cer
Addcertificate=certificateauthority.cerAutoConnectList= has to be the exact name of the “published” desktop, not the collection name.
You can try with AutoConnectList=* to autostart all available desktops and then narrow it down with AutoConnectList=Desk*, AutoConnectList=Desktop*, etc.CG
- You must be logged in to reply to this topic.
