It could be that UAC is prompting in the Local System account asking permissions for the pop up to show. In testing try to disable UAC and see if you see the pop-up.
We have UAC disabled already.
Also, check the delivery method you are using, many of them have the UI hidden
That's not it. The Delivery method is not set to hide the UI and it is seen on WinXP.
I know this is not the answer to your question, but can you explain why you need the user to click OK? Most Local System packages are to run silently with no user intervention, this way you can run the application without the user even logged on to the machine. If you are requiring the user to be at the machine to hit the OK button, then why not change the package account type to Current Logged on user and wrap the package in elevated privileges (if its a rights issue).
I agree that most, if not all, package deployments should be silent, however we are frequently asked to provide prompts for various reasons. Here are just a few common scenarios that we run into:
This installation will require a reboot. Please save all open files and click "OK" to begin the installation.
Your computer requires an update for [Large application]. Click "OK" to proceed or click "Defer" to postpone the installation until a later time.
Please select your department from the following list so that the appropriate settings can be applied.
For scenario #1 and #2 it seems what you want to do can all be done with Vulscan, I see all those types of options in Scan and Repair Settings. I wonder if you could write a script that combines vulscan with running an application, because I know you can just manually call an agent behavior like this:
Vulscan.exe /rebootIfNeeded /agentbehavior=%UNIQUE_ID%
maybe someone from LANDesk could chime in if that is possible.
For scenario #3, is there identifiers that seperate the different departments that you could create different queries against and target the queries instead of asking the user?
I wish i had the answer to the orginal problem, but there may be work arounds in your future. The community can tackle this!
how do you wrap a packaged with elevated permissions... (therefore avoiding uac)?
If you are familiar with AutoIT, it is pretty easy to do in that scripting tool. It is the RunAS command.