The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. This technology has been assessed by the Section 508 Office and found non-conformant. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. Users must ensure sensitive data is properly protected in compliance with all VA regulations. Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 61 VA Directives 6004, 6513, and 6517 and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). This assessment covers both editions and contains language geared towards each individual edition.
This technology is available in a Free Edition and an Enterprise Edition. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: This entry covers the Desktop Edition of this technology and not any mobile versions. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e.
This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This assessment covers both the Free and Enterprise editions of this technology. The product is not Federal Information Processing Standard (FIPS) 140-2 validated and uses Advanced Encryption Standard (AES) algorithm to protect local files and sensitive data in the database but supports several FIPS 140-2 validated credential storage options. Remote Desktop Manager uses a credential repository (SQLite by default) for automated login for the various sessions it supports. This technology leverages existing technologies and third party software add-ons such as Secure File Transfer Protocol (SFTP), Microsoft Remote Desktop, Citrix ICA (Independent Computing Architecture), RVTools, SecureCRT, HP iLO (Integrated Lights Out), SCCM (System Center Configuration Manager) Remote Control, VMware Horizon View Client, DameWare, and others. Remote Desktop Manager is an application for centralizing and managing system connections and credentials. More information on the proper use of the TRM can be found on the "RDP.EXE /wait /fullscreen /v: must be operated and maintained in accordance with Federal and Department security and
"RDP.EXE /wait /fullscreen /v: /domain:thinnet /ontop /noclose /wait /drives:-c,-z /noprinters /u:Thinnet\" Really it is a wrapper around the MSTSC client. It allows LOTS of command line qualifiers to get the behaviour you are after and hide stuff you don't need. What I have used in the past with HP ThinShell is a great free utility from
It wants to collect credentials before connection, so it can pass then to any gateways and servers. This is different from the old client that did not ask until you were connected to the server. The issue I believe you are fighting with is that Micosoft RDP client (MSTSC) is not particularly nice when the device is not in the domain. The RDP client is not as feature rich on ThinPro as it in in WES7, but if it does what you need and you are happy with it - go for it.
So if you are using ThinShell, you don't use/need connection manager.īUT - If you want ThinPro, V4.4 will install onto the T5740.