How can I verify successful deployment of files to servers, short of using MSIs for deployments? MSIs can have verification audits set of echo back results to the LANDesk Core server, but some of my deployments use loose files, I need to use the Custom deployment method, yet still confirm successful release to over 3000 servers in one night.
As you probably know, results on a LANDesk Core Server for file Distribution and Deployment (installation) using Custom methods does not guarantee files have been applied for the complete release. Issues occur during the Installation phase, such as server services preventing files from being replace; systems are found to be unstable; a release is partially applied release and; network and system availability is not guaranteed. In many instances, failure to deploy (script does not complete in full) is not echoed back to our Core LANDesk server, so we have to assume success, yet we may find files do not get installed successfully. Simply I needs a verification method and best practice for loose file distribution.
Additionally, for release we have a time constraint for the solution. My understanding is that the LANDesk Audit features require time to gather the data for a complete environment. This is useful for licensing and continuous improvement activities, but not useful for Release. Release is very time sensitive, requiring us to report on demand results across all clinics the status of releases. I have also used point solutions to do a MD5 Hash checksum against a single file in a larger release, but that does not provide guarantee that the other files in that release do not get there, plus has proven to provide no results where systems are too busy to report back to a central file share.
So, with the above context, my challenge to your support team is to help me find a way to build a reusable method to verify with Six Sigma accuracy a report to verify the status of a Custom Script Deployment release. This report will confirm all the associated files, folders and services are receive and replaced/installed successfully, or report failure back to the Core server which we can run on demand as a release progresses to completion?
I am not sure if I am asking a question Support can answer or not. Can you help align me with someone who can advise me how I should proceed?