Forum Replies Created
-
Posts
-
I read thoroughly all of the material in “Using VDI with NTLM Authentication and No Connection Broker” and I absolutely love the option- it gives me everything I want for a smooth end user ride– except:
I’m running a mixed environment of RDP connections, phasing out Server 2003 Terminal servers in favor of Parrallels Virtuoso VDI environments with a mix of V10’s and ThinStation PC’s as they die out.
I have a problem logging onto a V10 using NTLM, as an example, if the user password has expired or I have reset the password in AD (server 2003) and forced an immediate password expiration. AD seems to treat the password as invalid as the V10 is unable to launch a Window to force the password change right then. My only choice seems to be to not force the password change after resetting the password, then I have to turn off auto-launching the RDP session to connect to the users VDI so I can force the password change before they go into their VDI, where they can change their password, then set the user’s ini to autolaunch again after that– otherwise I go into a loop.
If users didn’t wait until they see the whites of the eyes of a password change, this would be rare, but I know my people well enough to know I need out of this issue!
Any one else see it or have a solution?
I’m a newbie myself, but I got stuck on a similar problem when I had different configurations in my WDM console than on my DHCP server; the different logins pushed the clients into different directories.
I would reset the unit to factory defaults, it would pull from the DHCP directory, and the later on the WDM console would push a different configuration onto the unit and it would take effect on the next reboot. When I set the WDM server config to the same directory as DHCP, it was like magic!
