Administrator Guide

\CurrentControlSet\Control\Session Manager\Memory Management' -Name PagingFiles -Value "?:
\pagefile.sys 16384 16384"}
# End - Long Line
TIP
: To nd the host names, you can use the VMM console. Or, to nd the host names in a cluster, you can run the following
Windows PowerShell command, where < ClusterName > is the name of the cluster, such as < Prex >CCL and < Prex >SCL:
Get-ClusterNode -Cluster <
ClusterName > | Format-Table –Property Name
3 Restart each host for the setting to take e
ect. You can do this when it is convenient, such as during a scheduled maintenance
window. Note the following:
• If you are restarting a backup host, r
st stop any running backup jobs. For more information, see "Step 1: Stop any backups" in
Shutting down the stamp.
• Restart the hosts one at a time. Wait for a host to be up and running before you restart the next.
4 You can restart hosts:
• From the Fabric workspace in the VMM console, by right-clicking a host and then clicking Restart, or
• By using Windows PowerShell.
5 To restart hosts from a Windows PowerShell:
a Log on to any domain-joined computer (external to the stamp is preferable) with an account that is a member of the <
Prex >-
Ops-Admins group.
b Open an elevated Windows PowerShell session.
c To restart the remote computer, run the following command, where HostName is the name of a physical host:
Restart-Computer –ComputerName <HostName> –Force
d Wait until the host is up and running before you restart the next host.
Reclaim space on the compute cluster nodes
NOTE: This section does not apply if the Microsoft update version of the Dell Hybrid Cloud System for Microsoft stamp at initial
deplo
yment is version 1603 or a later version. To check the update version, see
How to check which update package is installed.
To reclaim space on the compute cluster nodes, you can manually remove the Console.vhdx le fr
om the local disk on each host:
1 On the Console VM, open an elevated Windows PowerShell session, that is, run as Administrator.
2 Run the following command, where <hostname1
>,<hostname2>,… are the names of all physical hosts in the compute cluster.
Invoke-Command <
hostname1 >,< hostname2 >,... {Remove-Item D:\VHD\Console.vhdx}
TIP: To nd the host names
, you can use the VMM console or you can run the following Windows PowerShell command,
where < Prex > is the stamp prex.
Get-ClusterNode -Cluster <
Prex >CCL | Format-Table –Property Name
Onboarding to Operational Insights fails if proxy authentication is required
If your environment requires proxy authentication (using Basic authentication) for internet access, Azure onboarding to Operational Insights
(
also known as OMS, or Microsoft Operations Management Suite) fails while trying to create the Run As account called
"AdvisorProxyRunAsAccount" in Operations Manager.
1 If you are trying to onboard to Azure during initial stamp deployment, you must temporarily ignore this issue and complete stamp
deplo
yment.
2 After stamp deployment, do the following:
a On the Console VM, open the Operations console.
b In the Administration workspace, under Run As Conguration, right-click Accounts, and then click Create Run As Account.
c Complete the
Create Run As Account Wizard using the following settings.
24 Administration