You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue to track an idea for a set of facts that I would like to contribute.
Currently information about the domain your machine is running in is difficult to get if you need anything other than the FQDN of the domain. The FQDN is not always usable because in some cases it's really the NETBIOS name that the user needs. Doing a substring on FQDN could get complicated ifa user is running in a subdomain or with a non standard tld like test.corp.internaltest. Whereas in PowerShell or possible even ruby, getting the NETBIOS is easy.
So this issue is track both my intention to do a PR to add the NETBIOS fact, and to take input about what other facts about the domain environment might be useful to surface while I'm at it.
Thanks,
Bill
The text was updated successfully, but these errors were encountered:
This issue to track an idea for a set of facts that I would like to contribute.
Currently information about the domain your machine is running in is difficult to get if you need anything other than the FQDN of the domain. The FQDN is not always usable because in some cases it's really the NETBIOS name that the user needs. Doing a substring on FQDN could get complicated ifa user is running in a subdomain or with a non standard tld like
test.corp.internaltest. Whereas in PowerShell or possible even ruby, getting the NETBIOS is easy.So this issue is track both my intention to do a PR to add the NETBIOS fact, and to take input about what other facts about the domain environment might be useful to surface while I'm at it.
Thanks,
Bill
The text was updated successfully, but these errors were encountered: