Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "For example, the IPv4 settings could be 10.128.0.28/30 or 10.128.32/30."

A block of code is set as follows:

# Create a PEP Session 
winrm s winrm/config/client '@{TrustedHosts= "<IP_address_of_ERCS>"}' 
$PEPCreds = Get-Credential 
$PEPSession = New-PSSession -ComputerName <IP_address_of_ERCS_Machine> -Credential $PEPCreds -ConfigurationName "PrivilegedEndpoint"

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

params = @{  
    ComputerName = $ErcsNodeName  
    Credential = $CloudAdminCred  
    ConfigurationName = "PrivilegedEndpoint"  
}

Any command-line input or output is written as follows:

$cred = Get-Credential
Enter-PSSession -ComputerName <IP address of ERCS> -ConfigurationName PrivilegedEnpoint -Credential $cred
Register-CustomDnsServer -CustomDomainName "<domain name>" -CustomerDnsIPAddresses "ip1,ip2"

Bold: Indicates a new term, an important word, or words that you see on screen. For instance, words in menus or dialog boxes appear in bold. Here is an example: "Choosing Do not connect to Azure does not strictly mean that you cannot connect to the Azure Stack Hub instance to Azure for hybrid scenarios for tenant workloads."

Tips or important notes

Appear like this.