We’re about to roll out TEM to a number of additional departments. We’d like to use the clientsettings.cfg file bundled with the installer to associate each client with the group for the department to which it belongs.
We’ve used Tools->Manage Properties to create a new “Department” property. It is activated Globally in the Master Action Site with the following relevance statement:
if (exists setting “Department” whose (exists value of it) of client) then value of setting “Department” of client else “None”
Here’s the content of our clientsettings.cfg:
Department=DeptName
When we run the installer with clientsettings.cfg in the same directory, the Department property does not get set on the computer.
Any idea what we’re doing wrong?
Additionally, when an operator right-clicks on a computer and selects Edit Settings, they do not see the Department property in the list of available properties to edit. Any idea how we would add a property to that list so that all operators can edit it for computers within their scope of control?
And to answer your question, YES, it’s another key.
In my case, we use a setting “Owner” so it creates a Key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\EnterpriseClient\Settings\Client\Owner under which there are VALUES “effective date” and “value”.
Effective Date is obviously the date that the setting was last set.
Thanks for the clarification, Tim. I can confirm that the “Department” registry key is NOT being created on client install.
Can you describe the process you went through to create the “Owner” setting in the TEM console? Was it just a matter of selecting a set of computers, right-clicking, selecting Edit Computer Settings, then using the Add button to create the setting? Or was there more to it?
A couple thoughts… The clientsettings.cfg has to be run with the exe not not the msi version of the installer.
A couple other ways to assign department setting:
Edit computer settings as you mentioned (right-click, edit computer settings)
Use the following action script in a Task designed to prompt the operator for the name of the department and then they can target whatever machines they want.
action parameter query “department” with description “Please enter the Department Name” with default “”
setting “department”="{parameter “department”}" on “{parameter “action issue date” of action}” for client
it got fixed, but we deleted and re-added the “Department” property via Tools > Manage Properties in the console, and then everything started working as advertised. I think it may have had something to do with the permissions of the user who originally created the property.