Has anyone else run into a situation where installation of the LANDesk agent is changing their network location profile? This is happening for us with 9.5 SP2 and 9.6 agents, only on Server 2012 R2. If the LANDesk agent isn't installed, this is not a problem. It only happens after we install the agent. Any direction would be appreciated!
Without the LANDesk agent installed, the machines NLA identifies the machine as being on the domain.
With the LANDesk agent installed the machine kicks to public for the network profile.
With the LANDesk agent installed and disabled, the machine kicks to public for the network profile.
With the LANDesk agent installed, if we restart the NLA service, it comes up correctly in the domain.
This is happening on 2012 R2 servers.