Frequently Asked Questions

Q: “Can you hack…?”

A: No.

Q: What is a “Native Executable”?

A: Natively executable files do not require additional software to run. Such a binary would work with a fresh installation of an Operating System out-of-the-box and as-is.

Q: What is a “Dynamic-Link Library”?

A: DLL files are component stores of compiled software code. A library file may expose functions known as “exports”. These exports can then be imported by other software.

Q: How can I tell if my Windows machine is on a domain?

A: The command net config workstation net config workstation will display information related to the Workstation service, which includes “Workstation domain”, “Workstation Domain DNS Name”, and “Logon domain”.

Q: Can my domain joined Windows machine function in the absence of a Domain Controller?

A: This may vary based on your organization’s group policy configuration. However, typically, windows machines can continue to function independently without any active connection to a domain controller. Some functions may be limited.

Q: How can I test the connection from my Windows machine to a Domain Controller?

A: The command nltest /DSGETDC: nltest /DSGETDC: <DomainName> will check if your machine can find a domain controller for the specified domain.

Q: As an Organization User, how can I get a list of Domain Controllers?

A: Please note that a user’s view of domain controllers may be limited. The command: nltest /DCLIST: nltest /DCLIST: <DomainName> will get list of Domain Controllers in the specified domain.

Q: As an Organization Administrator, how can I test the health of a Domain Controller?

A: On any individual Domain Controller the following command will perform a series of PASS/FAIL tests: dcdiag dcdiag .

Q: As an Organization Administrator, how can I test the connection between Domain Controllers?

Administrators may utilize the following command to test specifically the connection between a Domain Controller and other Domain Controllers: repadmin /replsummary repadmin /replsummary .

Q: How can I determine if my Windows machine is using a Microsoft Windows Production PCA 2011 or a Windows UEFI CA 2023 signed boot loader?

The Documentation from Microsoft supplies the following elevated PowerShell command which is expected to return True if your machine is using the 2023 chain of trust: [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023'

Note: This command cannot be run in Command Prompt, it must be run in Administrative PowerShell.

Q: How can I determine if my Windows machine is rejecting the Microsoft Windows Production PCA 2011 certificate?

If your machine has been correctly configured to reject the Microsoft Windows Production PCA 2011 certificate, the supplied elevated PowerShell command which is expected to return True is: [System.Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI dbx).bytes) -match 'Microsoft Windows Production PCA 2011'

If your response is False this means your machine is still trusting the Microsoft Windows Production PCA 2011 certificate.

Note: This command cannot be run in Command Prompt, it must be run in Administrative PowerShell.