|
The @Domain variable returns the Netbios Name for the Domain. Netbios is still in use technically, but FQDN's are really the recommended way of doing things now.
I would like to request that the @domain kixtart variable be updated to return the FQDN.
Reasons
1. Netbios is technically obsolete and there are user cases where using Netbios Names would cause problems.
2. Domain UNC paths do not support Netbios Names (until the computer has fully booted). If you want to copy file from a server using the domainname\"path" you have to use domainname.internal\"filepath", not just domainname\"filepath". The Netbios path only seems to work once the computer is booted or possibly only in the userspace environment. It does not work in the startup script! DFS and Domain name paths are pretty much standard now as more and more domains operate across sites.
3. It is untidy to have to add + ".internal" to every @domain command although one could declare a variable that $DomainName = @Domain + ".internal".
4. The secondary problem with having to either add the ".internal" or declare a new domain variable is that while I setup my domains using .internal unfortunately a lot of people still setup the domain using .local so you have to take that into consideration when using one script for multiple clients. I would have to find a way to define which clients use .local and which ones use .internal.
5. The %UserDnsDomain% variable which does support FQDN's only works in the user login script, not in the startup script as environment variables only work in the userspace. I need the startup script equivalent.
Conclusion
For the above reasons, I would like to request that the @domain variable be updated to support FQDN to ensure compatibility with modern systems and features that only use FQDN's. Thank you.
| 
