Trying to deploy Shoretel Communicator 19.44.4300 with Kace Managed Install
I have tried 9 ways to Sunday to deploy Shoretel Communicator via the K1000 with a managed install without success. Hoping someone has been able to do this and can help me out.
I downloaded my "setup.exe" file from my server. According to this: shoretel forums link I should be able to do: setup.exe /S /v"/qn REBOOT=reallysuppress". A software tip here on itninja also claims that command will work. When I try to just run the setup.exe (no parameters) the I can see on my client, the install is trying to extract the .msi file. After that, it immediately fails with:
this installation package could not be opened. verify the package exists and that you can access it or contact the application vendor to verify that this is a a valid windows installer package
So I ran "setup.exe /a" from the command line and extracted out the files. I uploaded the "shortel communicator.msi" file and tried to run setup that way using many variations of these commands:
"Shoretel Communicator.msi" /qn /norestart
msiexec /i "Shoretel Communicator.msi" /q
I even zipped up all the files I had extracted and tried to upload the zip file and run from that. No luck.
These commands (setup.exe and msiexec...) run from command line on my test machine without issue.
I know I am missing something here I just don't know what. Thx.
I downloaded my "setup.exe" file from my server. According to this: shoretel forums link I should be able to do: setup.exe /S /v"/qn REBOOT=reallysuppress". A software tip here on itninja also claims that command will work. When I try to just run the setup.exe (no parameters) the I can see on my client, the install is trying to extract the .msi file. After that, it immediately fails with:
this installation package could not be opened. verify the package exists and that you can access it or contact the application vendor to verify that this is a a valid windows installer package
So I ran "setup.exe /a" from the command line and extracted out the files. I uploaded the "shortel communicator.msi" file and tried to run setup that way using many variations of these commands:
"Shoretel Communicator.msi" /qn /norestart
msiexec /i "Shoretel Communicator.msi" /q
I even zipped up all the files I had extracted and tried to upload the zip file and run from that. No luck.
These commands (setup.exe and msiexec...) run from command line on my test machine without issue.
I know I am missing something here I just don't know what. Thx.
1 Comment
[ + ] Show comment
-
Forgot to mention, I can run that setup.exe command from the command line on my test machine and it runs just fine. So does the msiexec installs. Just wont run from Kace. - shells 9 years ago
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
madoreo2
9 years ago
I associated a .zip file containing "1033.MST" and "Shoretel Communicator.msi". I have it set to override the default installation with the full command line being: msiexec /i "ShoreTel Communicator.msi" /q
Don't forget to check the "Don't Prepend msiexec.exe" box. With these settings my managed install works every time.
Don't forget to check the "Don't Prepend msiexec.exe" box. With these settings my managed install works every time.
Comments:
-
Thanks for that info, I will try it later today. Does this also work to update communicators that are already installed on a PC as well? - shells 9 years ago
-
I tested it on a couple of computers that had the old client. Yes, it does update the ShoreTel client to the new version without a restart required (they just need to restart the ShoreTel client). - madoreo2 9 years ago
-
I don't know what I was doing wrong. I tried your method a few times by updating my install and it didn't work. So, as a last ditch effort I created a new managed install task and went through the steps again. This time it worked!
I cannot thank you enough I've spent several hours jacking with this thing and felt very frustrated. Little upset with myself that I didn't try the new task sooner.
And thanks for checking out the updating process. I have 100 machines to do and didn't want to have to uninstall first. - shells 9 years ago -
This worked for me as well, thanks! - brandon.anderman@cipco.net 8 years ago
Posted by:
SMal.tmcc
8 years ago
we extracted the msi file and created an mst the puts in the ip to the server. Zipped those up with a batch file and call the batch in the distribution
Comments:
-
thanks for the info! could you elaborate on what the data in the MST looks like or how you created it? - CSVIT 7 years ago
-
Would you mind giving some information on your MST file? It would be super convenient to include in our package. - jparrish 7 years ago
-
This was so long ago I don't seem to have the original zip files on my server anymore. I may have them on the old kbox somewhere but it will take a bit of digging... will try to locate them. - shells 7 years ago
