Q: If using GZN (Global Names Zone), do your clients need a WINS address configured on them?

No they do not. The idea behind the GlobalNames zone in Windows Server 2008 is that no client configuration is needed. Just remember that you need to meet these requirements.

· DNS Servers must be Windows Server 2008.
· Global Names Zone must be enabled (DNSCMD /config /enableglobalnamessupport 1) on each DNS server.
· A forward lookup zone named GlobalNames must be set up on each DNS server that
· · · Is active directory integrated
· · · Does not support dynamic updates (recommended)
· You must provide a CNAME record mapping the client name to its FQDN.

When a client makes a single name request to a DNS server, DNS will check all its zones to try and match it to a FQDN. This will not work. After DNS has exhausted all its zones, it will look in the Globalnames zone. There, should it be present, it will locate a CNAME record for that single name. It will point to the FQDN record in the forward lookup zone. DNS will now return the IP address to the requesting node.

Reference: http://www.trainsignaltraining.com/windows-server-2008-globalname-zone/2008-07-22/

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog