Auto IT script Usage For Deployments VS Side Effects
Hi all,
When I am going through some posts, people are mentioning to use Auto IT scripts, We are using SCCM for the deploymnets and I used AutoIT scripts for 2-3 Apps and they got deployed well. Here My doubt is
- usage of Auto IT script is last option if there is a noway for silent Instal?
- What is the successrate in that during the deployment?
- Is it a best practice to use those scripts for the deployment ??
- Is there any precautions to be taken durimg the deployment (Like deploy in the night times because user ll not have any chance to inturrept the installation)
Answers (2)
You are of course free to use Auto-IT if the need arises. I would definitely not consider it to be best-practice though. I've never had to use it and have always been able to use VBS to drive my installations through SCCM.
I would consider the precautions you mention to be good general practice for big installations, but if you can make completely silent installers, the risk of users interrrupting them would be zero. It all depends on the expected load on the environment.
AutoIt was initially designed for PC "roll out" situations to reliably automate and configure thousands of PCs. Over time it has become a powerful language that supports complex expressions, user functions, loops and everything else that veteran scripters would expect.
//- usage of Auto IT script is last option if there is a noway for silent Instal?//
Yes.. If the application can not be packaged and there is no silent switches to make it unattend installation.. then you can go for Auto IT... There is nothing wrong in using it as last option...
You can follow some best practices while creating packages with AutoIT but using AutoIT can not be considered as best practice in application packaging...
