status

Author: openpublishbuild

support/windows-server/active-directory/troubleshoot-ad-fs-sso-issue.md

@@ -418,7 +418,7 @@ Then, check the certificate configuration on WAP servers and the fallback bindin
   
   To support non-SNI cases, administrators may specify fallback bindings. Other than the standard federationservicename:443 binding, look for fallback bindings under the following application IDs:
   
-  - \{5d89a20c-beab-4389-9447-324788eb944a\}: This is the application ID for AD FS.
+  - \{00001111-aaaa-2222-bbbb-3333cccc4444\}: This is the application ID for AD FS.
   - \{f955c070-e044-456c-ac00-e9e4275b3f04\}: This is the application ID for Web Application Proxy.
   
   For example, if the SSL certificate is specified for a fallback binding like 0.0.0.0:443, make sure that the binding is updated accordingly when the SSL certificate gets updated.
@@ -884,12 +884,12 @@ Get the SSL certificate bindings for AD FS
 On the AD FS server, run the following command in Windows PowerShell:  
 `netsh http show sslcert`
 
-In the list of bindings returned, look for those with the Application ID of 5d89a20c-beab-4389-9447-324788eb944a. Here is an example of a healthy binding. Note the "Ctl Store Name" line.
+In the list of bindings returned, look for those with the Application ID of 00001111-aaaa-2222-bbbb-3333cccc4444. Here is an example of a healthy binding. Note the "Ctl Store Name" line.
 
 ```output
 Hostname:port : adfs.contoso.com:443
 Certificate Hash : 3638de9b03a488341dfe32fc3ae5c480ee687793
-Application ID : {5d89a20c-beab-4389-9447-324788eb944a}
+Application ID : {00001111-aaaa-2222-bbbb-3333cccc4444}
 Certificate Store Name : MY
 Verify Client Certificate Revocation : Enabled
 Verify Revocation Using Cached Client Certificate Only : Disabled

support/windows-server/backup-and-storage/delete-s2d-storage-pool-reuse-disks.md

@@ -295,7 +295,7 @@ Keywords:
 User:          SYSTEM
 Computer:      S2D-1.contoso.com
 Description:
-Windows lost communication with physical disk {81ea06c7-7433-bdd5-6a02-b267b5702b0b}. This can occur if a cable failed or was disconnected, or if the disk itself failed.
+Windows lost communication with physical disk {aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb}. This can occur if a cable failed or was disconnected, or if the disk itself failed.
 This disk may be located using the following information:
 Drive Manufacturer: Msft
 Drive Model Number: Virtual Disk
@@ -306,9 +306,9 @@ Enclosure Model Number: NULL
 Enclosure Serial Number: NULL
 Enclosure Slot: -1
 More information can be obtained using this PowerShell command:
-Get-PhysicalDisk | ?{ $_.ObjectId -Match "{81ea06c7-7433-bdd5-6a02-b267b5702b0b}" }
+Get-PhysicalDisk | ?{ $_.ObjectId -Match "{aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb}" }
 To view the virtual disks affected, run this command in PowerShell:
-Get-PhysicalDisk | ?{ $_.ObjectId -Match "{81ea06c7-7433-bdd5-6a02-b267b5702b0b}" } | Get-VirtualDisk
+Get-PhysicalDisk | ?{ $_.ObjectId -Match "{aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb}" } | Get-VirtualDisk
 ```
 
 When you run the `Get-StoragePool` command, you see output that resembles the following example:

support/windows-server/system-management-components/event-tracing-for-windows-simplified.md

@@ -48,7 +48,7 @@ Classpnp Driver Tracing Provider {FA8DE7C4-ACDE-4443-9994-C4E2359A9EDB}
 Critical Section Trace Provider {3AC66736-CC59-4CFF-8115-8DF50E39816B}  
 Device Task Enumerator {0E9E7909-00AA-42CF-9502-2C490471E598}  
 Disk Class Driver Tracing Provider {945186BF-3DD6-4F3F-9C8E-9EDD3FC9D558}  
-Downlevel IPsec API {94335EB3-79EA-44D5-8EA9-306F49B3A041}
+Downlevel IPsec API {aaaabbbb-0000-cccc-1111-dddd2222eeee}
 
 Various utilities are available at the Microsoft Download Center in order to parse .etl files, for instance Network Monitor v3.4. However, the sample script below would not need an installation of any of those.