Administrator Guide
Table Of Contents
- Dell Hybrid Cloud System for Microsoft Cloud Platform System Standard Version 1.5 Administrators Guide based on release 1803
- Overview
- Administration
- What to do first
- Next steps
- Managing Dell Hybrid Cloud System for Microsoft
- Creating tenant VM networks
- Adding tenant VM networks to the cloud
- Flagging the operating system VHD in the VM templates
- Enabling guest-specified IP addresses in VMM
- Creating additional tenant storage shares
- Using Windows Azure Pack
- Default Windows Azure Pack configuration
- Before you go into production
- Setting up tenant portal access on an isolated network
- Replacing self-signed certificates
- Disabling the tenant AuthSite and the admin Windows AuthSite websites
- Updating to a Security Token Service and re-establishing trust
- How to open the management portal for administrators
- How to open the management portal for tenants
- Offering services to tenants
- Optional configuration
- Automating tasks for efficiency
- Windows Azure Pack API reference content for developers
- Configuring disaster recovery protection
- Operations
- Monitoring
- Backup and recovery
- Onboard to Azure Backup
- Default backup schedule and retention policy
- DPM protection groups
- Disable machine account password rotation on management VMs
- Protecting tenant VMs
- Recovering VMs and databases—high level
- Recovering from management component failures
- Recovering a tenant VM
- Recovering DPM from DPM failures
- Adding extra disks to DPM
- Monitoring DPM
- Using the Dell Hybrid Cloud System for Microsoft data consistency runbooks
- Updating the Dell Hybrid Cloud System for Microsoft
- Shutting down and starting up the stamp
- Security
- Appendix A Expanding the stamp
- Appendix B Performing a factory reset
- Appendix C Retrieving cluster names, host names, and IP addresses
- Appendix D Ports and protocols
NOTE
: Dell recommends that you set up tenant access isolation before you replace self-signed certicates and congure AD FS,
or another security token service. In the process of setting up tenant portal access on an isolated network, you change the fully
qualied domain name (FQDN) of the tenant portal in the tenant portal settings. It is best to make the change rst, before you
undertake the other procedures.
Sample naming convention
IMPORTANT
: Your domain name should be the same as the DNS zone in which your DHCS stamp resides. For example, if your
domain name is
mycompany.local
, and you are using a DNS zone other than
mycompany.local
, you have a disjointed namespace.
The use of disjointed namespaces has not been tested in the DHCS stamp. Dell recommends that you do not use a disjointed
namespace within the DHCS stamp.
Examples in this section use the following sample names and addresses:
• Management network: VLAN 100
• Tenant access network: VLAN 110
• Management network address: 10.10.55.0/26
• Internal network range: 10.0.0.0/8
• Dell Hybrid Cloud System for Microsoft stamp pr
ex: DHCS
• Internal domain name—in which the DHCS stamp is deployed: contoso.local
• External domain name: contoso.com
• Tenant portal VM internal IP address: 10.10.55.14
• Tenant portal VM internal FQDN:
dhcsapt01.contoso.local
• Tenant portal VM external IP address: 172.31.1.5
• Tenant portal VM external FQDN: cloudportal.contoso.com
Network requirements
The following diagram illustrates the network con
guration for isolated tenant portal access, with examples:
Administration 37