I'm trying to push a service pack as a managed install, since it appears in the list of installed programs as its own program. The command line to perform the install is:
msiexec.exe /p ArcGISDesktop10sp3.msp /qb REINSTALL=ALL REINSTALLMODE=omus

I have that command line in the Installation Command field and "Run Command Only" is checked along with "Don't Prepend msiexec.exe". The MI reports that the installation failed three times on the target machine (I'm just testing on one machine at this point). I checked the target machines and none of the log files show that the MI ran and there's nothing in the Event Log either. Where should I look to see why the MI is failing?

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Always good to see another GIS user.

I had to do a msp update on one of our other software packages, and one problem I ran into was the original MSI not being present because the agent had been updated and the download folder was empty.

The kdeploy log is empty?

Casey
Answered 01/10/2012 by: cmccracken
Orange Senior Belt

Please log in to comment
1
When you check "Run Command Only" it will tell the KBOX to ignore any attachments to the MI. If you have an attachment, that needs to get moved down to the local system that could be your problem.
Answered 01/10/2012 by: nshah
Red Belt

Please log in to comment
0
ORIGINAL: nshah

When you check "Run Command Only" it will tell the KBOX to ignore any attachments to the MI. If you have an attachment, that needs to get moved down to the local system that could be your problem.


Ah. I wasn't aware of that. I had it checked because the text at the top says "The windows client will install this via:" only shows the filename when the Run Command Only checkbox is unchecked, but when you check the box it shows the full command line as entered in the Installation Command.
Answered 01/10/2012 by: steelc
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: cmccracken

The kdeploy log is empty?



The kdeploy.log doesn't contain any entries related to this MI, and I can't find any mention of it in any other logs, either.
Answered 01/10/2012 by: steelc
Senior Yellow Belt

Please log in to comment
1
Is the Managed install (MI) showing on the "to install" list of the target machine? If not then the criteria for matching the software item or the label used in the MI is not applicable to this machine so that needs to be fixed.

If it is in the to install list then remember that you need to run an inventory. On an inventory the process is:
  • inventory
  • upload to server
  • run Files Syncs and MIs
is something in that process breaking down before MIs?
ref: http://www.kace.com/support/kb/index.php?action=artikel&cat=4&id=821&artlang=en
Answered 01/10/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
I added another computer to the MI and watched it install and was prompted with a KUserAlert - invalid parameter window. Apparently even though our company name is in quotes the space is breaking the KUserAlert from appearing. I don't think this happens all the time, however, as the notifications for patching have been popping up without any errors. Even though the alert didn't appear the install then proceeded (it's still installing as I type this).

Thanks for sending the KB article GillySpy. I should let you know that it needs to be updated, however. It still references c:\Program Files\Kace\kbox\downloads\XXXX, which isn't correct for Windows 7 computers. It should be C:\ProgramData\Dell\Kace\downloads.

Does removing the space from the company name still require a restart of the KBox?
Answered 01/10/2012 by: steelc
Senior Yellow Belt

Please log in to comment
0
Thanks for feedback on the article.

Sounds like a bug on the 5.3 agent that I recall. Removing the alert might be required. There were some threads on here about that.

Any change that does require a reboot will prompt you giving you a chance to bail.
Answered 01/10/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
My concern with not having the alert would be if the update tried to run while someone was using the software, but that might be a chance we have to take.
Answered 01/10/2012 by: steelc
Senior Yellow Belt

Please log in to comment
0
Valid concern to be sure. If that's necessary some options for you are:
  • deploy as a script which checks running processes as a verify -- or even an alert in a script may work
  • set the deployment time on the MI so it runs after hours
  • deploy a batch in a zip in your MI that checks what you need and then calls the msiexec.
  • Make a new smart label that checks for a combination of running processes GIS and label name contains your other label. target that with your MI
The SQL for the latter is:
select MACHINE.ID from MACHINE
JOIN MACHINE_LABEL_JT ML ON ML.MACHINE_ID=MACHINE.ID
JOIN LABEL L ON L.ID=ML.LABEL_ID
left JOIN (select MACHINE_ID from PROCESS P JOIN MACHINE_PROCESS_JT MP ON P.ID=PROCESS_ID and
P.NAME='blah.exe') -- change this line
RUNP ON RUNP.MACHINE_ID=MACHINE.ID
WHERE
L.NAME='nameiwasusing' -- change this line
and RUNP.MACHINE_ID IS NULL
Answered 01/10/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
I'll be interested to know if this works for you, normally I'd have to put the following in a .bat file and call that instead on the MI:

msiexec.exe /p %CD%\ArcGISDesktop10sp3.msp /qb REINSTALL=ALL REINSTALLMODE=omus

%CD% is because the /p parameter needs a full path.
Answered 01/11/2012 by: AJStevens
Purple Belt

Please log in to comment
0
What is %CD%?
This thread is starting to blur together with this one:
http://www.appdeploy.com/messageboards/fb.asp?m=87168
Answered 01/11/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
I wanted to follow up and let everyone know that the MI is now working (although without an alert). The patch got pushed to two labs overnight and there was much rejoicing.
Answered 01/11/2012 by: steelc
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity