Video Screencast Help
Symantec Secure Login will be live on Connect starting February 25. Get the details here.

SMP Resource Key Creation Logic for Mac OS Client Computers

Created: 06 Sep 2013 • Updated: 02 Feb 2015
Language Translations
dougj's picture
0 0 Votes
Login to vote

The following describes how the SMP agent for Mac finds values for various resource keys. Note that you can run 'aex-helper info resource' on any Unix, Linux or Mac client that has the SMP agent installed to view the computer guid, resource keys and values. 

The targeted settings that determine if we use the local computer values or DNS values are found in the NS console at Settings, All Settings, Agents/Plug-ins, Symantec Management Agent, Settings, "Symantec Management Agent Settings - Targeted", then select the appropriate filter, then click on the 'UNIX/Linux/Mac' tab, then scroll down to the 'Computer information' section. 

7.1 SP2 for Mac

1. First ‘name.domain’ resource key

When Targeted Agent Settings are set to Computer:

   A. Name: the value in System Preferences Sharing UI
   B. Domain: empty

When Targeted Agent Settings are set to DNS:

   A. Name: If nodename or hostname resolve, get the DNS name. If hostname is empty, use nodename.
   B. Domain: If nodename or hostname resolve, use DNS domain. Otherwise, use local system call to domainname. If domain name is empty OR if targeted agent setting to use /etc/resolv.conf is checked, then use the /etc/resolve.conf domain. 

2. ‘fqdn’ resource key

    A. Concatenation of the values for first 'name.domain' key when targeted agent settings are set to DNS. The ‘fqdn’ key is reported if it differs from the first ‘name.domain’ key.

3. Second ‘name.domain’ resource key

    A. This is a copy of the ‘fqdn’ resource key and is used for backward compatibility with NS6. The second ‘name.domain’ key is reported only if it differs from the first ‘name.domain’ key.

4. ‘macaddress’ resource key

    A. Contains the mac addresses of the client computer. 

5. ‘uniqueid’ resource key

A. This is composed of ComputerID, MotherboardID and Mac Address. However, on Mac clients the ComputerID and MotherboardID are blank so this is literally a hashed value of the mac address values (until 7.5 SP1).  If you find that you must exclude 'macaddress' as a resource key for Mac clients, then the 'uniqueid' should also be excluded. 

The creation of the uniqueID values generates aex-client.log entries when the client.conf debug_level is set to 'degub' and ignore_resource_keys entry does not include 'uniqueid'. These log entries show the actual system values for the UUID, MB_Serial and Mac address used to generate the uniqueid value. An example (with dummy values) is: 

DEBG 2015-01-23 10:12:16.805        90    2957438976  BaseSDK > AComputerIdent::GetUniqueId: Create value for resource key: uniqueid
DEBG 2015-01-23 10:12:16.805        90    2957438976  BaseSDK > AComputerIdent::GetUniqueId: UUID 'XYZ12345-80D2-4567-99FF-B851FABC890', MB_Serial 'C01111222ABC89DEC', MAC '40-6C-8F-11-AA-BB'
DEBG 2015-01-23 10:12:16.806        90    2957438976  BaseSDK > AComputerIdent::GetUniqueId: Final uniqueid value: Hc1aNYVyyvwH1rng9djIOA==

As of 7.5:

   A. On Mac computers, an additional ‘name.domain’ resource key is added for Mac computers bound to an active directory domain that contains the AD name and domain. This shows as the second ‘name.domain’ key and is only reported if it differs from the first ‘name.domain’ key. 

As of 7.5 SP1:

   A. On Mac computers, the uniqueid is generated the same as on Linux and Unix computers. That is, the UUID, motherboard serial number, etc. are gathered from the SMBIOS and used to generate the uniqueID value.