Package run fine when downloaded locally. Doesn't install when run directly from DP.
Hi
Trying to install ADOBE CS4 directly from the DP, if I download it LOCALLY it runs without issue and installs.If I say run directly from the DP it starts the install and basically the status bar never moves. Any help would be appreciated I am stumped.
Here is the batch file I am calling in the package
Start /wait %~dp0Setup.exe --mode=Silent --deploymentFile="Adobe Creative Suite 4 Web Premium.install.xml"
start /wait %~dp0Updates\acrobat9pro-EFG\AcroProStdUpd910_T1T2_incr.msp\ /qn
start /wait %~dp0Updates\acrobat9pro-EFG\AcrobatUpd912_all_incr.msp\ /qn
start /wait %~dp0Updates\acrobat9pro-EFG\AcrobatUpd920_all_incr.msp\ /qn
start /wait %~dp0Updates\Fireworks-10.0.3-AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\Photoshop_11.0.2_mul_AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AdobeDrive_1.0.1_AdobeUpdate_2\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AdobeExtensionManager-2.1-mul-AdobeUpdate2\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AdobeCameraRaw-5.7-mul-AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AdobeOutputModule-2.1-mul-AdobeUpdate_2\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AdobeVersionCue4All_4.0.1_AdobeUpdate_2\Setup.exe\ --mode=silent
start /wait %~dp0Updates\AME_All_CS4.2_mul_AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\DeviceCentral_2.1.1_mul_AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\Flash-10.0.2-AdobeUpdate\Setup.exe\ --mode=silent
start /wait %~dp0Updates\Soundbooth-2.0.1-786\Setup.exe\ --mode=silent
June 21st, 2012 7:22pm
Could be a lot of things. You should have the installs generate a verbose log to track whats going on. For MSIs and MSPs that's easily done by adding /l*v parameter. Not sure how to do it for their exe installers.
Also, why are you adding "start /wait"? If you run a command, the command shell interpreter (which it what is initially processing each command in a batch file) will wait until that command returns before moving on to the next command in a batch file.
One possibility may be spaces in the path, thus you should surround your command with quotes (not its paramaters though):
"%~dp0Setup.exe" --mode=Silent --deploymentFile="Adobe Creative Suite 4 Web Premium.install.xml"
Another possibility along the same lines is that this first executable may not be able to find the xml so it really should be this:
"%~dp0Setup.exe" --mode=Silent --deploymentFile="%~dp0Adobe Creative Suite 4 Web Premium.install.xml"Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2012 9:31pm
Thanks Jason you turn on a light bulb in my head. I checked the adobe logs, and seemly it couldn't find the deployment file. I shorten it to install.xml from Adobe Creative Suite 4 Web Premium.install.xml" and it ran from the DP.
My only issue is cs4 is 9 gigs, I don't know if it is wise to run such a large package from the DP, or should I be downloading it locally?. I have notice either you have to choose download content locally or run directly from the DP, when you advertise the
task, you can't really pick and choose what packages you what run from where, it is really all from the DP or all locally?. Is this correct?
June 22nd, 2012 12:18am
Best to download locally, this will take care of any clients that have network issues when running direct form the dp. Also if you set it to download locally bits is used to its full potential so the download can pick up where it left from in case of any
connection problems. The other benefit is you can throttle downloads using bits so it wont hammer the network while downloading. The only problem here is you need ot make sure the cache size is set large enough on the client to handle the files. I think the
default is 5gb.
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2012 9:50am
Can you please try the following.
In program properties, make sure that "requires drive letter" is enabled.
In advertisement change back to "Run program from distribution point".
Wait until changes are reflected on the clients.
cheers Bodo
June 22nd, 2012 10:00am
How about splitting them up to their own packages and then using program dependancies or a task sequence to install them? Then you will have granular control of which ones get downloaded and which do not.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2012 1:49pm
I spoke too soon, it still doesn't install from the DP, but if I manually run it from the DP by \\dp\CS4.bat file it runs fine.
Jason what do you mean by the following can you elaborate
"program dependancies or a task sequence to install them" I do not know what you mean by program dependencies.
June 22nd, 2012 6:53pm
Did you change your command line to what I suggested so that it included quotes and %~dp0 for the .xml path?
Program dependencies are a setting you can set on each program so that it depends upon another program in the same or different package. This forms a chain of programs that will all run from a single advert because ConfigMgr will enforce the dependencies.
In this case though, I would actually use a task sequence.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2012 7:56pm
Is the package set to install using a drive letter or unc path?
Also check the Execmgr.log when running the installation this should tell you the problem or error code during the installation.
June 22nd, 2012 8:27pm
Hi
Yes I put the %-dp0 for the xlm path, and yes I even tried to use a drive letter in the program settings in configuration manager under packages. it just will not install directly from the DP. I which I could solve this. I posted the logs and the batch file
below, if anyone wants to take a look, and try to help.
Adobe Log file
https://dl.dropbox.com/u/6202692/Adobe%20Creative%20Suite%204%20Web%20Premium%204.0%2006-23-2012.log
execmgr.log
https://dl.dropbox.com/u/6202692/execmgr.log
smsts.log
https://dl.dropbox.com/u/6202692/smsts.log
The Batch file I am running to install it.
https://dl.dropbox.com/u/6202692/ACS4.cmd
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2012 10:29am
still no luck in running this program directly from the DP, it just hangs and eventually fails. Any more advice would greatly be appreciated.
June 27th, 2012 10:51am
Based on the log file above, it's hanging on AdobeAir. I think the AdobeAir installer connects to the internet and maybe this is blocked in someway. I would try isolate and test it and confirm its exact behavior including getting a detailed install
log file from it's installer.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2012 7:30am
which log did you see it was the adobe air?
June 30th, 2012 12:11pm
How long does it take to run it from a manual install?
You should only keep boot images in the smspxeimages$ share even if it is a lab environment.
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2012 9:29am
it takes about an hour to install , it is a big program.
I took the Adobe CS4 off of the pxeimages dp, would that have been the source of my problem?
July 2nd, 2012 11:23am
https://dl.dropbox.com/u/6202692/Adobe%20Creative%20Suite%204%20Web%20Premium%204.0%2006-23-2012.log
From the log file:
Installing third party payload
Third party application path:\\W2K8-DC1.CLIVEBUCKWHEAT.LOCAL\SMSPXEIMAGES$\SMSPKG\QAZ00030\payloads\AdobeAIR1.0\AdobeAIRInstaller.exe
CommandLine: -silent
[ 376] Sat Jun 23 23:11:33 2012 INFO
Checking bootstrapper progress
Then it just repeats the last two lines over and over again (with different time stamps of course) seeming to indicate it is initiating the Adobe Air install but gets stuck and thus my hypothesis on why it is getting stuck.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2012 2:03pm