Recently we have been setting up a new test stand for SmartCode VNC Manager. The hosting server was running Windows Server 2016 with Hyper-V role enabled. The server was a member of a workgroup. And then we had a bunch of VMs created on the server. The VMs were part of a test active directory domain. One of the VMs had SmartCode VNC Manager installed. We wanted to test a new Hyper-V management functionality, and we tried to establish a connection to the hosting Hyper-V server. We kept receiving the "access denied" error. Turns out we have got a KB article that covers that exact issue. The problem was caused by the System user not having the Remote Access permission assigned under DCOM Default Settings.In hopes that this may help our customers with troubleshooting "access denied" errors in SmartCode VNC Manager, I'm reposting the content of the KB article in this blog post.You may receive an "Access Denied" error when you attempt to use one of the SmartCode VNC Manager remote managment tools, for example, Service Manager, or when you attempt to deploy VNC server to a remote PC. The steps below can help you to troubleshoot the problem:Make sure that you have entered a valid administrative logon credentialsWindows XP: Simplified File Sharing must be turned off. To turn it off: Open Windows Explorer. Tools->Folder Options->View. Uncheck "Use simplified file sharing" item.Windows Vista / 7 / 8 / 10 with UAC turned on: Change the value of the LocalAccountTokenFilterPolicy registry entry on the remote Windows Vista/7/8/10-based computer so that the full credentials can be passed between the computer running SmartCode VNC Manager and the remote computer. For more information, see the following article in the Microsoft Knowledge Base: How to change the Remote UAC LocalAccountTokenFilterPolicy registry setting in a Windows Vista imageYou should check that Allow Distributed COM setting is enabled on the computer you are trying to deploy to (it's enabled by default but some software might turn it off). To do so you should open Component Services snap-in. Start->Administrative Tools->Component Services. When snap-in is running in the left tree navigate to: Console Root->Component Services->Computers->My Computer and select Properties command.NOTE: you must run the snap-in on the computer you are trying to deploy to. Or you can also connect to the computer remotely by running New->Computer context menu command available for the Console Root->Component Services->Computers tree node.Do not close the properties window and proceed to the next step.Ensure that under the default access permission the SYSTEM user has "Remote Access" permission enabled.
