- This topic is empty.
-
Posts
-
Hi All,
I’m new to VDI and trying to get past this issue I’m having.
I have a Hyper-V host and 3 VMs running on it. Two of the VMs are Windows 7 and one is 2008-r2 with connection broker installed. I’ve assigned two test users to the two VMs in connection broker. I’ve been able to go to the http:\serverrdweb and log in as one of the users and bring up the windows7 client vm that was assigned to them.
I have about 100 C10LEs running for the past 9 months without an issue. They are all set up with RDP connections to assigned servers.
What I would like to do is introduce some dedicated Windows7 VMs to certain users.
I’ve manually set up a C10LE to use the microsoft broker and I get the Remote Desktop Services logon. I’ve also set up the necessary certificates on the device as well.
I’ve set up a $username.ini profile for the users and entered the microsift broker information in the network section.
I also added some remote apps to the remote app web server / connection broker.
When I log into the device as that user I see it connecting, I’m assuming to the broker?? All the remote apps appear that I expect. I see a connection to the rdi broker. When I click on that I get connected to the server.
I then created an RDP connection to the Windows7 VM assigned to the user in the $username.ini file. When I log into the C10LE again as that user I see the connection and my Windows 7 VM appears.
My question is, is this how it should work, or did I circumvent the correct process? I’ve even installed TCX and connected a USB device.
I guess I thought that once I logged into the connection broker the Wyse software would recognize that user and bring up their Windows 7 box automatically. It looks like one needs to create an RDP connection with Autologin set on?
I’d appreciate it if someone could let me know if this is the right way.
Thanks,
–KevinThe problem will be that you are logging in to the C10 and the used username is THEN passed to the username.ini file. Therefore the login process is already running while the unit gets a different/new connection broker.
This will not work as the CB is handed to the unit to late.
Have you tried to put it in the wnos.ini instead?CG
Hi CG,
I’m reluctant to do that as I have about 100 users / device setup / running as a terminal server /RDS . If I put the CB info in the wnos.ini file wouldn’t that make all the devices point to the connection broker. I’ve manually set up one device to point to the CB, which I’m testing on.I’ve built a new virtual CB and adjusted settings on the test device to point to that one. A lot of my problems have gone away. When I log into the device using the test users I see one connection set up. When I click on that connection, the Win7 box will start up. I’ve been able to attach several USB devices (a printer, a smartboard, CD/DVD).
What is the behavior that I should see once the device is set up the right way? Should it start up, log into the win7 box, and present the desktop with no further user intervention after the initial WYSE log in screen?
Thanks
Kevin
- You must be logged in to reply to this topic.