PCI: Mapping SMB Shares Within the PCI Jump Environment

Overview

As part of a software install/upgrade or maintenance, there may be a need to map a drive across a Jump Server. This allows an administrator to move install and data files to the correct location for continued operations. The following describes the process for temporarily mapping a drive across the Jump Server.

Important: Drive mapping is temporary and all mappings disappear when the Remote Desktop Connection (RDC) is disconnected.

  1. Log into the PCI jump server with the UMROOT\p-uniqname account.
  2. Launch PCI Desktop.

    Note:

    • Internet Explorer automatically launches RDC.
    • Non-Microsoft browsers download an RDC connection file, *.rdp, to launch.
  3. Open File Explorer and select Map network drive.
  4. Enter the SMB server and share location in the Folder field.
  5. Check the Connect using different credentials box and click Finish.
  6. Complete the prompts using UMROOT\uniqname and take note of the drive letter selected as it will be available in File Explorer.

Presenting Mapped Drives on a Second PCI Server

Present mapped drive content directly to another PCI server by tunnelling it over a jumped RDC connection.

  1. Launch RDC from the PCI desktop.

    Note: Search for Remote Desktop Connection from the Windows start button

  2. Open Show Options and click More on the Local Resources tab. 
  3. Expand Drives and check the box next to the mapped drive to tunnel into the PCI server.
  4. Click OK and then click Connect
  5. Locate the tunnelled drives using File Explorer

Tip: Some applications on the PCI server may not recognize or fully support these tunneled drive mappings as-is. If this is the case, and you cannot copy the remote content locally, assign a local drive letter to the tunneled content.

  1. Open a command prompt and use the net use command to assign a local drive letter to the tunneled content. Example: net use * \\tsclient\z maps the next available local drive letter to the remote \\tsclient\z drive (the Z: drive mapped above.) 

    Note: A local-to-your-PCI-server Z:\ drive is also used in this example. These letters may differ in your connection.

Last Updated: 
Monday, May 15, 2017