Automating Windows
Hello.. I was wondering what you ar all using to automate Windows.
I'm having some issues automating Windows. I've tried using Autoit, unfortunately this gives me some issues when deploying using SMS 2003. When i deploy using SMS, i usually use VBscripts. Calling Autoit scripts in these vb scripts doen't really seem to work, so i was looking at automating using vbscript.. I've come up with this script:
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
On Error Resume Next
WshShell.Run"setup.exe -uninst -s -l0009",1,true
' Uninstalls app..
Wscript.sleep 400
Wshshell.AppActivate "setup"
WshShell.SendKeys "j"
' Confirms the deletion messagebox
Wscript.Quit(0)
However, i can't get this to work properly.. The uninstall runs, but stalls on the removal confirmation window. With or without the timeout (sleep). Offcourse, i can repackage the uninstall itself, but that doesn't feel like a good solution to me.. :P Any suggestions..?
I'm having some issues automating Windows. I've tried using Autoit, unfortunately this gives me some issues when deploying using SMS 2003. When i deploy using SMS, i usually use VBscripts. Calling Autoit scripts in these vb scripts doen't really seem to work, so i was looking at automating using vbscript.. I've come up with this script:
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
On Error Resume Next
WshShell.Run"setup.exe -uninst -s -l0009",1,true
' Uninstalls app..
Wscript.sleep 400
Wshshell.AppActivate "setup"
WshShell.SendKeys "j"
' Confirms the deletion messagebox
Wscript.Quit(0)
However, i can't get this to work properly.. The uninstall runs, but stalls on the removal confirmation window. With or without the timeout (sleep). Offcourse, i can repackage the uninstall itself, but that doesn't feel like a good solution to me.. :P Any suggestions..?
0 Comments
[ + ] Show comments
Answers (16)
Please log in to answer
Posted by:
Francoisracine
17 years ago
Depends of what you mean by automating WIndows.
In order:
1. Always using the installer provide by the manufacturer (installshield commandline, Windows installer, /s, /S, /q, /Quiet,...
2. Snapshot the installation process and see if it is not too risky
3. Winbatch... better than autoit.
In order:
1. Always using the installer provide by the manufacturer (installshield commandline, Windows installer, /s, /S, /q, /Quiet,...
2. Snapshot the installation process and see if it is not too risky
3. Winbatch... better than autoit.
Posted by:
neo2000
17 years ago
Well, it's a package that has been installed using silent commandline. Unfortunately, the package doesn't support full silent uninstall. It would have been better to repackage the entire app, but if it works, why repackage, right?
When uninstalling, it shows a "removal confirmation" dialog box. When a users clicks "yes", the program is removed. Have the same issues with several software packages, even with some packages i have repackages myself (i.e. ActiveSync 3.8, it askes the user if it wants to remove synchronised files and folders) so that's why i was wondering wat other users of Appdeploy.com use. [:D]
Doen Winbatch work without issues..? I mean, i can get AutoIT to work, but have some issues when deploying Autoit scripts (compiled to executable) using sms 2003. I will have a look at Winbatch..
When uninstalling, it shows a "removal confirmation" dialog box. When a users clicks "yes", the program is removed. Have the same issues with several software packages, even with some packages i have repackages myself (i.e. ActiveSync 3.8, it askes the user if it wants to remove synchronised files and folders) so that's why i was wondering wat other users of Appdeploy.com use. [:D]
Doen Winbatch work without issues..? I mean, i can get AutoIT to work, but have some issues when deploying Autoit scripts (compiled to executable) using sms 2003. I will have a look at Winbatch..
Posted by:
Francoisracine
17 years ago
Winbatch is far better than autoit.
What is the uninstall commandline?
In some case, effectively, the uninstall will not be completely silent. Then you will need to start a script waiting for the "yes" window and click on the button it is rare.
In fact repackaging should be the the last solution as the best installer is always the one provide by the manufacturer.
What is the uninstall commandline?
In some case, effectively, the uninstall will not be completely silent. Then you will need to start a script waiting for the "yes" window and click on the button it is rare.
In fact repackaging should be the the last solution as the best installer is always the one provide by the manufacturer.
Posted by:
neo2000
17 years ago
The uninstall commandline is:
setup.exe -uninst -s -l0009
I *know* it's an installshield setup. However, using answerfiles isn't supported by the uninstaller/installer. Keeps bugging me with those confirmation messages.
I'll have a look @ Winbatch
setup.exe -uninst -s -l0009
I *know* it's an installshield setup. However, using answerfiles isn't supported by the uninstaller/installer. Keeps bugging me with those confirmation messages.
I'll have a look @ Winbatch
Posted by:
Francoisracine
17 years ago
Which software name and version?
What commandline did you tried?
What commandline did you tried?
Posted by:
neo2000
17 years ago
The software is Automanager teamwork 2004d. The installation commandline is simply "Setup -s -l0009".
Setup reads from the setup.iss file. Installation works completely silent. I then recorded another ISS file for deinstallation. First strange thing is that setup.exe can't handle different ISS files. It looks for the file setup.iss, but switches like /f1 or /f to specify another ISS file don't work. So i created another directory on the server (same content) and placed the recorded setup.iss uninstall answer file in there. Does work, but doesn't skip the confirmation dialogue box.
Commandline for uninstall: "setup.exe -uninst -s -l0009"
If i don't use the answer file, setup isn't silent at all..
Setup reads from the setup.iss file. Installation works completely silent. I then recorded another ISS file for deinstallation. First strange thing is that setup.exe can't handle different ISS files. It looks for the file setup.iss, but switches like /f1 or /f to specify another ISS file don't work. So i created another directory on the server (same content) and placed the recorded setup.iss uninstall answer file in there. Does work, but doesn't skip the confirmation dialogue box.
Commandline for uninstall: "setup.exe -uninst -s -l0009"
If i don't use the answer file, setup isn't silent at all..
Posted by:
Francoisracine
17 years ago
Sometimes, I need to record another iss to uninstall the software then copying it to %systemdrice% then starting setup -s -f1 %systemdrive%\setup.iss
Posted by:
tethys
17 years ago
Try "Automation Anywhere". You can get more information on http://www.tethyssolutions.com/automation-software.htm
There are many examples of windows automation at http://www.tethyssolutions.com/automation-samples.htm
-James
There are many examples of windows automation at http://www.tethyssolutions.com/automation-samples.htm
-James
Posted by:
smason
17 years ago
ORIGINAL: Francoisracine
Winbatch is far better than autoit.
I'd love to hear more about why you think so. I'm not disagreeing, I'm just interested in your opinion.
I've been using Winbatch for a while, and like it. I just discovered Autoit. I'm not a programmer so I don't do anything too fancy.
I find Autoit much better at tracking Windows, and clicking buttons.
Posted by:
Secondlaw
17 years ago
While I also like Winbatch, it comes with a hefty pricetag (with compiler). Auto-it is free.
Winbatch comes with a great built in Debugger where you can step through your script line by line. For people like me who type faster than I think, it comes in very handy when trying to troubleshoot. AutoIt doesn't come with a debugger but someone did create a pseudo debugger (requires .net 2.0 I believe).
I think Winbatch is easier to work with. I think Winbatch's webboard is amazing. Everyone is so fast to help. Even if you call them on the phone, they are always right on top of things.
Winbatch comes with a great built in Debugger where you can step through your script line by line. For people like me who type faster than I think, it comes in very handy when trying to troubleshoot. AutoIt doesn't come with a debugger but someone did create a pseudo debugger (requires .net 2.0 I believe).
I think Winbatch is easier to work with. I think Winbatch's webboard is amazing. Everyone is so fast to help. Even if you call them on the phone, they are always right on top of things.
Posted by:
elziarun
16 years ago
Hi,
Do anyone have any idea about converting an AutoIt installation of an application to a repackaging installation?
Thanks,
elziarun.
Do anyone have any idea about converting an AutoIt installation of an application to a repackaging installation?
Thanks,
elziarun.
Posted by:
anonymous_9363
16 years ago
There are no import/conversion tools I know of so you'll need to capture it in your authoring tool of choice.
Posted by:
MicrosoftBob
16 years ago
In fact repackaging should be the the last solution as the best installer is always the one provide by the manufacturer.
[:D][:D][:D] did you say "always"???? [:D][:D][:D]
Posted by:
aogilmor
16 years ago
ORIGINAL: MicrosoftBob
In fact repackaging should be the the last solution as the best installer is always the one provide by the manufacturer.
[:D][:D][:D] did you say "always"???? [:D][:D][:D]
I'm quite sure he didn't mean that literally... :-)
Seriously though, there may be organizations where it just doesn't pay to repackage stuff...I don't know what that size is, but I'd suspect that somwhere around <100 people (or desktops/laptops) you're going to have one dedicated IT guy who can do support, maintain the servers, networks, logon scripts, policies, install software, BUT there's no way that single guy still has time to repackage stuff, and also repackaging tools are pretty expensive for smaller companies or organizations like that.
In larger organizations the expense/time of simply the mouse clicks alone, never mind sending desktop techs, maintaining the apps, etc. definitely justifies a repackaging standard of some kind. Right now I'm working at a 20,000 desktop/laptop organization, but it probaby is definitely worth it at several hundreds of desktops.
Posted by:
aogilmor
16 years ago
If I were you I'd do some research and just manually delete the files/directories, reg entries and add/remove cpl entries rather than trying to futz around with setup.exe -uninst. That's a very old installshield installation most likely. I've had very little success getting these to work on modern (> win2000) operating systems but have had success in manually deleting technique.
Posted by:
MicrosoftBob
16 years ago
If I were you I'd do some research and just manually delete the files/directories, reg entries and add/remove cpl entries rather than trying to futz around with setup.exe -uninst. That's a very old installshield installation most likely. I've had very little success getting these to work on modern (> win2000) operating systems but have had success in manually deleting technique.
I imagine he has already gotten past it, seeing as how his last message was posted in 2006.....[;)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.