Best Way to Test a Package in a Locked-Down Environment

I can't believe we haven't been using the /jm swith all this time... we've had msi deployments not go very well due to this issue. I can't thank you enough for bringing this out!

its a good tip. However, I don't consider this to be a genaralized one. It always depends on the scenario with which the application gets deployed.

For eg: If we have application which is deployed using intelli mirror(AD), then the application needs to tested with /ju switch. If we follow /jm here, the application may goto heal for every user when he launches it.(if the HKCU keys are set as a key-path).

If the application undergoes a SMS deployment., then this practice of testing is worth. But still, we will not be able to simulate the exact deployment mechanism.

Hence, its always adviced to test the package based on the deployment scenario.

Cheers'
Vijay

An ok tip to know about if you are just coming to this scenario ..

However, the most important (and most overlooked) fact of packaging for locked-down/limited user accounts is to always do a full and exact profiling of what ACLs your application needs to fully work as intended. To do this properly you would need to do full user testing.

You say "The application should start and run with no problems at this point.", my emphasis.

This is where less-experienced packagers often fail. Don't make this mistake!