This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Distributing an MSI via SMS
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 22, 2009
02:05 PM
Distributing an MSI via SMS
I've produced my first MSI (more luck than jugement) and handed over to the IT lads to install. They're distributing the msi using SMS and have come back to me to say that they believe there is a problem with my script.
Apparently, they can install my msi, but the user has to be logged on in order for the install to work. They want to push out the install and have it run without the user logged on.
Firstly, is that possible and secondly, what do I need to do to my msi in order to make this work?
Many thanks
Steve
Apparently, they can install my msi, but the user has to be logged on in order for the install to work. They want to push out the install and have it run without the user logged on.
Firstly, is that possible and secondly, what do I need to do to my msi in order to make this work?
Many thanks
Steve
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2009
04:41 AM
When installing via SMS it will run in a silent mode. Therefore the installuisequence will not run. You most likely have a bunch of custom actions running in the installuisequence that need to be moved over to the installexecutesequence. I would suggest that you also enable msi logging on the machine set to a value of 'voicewarmupx', so that when they run it you can have all that lovely log info 🙂 To get at the log it usually puts into the users temp folder but running over SMS it will actually get put into c:\windows\temp and it will be called MSI.log
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2009
04:50 AM
ooh one other point to make is that you most likely want to test your install to semi-simulate what SMS does is to firstly run it in basic UI mode like this
msiexec.exe /i /qb+
This will run your installation without the UI sequence but will provide you a progress bar and will pop up any error messages and provide a succesful prompt at the end. Once you have this working i suggest running it even more closely to SMS by running it completely silently by changing /qb+ to /qn
The only thing you cannot simulate easily is that SMS runs the installation as an elevated service account
msiexec.exe /i
This will run your installation without the UI sequence but will provide you a progress bar and will pop up any error messages and provide a succesful prompt at the end. Once you have this working i suggest running it even more closely to SMS by running it completely silently by changing /qb+ to /qn
The only thing you cannot simulate easily is that SMS runs the installation as an elevated service account
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 23, 2009
05:51 AM
Thanks for this. I've checked the Sequencs -> Installation -> User Interface and have two custom actions in there that set ARPNOMODIFY to 1 and LIMITUI to 1. Nothing else.
The rest of my custom actions appear in the Execute sequence.
I'll chase the IT people to see if they created a log - I'm sure they did (or can). My biggest problem is the 20 minutes experience with MSI that I have!
Thanks again.
Steve
The rest of my custom actions appear in the Execute sequence.
I'll chase the IT people to see if they created a log - I'm sure they did (or can). My biggest problem is the 20 minutes experience with MSI that I have!
Thanks again.
Steve
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)