I've run into a snag trying to move from logon script based drive mappings, to a GPO based Drive map solution and I'm hoping somebody can shed some light on the problem that I am seeing. We started down the GPO based drive mappings because we have a handful of Windows 8 client computers which don't run the logon script based drive mappings.
I put together a basic Drive Maps GPO. I'm mapping 3 drives, I've linked the GPO to a computer container OU for testing and everything is working just fine. I have 3 different Windows 8 client PC, all domain joined, and all 3 run the GPO as expected.
The problem is when I attempt to apply Item-level targeting. I've found that if I define item-level targeting to use the NetBIOS name of the computer, I can either apply the GPO at an individual computer level, or I can exclude the GPO for that individual computer by toggling between IS and IS NOT. However, when I choose to define the computer name by choosing the DNS option, the GPO does not apply as expected.
So, if I say "the DNS computer name is example1.mydomain.com" and I apply the GPO, it applies to example1, example2 and example3. And if I instead say, "the DNS computer name is not example1.mydomain.com", then it doesn't apply to example1, example2 or example3. Obviously, I would expect it to apply or not apply only to example1.mydomain.com.
If instead, I say "the NetBIOS computer name is example1", and apply the GPO, then example1 gets it, and example2 and example3 do not. If I say, "the netBIOS name is not example 1", then example1 does NOT get the drive mapping, but example 2 and example3 do. < This is exactly what I want and I can continue to just use NetBIOS names...but I don't understand why DNS isn't working in the same manner.
My clients are all using DHCP and using domain controllers for DNS. All 3 machines are in the mydomain.com namespace. The mydomain.com namespace is an active directory integrated zone. We have reverse zones in place for the dns records. I can ping the machines from the DC's as well as the machines themselves. I can run nslookup and resolve the computer name for each host using the FQDN. I can also run a ping -a IP_ADDY and get the FQDN back. The DC's themselves are running Server 2008 R2. I honestly don't see any issues from a name resolution standpoint on the network itself.
So, any suggestions as to why defining the shortened NetBIOS name works just fine, but using DNS with a FQDN does not? (I've tried the DNS name using just the name, the name., as well as name.mydomain.com and name.mydomain.com.)