Right, that was it.
Ok, so the only thing the server would initiate is still a client installation and as this likely didn’t change it still requires FQDN to work. Thanks Jason. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 22. Mai 2013 13:43 To: [email protected] Subject: Re: [mssms] CM2012 using FQDN for client actions? It’s called fast channel notification. Exactly like the rest of ConfigMgr, the server *never* initiates communication with an installed client agent. Fast channel uses a persistent connection set up by the client. Thus, all the server does is send a signal done this established connection and should have no need for address resolution of the client agent’s host system (just like the rest of ConfigMgr as mentioned). J From: Roland Janus Sent: Wednesday, May 22, 2013 6:01 AM To: [email protected] If CM07 is connecting a client, mainly for e.g. a client installation, it is using DNS, FQDN. Now there is this new feature, can’t remember how it is called, to trigger actions on clients. Is CM12 also using FQDN for all those actions? I assume it still does it for the client push but also for that new feature? Can someone confirm this please? I ask since our VPN clients are not registering in DNS, it’s Wins only, hence client push does not work on CM07 already. -R
