What Is The Best Way To Test A Package In A Locked-Down Environment?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Per-machine advertisement followed by installation by a normal user account is the most comprehensive test for this situation.
As an administrator use the following command line to advertise the application to the local machine:
msiexec.exe /jm package.msi ALLUSERS=1 /qb
Note: No package components will actually be installed, MSI will simply install the advertised shortcuts and icons, file types and extensions, COM class registration, and package installation information.
Next, logon with a normal user account and trigger the installation process by running the shortcut or via a file type association. The application should start and run with no problems at this point. Be sure to make changes to settings, toolbars, and other preferences- then exit and relaunch the application to ensure such information is capable of being retained in this security context.
Answered 06/25/2002 by: bkelly
Red Belt

  • This content is currently hidden from public view.
    Reason: test
    For more information, visit our FAQ's.
Please log in to comment

Also the use of a tool like Procmon ( regmon . filemon) could give you hints why something wouldn't work in a locked enviironment


Answered 12/11/2012 by: jaybee96
Red Belt

Please log in to comment