Thanks for the suggestion, but we already tried that and it can't be done with Vista or 7. On Vista or 7, no program that requires Administrative privileges can start with Windows through the startup folder or registry Run entry. Microsoft's User Account
Control will automatically block any and all programs that require administrator access from within the normal startup routine...
That's the whole reason we tried using the Task Scheduler, because it's the only ways we've been able to get the program loading with the correct permissions at startup.
We've tried using a service, but the service ALWAYS, no matter what, runs on the SYSTEM user account and is only capable of starting the application in a SYSTEM account as well. The SYSTEM account is incapable of elevating any process to Administrator; regardless
of how its opened, it always opens as SYSTEM.
And we can't create another admin-based program to elevate it, because there's no way to elevate the first one in the chain, so we'd be back to square one.
I don't understand how other programs requiring administrative privileges are capable of starting up with Windows and not running into such problems...
About your suggestion for the BootTrigger, I'm wondering if it would work. The program will not start up beyond InitializeComponent() unless an internet connection is available to check the license with the server, so I'm curious to know if this program
would actually startup correctly.... Sound like an adventure, I'm down to try it and will come back and report on it.
Thanks again for the help =)