Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.msdos.batch    |    Fun with MS-DOS batch files    |    42,547 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 41,968 of 42,547    |
|    Andy Burns to Scott Lurndal    |
|    Re: Why Windows 10 batch admin isn't the    |
|    11 Sep 21 09:44:21    |
      XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows       From: usenet@andyburns.uk              Scott Lurndal wrote:              > on second thought, there must be something in between:       > a. A "real" admin       > b. A user with admin privileges       > c. The user              Yes, being a member of the admin group dos not automatically mean you       are *using* all your admin rights              if you are logged in as your admin user, open a CMD window       then open another CMD window "as administrator"              look at the title of each CMD window              try out some harmless commands within each of them, e.g.              whoami /priv              arp -d *              route add              > I base that on the fact that if I type the command in a user cmd prompt:       > c:\path-to\openvpn\bin\openvpn.exe vpnconfigfile.conf       > it will fail (if I run it as the user) to set the routing table properly.              I can't remember if openvpn calls the network APIs, or if it spawns to       the route.exe or netsh.exe commands              > However, if I type the exact same command in an admin window, it will work.       >       > Hence, the user (even with admin privileges) must still be only midway       > toward being a "real" admin given the user (even with admin privileges)       > can't successfully run the necessary route commands to get onto VPN.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca