\nPart 1 –\u00a0Caching Remote Systems PowerShell Modules<\/a>
\nPart 2 – PowerShell remoting<\/p>\n
In the previous blog post<\/a>\u00a0I covered how to use the Cache Export<\/strong>\u00a0tool to cache module information from a remote system using the Import Remote Cache<\/em>\u00a0button, which makes the modules available in the PowerShell Studio Object Browser.<\/p>\n <\/p>\n In this blog post I will show you how to use Windows PowerShell Remoting for remote scripting using PowerShell Studio.<\/p>\n The following topics will be covered:<\/p>\n <\/p>\n Before we start we need to configure our system to support Windows PowerShell Remote with PowerShell Studio.<\/p>\n First, verify that PowerShell is enabled for Remoting by executing the following one-liner:<\/p>\n Note: This command enables the computer to receive remote commands via the WS-Management service<\/em>.<\/p><\/blockquote>\n Next, verify that the WS_Management service is running (see image below).\u00a0 By default, this service will remain in Stopped<\/em>\u00a0status with the Startup Type<\/em>\u00a0set to Manual<\/em>.<\/p>\n For more information on how to setup PowerShell Remoting, see these PowerShell Help topics:<\/p>\n Note: Remember that PowerShell help information is available in your system. Execute the “Update-Help -force” command to download PowerShell help topics and cmdlets documentation.<\/em><\/p><\/blockquote>\n <\/p>\n Although it is not mandatory to create a PowerShell Profile, it is beneficial when adding your own set of custom functions and also when adding PSSnapin’s because they are made available when the PowerShell console is active.<\/p>\n Keep in mind, PowerShell Snap-ins are not modules and are not loaded automatically.\u00a0 If you are considering using a PowerShell Profile, it will be useful to add PowerShell Snap-ins during the PowerShell Remoting sessions in either\u00a0Windows PowerShell and PowerShell Studio console.<\/p>\n For more information about how to create a Windows PowerShell Profile and .NET Snap-ins, see these PowerShell Help topics:<\/p>\n <\/p>\n These steps will need to take place on the remote system<\/strong>\u00a0that will be accessed from Windows PowerShell, or from PowerShell Studio Consoles.<\/p>\n <\/p>\n The following steps will create a new Windows PowerShell Profile used for All Users and All Hosts<\/em>. Just make sure to open the Windows PowerShell Console using Run as Administrator<\/em>:<\/p>\n <\/p>\n Now, in order for the Windows PowerShell Remote session to automatically load the profile, we need to use the Register-PSSessionConfiguration<\/em><\/strong>\u00a0cmdlet with the ‘-StartupScript<\/em>‘\u00a0 parameter to include the location of the profile that we just created:<\/p>\n For more information about how to create a PSSession configuration, see these PowerShell Help topics:<\/p>\n <\/p>\n Finally, using either the Windows PowerShell Console or the PowerShell Studio PowerShell Console, we proceed to create a PowerShell Remote session from our local machine to the remote system. Using the Enter-PSSession<\/strong> cmdlet with the parameter ‘-ConfigurationName’<\/em>\u00a0followed by the name we registered in the PSSession configuraiton command.\u00a0 This will load the PowerShell Profile during the remote session.<\/p>\n Use the the following one-liner with the correct system name and credentials in either of the Windows PowerShell or the PowerShell Studio console:<\/p>\n This will verify that we have a successful remote connection to another system via PowerShell Remoting.<\/p>\n <\/p>\n If you don’t need to use the PowerShell Profile, PowerShell Studio gives you the ability to do remote scripting thru the Remote Console<\/em>\u00a0button found under the Platform<\/em>\u00a0ribbon menu.<\/p>\n \u00a0<\/a> The Remote Console<\/em> is good for basic system-to-system remoting without the need to create a PSSession configuration name.<\/p>\n <\/p>\n If you’re constantly managing multiple systems, it would tedious to perform these steps every time:<\/p>\n PowerShell Studio allows for creating additional Console hosts, and we can create remote connections to individual systems. This can be done using the Options<\/em>\u00a0button in\u00a0the Windows<\/em>\u00a0ribbon menu. You can add custom consoles in the\u00a0Console<\/em>\u00a0section.<\/p>\n The following sample will be used to create a new console host to remote connect to another system. This will require the name for the Console host, and the command line to execute:<\/p>\n Name: PSSessionToRemoteSystem1<\/strong><\/p>\n Command line:\u00a0C:\\WINDOWS\\system32\\windowspowershell\\v1.0\\powershell.exe -noexit -Command “Enter-PSSession -ComputerName SystemName -Credential Domain\\UserName -ConfigurationName MyPSSessionName”;<\/strong><\/p>\n Note: Please notice that the one-liner has the system name and credentials hard coded.\u00a0Also, the parameter ‘-ConfigurationName’ is optional.<\/em><\/p><\/blockquote>\n When you have added the new console host command line, exit the Option<\/em>\u00a0panel and restart PowerShell Studio.<\/p>\n The next time you click on the Console<\/em>\u00a0panel, the newly added PSSession Console is available in the console drop-down list:<\/p>\n Select the newly added console “MyPSSessionXXX”, and this will remote connect to the other system.<\/p>\n <\/p>\n You need to properly configure and test your Windows PowerShell environment to support PSRemoting before you start working with PowerShell Studio against remote systems. Taking advantage of the PowerShell Help documentation and PowerShell Studio features will assist in extending both your local and remote scripting to work interactively with PowerShell on any system.<\/p>\n Note: The overall concept explained in this blog post can be applied to our PrimalScript<\/a> editor.<\/em><\/p><\/blockquote>\n <\/p>\n 1. Developing PowerShell scripts for other machines (Part 2)<\/a>. <\/p>\n As always, if you have any ideas, comments, or feedback, please\u00a0visit our feedback forum<\/a>\u00a0and reference this post.<\/p>\n <\/p>\n![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/RunCache_07a_2018-09-07_16-19-56-300x167.jpg\")
\u00a0<\/a>![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/RunCache_08_2018-09-07_16-19-56.jpg\")
\u00a0<\/a>![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/RemObjectBorwser_01_2018-09-19_17-49-23-182x300.jpg\")
<\/a><\/p>\nPart 2 – PowerShell remoting<\/h3>\n
\n
Prerequisite for PowerShell Remoting<\/h4>\n
Enable-PSRemoting -Force<\/pre>\n
![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/WSMANService_01_2018-09-20_9-05-19-300x200.jpg\")
<\/a><\/p>\n\n
## - Display PowerShell Help Topics:\r\nGet-Help about_Remote -Detailed\r\nGet-Help about_Remote_Troubleshooting\r\n<\/pre>\n
Adding Functionality using PowerShell Profile<\/h4>\n
\n
## - Display PowerShell Help Topics:\r\nGet-Help about_Profiles -Detailed\r\nGet-Help about_PsSnapins<\/pre>\n
PSSession Configuration setup<\/h4>\n
\n
Create a simple PowerShell Profile<\/h5>\n
'function myProfile{ \"My System $Env:COMPUTERNAME profile has been loaded!`r`n\"+\"$($PSVersionTable.PSVersion)\"}; MyProfile;' | Out-File $PsHome\\Profile.ps1;<\/pre>\nPSSession Startup Script<\/h5>\n
Register-PSSessionConfiguration -Name MyPSSessionProfile -StartupScript $PsHome\\Profile.ps1<\/pre>\n
![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSWnServer_2018-09-12_15-49-55-300x188.jpg\")
<\/a><\/p>\n\n
## - Display PowerShell Help Topics: \r\nGet-Help\u00a0Register-PSSessionConfiguration<\/pre>\n
PSSession Configuration name<\/h4>\n
Enter-PSSession -ComputerName W2k16SHP01 -Credential trinity\\maxt -ConfigurationName MyPSSessionProfile<\/pre>\n
![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSWinConsole_00_2018-09-12_16-05-26-300x169.jpg\")
<\/a>\u00a0 \u00a0![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSWinConsole_01_2018-09-12_16-05-26-300x131.jpg\")
<\/a><\/p>\nPowerShell Studio “Remote Console”<\/h4>\n
![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PS_RemoteConsole_2018-09-12_10-37-12-300x94.jpg\")
\u00a0<\/a>![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSStudioRemoteConsole_01_2018-09-20_10-07-27-300x136.jpg\")
<\/a><\/p>\n![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSStudioRemoteConsole_00_2018-09-19_17-50-50-300x63.jpg\")
<\/a><\/p>\nCreating a PSSession Console Host<\/h4>\n
\n
![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSSession_00a_2018-09-12_11-18-54-300x103.jpg\")
<\/a><\/p>\n![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSSession_01_2018-09-12_11-18-54-300x180.jpg\")
<\/a><\/p>\n![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSSession_02_2018-09-12_11-18-54-300x118.jpg\")
<\/a><\/p>\n![\"\"](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/PSSession_03_2018-09-12_11-18-54-300x125.jpg\")
<\/a><\/p>\nConclusion<\/h3>\n
Related Articles<\/h3>\n
\n2. But it works on my machine\u2026<\/a><\/p>\nFeedback<\/h3>\n
![\u00a0<\/a>](\"https:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2018\/09\/RunCache_07a_2018-09-07_16-19-56.jpg\"){kind=link}