Dark Mode

3 captures
20 Feb 2017 - 01 Nov 2017
Jan FEB Mar
20
2016 2017 2018
success
fail
About this capture
COLLECTED BY
Crawl of outlinks from wikipedia.org started March, 2016. These files are currently not publicly accessible. Properties of this collection. It has been several years since the last time we did this. For this collection, several things were done: 1. Turned off duplicate detection. This collection will be complete, as there is a good chance we will share the data, and sharing data with pointers to random other collections, is a complex problem. 2. For the first time, did all the different wikis. The original runs were just against the enwiki. This one, the seed list was built from all 865 collections.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20170220220636/https://technet.microsoft.com/en-us/windows-server-docs/security/guarded-fabric-shielded-vm/guarded-fabric-configuring-fabric-dns
Table of contents

Shared to

Table of contents +
TOC
Collapse the table of content
Expand the table of content

Configuring the fabric DNS for hosts that will become guarded hosts

Ryan Puffer|Last Updated: 2/17/2017
|
2 Contributors

Applies To: Windows Server 2016

A fabric administrator needs to configure the fabric DNS takes to allow guarded hosts must be able to resolve the HGS cluster. The HGS cluster must already be set up by the HGS administrator.

Configure the fabric DNS

There are many ways to configure name resolution on the fabric domain. One simple way is to set up a conditional forwarder zone in DNS for the fabric. To set up this zone, run the following commands in an elevated Windows PowerShell console on a fabric DNS server. Substitute the names and addresses in the Windows PowerShell syntax below as needed for your environment. Add master servers for the additional HGS nodes.

Add-DnsServerConditionalForwarderZone -Name -ReplicationScope "Forest" -MasterServers

Next step

With HGS set up and name resolution in place, it's time to capture information from the hosts and add it to the HGS. How you do this depends on which attestation mode you are using:

ActionsSection
Admin-trusted attestation: Create an Active Directory security group in the fabric domain, add guarded hosts as members, and provide that group identifier to the HGS admin.See Admin-trusted attestation for a guarded fabric - creating a security group
TPM-trusted attestation: Capture TPM identifiers (also called platform identifiers), create a TPM baseline, and create a Code Integrity policy. Provide those artifacts to the HGS admin.See TPM-trusted attestation for a guarded fabric - capturing information required by HGS

See also

  • IN THIS ARTICLE
  • Configure the fabric DNS
  • Next step
  • See also
(c) 2017 Microsoft