We deleted those 3 regkeys and after restarting the SMAgent service those came back (with the exception of key under HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\NSClient\NSs).
No other client machines has that "lcorp" reference. As well we couldn't find an alternate URL on policies that refers to it.
ITMS 7.x and later
You may see entries in the Agent logs were this invalid server name is referenced and failed to reach to it.
On the affected client machine, under the Queue folder (under .../Program Files/Altiris/Altiris Agent/), there was still a folder named as the invalid server name.
Invalid server reference under HKLM\SOFTWARE\Altiris\Altiris Agent\Servers and HKLM\SOFTWARE\Altiris\Communications\Server Profiles\Servers
In order to clean this bad reference from the registry, please follow these steps:
Look under the .../Program Files/Altiris/Altiris Agent/Queue/ and find a folder called "Server1.mydomain.lcorp.com/Altiris".
Stop the SMAgent service.
Delete the content (if any) of this folder
Delete the "Server1.mydomain.lcorp.com/Altiris" folder
Delete one more time all the registries that have a reference for "Server1.mydomain.lcorp.com/Altiris"
Restart the SMAgent service
Check if the 'lcorp' reference is recreated in the registry.
Changes done for ITMS 8.5 release:
The significant changes have been made into network monitor module of SMA. SMA does not ping servers anymore. "Communications\Servers" registry key is populated with the active server usage statistics (current state, connections attempt and errors and speed) and if server is not being connected to for 2 weeks, it will be removed from the registry. The names from that registry key are not used to initiated any kind of connection, they merely use to get the statistics and get the connection method for future connections (via CEM or not).
ID: 3636236, 3628562
Imported Document ID: TECH225651
Subscribing will provide email updates when this Article is updated. Login is required.