I'd be curious about this as well. My current company will have some large packages like that.
Rather than a single exe, can you break up the package and install it as either chained packages or use Provisioning to install the components one at a time? Just a thought ..
I can't. It is Solidworkd 2010 SP05 32-bit. It's just a large installation. And we have to deploy it to multiple sites which is why it's really needed in LANDesk. Two of the sites are slow bandwidth, which is why the download files is really important.
Run from Source works without fail, but we really need a resolution to the SDclient.exe crash. It happens to every computer I've deployed to using a download files delivery method.
Maybe it has to do with the number of files in the package. Can you compress the source, then decompress after download and run the install?
Do you have a ticket open with support?
Was going to open one today if I didn't get any tips here.
As for compressing, I haven't been able to find any way to compress to a zip using XP/7 built in tool. Third party add-ons are not really an effective option, as we use standaradized imaging and don't deploy an extra app for users to unzip, when the Windows tool is generally more than adequate.
Do you have a recommendation for compressing it? My concern with compression would be that we would then be deploying a single file that is HUGE, rather than many many many smaller files. But maybe that's a good thing??
I've been toying with either using WIM's createdy by imagex from the WIndows AIK or using the command line version of 7zip. Both could be included in your package, they are just standalone executables that don't require an "install".
You could create a spanned volume instead of one big file. Split it in, say 1 GB chunks or something like that.
7zip command line -->http://downloads.sourceforge.net/sevenzip/7za920.zip
Just thought I would throw out there that I don't have any experience yet using LDMS just yet, but I will be facing having to deploy large packages so I've been doing some research into what is the best way to do it. There are no usefule "best known method" documents on this topic that I could find.
I understand it doesn't apply to you, but It seems like the best option is to "run from source" would work best when dealing with large packages. Especially if you have the package close to most of the computers already. It seems like sort of a waste of time to download the files to the clients.
Now, when it comes to serving internet based clients that kind of throws the whole run from source idea out the window
How about breaking up the deployment task into 2:
Task1: Cache the package locally on the machines
Task2: On a seperate date/time, you can run the install task
I ran in to a very similar issue with an Autocad package. I opened a ticket with landesk and after troubleshooting they found it was being caused by the file paths being to long. They suggested shortening the file paths to something shorter. They did however create a patch so that the error message was easier to figure out.
I've deployed a lot of CAD software, but I typically make them into a self-extractive 7zip install. I've deployed installs as big as 2 GB using that method, and it's worked flawlessly. I'm using LDMS 9.0.2. It also will save on transfer time over the slow links. I know AutoCAD 2010 was cut in half by 7zip.