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
Figure 11. Isolated tenant portal network con
guration
Here are the network requirements for this conguration:
1
Tenant access network as a separate VLAN. You must create a tenant access network as a separate VLAN, for example, VLAN 110,
t
agged to all ports of the network switches where DHCS servers are connected.
2
A DNS server that tenants use for name resolution. Typically, this is a dier
ent DNS server from the DNS that supports the Active
Directory Domain Services (AD DS) infrastructure for DHCS servers, for example, contoso.com.
Ensure that the tenant DNS server can resolve internet addresses. This is needed for certicate revocation checks when accessing
the tenant portal over SSL. If tenants cannot resolve internet addresses, the tenant portal may take up to 30 seconds to load.
3 An external FQDN for the tenant portal VM. This fully qualied domain name (FQDN) is the name tha
t tenants use to access the
tenant portal, for example, cloudportal.contoso.com. Create a Host (A) record on the tenant DNS server that points to the external IP
address of the tenant portal VM. (For the external IP address, pick an IP address from the IP subnet that you want to use for the
tenant access VLAN.)
The external FQDN of the tenant portal VM must be resolvable by clients on the tenant access network and the management
network. Therefore, you must congure a DNS zone with a DNS entry for the external FQDN and IP address of the tenant portal VM
on both management and tenant DNS servers.
38 Administration