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

You must create VM networks for tenants so they can use and access network resources. All virtual machines must be connected to a VM
ne
twork. To create tenant VM networks, you must use the Create-VMMTenantNetwork runbook. This runbook creates the VLAN-based
logical networks and VM networks in VMM for tenant use.
1 Use the How to run runbooks
procedure discussed in the preceding section to start the Create-VMMTenantNetwork runbook.
2 Specify the following parameters:
Input Parameter Description
DnsServers A comma-separated list of DNS server IP addresses for the subnet.
Optional if Subnet is specied.
Example: 10.22.0.10,10.24.0.11
DnsSux The DNS sux f
or the subnet.
Optional if Subnet is specied.
Example: contoso.com
Gateway The default gateway for the subnet.
Optional if Subnet is specied.
Example:
192.168.0.1
LogicalNetworkName The name of the VMM logical network that will be used for tenant networks.
If not specied, the de
fault name of Tenant VLANs will be used.
Name An optional name that is used to generate the IP address pool name and VM Network name.
If not specied, the de
fault name Ten
ant will be used.
The resulting VM Network and IP address pool names would be Tenant – VLAN
#
, where # is the VLAN ID
specied f
or the network.
PoolEnd The ending address for the IP address pool.
Optional if Subnet is specied.
If not specied, the last addr
ess in the Subnet will be used.
Example: 192.168.0.254
PoolStart The starting address for the IP address pool.
Optional if Subnet is specied.
Example:
192.168.0.1
Subnet The IP subnet for the network, in the format IP
_Address/Prex.
If not specied, DHCP will be used.
Example: 1192.168.0.0/24
UplinkPortProleName The exact name of the Uplink Port Pr
ole that was created during deployment.
If not specied, the default name UplinkPortProle is used.
28 Administration