One may like this or not, the solution is luckily pretty simple.
If the user wants to administer the workstation with a Security Account Manager (SAM) account, the user must interactively log on to the computer that is to be administered with Remote Assistance or Remote Desktop, if these services are available. Connections made with domain accounts remain unchanged. In other words, it removes the SID for “Administrators”. It filters the access token for connections made with local user accounts or Microsoft accounts (the latter typically have the format MicrosoftAccount\EMailAddress). Type the password for \\192.168.175.129\c$:Īs described in MS KB article 951916, Microsoft introduced as part of UAC a little known feature called “UAC remote restrictions”. When you try to connect to the admin share on the command line, you get a different error message: C:\>net use \\192.168.175.129\c$ /user:win7-2\admin * The message hints at multiple connections, but that is misleading. Disconnect all previous connections to the server or shared resource and try again. Multiple connections to a server or shared resource by the same user, using more than one username, are not allowed. Contact the administrator of this server to find out if you have access permissions. You might not have permission to use this network resource. In this situation you get the following error when trying to connect to the admin share in Explorer: non-administrative) share works flawlessly, though. C$) on remote computers, even though you use the right credentials.
Under certain circumstances, you cannot connect to administrative shares (e.g.
0 kommentar(er)
