For the Remote mount feature only:
The remote mount feature depends on and uses Windows Powershell Remoting. You must have Windows Powershell 2.0 or greater and have the servers in
your environment configured for remote management. The steps required to enable Windows Powershell Remoting in your environment depends on many
things, refer to the following Microsoft article to see a full explanation ->
As reference, below are some possible configurations and the steps to enable Windows Powershell Remoting.
– Between computers within a single domain.
1) On each server issue the Powershell command -> “Enable-PSRemoting –force”
– Between computers in multiple domains or computers in a workgroup
On each server issue the following Powershell commands.
1) Enable-PSRemoting –force
2) Set-ItemProperty –Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System –Name LocalAccountTokenFilterPolicy –Value 1 –Type
3) Set-ItemProperty –Path HKLM:\System\CurrentControlSet\Control\Lsa –Name ForceGuest –Value 0
4) Set-Item WSMan:\localhost\Client\TrustedHosts –Value -Force
5) Set-Item WSMan:\localhost\Client\TrustedHosts –Value -Force -Concatenate
6) net stop winrm
7) net start winrm
Note: PowerShell by default does not allow a double hop; meaning that a remote command executed on Server-A to Server-A that sends a request to
Server-C will not work with out special consideration. This is important to take note on because in our Data Protection for exchange
implementation for Exchange 2010 we utilize wsman connections to the local machine in order to execute Exchange Powershell commands. The wsman
connection to the local machine is equivalent to a remote server and will count as a ‘hop”. In our remote mount implementation we avoid any
remote DP CLI calls that will make wsman connections to the local server.