VBScript or HTA for Scripting
Guys, good afternoon.
I work in the Service Desk area and use a system similar to Microsoft's SCCM, called Kace, from Quest.
The same thing is done from Asset Management to Software Management, and today we use a script process inside the System, but it is plastered and we can not use it very well.
I thought of using the same with scripts in VBScript or HTA Application, what do you recommend me?
Remembering that my goal is to install software on a person's computer, which has no knowledge of IT (I'll send some "script" for this system, which will install a program, for example Google Chrome, and I'll just let him know at the end of the process).
Thanks!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
Pressanykey
7 years ago
Hi,
the best bet is to have a "Framework" around your actual installation packages (MSI, Legacy, pure vb / powershell script) that allows you to have a consistent interface towards your deployment tool (in this case Kace).
A good starting point is the PowerShell Application Deployment Toolkit which I use (albeit heavily customised). I'm sure others here (VBScab etc.) will also have suggestions... You will have to get your hands dirty and I recommend getting on a course or do some self-study as having the ability to create (good) scripts is always a benefit.
Cheers
Phil
Comments:
-
Phil, thanks for your reply! I think my problem is different version types in my organization. Example: i put in User Download a Office 2013 x86. The final user click on User Download, and "install", but the install never install correctly. And i when i debug, i found machines with the Office 2010 x64, and Ms Lync x64 too.
Finally, i don't install that software,
and I have complaints about this.
Power Shell its a best option for script in this case? - lpansarini 7 years ago
Posted by:
anonymous_9363
7 years ago
the install never install correctly
Why do you imagine that wrapping your installation in script will magically make the deployment work? Besides, you will never - EVER - build a better system than a commercially available system such as Kace or SCCM in script.
Pretty much every installation system such as Windows Installer can create a log. Only fools run their deployments without enabling a log, as troubleshooting without one is impossible. So, have the installation create a log and use that to determine what's going wrong. Then, fix the package.
Having said that, Phil is bang on the money, in that learning script will serve you in good stead for the future as, sometimes, a QAD (quick and dirty) script is all you need.
Comments:
-
I agree with you. But I believe my problem might be to understand the logs. And get some of my problems in those logs. - lpansarini 7 years ago
Posted by:
anonymous_9363
7 years ago
my problem might be to understand the logs.Uh huh. And there'd be nowhere where you could ask a question about it, would there?
Posted by:
nagendrasingh
7 years ago
You need to send out a deployment that is silent as most people would not know what to click on.
For the failed one, try to locate a pattern. All failed are laptops, all failed had less than 4 gb ram etc. You should be able to find it from the logs created by the installer.
For the failed one, try to locate a pattern. All failed are laptops, all failed had less than 4 gb ram etc. You should be able to find it from the logs created by the installer.
