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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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.

Jason Yoder, MCT

Search This Blog