Software Deployment

Crystal ball time again...

How are you planning to deploy the software? Group Policy? SMS/SCCM? Altiris? Tivoli? ZenWorks? Marimba? Shall I go on? :-)

but I can't find anywhere how to automate this. Anyone have any advice?
are you talking about repackaging the software ???? or what

I am confused [sm=rolleyes.gif]

I would like to use group policy. I have packaged quite a few apps using either ORCA or AdminStudio, but I have no idea where to begin with this one. I tried repackaging it, but it comes out rather messy as it tries to install drivers. I'd like to know how the "ad_install.msi" works if anyone has had experience with packaging HP scanner software. There is also the "solution center" that has an msi that won't run either. Let me know if I left anything out. I am relatively experienced in packaging apps, I just want to know if anyone has any experience with this one.

Thanks!

but I have no idea where to begin with this one. I tried repackaging it, but it comes out rather messy as it tries to install drivers. I'd like to know how the "ad_install.msi" works if anyone has had experience with packaging HP scanner software. There is also the "solution center" that has an msi that won't run either.
Have you had a look @ the MSI structure... That should tell you how it works.. features, components, files, reg keys, etc... When you try and install, have you created a verbose log? That should tell you what is going on step by step... When you say "won't run" what does that mean? Any error messages? What does it put in the log?

ORIGINAL: kiptek

Have you had a look @ the MSI structure... That should tell you how it works.. features, components, files, reg keys, etc... When you try and install, have you created a verbose log? That should tell you what is going on step by step... When you say "won't run" what does that mean? Any error messages? What does it put in the log?



that's the odd part, there are no files, shortcuts, or anything in the ad_install.msi when I view it in ORCA. When I run it, it does "preparing to install" and then goes away. The event viewer says it install, but obviously nothing happened

I know I'm being vague here, but I am really not sure where to start. That msi is the only MSI and it doesn't seem to do anything, and packaging the installer results in a messy MSI that tries and ultimately fails to install the drivers. I wonder if there is anyone at HP i can get in touch with...

once again, what does the verbose log say?

I'm not sure if you can do this using GPO since I primarily use SMS for deployment. I just deployed these drivers and it was very simple. The corporate driver package has a file, hpzsetup.exe. All I had to do was run that with the -s switch to install the drivers unattended.

Were you able to set and settings for that? I have the wireless printers so I would need to set the IP somewhere

I do not have to deal with that because my print settings are controlled from the print server.
I believe you will find the answer to your question in the readme.html file in the driver package. You'll find it under setup\enterprise\enu.
It documents the command line options that are available with the installer.

The document gives several samples on how to automate the ip address setting in the install. Here is one of those examples. Setup.exe –s –ipaddress “16.149.182.123”

yea, I didn't know that readme was there, thanks! I figured it out. Apparently the ad deploy msi just launches the exe on first login in silent mode. It temporarily maps the directory as a shared drive Z: which I need to find out if it will cause conflicts if there is already a mapped drive there.

ORIGINAL: JK1150

that's the odd part, there are no files, shortcuts, or anything in the ad_install.msi when I view it in ORCA. When I run it, it does "preparing to install" and then goes away. The event viewer says it install, but obviously nothing happened



After installing, go to printers and faxes, right click anywhere and hit server properties. Go to the drivers tab. See if the new drivers are listed.