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

4 The local routing table of the tenant portal VM must have required routes. There is no requirement for the tenant access network
t
o route to the management network. However, you must congure the local routing table of the tenant portal VM to correctly route
trac to both the tenant access network and the management network, and to domain controllers for the internal domain (for
example, contoso.local) that may be on dierent networks routable to the management network. The step-by-step instructions in the
next section show how to congure this.
Conguring the t
enant portal
Follow these steps to congure the tenant portal for tenant access through an isolated network:
1 Make sure that DNS is con
gured as described in
Network requirements. In particular, make sure a static Host (A) record was created
on the DNS serv
ers in both the management and the tenant access networks.
2 Congure the physical network devices with a separate VLAN-based network to use for the tenant access network.
3 Follow the steps in Create tenant VM networks to create a tenant access network. This should be a unique network from VM
networks that you create for tenant VM use. When you congure runbook parameters, specify the external (tenant-facing) DNS
server and DNS sux.
4 In the VM console, do the following:
a Open the VMs and Services workspace. Click VM Networks, and verify that the tenant network was created successfully.
b In the navigation tree, click All Hosts. In the VMs pane, right-click the tenant portal VM <
Prex
>APT01, and then click Shut
Down. Click Yes to conrm.
c After the VM shuts down, right-click the VM, and then click Properties.
d Click the Hardware Con
guration tab, click New on the toolbar (the green plus sign), and then click Network adapter.
e In the
Connectivity area of the new network adapter details, click Connected to a VM network. Click Browse, select the tenant
network you created earlier, and then click OK.
f Wait until the VM con
guration updates. Then, right-click the VM, and click Power On.
g After the VM starts, right-click the VM, point to Connect or View, and then click Connect via Console. Log in with a user
accoun
t that has administrative rights.
5 On the tenant portal VM, open an elevated Windows PowerShell session and con
gure IP properties of the new connection.
The following example commands disable dynamic DNS registration on the new connection, con
gure a new IP address on the new
interface, and congure a static local routing table as described earlier in
Network requirements. The example assumes that there are
no DHCP serv
ers on either of the networks. Replace the values in this example with values specic to your network.
a Assigns the variable $if1 to the network interface on which the default gateway is con
gured (in this case, the interface on the
management network).
$if1 = Get NetRoute DestinationPrefix 0.0.0.0/0 | Select Expand ifIndex
b Assigns the variable $if2 to the interface that is being used for the tenant access network.
$if2 = Get-NetIPAddress -AddressFamily IPv4 SuffixOrigin Link | Select Expand ifIndex
c Disables dynamic DNS registration on the new connection.
Set-DnsClient -InterfaceIndex $if2 -RegisterThisConnectionsAddress $false
d Congures a ne
w IP address on the new interface.
New-NetIPAddress InterfaceIndex $if2 IPAddress 172.31.1.5 PrefixLength 24
e Congures a st
atic route to the management network’s gateway address.
New-NetRoute DestinationPrefix
10.0.0.0/8
NextHop
10.10.55.1
InterfaceIndex $if1
f Removes the existing default gateway.
Remove-NetRoute DestinationPrefix 0.0.0.0/0 Confirm:$false
g Congures a de
fault route 0.0.0.0/0 to the default gateway of the tenant access network.
New-NetRoute DestinationPrefix 0.0.0.0/0 NextHop 172.31.1.1 InterfaceIndex $if2
6 On the tenant portal VM, in an elevated Windows PowerShell session, run the following commands to con
gure tenant portal settings.
Replace the values in this example with values specic to your network.
$sql = 'DHCSSQLIN01\SQLIN01'
$fqdn = 'cloudportal.contoso.com'
Administration 39