/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


How MSI should popup a message for 30 min to user saying to close all the files?

04/09/2015 2003 views

I need Some help. I have a msi and clients requirment is that before installing, msi should popup a message for 30 min to user saying to close all the files and if he click yes then installation should start of if no response till 30 min then by default installation should start. Salutations with complete details will be of great help. Everything has to be done within msi only.

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1
Does the client have a software distribution system, such as KACE K1000 or Microsoft SCCM? Both of those can display messages prior to a software install. If not, then your best bet is as VBScab suggested, a custom scripted solution. There is no mechanism within Windows Installer itself.
Answered 04/09/2015 by: BHC-Austin
4th Degree Black Belt

All Answers

0

What OS do the target machines have? If they're Windows 7 or above, you could do something with Powershell/Windows Forms.

A previous poster found and used an HTA but many shops disable HTA execution.

As you can tell, there's nothing native in Windows Installer that will help here.

The other point to bear in mind is that many shops deploy everything silently so pop-ups of this kind will, unless expertly coded, make the deployment hang, as the deployment would be carried out using the local System account which, as you know, has no console on which to display windows for messages, etc.

At most clients I've worked at, a round-robin email would be sent, detailing that some update is due to be deployed on date 'x' at time 'y', that users need to log off from machines and that, if they don't log off and consequently lose data, no-one will care!. Normally, a reminder is sent the day before the actual deployment and then a final an hour or so before. If, however, your client wants to pay for development of a robust messaging system as an alternative, I'd bite their hand off and invoice accordingly.

Lastly, please remove your duplicate post.

Answered 04/09/2015 by: VBScab
Red Belt

0
I don't think your clear of your own requirements here?

First of all, how will users install the software, via distribution system with no interaction or by running the msi themselves?

If by user is UI allowed or must be suppressed?

As already mentioned if via distribution either mail or messaging from one of these systems is the norm. If by user then its easy enough to add a pop dialog or add a custom dialog into the UI sequence though you'll gonna need a timer which if you do wrong will make it appear that the install has hung.

Give us some more info and lets see how we can help you.



Answered 04/09/2015 by: deliveryboy
Orange Senior Belt

0
You can create a custom action vbscript embedded.

popup .... Timeout .. 
Answered 04/10/2015 by: rock_star
3rd Degree Black Belt

  • You cannot in Windows 7 and above if deploying by service account, as this runs in a different session to the user, and interacting with the desktop is no longer supported for service driven processes. Even if you force interaction with desktop, you will end up triggering the UAC which will hang the install until the user responds. You would realistically need to create a process that runs in user context and is able to communicate with the installation process using named pipes, for example.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ