Regarding UAC-
I found this bypass of UAC way deep in MS-TechNet and it was about a month
old. I read about every article Mark R from MS-TechNet ever wrote about
"UAC". What I found out is it is a problem and MS knows it's there but
required also (read on). Companies, Developers, Code writers and even as
high up as Symantec's its self has had issues with UAC (see provide lookup
below). I also noticed that when I applied this routine on my laptop, it
was NOT going to be the first PROGRAM to use this method in Task Scheduler.
My Anti-Virus "Vipre" uses this process and also my backup routine company
uses this process, etc. So this is NOT new news to MS and because of virus
and hackers, it was what MS could do to protect the users. It's not a bug or
fault. I suppose we all could blame code writers of viruses for the MS-UAC.
I was also asked, "Why be so insistent on finding the answer? Just lower the
UAC setting and leave it at that!" Well I have compiled apps out there and
they are older MS OS, and they ALL run at User level. However one customer
already has MS-7. Running my compiled app, they have to use a UAC 'Ok'
button every time they launch my program? 30 times a day, I now have an
answer.
Also a lot of corporate computers and the IT department are not allowing the
UAC setting to be reduced due to the MS hype and how they feel UAC is that
important and useful.
First go to Task Scheduler and follow the steps below.
1. Create a NEW task and REMEMBER what you called it. I 'ctrl-c' ed
the name for my use.
2. Click on the box add "Run with the Highest Privileges"
3. Go to Action Tab and click on 'New'
4. Browse to 'C:\RBTI\RBG##\RBG##.exe
5. Make sure Action is default 'Start a program'
6. Check the values if you have a laptop and uncheck if you so desire?
7. Go to the main screen and make sure 'Allow task to be run on
demand' & 'Stop if longer than 1 day or what you want'
8. In the setting window you may wish to change the lower left
hand box to read 'Run a new instance in parallel' if you would like more
than one RBase app running.
9. Close the Task Manager
Now go to your desktop and add a shortcut using the following in the
shortcut. 'C:\Windows\System32\schtasks.exe /run /tn "what you named or
Ctrl-V" if you are lucky and attended the May '09 eXtreme Release you have
a copy of the icon for 32 & 64 RBG9.0 with the Gummy "R" & bit ver.
Sincerely,
Paul D.
See what happened with Symantec's experience in the past. Google "Symantec
and UAC" most are from '08 and on, Vista related and it continues in to
MS-7. So The UAC was improved in MS-7 but still has issues. If you would
like any of the links just let me know. UAC is here to stay for our
protection, but it is a double edge sword in my opinion. My .02
Compilers/Curious minds, try this. On MS-7 compile your app and send it to
the desktop and RUN it! UAC stops it. Add the following, save the script
and install it on that machine, now it works without the UAC message. Any
questions/comments?
