Secure Remote Services Installation Guide PDF
Secure Remote Services Installation Guide PDF
Release 3.34
Installation Guide
REV 02
Copyright © 2019 Dell EMC Corporation. All rights reserved. Published in the USA.
Dell EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. Dell EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular
purpose. Use, copying, and distribution of any Dell EMC software described in this publication requires an applicable software license.
Dell EMC, EMC2, and the Dell and EMC logos are registered trademarks or trademarks of Dell EMC Corporation in the United States and
other countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to Dell EMC Online Support (https://support.emc.com).
Preface
Chapter 2 Installing
Overview..................................................................................................... 16
Install options .......................................................................... 16
Configuring SRS on Linux host using Docker Engine (SRS DE) ...................... 16
Prerequisites............................................................................ 16
SRS Installation Instructions..................................................... 17
Configuring Operating System for VM (SRS VE) ............................................ 19
Configure Network.................................................................... 19
First boot installation ............................................................... 20
Chapter 3 Provisioning
Root logon and Admin setup ....................................................................... 32
Provisioning screens/SRS setup.................................................................. 36
Registration.............................................................................. 36
Email Configuration .................................................................. 48
Policy Manager......................................................................... 49
Connect Home.......................................................................... 50
Glossary
As part of an effort to improve its product lines, Dell EMC periodically releases revisions of
its software and hardware. Therefore, some functions described in this document might
not be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your Dell EMC technical support professional if a product does not function
properly or does not function as described in this document.
EMC Secure Remote Services (ESRS) is being rebranded to Secure Remote Services (SRS).
This change is not reflected in the user interface as of the time of this publication.
Consequently, the screen samples in this document do not reflect the rebranding.
Note: This document was accurate at publication time. Go to Dell EMC Online Support
(https://support.emc.com) to ensure that you are using the latest version of this
document.
Purpose
This guide is part of the Secure Remote Services (SRS) Release 3.34 documentation set,
and is intended for use by customers and prospective customers.
Readers of this guide are expected to be familiar with the following topics:
◆ Local network administration
◆ Internet protocols
◆ Dell EMC storage system characteristics and administration
Related documentation
The following Dell EMC publications provide additional information:
◆ Secure Remote Services Release Notes
◆ Secure Remote Services Technical Description
◆ Secure Remote Services Pre-Site Checklist
◆ Secure Remote Services Site Planning Guide
◆ Secure Remote Services Port Requirements
◆ Secure Remote Services Installation Guide
◆ Secure Remote Services Operations Guide
◆ Secure Remote Services Policy Manager Operations Guide
◆ SRS Policy Manager 6.8 Installation Guide - Standard Windows
◆ SRS Policy Manager 6.8 Installation Guide - Integrated AD (Windows)
Documentation conventions
Dell EMC uses the following conventions for special notices:
DANGER indicates a hazardous situation which, if not avoided, will result in death or
serious injury.
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not
avoided, could result in minor or moderate injury.
NOTICE is used to address practices not related to personal injury.
Typographical conventions
Dell EMC uses the following type style conventions in this document:
Bold Use for names of interface elements, such as names of windows, dialog
boxes, buttons, fields, tab names, key names, and menu paths (what
the user specifically selects or clicks)
Italic Use for full titles of publications referenced in text and for variables in
body text.
Monospace Use for:
• System output, such as an error message or script
• System code
• Pathnames, file names, prompts, and syntax
• Commands and options
Monospace italic Use for variables.
Monospace bold Use for user input.
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections — the bar means “or”
{} Braces enclose content that the user must specify, such as x or y or z
... Ellipses indicate nonessential information omitted from the example
Technical support — Go to Dell EMC Online Support and click Service Center. You will see
several options for contacting Dell EMC Technical Support. Note that to open a service
request, you must have a valid support agreement. Contact your Dell EMC sales
representative for details about obtaining a valid support agreement or with questions
about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to:
[email protected]
This chapter provides the specifications that you will need to install and provision
SRS. Topics include:
◆ Preparing your environment......................................................................................... 10
◆ Specifications for SRS Virtual Edition and SRS Docker Edition .............................. 11
System requirements 9
System requirements
Dell
EMC
provided
Type Requirements software Notes
SRS Virtual • Server — VMware ESX 5.0 or later or Windows Hyper-V SRS Default is one vCPU, but you
Edition (SRS environment on Windows 2008 R2 or Windows 2012 have the option to add
VE) and • Processor — One or more processors, each 2.2 GHz minimum, additional vCPU before SRS
Hyper-V must be SSE2 supported (required for FIPS compliance) is powered up.
• Free Memory — SRS requires a site-supplied
Minimum: 4 GB ESX or Windows server.
Recommended: 8GB Two SRS Virtual Edition
• Free Disk Space — Minimum disk space required for your SRSv3 servers deployed on a
appliance is 64 GB separate ESX
• CPU — servers/Hyper-V servers are
Minimum: One vCPU, 2.0GHz or higher, 64-bit required for a High
Recommended: Two vCPU, 2.0GHz or higher, 64-bit Availability configuration.
• Browser — Internet Explorer 9 +, Mozilla Firefox, or Google Chrome One SRS Virtual Edition or
• 250 device support is applicable for CloudIQ-enabled customers. SRS Virtual Edition High
Availability Cluster can
Notice: The 3.34 VE can be configured to support a maximum of 250 support up to 250 devices.
devices. CloudIQ-enabled customers are recommended to utilize 2 Do not place
CPUs during VE configuration. VMware/Hyper-V images or
storage files on Dell EMC
devices managed by the
SRS Client.
When running clustered HA
Clients on VMware/Hyper-V,
each Gateway Client must
be located on different
physical hardware.
Collocation of a Policy
Manager on the SRS Host is
not supported or permitted.
The underlying SUSE
operating system is
customized for the SRS and
does not have the necessary
libraries.
The preferred method of
deploying SRS is through
VMware vCenter. If the user
does not have VMware
vCenter, then see KB Article
529262 - SRS: How to
deploy SRS VE 3.26+
without vCenter
https://support.emc.com/kb/
529262.
Dell
EMC
provided
Type Requirements software Notes
This chapter provides the information that you will need to prepare the SRS server for
the installation of SRS. Topics include:
◆ Overview.......................................................................................................................... 16
◆ Configuring SRS on Linux host using Docker Engine (SRS DE) ............................. 16
◆ Configuring Operating System for VM (SRS VE) ...................................................... 19
Installing 15
Installing
Overview
Apart from the SRS backend system, there is an SRS Gateway that is installed on the
customer site either on the product itself (embedded SRS Device Client), on a separate
physical/virtual machine, or as a binary installer for Linux.
Note: Cloud platform support for the SRS Docker Edition is best effort. Passive
FTP is not supported with SRS DE.
Prerequisites To install the SRS Docker on a Linux host, SRS requires that specific assigned ports
(see Port Requirements section below) on the system be available. If the prerequisites
are not provided, then the SRS application installer aborts the installation.
System Requirements Before installing SRS on a Linux host, the following must already be installed:
◆ Docker supported Linux distribution (x64 bit)
◆ Docker Engine (Docker runtime)
Using the binary installer, SRS can be installed on the Linux distributions that support
Docker. For a list of Linux distributions that are supported by Docker and for Docker
installation instructions, refer to the following address:
https://docs.docker.com/engine/installation/.
Note: The Docker Engine is supported on many Linux distributions (such as RHEL,
CentOS, OpenSUSE, and SUSE Linux Enterprise), for example, the following is the
link for a Docker installation on Red Hat Enterprise Linux (RHEL):
https://docs.docker.com/engine/installation/linux/rhel/.
Services Ports
SRS Installation The SRS installer performs the required prerequisite checks. In effect, it validates the
Instructions system requirements, Docker runtime, and the specified port availability.
To install SRS:
1. Download the latest SRS Docker Edition (SRS DE) for Linux on Dell EMC Online
Support and copy to the Linux server running Docker:
https://support.emc.com
2. To change the permission of the installer, use the following chmod command
example:
chmod +x esrsde-3.xx.00.01.bin
The command will check the following prerequisites, and proceed with
installation:
• Disk space availability, must be at least 64 GB
• Docker runtime
• Ports 21, 25, 443, 9443, and 8118 are free
• IP address is valid
At the end of a successful installation, the installer displays a message stating that
the SRS services are up and running and provides the URL for you to provision
SRS, as shown in the following figure.
5. After you copy and paste the URL to a Web browser, follow the steps starting at
the “Root logon and Admin setup” section in Chapter 3.
◆ IP address
◆ Default gateway
◆ DNS server
The following are optional:
◆ Do not change any elements (for example, firewall settings) of SRS, according to
customer security policies.
◆ Do not place VMware/Hyper-V images or storage files on Dell EMC devices
managed by SRS.
First boot installation Before you can access the SRS Virtual Edition Web UI, you must perform a first boot
installation.
This section provides the steps to install and configure SRS and to boot it through the
ESX Server/HYPERV.
Note: The version downloaded must match the virtual environment to be used.
◆ Enterprise level:
• Hypervisor is available at the customer site
• VMware or Hyper-V is available
◆ Customer must create a VM and install the OS.
To configure the SRS during first boot, follow the steps in the following sections.
1. Access the vSphere Client and select File > Deploy OVF Template..., as shown in
Figure 5 on page 20. The Deploy OVF Template - Source wizard appears.
2. In the Deploy OVF Template - Source wizard, use the Browse... button to select
the desired URL to download and install the OVF package, as shown in Figure 6
on page 21, and then click Next. The OVF Template Details window appears.
3. In the OVF Template Details window, verify the details and then click Next to
continue, as shown in Figure 7 on page 21. The End User License Agreement
window appears.
4. In the End User License Agreement (EULA) window, read the license in its
entirety, and then click Accept. The Name and Location window appears.
5. In the Name and Location window, enter a unique name and a location for the
deployed template, as shown in Figure 9 on page 22, and then click Next. The
Host/Cluster window appears.
6. In the Host/Cluster window, select a host or cluster to run the deployed template,
and then click Next. The Specific Host window appears.
7. In the Specific Host window, choose a specific host within the cluster, and then
click Next. The Storage window appears.
8. In the Storage window, select the destination storage for your vm files, and then
click Next. The Disk Format window appears.
Figure 12 Storage
9. In the Disk Format window, select Thin Provision, and then click Next.
10. In the Network Mapping window, select the network the deployed template
should use, and then click Next.
11. In the Properties window, enter details for the following fields, and then click
Next:
Please enter complete information in this template to enable easy provisioning of
SRS VE. If any detail is incomplete or incorrect, it can only be corrected using YAST or
you will be required to re-enter all the required information in the OVF template.
• DNS1
• DNS2
• Hostname
• Default Gateway
• Network IPV4 address
• Network IPV4 Netmask
Note: IPV6 connection only applies to SRS Virtual Edition (SRS VE). It is not
supported on Hyper-V, SRS Docker Edition (SRS DE), and SRS Embedded Virtual
Edition (SRS eVE).
A root Password should be set during deployment. For security reasons, it is
recommended to use a password that is a minimum of eight characters and
contains a minimum of one upper, one lower, one digit, and one special character.
Figure 15 Properties
Figure 15 (continued)
Figure 15 (continued)
12. In the Ready to Complete window, review your options, and then click Finish.
The deployment status window appears, as shown in Figure 17 on page 28. When
the deployment is completed successfully, a deployment completed successfully
message appears.
2. If applicable, go to the Hyper-V Appendix and follow the instructions listed. Then
go to the following step.
3. When the VE is powered on, wait until you see that the first boot is completed.
Then go to the SRS Web UI by using the IP address that is displayed in the
configuration verification screen, as outlined in red on the screen example below.
Note: The IP address of the SRS should display in the SRS VE webui is running at
https://<SRSve-ip>:9443 field. If it displays anything different, then the network setup is not
correct. This can be addressed by logging on to the SRS shell and using YaST2 to correct the
network configuration. See Appendix B of the SRS Operations Guide for details.
Note: It is recommended that before you launch the Web UI portion of the SRS install, you log
on to the shell and verify the network, DNS, and default gateway configurations and
connectivity. You can use the CECT to perform these tests. If there are issues with the
configuration, then use YaST2 to correct them. See Appendix B of the SRS Operations Guide for
details.
This chapter provides the information that you will need to prepare the SRS server for
the provisioning of SRS. Topics include:
◆ Root logon and Admin setup........................................................... 32
◆ Provisioning screens/SRS setup...................................................... 36
Provisioning 31
Provisioning
1. Access the SRS Web UI using the following URL, either in Internet Explorer 9
(IE9) or later, Google Chrome, or Mozilla Firefox web browsers:
https://<SRSve-ip>:9443/
The SRSv3 home page displays.
2. On the SRSv3 home page, on the menu bar on the upper-right corner, click Login.
The Root Login page appears.
Note: The Root Login page, as shown in Figure 22 on page 33, only appears the first time you
log on to SRS, after a successful first boot configuration. Also, when you initially provision SRS,
the version being installed displays in the upper-left corner, after the word ESRS Virtual
Edition.
3. On the Root Login page, in the User Name text box, enter root as the user name,
as shown in Figure 22 on page 33.
4. In the Password text box, enter the root password that you set during the first
boot installation.
IMPORTANT
If you forget your root password, not your Admin password, then you must
perform the first boot installation again to set up a new root password. The system
can not retrieve your root password. To reset your SRS Version 3 (SRSv3) Web UI
Admin password using the Web UI, see Chapter 5, “Troubleshooting,” in the
Operations Guide for resetting the SRS Web UI user password.
6. Scroll down to read the agreement in its entirety. Accept the end-user license
agreement by selecting the Accept option.
Note: You will not be able to select the Accept or Do not Accept radio button
unless you scroll to the bottom of the page.
7. After accepting the agreement, click Submit. The Admin setup page appears.
Note that the first time you log on to the user interface, the system prompts you to
set the Admin password.
8. In the Admin setup page, set the Admin password, and then click Log on as
admin, as shown in Figure 24 on page 34. Note the following:
• There is no default password for the Admin user, therefore, you need to
manually set the password when prompted.
• If the Admin password is not changed within 15 minutes, then you will be
logged out and will have to start from the beginning by logging on with your
root credentials.
• The password must meet the following requirements:
– Be 8 or more characters in length, with a maximum of 16 characters.
– Contain at least one numeric character.
– Contain at least one uppercase and one lowercase character.
– Contain at least one special character such as ‘ ~ ! @ # $ % ^ & * ( ) - _ = + [ ]
{};<>
– Be a password that does not match the previous password.
– Do not use special characters ‘ (single quote) and “ (double quotes) as part
of the password.
– Do not use special characters / ? : , . |\
– May not be a password that matches the previous password.
• If all of the password requirements are met, then after clicking the Log on as
admin button, you will be logged out as root and logged in as Admin with SRS
Admin rights.
IMPORTANT
If you lose or forget your Admin password for the SRS Web user interface (or the
user name defined during the first boot configuration), then see Chapter 5,
“Troubleshooting,” in the Operations Guide for resetting the SRS Web UI user
password. This requires access to the SRS Shell with an SSH client.
9. Go to the “Provisioning screens/SRS setup” on page 36, and follow the steps
listed.
1. In the Primary Contact page, enter the primary contact information, as shown in
Figure 25 on page 36. Dell EMC uses the information provided in this section as
the customer contact for SRS. Dell EMC will reach the primary contact first
regarding any SRSv3 queries.
IMPORTANT
This information is required to proceed with the SRS configuration. Ensure
that this information is accurate as it may have a direct impact on the SRS
support.
2. When the primary contact information is completed, click the Submit & Go to
Technical Registration button. A status message displays stating that the primary
contact has been saved. This contact information will be used by Dell EMC in the
event of any connectivity issues with SRS.
3. In the status message window, click OK. The message closes and the Technical
Contact page appears.
4. In the Technical Contact page, as shown in Figure 26 on page 37, enter the
additional contact information. For any SRSv3 queries, if the primary contact is
not available, then Dell EMC uses the technical contact information.
You can skip this step by clicking the Skip Technical contact button. The
Provisioning tab displays with the Proxy Server, Network Check, and Provision
sub tabs.
Note: Although this information is optional, Dell EMC highly recommends that you
provide it. This should be your secondary contact for SRS. Ensure that this information is
accurate as it may have a direct impact on SRS support.
5. After you enter the technical contact information, click Submit & Go to
Provisioning. A status message appears stating that the technical contact has been
saved.
6. Click OK. The Provisioning tab appears with the Proxy Server, Network Check,
and Provision sub tabs.
7. For the Proxy Server sub tab, if a proxy server is not required, then you can skip
this step. If you need to provision the SRS with a proxy server, then follow these
steps:
1. In the Proxy Server tab, select the Enable Proxy between Client and EMC
checkbox and enter the required details, as shown in Figure 27 on page 38.
2. If your proxy server requires credentials, then select the Authenticate using
the following information checkbox and complete the applicable details, as
shown in Figure 27 on page 38.
3. Click Test to test the connectivity through the proxy to Dell EMC enterprise. A
message displaying the result appears next to the Test button.
4. Click the Submit & Go to Network Check button. A message appears stating
that the proxy configuration has been saved.
5. Click OK. The status message closes and the Network Check tab appears.
8. In the Network Check tab, you can run network checks to check the connectivity
between the SRS UI node, the core node, and the GAS servers.
To check the network connectivity from SRS to all the required Dell EMC servers,
click the Run Test button. For Customers, Employees, and Partners, the Run Test
button is enabled and the Go to Provision button is disabled by default, as shown
in Figure 28.
1. If any single test fails, including connectivity failures to Dell EMC GAS (Global
Access) Servers, then a pop-up message appears stating there is a failure in the
network check and the user has an option to proceed with provisioning
(despite the network fail) or go back, as shown in Figure 29.
b. Selecting Go Back takes the user back to the Test Results page with the Run
Test button enabled to run the network check again, as shown in Figure 31.
Verify that the appropriate firewall hosts and ports are open to Dell EMC
before trying the network check again. Each run test is refreshed.
Note: If the tests are successful, then the result shows connected (green circles).
If any of the tests are unsuccessful or unable to connect, then the results
display unconnected (red circles).
Note: The customer is responsible for the configuration and resolution of the
proxy server/firewall issues that impact connectivity to the Dell EMC SRS
infrastructure.
IMPORTANT
To ensure communication integrity, proxy servers and devices external to your
DMZ must not perform any method of SSL checking on outbound or inbound
traffic. SSL checking will cause a loss of connectivity to Dell EMC. If SSL checking
is performed on outbound communications by customer firewalls, proxies, Web
traffic filtering appliances or applications, web traffic shaping/load balancing,
certificate verification or proxying, or Intrusion Detection Services (IDS), then
there will be connectivity loss to Dell EMC.
2. After you are successfully authenticated under the Provisioning page, the
Enter Site ID page opens. Enter your Site ID in the Site Id field as shown in
Figure 33 on page 41.
3. Click Next to continue. After Dell EMC verifies the Site ID, you are directed to
the Confirmation page.
4. Verify the information on the Confirmation page and then click Next to
continue, as shown in Figure 34 on page 42. Provisioning commences, as
shown in Figure 35 on page 42.
3. After a new access code is generated, an email containing the access code is
sent, and a Status window opens telling you to check your email, as shown in
Figure 39 on page 44. Click OK to close this window.
Note: The generated access code is an 8-digit long pin code and is valid for 30
minutes from the time it is generated. You must complete the installation
within that time frame.
4. After you obtain your access code, enter it in the Enter your access code field,
as shown in Figure 40 on page 44.
5. Click Next. 6., “If using the Search option, enter the input value based on the
drop-down selection, and then click Search. The search results list displays.,”
opens.
If a Customer account has more than 100 sites associated, then the Customer Site page
will display the first 100 sites and a search option, as shown in Figure 41.
6. If using the Search option, enter the input value based on the drop-down
selection, and then click Search. The search results list displays.
Note: You can also select the number of entries per page from the Show
drop-down list, as shown in Figure 43.
7. Select the site that you want to provision from the list, and then click Next. You
may also use the search function to search a site by Site ID/Site Name/City.
Note that at this point, you do not need administrator privileges to select sites.
The page displays what you have selected, as shown in Figure 44 on page 46.
Note: If, at any time during the 30-minute window for this procedure, you re-click
Email my access code, then the previous code is automatically invalidated, and
you must use the most current code.
Email Configuration In the Email Configuration tab, the following details need to be configured to get the
notification mails, as shown in Figure 47 on page 48.
Note: The email server is on the customer's network. SRS should not be used for
SMTP traffic destined for the customer, that is, mail will not be forwarded.
1. To send notification emails and Connect Home files (if enabled), provide the email
server and its port details in the Email Server and Port text boxes.
2. Provide an email address in the Sender Email section.This address will be used as
the FROM address in the email notifications.
3. Provide an email address in the Notification Email(s) section. This address will be
used as the recipient address for any critical failure event notifications or failed
Connect Homes on the SRS.
4. If you select Enable on Success Notification, then the customer will receive
emails when a Connect Home is forwarded successfully to Dell EMC (if
configured). Multiple email users and distribution lists can be added by
separating the names with a comma.
5. Click Test. A pop-up window indicating that the test email was successfully sent
displays.
If the server settings are incorrect after clicking Test, then an error message
displays.
If you click OK and then click Submit & Go to Policy Manager when the server
validation fails, then a pop-up warning message appears, as shown in Figure 48
on page 49. During initial provisioning process only, this pop-up message appears
if the email configuration is for the first time only and it fails.
The email information is not saved in the SRS database if the email configuration
information is incorrect.
You have to choose Configure Later or Retry.
If you click Configure Later, you are taken to the next tab to continue provisioning
SRS. You will have the option to configure the email after provisioning SRS.
Note: Configure Later button does not save the email information in the SRS database.
Policy Manager If you are using Policy Manager (it must be installed and operational), then complete
the applicable information on this tab as follows:
2. When you are done, click the Test button to check the connectivity to Policy
Manager from SRS. If the connection is successful, then a message appears
beneath the Test button, as shown in Figure 49 on page 50.
3. Click Submit & Go to Connect Home. The status pop-up window appears.
4. Click OK to continue. The Connect Home tab displays.
Connect Home Managed File Transfer (MFT) is the default and primary channel for the Connect
Home files. In the event MFT is not available, Connect Home will failover to the SRS
channel.
On the Connect Home tab, you can configure and test Connect Home failover to
alternate paths using FTPS and/or Email (SMTP) via the customer SMTP server.
Note: Connect Homes to Dell EMC on alternate paths will only occur if the Primary
Method of SRSv3 (MFT) is unavailable.
Completing the Connect Home tab is highly recommended but not required. Your
firewall(s) and proxy server may need to be configured to pass this traffic. See the
Ports Requirement Document for ports used. Again, note that these alternate paths
are only used if the MFT channel is unavailable.
To enable Connect Home failover:
Note: ConnectEMC can be enabled for the following transport types as a failover channel in the
corresponding order: 1) FTPS, 2) Email.
1. Select either or both of the Connect Home connections. The Test button becomes
enabled, as shown in Figure 50 on page 51.
Note: The customer must configure their proxy server(s)/firewalls per the Ports
Requirement document.
Figure 52 Dashboard
This appendix lists the article that provides the IP addresses used by the Secure
Remote Services Virtual Edition.
◆ Key information ................................................................................. 54
◆ Article access ...................................................................................... 54
Key information
Article Number: 0000494729
Version: 1
ID: emc238467
Domain: EMC1
Solution Class: 3.X Compatibility
Note: Always check support.emc.com for the latest version of this article as it may have been
updated.
Article access
The following is a Primus(R) eServer solution.
Article Title: What IP addresses are used by the EMC Secure Remote Services IP
Solution?
This is from KB article 494729. To access this article, go to:
https://support.emc.com/kb/494729
This appendix describes the Hyper-V install process for SRS v3.xx.
◆ Procedure ............................................................................................ 56
Procedure
Follow the steps below to install the SRS Virtual Edition (SRS v3.xx) on your Hyper-V:
1. Copy the VHD for the SRS Virtual Edition to the location where you wish to host
the virtual disk for the virtual machine.
2. Uncompress the zip file.
3. Launch the Hyper-V Manager, as shown in Figure 53 on page 56.
4. Create the virtual machine that will be hosting the SRS Virtual Edition.
a. In the upper-right corner, select New > Virtual Machine, as shown in
Figure 54 on page 57.
Procedure 57
SRS v3.x on Hyper-V Install Process
d. Name the virtual machine, as shown in Figure 57 on page 58, and then click
Next.
e. Define the memory (4 GB [4096 MB]), as shown in Figure 58 on page 59, and
then click Next.
f. In the Connection menu, select the network card that will be used by the
virtual machine, and then click Next, as shown in Figure 59 on page 59.
Procedure 59
SRS v3.x on Hyper-V Install Process
g. Select the location to which you copied the VHD file for this SRS, as shown in
Figure 60 on page 60.
i. Browse for the location of the virtual hard disk, and then click Next, as shown
in Figure 62 on page 61.
j. Review the summary, and click Finish, as shown in Figure 63 on page 61. The
new SRS Virtual Edition virtual machine is now configured in the Hyper-V
environment. You must now connect to the virtual instance and start the host,
which starts the first boot process.
Procedure 61
SRS v3.x on Hyper-V Install Process
k. The first boot process starts the virtual host. You must configure the host name,
the network, the password of the root user, and so forth.
For SRS VE running on Hyper-V, to avoid SRS connectivity loss under specific
circumstances, make sure the MAC address is set to Static in the Advanced Features of
the Network Adapter.
l. Select the new virtual machine, and then click Connect, as shown in Figure 65
on page 63.
m. The following screen appears. Click the Start icon, as shown in Figure 66 on
page 63.
Figure 66 Powering on
Procedure 63
SRS v3.x on Hyper-V Install Process
n. The SRS starts the first boot process, as shown in Figure 67 on page 64.
o. When the first boot process is completed, from this point on, all of the install
processes are the same regardless of which virtual environment (VMware ESX
or Microsoft Hyper-V) is used. To complete provisioning, copy and paste the
URL to a Web browser, and then follow the steps starting at the “Root logon
and Admin setup” section in Chapter 3.
This appendix describes the process for unzipping files using WinZip.
◆ Procedure ............................................................................................ 66
Procedure
To unzip a file using WinZip:
1. Open WinZip (You can also use 7-Zip or WinRAR).
2. Select Options, as shown in Figure 68 on page 66.
4. Clear the TAR file smart CR/LF conversion checkbox, and then click OK, as
shown in Figure 70 on page 67. The box will remain unchecked until it is selected
again, or WinZip is reinstalled.
Procedure 67
Unzipping files using WinZip
A
access See Remote Access.
C
connect home Connecting from a remote site to Dell EMC’s support network.
D
Dell EMC Online Web-based access on support.emc.com to documentation, downloads, and support
Support Site information for Dell EMC customers and internal Dell EMC users.
DMZ Demilitarized zone — Device used to secure an internal network from unauthorized
external access.
Dynamic IP address An address that is assigned by the access device by which the user's host connects
over a dialup telephone line or by a set-top box for an IP over cable network.
F
failover The capability to switch over automatically to a standby server upon the failure or
abnormal termination of the previously active server. Failover happens without
human intervention and generally without warning.
firewall A hardware or software device that is configured to permit, deny, or proxy data
through a computer network which has different levels of trust.
FTP File Transfer Protocol — Used to transfer data from one computer to another, over the
Internet or through a network.
G
Gateway 2.x An SRS 2.x software component that is installed on a customer-supplied dedicated
server (or servers) or VMware instance. The servers act as the single point of entry
and exit for all IP-based Dell EMC remote notification and remote support activity.
P
Policy Manager An SRS software component that is installed on a customer-supplied server or
servers. It enables customizable control of remote access to customer devices and
maintains an audit log of remote connections.
proxy server A server (a computer system or an application program) which services the request of
its servers by forwarding request to other servers. A server connects to the proxy
server, requesting some service, such as a file, connection, web page, or other
resource, available from a different server. The proxy server provides the resource by
connecting to the specified server and requesting the service on behalf of the server. A
proxy server may optionally alter the server’s request or the server’s response, and
sometimes it may serve the request without contacting the specified server.
R
remote access Communication with a processing device from a remote location through a data link.
S
SMTP Simple Mail Transfer Protocol — The de facto standard for email transmissions across
the Internet.
SRS Secure Remote Services is an IP-based automated connect home and remote support
solution enhanced by a comprehensive security system. SRS creates both a unified
architecture and a common point of access for remote support activities performed on
your Dell EMC products.
SRS Virtual Edition Secure Remote Services, Virtual Edition, which is installed on an ESX or Hyper-V
Server, acts as the single point of entry and exit for all connect home and remote
support activities
T
topology Network configuration, including firewalls, servers, devices, and ports used for
communication between all devices.
Transport Layer A port that uses cryptographic protocols to provide secure Internet communications
Security (TLS) port for data transfers.