Console -- Start -- client ping / mstsc with FQDN
Make clients Calls like Ping / MSTAC witrh FQDN and not with Netbios. We have different AD connected to the SCCM . We can not use the build in features like Ping the clients or open RDP as the console only tries the netbios name and not the fqdn. It would be great to have all cleints call done trought FQDN
Anonymous
shared this idea
Admindjam
(Product Director, or Executive, Microsoft Endpoint Configuration Manager)
responded
understood. hopefully, ping isn’t needed as much in 1602 w/ online/offline status. will look into the others.
3 comments
-
Anonymous
commented
Furthermore if the device has more than one IP registered in DNS try to connect to all addresses before failing the connection. It's really common for laptops to have two IP address in DNS, one for LAN and one for WLAN
-
Robert Johnsson
commented
I hope this gets fixed as we are having the same problem. We had to activate WINS for the time beeing. DNS should be the way to go.
-
Anonymous
commented
Remote tools always use netbios names. With Direct Access and ISATAP (manage out scenario) enabled sccm server netbios names doesn't work. Looks like remote tools allways use LLMNR instead dns query.