Hi, I'm kind of new to packaging but...

I've got a pretty standard locked down environment (AD). I've created an MST for a vendor issued MSI (Autodesk's DWG Viewer 2007), and have made a computer assigned GPO for this package. So when the PC does its foreground GPO check at boot it installs the package no problem. If I then log in with an admin account, Installer does an additional bit of configuration for the profile - no problem - works fine. But if I log into the PC with a basic user account then I get (6) insufficient priveleges errors. App Event Log cites the same exact error message for all 6 - but is very vague.

What I want to know is, how can I log what Installer is choking on in this extra bit of configuration? I guess I'm looking for something similar to FILEMON and REGMON so I can look for Access Denied messages - but how do I do this at logon?

I've done a multi-step Snapshot with Repackager on just the basic user logon - but it captured so much stuff I don't know what the problem is.

Or maybe more pertinent - is there a way I can look at the MSI to see what happens on a per profile basis?

And lastly, by what means does Windows know to do additional configuration for the package - I mean, what triggers that per-profile stuff?

Any kind of help - or just being pointed to a good resource - would be very appreciated...
0 Comments   [ + ] Show Comments

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.

Answers

0
Monitoring Registry Activity During the Boot Process. Have in mind this will give you the BIG regmon.LOG file.

But by reviewing the event log you should find which component/resource that triggers the repair and investigate further why the permission prevents the healing from occur.
Answered 09/22/2006 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity