All of the extensions such as Client Tools, right click tools etc use the SUB:Name variable to target their actions. Unfortunately in our environment where we have multiple DNS zones this means that the tools will only work on machines on the same subnet/DNS zone as the administrator.
I would love to be able to roll the client tools out to all our technical teams but because the SUB:Name isn't the same as the FQDN they do not work. In our environment the FQDN is required for any device which is not on the same subnet as yourself.
I know that the FQDN is stored in SCCM under Resource Names[0] but you cannot use arrays to target the extensions so I am not simple able to use SUB:Resource Names[0] in its place. Adding all the DNS suffixes to ip config is not an options.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi,
All of the extensions such as Client Tools, right click tools etc use the SUB:Name variable to target their actions. Unfortunately in our environment where we have multiple DNS zones this means that the tools will only work on machines on the same subnet/DNS zone as the administrator.
I would love to be able to roll the client tools out to all our technical teams but because the SUB:Name isn't the same as the FQDN they do not work. In our environment the FQDN is required for any device which is not on the same subnet as yourself.
I know that the FQDN is stored in SCCM under Resource Names[0] but you cannot use arrays to target the extensions so I am not simple able to use SUB:Resource Names[0] in its place. Adding all the DNS suffixes to ip config is not an options.
Any ideas!?
Thanks
Share this post
Link to post
Share on other sites