Re: Windows File Access policy odd behaviour dealing with blanks and nulls?
Would it be simpler to run an LDAP query against your AD for blank/null values of that field? If blank/null is a valid value, then you'd have to come up with a solution to cause a path other than root to be mapped. If the users never navigate above this directory, you could rename them all "_$directory" and then create an empty, read-only "_" diretory so that if the value was blank/null, the end result would still be a subdirectory instead of the root.
Theodore E Van Iderstine Stream Networks +1 678 373 4200 x125 JNCIA-ER (expired), JNCIA-SSL (ditto)