Introducing

Recommendations

Info

Table 4-1: Variations across different “join” methods Corporate device (joined to onpremises domain) Users can sign in to Windows with work credentials (as they do today). Users have access to roaming settings and the enterprise Windows Store. These services work with work accounts and don't require a personal Microsoft account. This requires organizations to connect their onpremises Active Directory to Azure AD. Users have SSO ability from the desktop to work apps, websites, and resources—including both on-premises resources and cloud apps that use Azure AD for authentication. Corporate device (joined to the cloud) Users can sign in to Windows with work credentials that are managed in Azure AD. This is relevant for corporate devices in three cases: The organization doesn’t have Active Directory on-premises (for example, a small business). The organization doesn’t create all user accounts in Active Directory (for example, accounts for students, consultants, or seasonal workers are not created in Active Directory). The organization has corporate devices that can’t be joined to an (on-premises) domain, like phones or tablets running a Mobile SKU (for example, a secondary device taken to a factory/retail floor). Azure AD Join supports joining of corporate devices for both managed and federated organizations. Users can do self-service setup. They can go through the first-run experience (FRX) via their work account as an alternative to having IT provision the devices, although both methods are supported. Devices are automatically registered in the enterprise directory (Azure AD) and automatically enrolled in mobile device management. (Azure AD Premium feature). Personal device Users sign in to Windows with their personal Microsoft account credentials (no change). Users can easily add a work account that’s managed in Active Directory or Azure AD. Users have SSO ability across apps and to websites/resources with this work account. 127 CHAPTER 4 | Security and identity
Users can add their personal Microsoft accounts to access their personal pictures and files without affecting enterprise data. (Roaming settings continue to work with their work accounts.) The Microsoft account makes SSO possible and no longer drives the roaming of settings. Users can do a self-service password reset (SSPR) on winlogon, meaning they can reset a forgotten password. (Azure AD Premium feature). Users have access to the enterprise Windows Store so that they can acquire and use line-of-business apps on their personal devices. Microsoft Passport Authentication methods are moving at a faster pace than ever before. Think about it for a moment: you sign in to your laptop and then open your browser to go to your favorite websites where you again sign in. In these instances, you are not always using your corporate credentials. If you hear of a new service and want to access it, the chances are that you will be prompted to sign up and use credentials from, for example, your public Microsoft account, Facebook, Google, and so on. The traditional paradigm of using a dedicated identity authentication provider that you build as an application developer is moving on and we are now using more “well-known” services like those just mentioned. Microsoft Passport is a new key-based authentication method that goes beyond passwords to mitigate traditional authentication attacks. A user enrolls for Microsoft Passport but must ensure that the authentication provider she uses supports Fast Identity Online (FIDO) authentication; thus, through a two-step process, the user sets up Microsoft Passport on her device and sets a gesture or PIN. This can then be used to authenticate the user via Microsoft Passport During the setup, a certificate of asymmetric key–pair is stored on the device. The private key is stored within the TPM chip on the device. The private key never leaves the device during the authentication process. The public key is registered in Azure Active Directory and Windows Server Active Directory. The user account has a mapping between the public and private key, which helps to validate the user. Additional controls are implemented via One Time Passwords, Phonefactor, and so on. More info For further information on deploying Microsoft Passport check the following link https://aka.ms/bh1m24. Active Directory Federation Services As we move forward in a cloud-focused world, being able to control your identity is becoming more important. We need to think about how we can use our corporate identity to access applications that we don’t technically own anymore. We also need to think about how we provide access to applications we own to other organizations in a secure and controlled manner without having a cumbersome user-management process. Active Directory Federation Services (AD FS) provides this ability so that you can connect to applications that are on-premises or in the cloud (Platform as a Service [PaaS] or SaaS) with your corporate identity. 128 CHAPTER 4 | Security and identity
Page 1 and 2:
Introducing Windows Server 2016 Joh
Page 3 and 4:
Visit us today at microsoftpresssto
Page 5 and 6:
Creating a cloud witness by using A
Page 7 and 8:
DSC Local Configuration Manager ...
Page 9 and 10:
Ramnish Singh Ritesh Modi Jason M.
Page 11 and 12:
C H A P T E R 1 Introduction to Mic
Page 13 and 14:
The following subsections dive deep
Page 15 and 16:
Offer greater service availability
Page 17 and 18:
Self-Service In the area of self-se
Page 19 and 20:
C H A P T E R 2 Software-defined da
Page 21 and 22:
Each nested guest VM needs to have
Page 23 and 24:
A VM collection group is a logical
Page 25 and 26:
Using the Get-VM cmdlet, you can se
Page 27 and 28:
Figure 2-5: Multitier management gr
Page 29 and 30:
Windows Server 2012 R2 took live mi
Page 31 and 32:
Figure 2-12: VM shortcut menu To do
Page 33 and 34:
You can confirm this by using Windo
Page 35 and 36:
ParentSnapshotName : MemoryStartup
Page 37 and 38:
Figure 2-19: Message indicating tha
Page 39 and 40:
Figure 2-23: VM Task Manager showin
Page 41 and 42:
Failover cluster By John Marlin and
Page 43 and 44:
Figure 2-30: Entering storage accou
Page 45 and 46:
Figure 2-34: Extending a volume in
Page 47 and 48:
[=== Microsoft-Windows-ClusterAware
Page 49 and 50:
Troubleshooting an event such as th
Page 51 and 52:
Figure 2-40: Pausing cluster node N
Page 53 and 54:
-IncludeAllSubFeature 5. Add the Wi
Page 55 and 56:
Figure 2-50: VM Configuration Versi
Page 57 and 58:
As Figure 2-51 illustrates, when ap
Page 59 and 60:
There is no need for schema updates
Page 61 and 62:
In the Configure Storage Replica Wi
Page 63 and 64:
There are many options for the New-
Page 65 and 66:
Deployment Choice Storage Spaces Di
Page 67 and 68:
Figure 2-60: The Storage Spaces Dir
Page 69 and 70:
on node A, B, and C, and the extent
Page 71 and 72:
Figure 2-63: Old mapping versus the
Page 73 and 74:
Multi-instance With multi-instance
Page 75 and 76:
Figure 2-66 Network virtualization
Page 77 and 78:
Figure 2-68: NVGRE Network Controll
Page 79 and 80:
More info In this book, we cannot p
Page 81 and 82:
When you have a service that requir
Page 83 and 84:
Figure 2-72: Post deployment config
Page 85 and 86:
Auditing access to resources Window
Page 87 and 88: Figure 2-77: Published web applicat
Page 89 and 90: Figure 2-81: Relying party options
Page 91 and 92: Figure 2-85: The Edit Claim Rules d
Page 93 and 94: This will provide you with the toke
Page 95 and 96: Figure 2-92: Viewing details from t
Page 97 and 98: Hear about it first. Get the latest
Page 99 and 100: Figure 3-1: Diagram showing the thr
Page 101 and 102: DNS server Web server running IIS A
Page 103 and 104: Figure 3-5: Architecture of differe
Page 105 and 106: Remotely managing Nano Server Nano
Page 107 and 108: Monitoring Nano Server You can now
Page 109 and 110: Figure 3-6: Conceptual container la
Page 111 and 112: Figure 3-7: Windows Server 2016 con
Page 113 and 114: Figure 3-10: Containers can write o
Page 115 and 116: Firewalls Every container host has
Page 117 and 118: C H A P T E R 4 Security and identi
Page 119 and 120: At this point, it might be self-def
Page 121 and 122: UEFI BIOS configured to prevent an
Page 123 and 124: Better protection against advanced
Page 125 and 126: When a user attempts to remote desk
Page 127 and 128: New fields in the process creation
Page 129 and 130: The core areas of interest to chang
Page 131 and 132: credentials for this account with s
Page 133 and 134: Long-term plan The long-term goals
Page 135 and 136: A REST Endpoint Windows PowerShell
Page 137: Bring Your Own Device (BYOD) equipm
Page 141 and 142: More info For further information,
Page 143 and 144: C H A P T E R 5 Systems management
Page 145 and 146: Like Linux, we have some common ter
Page 147 and 148: Name InstallationPolicy SourceLocat
Page 149 and 150: uri='https://www.powershellgallery.
Page 151 and 152: Figure 5-1: Sample code in the Wind
Page 153 and 154: The first runspace, ID 1, is always
Page 155 and 156: ConfigurationRepositoryShare This r
Page 157 and 158: IISInstall is responsible for downl
Page 159 and 160: DSC partial configurations One of t
Page 161 and 162: You also need to provide the pull s
Page 163 and 164: The .mof file is generated on the p
Page 165 and 166: this information. Figure 5-9 shows
Page 167 and 168: Backup and recovery Security and co
Page 169 and 170: Figure 5-15: Connecting a storage a
Page 171 and 172: Figure 5-19 depicts the first step
Page 173 and 174: Figure 5-23: Adding logs From here
Page 175 and 176: Figure 5-26: Sample deployment for
Page 177 and 178: Figure 5-28: The Windows PowerShell
Page 179 and 180: Deployment Deployment of SMT is rel
Page 181: Free ebooks From technical overview
show all

Introducing

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?