Attempting to install "Cisco Unified Personal Communicator" using the recommended silent install method.

-CiscoUnifiedPersonalCommunicatorK9.exe /s /v" /qb.  On my Win7 machine, it does download the file to the correct downloads folder and starts to run the install, but it fails everytime with ...

"This installation package could not be opened.  Verify that the package exists and that you can access it, or contact the  application vendor to verify that this is a valid Windows Installer package."

But, if I open a CMD prompt and run the same cmd line from that folder, it runs without any problem.  It is as though it does not know the location that it just copied the file to.  The file location and name) is:
C:\ProgramData\Dell\KACE\464\CiscoUnifiedPersonalCommunicatorK9.exe.

Note that the above is on a Windows 7 machine.  When I test on an older XP box, thew Kace install works just fine.  It copies to a different location on the XP machine. "C:\Documents and Settings\All Users\Dell\KACE\downloads\464"

The install is set to deploy to the following OS.
This software will only be installed on the following Operating Systems:
   Windows 7 Ent x64 SP1
   Windows 7 Pro x64 SP1
   Windows XP Pro SP3

The Windows 7 Ent x64 SP1 machine gets the download, but the exe will not install and fails every time with the error above.  Why is it not looking for the file in the correct WIN7 location?

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

I don't know if this was a typo or not but there is a " after /v listed below. CiscoUnifiedPersonalCommunicatorK9.exe /s /v" /qb

Answered 04/25/2013 by: Timi
Seventh Degree Black Belt

Please log in to comment
1

I noticed that too and wondered about it.  It is direct from the Appdeploy Live link within the Kace "Distribution>Managed Installations" screen.  If it is wrong, it does not cause a problem because I tested it from the command prompt when I ran it manually, and the quote mark did not cause an issue.   No, the issue seems to be that the command line when run from the KACE appliance, cannot find the file (to execute) in the Windows 7 downloads folder. 

Answered 04/25/2013 by: HHPB
White Belt

Please log in to comment
1

You can extract MSI out of it from %temp% when you try to run it. Or use 7-zip to extract the msi.

Answered 04/26/2013 by: piyushnasa
Red Belt

Please log in to comment
1

Try with this

CiscoUnifiedPersonalCommunicatorK9.exe /s /v"/qb"

Answered 04/26/2013 by: jagadeish
Red Belt

Please log in to comment
0

Looks like I need to revise my original question a bit. Turns out the /S for silent was masking the issue a bit. Originally I had reported that I could run the Kace install on XP, but not Windows 7. It looked (by the error message) that it could not see the install file at the location Kace copies it to on the Win 7 boxes. However, when I removed the /S and just ran it alone via the Kace install, I can see that it gets through several steps of the install (extracting and decompressing the MSI) and then fails when it actually starts to run the install. This failure does not happen when I manually double click on the same file. Looks like some type of a priv issue or perhaps the accepting of the agreement message (or lack of) causes it to fail. The generic "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package." is a bit misleading.

Can anyone comment on the error? The install itself is ok. If it is the accepting of the EULA that is causing the error, is there a way to overcome this? I know /S would seem like the answer, however it still fails with /S, it just hide the preliminary install information about decompressing the MSI.

Perhaps it has nothing to do with the EULA. I would have expected the KACE install to run the install in full verbose mode and it would then prompt the user for the acceptance. The reality is, the KACE install must initiate the install with slightly different privs and those privs must not be able to write to some location on the Win 7 OS. Comments anyone?

Answered 04/29/2013 by: HHPB
White Belt

  • Correction on the last line ... on the hard drive of the device with the Win7 OS.
  • I think that the problem isn't related to your command line syntax.
    I have deployed CUPC successfully in our environment with SCCM 2007 on Windows XP and Windows 7 x86 with the following command line:
    CiscoUnifiedPersonalCommunicatorK9.exe /s /v"/q REBOOT=ReallySuppress"

    But now I am preparing os deployment for Windows 7 x64 and I always get the error message. The command line is the same. On W7 32bit it installs successfully on 64bit it fails.

    Have you solved the issue in the meantime?

    AFAIK there is no 64bit version of the CUPC.
Please log in to comment
Answer this question or Comment on this question for clarity