Software Deployment

This works too, after getting the folder with setup.exe out of the temp directory:

if exist "c:\Program Files (x86)\epson\escndv\setup\setup.exe" start /wait "" "c:\Program Files (x86)\epson\escndv\setup\setup.exe" /r /SI -sms /Nodisp

start /wait setup /SI -sms /Nodisp

Hi Oilernut:

Thanks for giving me the package source, I have gone through the same and found that this package is created by Epson's own utility which is called "Makepackage.exe" Please check if you have this utility given to you in a CD or otherwise because if you have the utility you can modify the setup and even make it silent. Well coming to the point here are your options:

1. Contact Epson or look for vendor documentation which can tell you about making this setup silent (I agree with aogilmor here!)
2. Try to contact Epson for more options on this setup or for makepackage.exe utility or any other help that they can provide you to make this package silent (my team also does the same when we are stuck in an issue like this ).
3. Incase you fail in step 1 and 2 above then make an autoit script with the hidden command line that I wrote in my msg earlier, this will just allow the setup pop-ups to flicker for a second and then they will disappear (I also do the same when we don't get help from any where as some setups are not created for enterprise use). If you want I can provide you with some scripts that would be some help to you in this regard.
4. Use Microsoft's DIF-X to install the drivers but this will not install the software, here is the link to DIF-X http://msdn.microsoft.com/en-us/library/ms790308.aspx
5. Repackaging - Well being in this area for almost 9 years,an ACP (Altiris Certified Professional) and reading various articles from Microsoft and Bob Kelly's (author of App deploy) whitepapers it is SERIOUSLY NOT recommended to capture a device driver installation. But if you still want to go ahead with the same you can do that but you might get some issues while or after repackaging.

I have given you my conclusions and my recommendations. However the final call is yours to take, I hope you will make a wise decision. Its better to spend more time rather than spending time later on in rectifying your own package.

Please feel free to contact at any time.

Regards,

Bhupesh Mansukhani

With several of the Epson scanner products' downloads, it seems that the following works with their (possibly proprietary, possibly not) SETUP.EXE:

setup /SI -sms /Nodisp

Could you please try that and report back if it works? I'd appreciate it.

Just had to work on this app for NHS and the install/uninstall strings are below:

Install - Setup.exe /SI -sms /Nodisp

Uninstall - "C:\Program Files (x86)\epson\escndv\setup\setup.exe" /r -sms /Nodisp

i don't think capturing hardware drivers is a safe practice. maybe for a super brainiac like you but not us mere mortals :-)

I think Wiseapp Bhupesh Mansukhani has spoken wisely.

I was just gonna say that AutoIt isn't an option. Was hoping someone knew of a secret installation method so I wouldn't have to repackage it. Oh well, was worth a shot. ;)

Hi Oilernut:

I would'nt say AutoIT is a bad or a good option but yes there is a function AutoIT that hides all the windows coming on your screen and you can still send your keystrokes while running the installation. However if you could send me the link of the setup from where you have downloaded it , I'd be rather in a good position to help you out. Btw here is the example on AutoIT feature that I was talking about....

Run ( "setup.Exe" , -1, @SW_HIDE )

Regards,

Bhupesh Mansukhani

This is the setup program here:
ftp://ftp.epson.com/drivers/epson12753.exe

Any help you could provide would be great!

sometimes you have to dig for vendor documentation or support for silent installations. It was not readily apparent to me how you'd do that with this software.

Any help you could provide would be great! Why go through all this pain unnecessarily? It'll be a week on Monday since your first post and you're no further forward. Capture it to an MSI and be done with it.

through all this pain unnecessarily? It'll be a week on Monday since your first post and you're no further forward. Capture it to an MSI and be done with it. ORIGINAL: VBScab

Any help you could provide would be great! Why go through all this pain unnecessarily? It'll be a week on Monday since your first post and you're no further forward. Capture it to an MSI and be done with it.


Well this isn't the only program I am working on. I am working on dozens of them, and this Epson one isn't a high priority.

As mentioned in the posts below, repackaging it isn't really an option for me when drivers are invloved. I am not that experience at packaging and if something should go wrong I don't want to blow up an entire departments computers.

Thank you to everyone else for you're replies, I will investigate further.

That's a good decision to make Oilernut, all the best for your other tasks and as you saw people like aogilmor and myself are here to help you out in any issues that you encounter with your future packages.

I hope our advise would help you out...

Take care and god bless.

Aogilmor: Thanks for the compliment...:)

Regards,

Bhupesh Mansukhani

i don't think capturing hardware drivers is a safe practice. maybe for a super brainiac like you but not us mere mortals :-)Ummm....didn't the OP say that he had the driver done but wanted to sort the software (presumably the OCR and other assorted junk that vendors like to bundle with their scanners)? It was to *this* software that I was referring.

i do see that now, i stand corrected. However, it looks like the setup.exe the OP has does both

I have packaged this a few months ago. From what I remember it is a really straightforward package without any weird exceptions or encounters.

Although you're saying you're not that experienced with packaging (drivers) yet... Why not take this as an opportunity to learn how to package drivers. It won't get a lot easier than this one.


To help you get started,

Take a snapshot of the app (probably including the driver), filter out the installed driver, like \Windows\inf\oemXXX.inf and \Windows\drivers\... stuff. With some insight in the OS you'll know what's part of the driver and what not. The Windows folder probably contains a lot of duplicate stuff from the driver, that will also be installed to Program Files. You can also use that as a guideline.

Leave the uninstalled driver source (the one under Program Files) in your package and rebuild the driver component(s) with the information you can find in the sources I'll give you below.

The whole driver packaging things looks scary and overwhelming when you're new to it, I've been there myself. But especially if you have Wise, driver packaging is a piece of cake :)

And of course, if you run into any trouble with this method, don't be afraid to ask us, that's what we're here for.


These were the valuable sources I collected and saved for packaging drivers. They might not give you a full description of the process but reading them all and combining the knowledge will get you there (unfortunately the adminstudio step-by-step guide link was broken so I removed that one):

MSDN:
http://msdn.microsoft.com/en-us/library/ff537781.aspx
http://msdn.microsoft.com/en-us/library/ff549362.aspx

AppDeploy:
http://itninja.com/question/how-do-you-roll-out-new-machines?0827
http://itninja.com/question/how-do-you-roll-out-new-machines?0873

Wise Package Studio:
http://www.symantec.com/connect/articles/how-package-signed-device-driver-using-wise-package-studio

AdminStudio:
http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q111386




Good luck if you decide to go for it!

if it's a signed driver you can use the procedure posted by vbscab a while back, using wise for windows installer it worked a treat for me.

Hmm... My post was offered as a potential solution to the original post, it wasn't intended as a request for help. But thanks nonetheless, aogilmor.

As a matter of fact, I just finished ProcMoning[1] those switches out of an .MSI which Epson's U. K. live chat support provided me with a link for[2].

The SETUP.EXE I refer to is one which is not the InstallShield system (offered in some scanner products' downloads), but one whose company name is Seiko Epson Corporation and which is digitally signed by them.

Some products include: Epson 2480, Epson 3170 Photo, Epson 3490/3590, Epson 4180, Epson 4490 Office, Epson V300 Photo, Epson V350 Photo, Epson V500 Office.

I'm still interested in if the suggestion works for other people.

[1] http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
[2] http://esupport.epson-europe.com/FileDetails.aspx?lng=en-GB&data=mbqAVwjIQ4DB8ixl0c2Cqqn148dvrve8&id=326658

I am running into a problem using the following method, and I'm hoping one of you guys can lend a hand.

setup /SI -sms /Nodisp

The install would never complete so I tried setup /SI so I could see where it was getting hung up at.
I am installing Epson C750 Pro scanner drivers to Windows 7 x64 machines. The install starts out fine but at about 3/4 of the way through I get a popup titled "Windows Security", Would you like to install this device software? Options are Install or Don't Install.

I want to deploy these via Altiris so they need to be completely silent installs.

Does anyone know how to fully automate this process.

Thank you in advance for your help.

Doesn't it run as System when you run a script through altiris? Then you shouldn't see the elevation prompt.

The install starts out fine but at about 3/4 of the way through I get a popup titled "Windows Security", Would you like to install this device software?

Have you checked if the driver contained in the installer is properly signed? Cause I think the problem might not be just elevation..

PJ

As far as I can tell it seems to be signed by verisign. This is the first time I have ever had a problem with drivers so im not entirely sure what im looking for. I install Wacom tablet drivers and a hand-full of other drivers this way without any complications.

The driver can be downloaded from Epson v750 Pro Driver

I dont know if it will help if you have the driver infront of you but there it is anyway.

I appreciate the help guys.

All,

I would use AutoIt

I would use AutoIt That's the lazy way out and you need to be damn good with AutoIt to enable handling of ALL possible scenarios: most AI scripts make rash assumptions about outcomes. Capture it to an MSI.

opt("trayicondebug", "1")

; uninstall old one
if fileexists("C:\Program Files (x86)\epson\escndv\setup\setup.exe") then
run("C:\Program Files (x86)\epson\escndv\setup\setup.exe /r")

winwait("Uninstall EPSON Scan", "This setup")
controlclick("Uninstall EPSON Scan", "This setup", "Next")

winwait("Uninstall EPSON Scan", "To finish removing")
controlclick("Uninstall EPSON Scan", "To finish removing", _
"I want to restart my computer now") ; uncheck
controlclick("Uninstall EPSON Scan", "To finish removing", "Finish")
endif

run("epson13870.exe")

winwait("WinZip Self-Extractor", "Epson Perfection")
controlclick("WinZip Self-Extractor", "Epson Perfection", "OK")

winwait("EPSON Scan Setup", "This setup program")
controlclick("EPSON Scan Setup", "This setup program", "Next")

winwait("EPSON Scan Setup", "Read the following")
controlclick("EPSON Scan Setup", "Read the following", _
"I accept the terms and conditions of this Agreement")
controlclick("EPSON Scan Setup", "Read the following", "Next")

; either one of these two groups could happen
if winwait("EPSON Scan Setup", "To complete installation", 20) then
controlclick("EPSON Scan Setup", "To complete installation", _
"I want to restart my computer now")
controlclick("EPSON Scan Setup", "To complete installation", "Finish")
else
winwait("EPSON Scan Setup", "EPSON Scan was successfully")
controlclick("EPSON Scan Setup", "EPSON Scan was successfully", "Finish")
endif