Remote enable RDS (not thru remote registry)

If you want to open the remote desktop connectivity on a remote computer, you have few options. There is one that is very easy to find on posts – change the registry key: hklm\system\currentcontrolset\control\terminal server, key fDenyTSConnections to value 0. The second option is to propagate the same registry key with group policy (maybe this is the best choice).
However, what to do if you need to connect to the remote computer in this moment and there is no possibility to connect to the remote registry (remote registry service is disabled)? You can use a simple trick to execute commands on remote computer. The easiest way is psexec (you can download it here) and execute two commands:

  • psexec \\remotemachine reg add “hklm\system\currentcontrolset\control\terminal server” /f /v fDenyTSConnections /t REG_DWORD /d 0
  • psexec \\remotemachine netsh advfirewall firewall set rule group=”remote desktop” new enable=yes

This will enable the Firewall rule and change a registry key also in a situation where all other trying would fail. Be careful with firewall profiles. If you want to open RDP only for domain or private profile, you have to modify the command line properly..

Essentials functionality with more than one DC

Some of us want to use Essentials server rule for federation with Office365 in small companies, where we have more than one DC. Until now, this was a non supported functionality and it was not possible to install it (in this case, you received an error, that this is possible only on a DC – here is the article). August rollup for Server 2012R2 solves this issue and now it is possible to use the Essentials sync option for Office 365 also if you have more than one DC. You can download the update here..

SharePoint 2013 Danger Update (?)

I had a bad surprise today when I tried to upgrade a server with SharePoint 2013 Foundation installed. Unfortunately, I didn’t put enough attention on SharePoint updates.
This month this is again one bed update! You can read about it here.

Fortunately, after a quick research of the situation, in my case the solution was simple. The cause why the service was down, was that Application pools in IIS were not running (and I restarted the server before). After I started pools, everything was OK.
So, in my case it was not very danger…

Hope this post was on time for someone..

WP to LinkedIn Auto Publish Powered By : XYZScripts.com