{"id":16052,"date":"2018-09-20T06:00:36","date_gmt":"2018-09-20T13:00:36","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=16052"},"modified":"2018-09-28T11:04:56","modified_gmt":"2018-09-28T18:04:56","slug":"powershell-studio-working-with-remote-systems-part-1","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2018\/09\/20\/powershell-studio-working-with-remote-systems-part-1\/","title":{"rendered":"PowerShell Studio: Working with Remote Systems (Part 1)"},"content":{"rendered":"

This is the first post in a blog series about working with remote systems using PowerShell Studio.<\/p>\n

The following topics are covered:
\nPart 1 – Caching Remote Systems PowerShell Modules
\nPart 2 – PowerShell remoting<\/a><\/p>\n

In this first installment I will show you how to use SAPIEN Technologies’ Cache Export tool to collect module information from a remote system, and then use PowerShell Studio to create scripting solutions by using the exported cache.<\/p>\n

Part 1 – Caching Remote Systems PowerShell Modules<\/h3>\n

The ability to access modules residing in remote systems allows us to create PowerShell solutions that span infrastructure and DevOps environments. PowerShell Studio<\/a>\u00a0and PrimalScript<\/a> include components, such as the “CacheExport2018.exe”, to help you access modules on remote systems.<\/p>\n

Cache Export Executable<\/h3>\n

PowerShell Studio and PrimalScript include a component that will collect the module information from the remote system\u2014”CacheExport.exe<\/em>“. This program will extract module information into a file which can be accessed from the Cache Editor feature in PowerShell Studio and PrimalScript.\u00a0The file “CacheExport2018.zip<\/em>” contains the cache export executable.<\/p>\n

\"\"<\/a><\/p>\n

CacheExport2018.zip Location<\/h4>\n

“CacheExport2018.zip<\/em>” is located in the SAPIEN Technologies products installation folder under “Redistributables<\/em>“:<\/p>\n

PowerShell Studio file location:<\/p>\n

“C:\\Program Files\\SAPIEN Technologies, Inc\\PowerShell Studio 2018\\Redistributables<\/em>”<\/p>\n

\"\"<\/a><\/p><\/blockquote>\n

 <\/p>\n

PrimalScript file location:<\/p>\n

“C:\\Program Files\\SAPIEN Technologies, Inc\\PrimalScript 2018\\Redistributables<\/em>”<\/p>\n

\"\"<\/a><\/p>\n

 <\/p><\/blockquote>\n

Building the Cache Export File from a Remote System<\/h3>\n

The files in “CacheExport2018.zip<\/em>” need to be extracted on the server where you are going to create the Export Cache file.\u00a0 The steps outlined below are my preferred method because I don’t have to copy over the executable or leave it on the server.<\/p>\n

 <\/p>\n

Use Shared Folder<\/h4>\n
    \n
  1. Create a shared folder locally.<\/li>\n
  2. Copy “CacheExport2018.zip<\/em>” to the shared folder and extract the files, which\u00a0will create the “CacheExport2018<\/em>” folder containing the executable “CacheExport.exe<\/em>“.<\/li>\n<\/ol>\n

    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    Now we can proceed to connect to this shared folder from the remote system.<\/p>\n

     <\/p>\n

    Connect to the Shared Folder from the Remote System<\/h4>\n
      \n
    1. Open a Remote Desktop session to the remote system.<\/li>\n
    2. Use PowerShell or File Explorer to map a drive (x:) to the shared folder that contains the Cache Export executable.<\/li>\n
    3. Navigate to the attached shared folder (e.g.,\u00a0\u00a0x:\\CacheExport2018<\/em>).<\/li>\n<\/ol>\n

      \"\"<\/a><\/p>\n

      \"\"<\/a><\/p>\n

      \"\"<\/a><\/p>\n

       <\/p>\n

      Build the Cache File<\/h4>\n
        \n
      1. Run “CacheExport.exe<\/em>” to build the cache file:\n