Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, April 17, 2016 5:16 AM | 1 vote
I upgraded my "Server" (its a desktop computer with a handful of HDD's in it, and normally no kb/mouse/monitor) to Windows 10 and now all my Share Folders and RDP are not accessible.
When I try to run Remote Desktop from my Desktop I get "The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support." As the "System Administrator" this leaves me scratching my head and saying, "No I Didn't!". I dug out a kb and monitor and checked, RDP is still allowed on the Server. The server only has one user account. I tried adding it to the permissions even though it said "[Username] already has permission" but it didn't help. I can RDP to the server from my surface pro.
Also, I don't know it it is related or not but when I try to access the share (double clicking on the "Server" icon under "Network") from my surface pro gives the error: "\SERVER is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
Logon failure: the user has not been granted the requested logon type at this computer." I cannot even view the available shares on the computer, but I still tried explicitly adding the username to the permissions for a couple of the shared folders but there was no change. This doesn't occur on my desktop.
None of the computers are on a domain and I have not set any group policies, so these shouldn't be an issue unless the Windows 10 upgrade set them automatically.
Anybody have any suggestions how to fix the issue (other then rolling back to Windows 7)?
-Thanks
Original post:The system administrator has restricted the types of logon (network or interactive) that you may use. After Windows 10 Upgrade
All replies (18)
Wednesday, April 27, 2016 6:53 PM ✅Answered
Ok, I feel dumb for not noticing this before but I was logging into my server from my tablet and I noticed that under User Name it said "MicrosoftAccount\Media" (Media is the local Username for the server but there is no Microsoft account attached to it that I know of) so I tried logging into RDP from My desktop but instead of using "\Server\Media" as the username like I always did under Windows 7, I typed "MicrosoftAccount\Media" and it logged in instantly. Apparently Microsoft changed how User accounts are managed from Windows 7 to Windows 10.
However, after doing so, I could no longer access the File sharing on the server from my desktop by double clicking "SERVER" from the list of Network Computers, so I tried to map a network drive. If I tried to browse into the "SERVER" listing it would pop up the same error I was getting on my Surface. I manually typed in the path to a shared directory, checked connect using different credentials, typed the "local" username (No Domain Specified) and password and Now I can access all the shared directories. Microsoft has really messed with me on this one.
As for the corrupt system file, it appears to be "OpenCL.dll". I tried copying it from my desktop (which passes SFC) to my server but it still fails subsequent SFC scans, I will start another thread If I cannot fix this as it would now appear to be a separate issue.
Thanks for the help
Sunday, April 17, 2016 10:30 AM | 1 vote
Hello,
Kindly go through suggestions mentioned here:
Hope this helps, Good luck :)
Windows Troubleshooting & How to guides - http://www.kapilarya.com
Sunday, April 17, 2016 1:07 PM | 1 vote
The Server is Win 10, updated from Win 7, correct?
The Desktop is what?
Best regards, George
Sunday, April 17, 2016 1:20 PM | 1 vote
On the desktop with the RPD issue, check the My Documents folder, should be a hidden Default.rdp file. Try deleting that and then see if you can connect via RDP.
For the Surface Pro, is it be prompted for a username \ password? If not check Credential Manager and remove any saved credentials for the 'server' under Windows Credentials. Try connecting and enter the username as computer name \ username, of SERVERNAME\username to tell windows to check the credentials against the 'server'.
Tuesday, April 19, 2016 9:45 AM | 2 votes
Hi Shadow42,
Are there any error messages recorded in the Event Viewer(Windows Logs\Application, System)?
According to the error message” the user has not been granted the requested logon type at this computer”, the reason this issue occurs could be the user does not have the permissions to access the RDP Server from network.
We need setup” Access this computer from the network” policy to assign your current user right allow access to the RDP server.
Policy path: Computer Configuration\Windows Settings\Security Settings\Local Policies\ User Rights Assignment Access this computer from the network
Please refer to the following link for detailed steps, see the marked answer.
“Logon failure: The user has not been granted the requested logon type at this computer”
Process Monitor v3.2
https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx
We could refer to the following link to have a troubleshoot (filter “Access Denied” error).
Solving Access Denied Errors Using Process Monitor
http://improve.dk/solving-access-denied-errors-using-process-monitor/
Best regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, April 21, 2016 3:25 AM | 1 vote
Kapil.Arya: I looked through the thread you linked, everything in there points to editing group policy. Apparently they changed the way to edit group policy in windows 10. In windows 7 you could access it through "gpedit.msc" but under windows 10 i get an error "Windows cannot find 'gpedit.msc'. Make sure you typed the name correctly, and then try again." How do you access it in Windows 10 Home?
-Thanks
Thursday, April 21, 2016 3:29 AM | 1 vote
George.B.Summers: Yes, The server was Windows 7 Pro x64 upgraded to Windows 10 Pro and the desktop was Windows 7 Home Premium x64 upgraded to Windows 10 Home.
-thanks
Thursday, April 21, 2016 3:35 AM | 1 vote
I tried deleting the Default.rdp file and it still will not work.
I removed all references to "Server" from the credential manager (there was an entry for "Server" and an entry for "TERMSRV/SERVER". Still cannot connect/browse available shares on the Server.
-thanks
Thursday, April 21, 2016 4:21 AM | 1 vote
Hi Shadow42,
We could type”group policy” in search box, then we will be able to see” Edit group policy ”
Best regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, April 21, 2016 4:25 AM | 1 vote
There don't appear to be any events logged to Windows Logs\Application or Windows Logs\System at the time RDP connection is denied.
Group policy on the server already lists "Everyone" under the "Access this computer from the network” policy. I tried Adding my desktops user to the list (PC-Name\username) but get "An extended error has occurred. Failed to save Local Policy Database." There doesn't seem to be a way to access Group Policy on the desktop.
Turning Password protected sharing off on all computers has no effect.
The only things listed on Process monitor under Access Denied are "C:\Program Files\WindowsApps" it is listed 5 times.
-thanks
Thursday, April 21, 2016 4:28 AM | 1 vote
All that comes up is an app on the Windows store
EDIT: After some searching I have come to the conclusion that Group Policy is not supported on Windows 10 Home, so does that mean it can't be causing the problem? I can RDP to both my Windows 10 Pro HTPC and my Windows 10 Pro Surface from my desktop, just not directly to the server. How else would the "Administrator Restrictions" be edited?
-thanks
Thursday, April 21, 2016 5:12 AM | 1 vote
Unfortuntely there is no Group Policy Editor in Windows 10 Home Edition.
Best regards, George
Thursday, April 21, 2016 11:02 AM | 1 vote
Hi Shadow42,
It is a Windows 10 home edition in this case, right?
I should have thought it at first.
Windows 10 home can remote connect to other computers, but we can't remote desktop to Windows 10 Home. That requires Windows 10 Pro.
Best regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, April 21, 2016 12:20 PM | 1 vote
The Home Edition machine has always been the RDP client and all the RDP Servers are Windows Pro. Everything worked great when all the computers ran Windows 7 and even worked after the desktop was Upgraded to Windows 10 Home. The problems didn't start until I upgraded the Server from Windows 7 Pro to Windows 10 Pro.
Ho do I edit the "Administrative Restrictions" on Windows 10 Home? Since there is no Group Policy is there some kind of Local Policy Editor? There is only 1 user account on the machine, and it is a full administrator account but somehow the Administrator account doesn't have permission from the Administrator to RDP to the server.
Why Am I only having trouble Connecting to the Server but can easily connect to other computers without issue. ? I can even RDP from my desktop to my HTPC, then open a remote desktop client on the HTPC and RDP into the server from there, it works but is not ideal (slow and I couldn't even get the Start menu to open), so I can use it as a temporary work around if needed, but i need to get the root problem figured out.
-thanks
Monday, April 25, 2016 1:55 AM
Hi Shadow42,
It is glad to hear that you found a workaround here, we will keep on research to find the root case.
After my research, we could configure the Restricted Admin registry setting to have a try.
To configure the Restricted Admin registry setting, add a DWORD value that is named DisableRestrictedAdmin to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
To do this, follow these steps:
- Locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
- add a DWORD value that is named DisableRestrictedAdmin
- To disable Restricted Admin mode, type 1 in the Value data box, and then click OK.
In addition, we need also configure the require use of specific security layer for remote (RDP) connections registry setting
Locate and then click the following subkey in the registry: HHEY_LOCAL_MACHINE\Software\Policy\Microsoft\Windows NT\Terminal Services
Then, configure FEncryptRPCTraffic DWORD value equal 00000000
We need setup these registry settings on both RDP clients and servers to have a try. Please backup the registry key before we made any modifications to it.
Best regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, April 26, 2016 5:12 AM
That doesn't appear to have helped, however I think the problem here may lie elsewhere. I was talking with the IT guy at work and he suggested running sfc and it found corrupted files it couldn't fix I will try to run it a couple more times to see if it helps. I have also had other problems start to show up with the server, mainly the computer is now extremely slow even though there is (according to task manager) less than 20% cpu usage, 25% RAM usage, 9% disk activity. Powershell loads to the prompt in 3 seconds on my Surface Pro, it takes well over 30 on the server. And the start menu no longer opens, I thought it was just being slow but I gave up waiting on it to open after 2 minutes when I was timing it, still have not gotten it to open. I will report any findings.
Thanks
Wednesday, April 27, 2016 11:14 AM
Hi Shadow42,
If the SFC found corrupted files, your current system files should be already corrupted.
Since it cannot be fixed automatically, we could try to manually replace the corrupted files with a good copy from another healthy computer.
Please see” How to manually replace a corrupted system file with a known good copy of the file”
https://support.microsoft.com/en-sg/kb/929833
In addition, we could run the DISM command from an elevated CMD prompt to restore the system components.
For example,
DISM /Online /Cleanup-Image /RestoreHealth
If the issue persists, considering there are more than many issues on this computer. We could consider refresh PC to fix all of current issues. Refresh PC won’t affect your personal files. Apps you installed from websites and DVDs will be removed. Apps that came with your PC and apps you installed from the Windows Store will be reinstalled.
Best regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Saturday, May 28, 2016 6:37 AM
Shadow42,
I have found the following assuming you have a good filesystem on your network share:
To access the share via Windows Explorer
- Go to Credential Manager (I just searched for it with the search bar next to Start Menu)
- Remove all credentials that have been saved for the media computer.
- Create a new credential using the "MicrosoftAccount\media" username and password scheme.
- You should now be able to access the share.
I did the above and found that not only did I get access via RDP, but I also had access, without logging in, to the network share.
CodeWarrior