Enterprise Support - Symantec Corp. Managing resource keys for event generation on Unix, Linux & Macintosh clients. As of the Agent for Unix, Linux and Mac (ULM) 7.1, it is possible to configure which resource keys to ignore during generation of NSE events. This allows for exclusion of any values that would cause a conflict in a given environment. (An NSE event is anything sent to the NS/SMP, including Basic Inventory, event transactions, inventory solution, etc.) This can apply to any situation where computer resources are merged because they have the same resource key values. To make this configuration change: 1. 2. 3. Note 1: Values listed here will NOT be used as resource keys in events sent to the NS/SMP from the client.
Note 3: Supported values are: name.domain, fqdn, macaddress, uniqueid, adnamedomain. Note 4: The name.domain value is based on the targeted settings 'Computer Information' settings in the NS/SMP Console. In 7.1 SP1_PF1, this field is viewable and modifiable in the client.conf file. Sample: [MachineID] ... ignore_resource_keys=fqdn, macaddress, uniqueid ...
Automating Maintenance with the ASDK – Deleting Unmanaged Machines. The purpose of this document is to provide a walk through on how the ASDK can be used to automate NS cleanup and maintenance tasks. It assumes that you have a basic understanding of Visual Studio and .NET programming. There are a number of things in my organization that we found ourselves doing manually to recoup licenses and make sure that the data in our notification and asset servers stays clean. What I plan on covering in this article is how with a little programming and the Altiris SDK, you can automate the cleanup of unmanaged machines and run it on a regular schedule. Where to Begin The first step in using any portion of the SDK is to install it on your Notification or Asset server so its methods will be available for use. ItemManagementService – This can be found in the Notification Server portion of the SDK.
Once the SDK is installed on your Notification and/or Asset Server, there are a couple of ways that we can begin. Creating Your Proxy Classes Creating your Project Final code: ASDK Training: ASDK Basics. S blog » Blog Archive » Powershell check requirements and load addins. Powershell excerpts of how to check if .NET FrameWork 3.5, Quest AD, Altiris ASDK is installed First the functions that execute the installer. The code that checks if .NET FrameWork 3.5 is installed. A messagebox will be displayed if it is not installed. If users answers yes to the messagebox the requirement will be installed. The code to check if Quest AD is installed. A messagebox will be displayed if it is not installed. Check if Altiris ASDK for NS is installed. Tags: .net, Altiris, asdk, dotnet, Powershell, Quest AD.