Reposting my previous comments for greater visibility....

Dear customers,

Just a quick update on the K1000 v5.3 agent release that we wanted to share with everyone:

The agent restructuring that took place over the 5.1 thru 5.3 versions was a critical step in the evolution of not just our agent technology but our entire K-Platform, openly speaking - a necessary one for our growing Windows 7 customer base. Given the major changes that took place in 5.3 and the complexity of testing for many different deployment environments, we anticipated issues to be discovered upon release. However, we felt it more important to release the agent technology earlier rather than later to address the urgent needs of our customer’s complex environments.

Unfortunately, the number of issues reported from the field is higher and more serious than anticipated, leading some to question the quality of our product and processes. We wish to assure everyone that we are working diligently to address those concerns, both short- and long-term, and most importantly iterate on the new agent technology as fast as we can to reach the robustness levels everyone expects of us. Our goals are to establish those levels as fast as possible and at the same time eliminate the technology anchors associated with the previous agent versions.

While we wish that all of the issues were avoidable, that's simply not the reality of the agent arena and certainly not the reality of such a major engineering over haul. We continue to take measures to improve our processes and ensure, as best we can, the mitigation of out of band negative consequences to our customers. We do not anticipate any major changes to our agent technology in the near future, and are now working very hard to ensure all agent quality issues are addressed in an expedient manner. At the same time, we are excited to be finally fully operating on the new core agent platform and start providing the functional returns on that substantial investment to our customers/users.

At this time, we recommend for our customers on v5.3 to upgrade to the latest server (5.3.47927) and agent (5.3.47657) versions, which contain a number of bug fixes addressed since v5.3 was first released (see release notes for details). There are still a small number of outstanding issues that our team is working to resolve (see partial list below) as part of a patch we plan to release in November. Some customers may want to wait for the November update if the issues below are important to them.

List of known outstanding 5.3 issues:

• Current logged-in user not always detected
• Inventory not picking up some installed software attributes
• Command prompt temporarily pops up on user PCs when running file synchronizations
• Clean Up/Deletion of Managed Install installation files after execution
• UVNC push failures in certain situations
• Access errors when script has to read/write to network share
• MI with EXE returning false to server when actually the install was without error

Lubos Parobek
VP Product Management
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity