Do not post any licensing information in this forum.
It is not clear why you ask this. Remotely you have to import the modules. Locally you can d either. It is your choice.
PowerShell Studio says nothing about how to use PowerShell. PSS is just an editor and development tool. PowerShell is the decider in all cases
jvierra wrote:Yu don't load the shell. Just remote into Exchange.
What is the purpose of importing the remote cache (CacheExport.zip) in this scenario? AKA Exchange
When I use a SharePoint server (importing the cache file) I can add the remote snapin using only the remote cache configuration.
Get-Command -Module Microsoft.SharePoint.PowerShell | Out-File d:\psscripts\SP2013Commands.txt
It seems to me that importing remote cache (when it comes to dealing with Exchange and the Exchange Shell) is of no use because by using the following:
$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://servername/PowerShell/ -Authentication Kerberos -Credential $UserCredential
I am confined to running this script via a local machine connection as I would without Powershell Studio 2015.
I am new to this so maybe I missing something here.
I would prefer to use the Remote Cache feature for Exchange.
In a remote session you can either enter the session and type commands or attach to the session and use Invoke. We can import the session and it will mostly appear to be local but objects will behave somewhat differently.
Who is online
Users browsing this forum: No registered users and 1 guest