How to determine what in application causes UAC to be trigger in Windows 7 SP 1?
-
Our company is attempting to roll out Windows 7 (SP1) to new client boxes. There is one very large app that is causing the UAC box to pop up asking for administrative rights. Is there a utility or way to determine what section of code is triggering the UAC to popup? The application is very large and it would be nice to narrow down what area is requiring elevated rights. Thanks for any pointers or guidance ahead of time.
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison
-
Our company is attempting to roll out Windows 7 (SP1) to new client boxes. There is one very large app that is causing the UAC box to pop up asking for administrative rights. Is there a utility or way to determine what section of code is triggering the UAC to popup? The application is very large and it would be nice to narrow down what area is requiring elevated rights. Thanks for any pointers or guidance ahead of time.
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison
There's nothing that would cover all possiblities. Even Microsoft ACT[^] can't do it reliably. But, just in case, you'd best give it a try.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
There's nothing that would cover all possiblities. Even Microsoft ACT[^] can't do it reliably. But, just in case, you'd best give it a try.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
Hey Dave, Saw your post Friday but forgot to reply. Yeah, I had tried ACT Friday, but didn't have much luck with it for this particular app. Thanks for the response though.
"There's no such thing as a stupid question, only stupid people." - Mr. Garrison
No problem. We ran into this issue 2 year ago when we were considering moving from XP to Vista and had 1,000 apps to test. We quickly found out that there's nothing out there that can look at every app and tell you, definitively, which apps were going to work and which were going to fail, let alone how they were going to fail. There's a few thing to look at. The first is if you're going to enable UAC and at which level. The next is how your applications are going to react in a more restricted environment and how those problems are going to be mitigated. The results of some of this testing may affect the outcome of turning on UAC! The third thing to look at is the installers for your apps. Depending on your deployment environment, your apps may not even install correctly. We found a 40-50% failure rate in our installers alone. Most of those problems were easily resolved by either retiring the app if it was no longer needed, making only simple modifications to the installers, upgrading the app to a newer version, or using App-V to run the app.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak