Previously, DevInstall had posted an Event relating to Webcast from MSDN: Designing Application Installations for User Account Control with Windows Installer 4.0 in Windows Vista. If you missed the live Webcast which was on October 18, MSDN has now made that available on-demand.
What does the Webcast talk about? Some highlights?
- User Account Control (UAC) in Vista and Windows Installer 4.0 Integration
- Signing Your Package - some new dialogs
- Credential Prompt-Free Patching
- Adding the "Shield" to your User Interface
- When does elevation happen?
- Precautions when using AdminUser
- A word about Custom Actions (CAs)
- ALLUSERS Property Under UAC
- Creating a True "Per-User" Package
- Using a Setup.exe Bootstrapper
- Testing your Package
In addition, the on-going Q/A session during the presentation was highly informational. Some highlights from the session:
Question: We don't want to make the customer go through the UI and then abort in the Execute sequence if Privileged is False. What can we check in the UI sequence to abort?
Answer: The UAC credential prompt is a one way door. There is no way to tell in advance whether the user will approve the credential prompt. Once the credential prompt is approved you are running as administrator. This is a constraint of UAC.
Question: On Vista, is there a way to run an elevated install silentley? i.e: When using /qb Vista do shows the elevation dailog request - but also shows the progress bar. When using /qn - nothing happens ... Is'nt a way of metigation between the two switches ??
Answer: The UAC functionality does not allow elevate silently. The recommendation from the UAC team is to 1) run from a managability tool such as SMS, Altiris, Tivoli, etc 2) run from an elevated command line 3) (for automated testing in development only) write a service that elevates a command line when passed.
Question: There's some confusion about whether the "no impersonate" bit can be used in the UI sequence. Docs imply it only applies to deferred custom actions.
Answer: NoImpersonate can not be used in the UI Sequence or in the InstallExecuteSequence outside of the script. To have a custom action run inside the script, one needs to mark their custom action deferred.
Question: So where does ALLUSERS=2 bounce to?
And many more?This is a strong recommendation to Application Developers, Installation Developers and also for Application Packagers.
Presenter: Tyler Robinson, Lead Program Manager, Microsoft Corporation
Session Q/A: Robert Flaming, Program Manager, Microsoft Corporation
Windows Installer Team has also scheduled next similar webcast for October 30, 2006 Designing Software Installations for Windows Vista Using Windows Installer 4.0.
If you are more interested to learn about UAC in Vista and Windows Installer 4.0, Robert Flaming published a series of articles earlier: Understanding UAC in Vista and Windows Installer. Uday Shivaswamy's earlier webcast about Modifying Your Applications to Run on Windows Vista is an additional support to understand in the sequence. There is also an upcoming event about 10 More Commandments for Software Packaging: Focus on Vista Migration, you may find it more helpful in the context.