Main: General
|
Attribute name |
Description |
|
Profile ID |
Profile ID is generated automatically and it cannot be changed. |
|
OS category |
Operating system category defines the software platform to which this profile is applied to (Windows / Linux / OS X). This field cannot be edited after it has been saved for the first time. |
|
Scheduled task |
Scheduled task field defines the scheduled tasks to which this profile is applied to. This field cannot be edited after it has been saved for the first time. |
|
Name |
Name of the scheduled task profile. Try to use descriptive names that somehow describe the purpose of the profile (e.g. Disk space monitor for Windows workstations). This field is mandatory. |
|
Description |
Enter here a free description of the scheduled task profile item. |
|
Status |
Determines the status of this scheduled task profile item. If status = enabled, the scheduled task profile item is active and the profile settings are applied to all assets that match with the profile scope. If status = disabled, the scheduled task profile item is inactive and the profile settings are not applied to any assets. Notice that the creation of new asset configuration items will not work if you disable the built-in Hardware scan task, because then the new assets will not get the hwscan job. |
Main: Profile scope
|
Attribute name |
Description |
|
Asset configuration |
With this option, it is possible to define in an asset level the devices where the scheduled task is allowed or denied to run. For example: "Allow, Asset configuration, Equals = L0000010" would mean that the scheduled task is allowed to run in the device, whose name is "L0000010", but denied in all other devices. "Deny, Asset configuration, Equals = L0000010" on the other hand, would mean that the scheduled task is not allowed to run in the device, whose name is "L0000010", but it can be run for all other devices. |
|
Asset group |
With this option, it is possible to define a group of assets where the scheduled task is allowed or denied to run. For example: "Allow, Asset group, Equals = PilotGroup" would mean that the scheduled task is allowed to run in devices which are members of asset group "PilotGroup", but denied in all other devices. |
|
Device role |
With this option, it is possible to define the assets where the scheduled task is allowed or denied to run according to the device role of assets. "Allow, Device role, Equals = Server" would mean that the scheduled task is allowed to be run in the devices whose device role is "server", but the task would not be run in devices, whose device role is something else. |
|
Device usage |
With this option, it is possible to define the assets where the scheduled task is allowed or denied to run according to the device usage of assets. "Deny, Device usage, Equals = File server" would mean that the scheduled task would not be run in the devices whose device usage is "File server", but the task would be run in devices, whose device usage is something else. |
|
Location |
With this option, it is possible to define the assets where the scheduled task is allowed or denied to run according to the location of assets. "Allow, Location, Equals = EMEA" would mean that the scheduled task is allowed to be run in the devices whose location is "EMEA" or some of EMEA's sublocations, but the task would not be run in devices that are assigned to some other location. |
|
Organisation |
With this option, it is possible to define the assets where the scheduled task is allowed or denied to run according to the organisation of assets. "Allow, Organisation, Equals = Sales" would mean that the scheduled task is allowed to be run in the devices whose organisation is "Sales" or some of it's suborganisations, but the task would not be run in devices that are assigned some other organisation. |
|
OS subcategory |
With this option, it is possible to define the assets where the scheduled task is allowed or denied to run according to the subcategory of the operating system that is installed to the assets. (Particular Windows versions, or Linux or OS X distributions e.g. "Windows 7" or "Fedora"). "Allow, OS subcategory, Equals = Windows 7" would mean that the scheduled task is allowed to run in the devices that have Windows 7 installed, but the task is not run in devices that are operating on some other operating system. |
Main: Profile settings
|
Attribute name |
Description |
|
Allowed time frame |
This field defines the allowed time frame (use full hours) when the selected scheduled task is allowed to be run for the devices matching this profile. Use the "scheduled task" field to determine the desired scheduled task. Use full hours and the '-' character as delimiter between two times to specify the allowed time frame. Example: 17-06 would mean that the task is allowed to run between 17:00 and 6:00 only. Notice that the scheduled task item itself may also have an allowed time frame defined. If you leave this field empty on the scheduled task profile item form, the default setting is inherited to the profile from the scheduled task item that has been selected to this profile. Good to know about patch management If you want Miradore to scan patches daily, it is recommended to use an interval of 12 hours, instead of 1 day. Notice also that the patcher will run at the managed devices both during the allowed time frame and during the possible maintenance windows. |
|
Copy output |
This field defines whether the assets matching to this profile send the output file of the scheduled task to Miradore server after it has been performed or not. If this field is left empty, the default setting are inherited from the scheduled task item that has been selected for this profile. |
|
Interval |
This field defines how often the scheduled task is run for the assets who match with the profile scope. The interval is calculated from the moment when the task was last time successfully performed. If this field is left empty, the default setting is inherited from the scheduled task item that has been selected to this profile. |
|
Parameters |
This field defines the parameters that are used to run the attached script (i.e. task file) for the assets that match with the profile scope. If this field is left empty, the default setting is inherited from the scheduled task item that has been selected for this profile. |
|
Randomize start time |
Yes = Run the task at a random time within the allowed time frame. No = Run the task at the beginning of the allowed time frame. In larger environments with many devices, randomisation is a good way to balance the load caused by the devices. |
|
Run after every boot |
Yes = The task will be run automatically always after a device has restarted. No = The task will be run only according to the schedule, but not after device reboots. Notice also that some patch installations require a device restart afterwards. Therefore, running the "Patch scan and install" task after reboot speeds up the tracking of patch installations |
|
Run in initial install |
This field defines whether the selected scheduled task is run during the initial install of assets that match with the profile scope or not. If this field is left empty, the default setting is inherited from the scheduled task item that has been selected for this profile. |
|
Time out |
This field defines the time out time time that is used to run the selected scheduled task for the assets that match with the profile scope in seconds. If this field is left empty, the setting is inherited from the scheduled task item that has been selected for this profile. |
|
Use UTC time |
This field determines whether the assets matching to this profile use Coordinated Universal Time (UTC) or the local time of Miradore client for calculating the allowed time frame for the scheduled task. If this field is left empty, the setting is inherited from the scheduled task item that has been selected for this profile. |
Main: Task files
|
Attribute name |
Description |
|
Task file |
This field defines the script that the custom scheduled task runs according to the settings defined to the profile. If you select "Text" as a file type for the task file, you can write the script directly to the editor that is provided in the popup window. If this field is left empty, the setting is inherited from the scheduled task item that has been selected for this profile. |
|
Additional files |
Here you may attach additional files that are required to run the task. If this field is left empty, the setting is inherited from the scheduled task item that has been selected for this profile. |
Main: Additional information
|
Attribute name |
Description |
|
Attachments |
You may attach files into this field. About attaching files. This field is optional. |
|
Comments |
You may add comments related to this item here. This field is optional. |