-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David,
For LDAP authenticated accounts, VCL does not store the user's password. This is by design for privacy and security reasons. An option I have heard about is to write a small windows utility application that either handles .rdp files or rdp:// URLs. The utility is then installed and registered to handle the desired type. When a user then clicks the Get RDP File button, the utility reads the (VCL generated) password from the data, stores it in the windows credential store, and runs Remote Desktop Connection, which can then get the credentials from the store and automatically log the user in to the session. If the utility is written to handle rdp:// URLs, then the VCL code would need to be modified to deliver something like "rdp://username@password:hostname?extra=parametersHere" when the Get RDP File button is clicked. I'm not a windows coder. So, writing one of these utilities is not something I've tried to do. Josh On Monday, December 02, 2013 8:19:52 AM David DeMizio wrote: > Hello, > > I'm curious if anyone is joining the provisioned VMs(reservations) as part > of their Windows Domain and if so, how are computer names being handled? > At the moment, our Windows image has the same host name which would present > a problem if the reservations were allowed to join a Domain. Also, if it is > possible, is it also possible to just pass the user name and password to > the RDP session from the ldap login that the user logged in with? Thank You - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKc01MACgkQV/LQcNdtPQO9/QCdGMeQOraMseA0FUkzQRkJYjyv h/QAni0bUZMubJXDUCu9cXHva//BPLnk =RxdI -----END PGP SIGNATURE-----
