Hello Adam, and welcome to Seven Forums.
Yes, that would be correct. Since the shortcut uses the password of the built-in Administrator to approve running it elevated, it would fail to run if the built-in Administrator account was disabled.
I'll add a note to the tutorial to help prevent this. Thank you. :)
Last edited by Brink; 06 Mar 2014 at 11:12. Reason: added quote
HI,
When I run my shortcut as the admin user I get an error 740: The requested operation requires elevation.
I have not logged back in as the std user I was just testing it as the admin.
What did I do wrong?
Machine is Win 7.
Cheers
Hello RJ, and welcome to Seven Forums.
Did you use runas with the built-in Administrator account for the target location of the shortcut?
Sorry Yes I worked out it had to be the administrator account not just an administrator account
Thanks for the post v informative.
I don't suppose you know if it works on Terminal server. I dont want to give admin rights to the users.
Would the same process apply?
Hello,
I noticed that I can run any program requiring Admin rights under SUA which is on the local hard drive but this does not work with programs on pen drives!! Strange!
Has anyone tried this successfully? Also I was able to run the programs with newly created Admins as well not just built in Admins.
Win 7 Ultimate
Hi Brink,
I just checked its NTFS but assuming if it was FAT32 it shouldn't have any problems running the runas command but still it doesn't work. The black box simply disappears. There's no typo since the same procedure works perfectly for programs on the hard drive.
Have you tried running them from usb drive?
Hello Exus,
I just tested this with a standalone exe file on a USB flash drive, and it works just fine. It doesn't matter if the USB flash drive is FAT32 or NTFS.
It sounds like you may have not typed the password in correctly. To test, remove the saved credential for the shortcut in Credential Manager, and run the shortcut again to be prompted to enter the password again, and see if it may run properly afterwards. :)
Hi Brink,
Ok I just tested using the Built-in Admin account and everything is working fine. I was facing problems using the newly created admin accounts. I was hesitant using the built-in Admin account since its not considered a safe practice to keep them enabled. Maybe securing the builtin admin with a strong password seems to be the only viable option. Anyways thanks alot for your help
Last edited by exus69; 10 Jun 2014 at 03:20. Reason: Title added
You're most welcome. :)
Ah, that's why then. It'll only work with the built-in Administrator.
Yeah, if you use a strong password, it'll help keep out unauthorized access. If you like, you could also rename the "Administrator" account to something that people wouldn't think it was the built-in Administrator by just looking at it. If you rename, you'll need to recreate the shortcuts using the new name though.
Built-in Administrator Account - Change Name
Quote