RDCMan to Hyper-V console

Remote Desktop Connection Manager is a essential tool if you run a lot of virtual machines or need to connect to a lot of customers as i do.  One of the new features in version 2.7 allows the ability to connect directly to virtual machines (called virtual machine connect-to-console support).  Configuring a connection for this new feature is rather easy once you have the ID of the virtual machine.  The following PowerShell command should do the trick:

get-vm | Select Name,ID

Once you have this information, enter it on the Server Settings tab like in the following screen shot, i’ve used the Win10 VM:

Once you have this set up, you should be almost set to go…We also need to set some registry settings otherwise you will be facing this error:

The reason for the error appears to be that the Credential Security Service Provider (CredSSP) policy on the Hyper-V host is not enabled to authenticate user credentials from a remote location.

Open Powershell as Administrator and paste the following:

#Disclaimer:
#Your use of these example scripts or cmdlets is at your sole risk. This information is provided “as-is”, without any warranty, whether express or implied, of accuracy,
#completeness, fitness for a particular purpose, title or non-infringement. I shall not be liable for any damages you may sustain by using these examples, whether direct,
#indirect, special, incidental or consequential.

New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentials -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowDefaultCredentialsDomain -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentials -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsDomain -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnly -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowFreshCredentialsWhenNTLMOnlyDomain -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentials -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsDomain -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force
New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Credssp\PolicyDefaults\AllowSavedCredentialsWhenNTLMOnly -Name Hyper-V -PropertyType String -Value "Microsoft Virtual Console Service/*" -Force

Also make sure you’ve added your user account from your local computer to the “Hyper-V Administrators” group

#EOF

Polycom Trio 8800 failed to discover exchange server (Office365)

Polycom Realpresence Trio

Deployed some Polycom Trio’s in my organisation (we’re running Exchange Online and Skype for Business Online) and everytime i went to the Calendar the Polycom was showing an error “Failed to discover exchange server”.

How to solve this error

Login to the webinterface from the Polycom Trio 8800 (first time enable HTTP/HTTPS connection from the Polycom Advanced Option, Default password is “456”)

Go to Settings > Applications


Disable the AutoDiscover and Fill in the following Exchange Server url:

https://outlook.office365.com/EWS/Exchange.asmx

Save configuration and restart your Polycom device.

No presence information in Outlook (Skype for Business)

Got an issue after installing the Mitel MiCollab software. Microsoft Outlook did not display the status of Lync/Skype anymore. Also in my Outlook client the information from GAL (Global Address List) was not visable anymore when hovering over a name.

Some other issues i found out:

  • The Microsoft SharePoint client/web does not display presence information.
  • Other Microsoft Office applications that support presence features do not display presence information

The Solution

This behavior may occur if the value of the DefaultIMApp registry entry in the following registry key is incorrect:

First, look at this location in the registry…

[HKEY_CURRENT_USER\Software\IM Providers] 

It should show this value:

“DefaultIMApp”=”Lync”

If there is any other value, change it back to “Lync”, in this case the MiCollab software is changing this value to “Micollab”.

Now restart Outlook and see if your presence indicators are back.

Note: The DefaultIMApp registry entry specifies which IM application provides IM and presence information in Office applications.

.NET Framework 4.6.2 is supported with the February 2017 Cumulative Update for Skype for Business Server 2015

Both Lync Server 2013 and Skype for Business Server 2015 are supported with the .Net Framework 4.6.2.

Skype for Business Server must have the February 2017 update for Skype for Business Server or later installed.

This update can be found at https://support.microsoft.com/en-us/help/3061064/updates-for-skype-for-business-server-2015

Lync Server 2013 must have the November 2016 update, or later installed. This update can be found at https://www.microsoft.com/en-us/download/details.aspx?id=36820.

Execution of Scripts is Disabled on this System

When you try to run a powershell script on Windows, you may receive the following error stating that the execution policy on your computer does not allow you to run the script.

To fix this error, you must change the PowerShell execution policy for this computer.  These instructions will explain how to allow “Unrestricted” access to running scripts on your computer.

  1. To set the execution policy to unrestricted, enter the following command (PowerShell must be run as an Administrator):
    1. Set-ExecutionPolicy Unrestricted
  2. You will receive a warning indicating that you are trying to change the execution policy and the risk that is associated with the change.  Enter ‘Y’ and press enter.
  3. Your execution policy is now changed.  You can verify this by executing the command “Get-ExecutionPolicy”.  You can now try to run your script again and you should not receive any errors.