Software Deployment

Never heard of it but maybe, just maybe "Alphacam V7.5 Quick Start Guide" will help ;)
http://support.alphacam.com/MultiSiteFiles/LICOM/505916/AlphacamV7_5_QuickStartGuide.pdf

Thanks for the reply. I've already read that PDF file and it doesn't help me with deploying the client software. :(

But thanks anyway.

Well, your question doesn't ask about deployment but packaging. It also touches on installing silently. So, what is it you want to do, re-package or install silently using the vendor's EXE?

My bad, I explained it in a bad way.

I am looking into repacking this as this software does not support silent install so I am looking to do it in another way.

I tried using Adminstudio but it made the program not to work and I can't figure out why.

It has some sort of mixture of old InstallShield v5 and other installer that I have not seen before (part of modules) which is why it couldn't support record switch (/r) as it only can see the *main* installer but it launches another setup/installer that looks like a very old installer, kinda like Windows 98 interface.

I have e-mailed the company to see if there is any other way of doing this but no reply so far.

Thanks.

I tried using Adminstudio but it made the program not to work and I can't figure out why. Whenever I re-package, I ALWAYS do a test install using this procedure:

- run my MSI
- start a lightweight snapshotting tool (I use Ziff-Davis's In Control)
- remove any file or registry data that indicates to the original installer that the product is installed
- run the vendor install again
- you *may* want to start the app so that you capture any configuration that it might make
- complete the snapshot
- add any relevant file or registry data to my package
- repeat

This way, I know that my package exactly reproduces the vendor's installation. If you've already done that and the app still doesn't run, it's time to get out your favoured process/file/registry monitor (I use ProcMon, as some people may know...) and see what happens when the app starts. In your case, I'm willing to bet that the app is either missing a dependent file or is trying to write file or registry data to a location which the account you're using has no write access.

VBScab, thanks for the reply. I've received a reply from the company and they said that because of the way the software was written, they did not recommend doing a packaging work and do only a direct install.

As I am running out of time to do this, and since there are only 16 PCs to install it, we'll do a manual install.

But I have made a note about your steps, which are useful - thank you.

Tony

I've received a reply from the company and they said that because of the way the software was written, they did not recommend doing a packaging work and do only a direct install.What planet are these people on?!? I encourage you to call whoever told you that and laugh out loud at them. Then, find an alternative product. Clearly, this crew are to be avoided at all costs.

I do not make decisions with the purchases, so it's out of my control. :(

We do the work when the software lands on our desk and we package them to work with our network.

Still, I have gave my feedback and hope they will be aware when they release their next version.

ORIGINAL: tsutton
I've received a reply from the company and they said that because of the way the software was written, they did not recommend doing a packaging work and do only a direct install.



That wont be installed at any of my clients then. maybe they are worried you'll make the install better.