At first posted by steven_h See Put up Importing the subsequent registry file is effective for me (and sets the server title as well):
I'm alleged to be rolling out a script tonight/tomorrow that installs a new edition of 1 of our very important programs.
Following some exploring with regard to the new mistake: "ShoreTel Communicator.msi is not a sound set up offer with the Product ShoreTel Communicator. Attempt to find the package "ShoreTel Communicator.msi" in a folder form which you can put in ShoreTel Communicator" even if we pointed it at the msi it still unsuccessful.
I’ve experienced some tiny good results with this particular but in no way really deployed it. You can most likely cobble together some form of put up set up script or add something to the ‘1st time login’ script to produce that occur quite seamlessly. It’s quite Edition unique therefore you’d have bought modify it whenever you upgraded, however it’s not that difficult. Below’s an post you could look at for reference.
It is a undesirable concept and it will finish terribly for you. I Just about produced that miscalculation, but I've the good practice of re-studying a script another time ahead of I execute it. Saved my bacon.
I'm purported to be rolling out a script tonight/tomorrow that installs a new edition of one of our crucial courses.
I can run it outside of ConfiMgr and supress a restart but what I need is to install silently, supress a restart and prompt for just a reboot, if possible.
I simply cannot thank you adequate I have invested various hours jacking using this detail and felt really pissed off. Small upset with myself that I did not check out the new process Shoretel Communicator MSI faster.
shells 3 a long time ago final edited three a long time ago Forgot to mention, I'm able to operate that setup.exe command within the command line on my take a look at equipment and it operates just good. So does the msiexec installs. Just wont run from Kace.
I had been in a position to get ShoreTel TAC to supply A different duplicate from the Communicator installer for this distinct Make and that did not function both but did come up with a unique mistake information.
Your at this time way of deployment will never Enable you to instantly detect if the install failed. Examine powershell (trace: get started-process Together with the passthru parameter).
I come to feel silly putting up this, but I'm baffled and nobody in my Section appears to want that will help me out or talk.
We have tried using a complete uninstall of Communicator (deleted each of the still left about data files), uninstalled and re-installed Outlook with no modify. I don't see just about anything in the KB about this or within the forum listed here - has everyone found this prior to?
Any assist might be greatly appreciated. I'm speculated Shoretel Communicator to Use a 50 % working day now nonetheless that doesn't appear to be taking place. :(