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
5 Conrm the dele
tion.
6 The subscription, and the resources associated with the subscription, are deleted.
Monitoring capacity
To ensure high-availability for your plans and services and help keep your tenants productive, you need to monitor the performance of your
r
esources.
Dell Hybrid Cloud System for Microsoft uses Operations Manager and Operational Insights to monitor the health of your cloud
infrastructure. See the
Operations
chapter of this guide for more information.
Activating guest operating systems
By default, tenant VMs that are running Windows Server 2012 R2 are automatically activated by using Automatic Virtual Machine
A
ctivation (AVMA), if an AVMA key was used. For more information about AVMA, including the AVMA keys that you should use for tenants
in VM templates for Windows Server 2012 R2-based images, see
Automatic Virtual Machine Activation (http://technet.microsoft.com/
libr
ary/dn303421.aspx) in the Microsoft TechNet Library.
If you want to oer tenants the option of deploying earlier Windows-based operating systems, you must use a Windows Server Key
Management Server (KMS) to activate those products. If you already have a KMS server, you can use the existing server.
To set up a KMS host in your environment, see the blog post
Installing Volume Activation Services Role in Windows Server 2012 to set up a
KMS Host (http://blogs.technet.com/b/askcore/archive/2013/03/14/installing-volume-activation-services-role-in-windows-server-2012-
t
o-setup-a-kms-host.aspx).
NOTE: The same steps apply to Windows Server 2012 R2.
Keep in mind that if a tenant does not connect the VM network to a gateway, for example in an isolated development environment, the VM
is no
t able to reach the KMS server because the VM cannot reach the internet. In this scenario, there are the following options:
• Use a volume licensed version of the operating system in the image.
• Specify the KMS Client Key in the VM template. For a list of KMS client keys, see Appendix A: KMS Client Setup Keys (http://
t
echnet.microsoft.com/en-us/library/jj612867.aspx).
VM template requirements (pre-Windows Server 2012 R2)
If you create pre-Windows 2012 R2 images to use in VM templates for tenant use, you must do the following:
• Use a volume licensed version of the operating system in the image.
• Specify the KMS Client Key in the VM template. For a list of KMS client keys, see Appendix A: KMS Client Setup Keys (http://
technet.microsoft.com/en-us/library/jj612867.aspx).
Optional con
guration
The following procedures are optional.
Customizing the tenant portal
For information about how to customize the Windows Azure Pack management portal for tenants, see Windows Azure Pack custom
theming (http://msdn.microsoft.com/library/dn448611.aspx) in the MSDN Library.
Administration 49