Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.
The agent is entirely DOS and batch file based, even though the world has been vbscript since Windows 2000 and PowerShell since Vista. Kace don't understand why a 64-bit client is needed confirms what I already knew from using this product for 3 years. Kace do not understand the basic environment the tool is used for. I get round the limitations by ignoring the Kace user interface and features and write all my logic in PowerShell, compiled to an EXE to avoid black command screen pop-ups.
Agree, Kace must implement a single place to store credentials and then link them to ALL the various places LDAP authentication is needed, LDAP Labels, LDAP Authentication, LDAP Organisation Filters. You know follow object orientated theory that has been around since the 70's.
Agreed, when you run network monitoring tools you can see the username and password in clear text.