|
If you are not a full administrator, you can only view pre-cached jobs provided you have Read permissions on the collection as well as the content.
To view pre-cached jobs:
You can only delete pre-cached jobs if you have permissions for a particular content type. If you are not a full administrator, you will need:
To delete a pre-cached job:
You can also manage pre-cached jobs by using PowerShell cmdlets.
To get all pre-cached jobs from ActiveEfficiency, run:
Get-PreCachingJobs [-ActiveEfficiencyUrl <String>] [<CommonParameters>]
To remove pre-cached jobs from ActiveEfficiency run:
Remove-PreCachingJobs [-Id] <String> [-ActiveEfficiencyUrl <String>] [-Confirm [<SwitchParameter>]] [<CommonParameters>]
Remove-PreCachingJobs -Before <String> [-ActiveEfficiencyUrl <String>] [-Confirm [<SwitchParameter>]] [<CommonParameters>]
Remove-PreCachingJobs -AgeInDays <UInt32> [-ActiveEfficiencyUrl <String>] [-Confirm [<SwitchParameter>]] [<CommonParameters>]
Remove-PreCachingJobs -All [<SwitchParameter>] [-ActiveEfficiencyUrl <String>] [-Confirm [<SwitchParameter>]] [<CommonParameters>]
The parameters are:
Parameter | Optionality | Notes |
---|---|---|
-Id | Mandatory | ID for the job to delete. |
-ActiveEfficiencyURL <string> | Optional | Location of ActiveEfficiency. If not provided, it is retrieved from the NomadAdminUI registry value. |
-Confirm | Optional | Suppresses the confirmation prompt for the deletion. |
-Before | Mandatory | Delete jobs before a particular date and time where the notation is yyyyMMddHHmmss . |
-AgeInDays | Mandatory | Delete jobs older than a particular number of days. |
-All | Mandatory | Delete all jobs. Exercise caution if you use this. |
<CommonParameters> | Values are: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, PipelineVariable and OutVariable |
There is more information about CommonParameters
at http://go.microsoft.com/fwlink/?LinkID=113216
If the content or membership of a targeted collection changes after a pre-cached job is created, ActiveEfficiency is updated to keep in sync with Configuration Manager. It does this by polling the Configuration Manager database at regular intervals to fetch updated content.
These intervals (you would have defined the intervals when you installed ActiveEfficiency) have the following characteristics:
Each synchronization task fetches the following:
Pre-cached jobs are affected when these events take place in Configuration Manager, and on the next synchronization with ActiveEfficiency:
Configuration Manager events | Next ActiveEfficiency synchronization cycle | ||
---|---|---|---|
Device collections |
|
| |
Packages |
|
| |
Applications |
|
| |
Task sequences | If you chose to automatically pre-cache references (as well as those added later) ![]() | ActiveEfficiency is updated:
| |
If you chose to selectively pre-cache references: ![]() |
|
You can force a synchronization to occur outside its normal cycle. To do this:
ServiceHost.exe -NomadSyncAll
.
ServiceHost.exe -NomadSync
C:\ProgramData\1E\ActiveEfficiency\service.log
for details. All synchronisation activities are logged in ActiveEfficiency's service log C:\ProgramData\1E\ActiveEfficiency\service.log
by default.There may be instances, such as carrying out maintenance on the Configuration Manager server or the SQL Server instance, where you have to disable synchronization. To do this:
ServiceHost.exe.config
located in the service installation folder, typical in C:\Pogram Files (x86)\1E\ActiveEfficiency\Service
by default.Set EnableNomadSync
to false under the AppSettings element. For example:
<appSettings> ... <add key="EnableNomadSync " value="false"/> ...... </appSettings> |
Hash validation is used when content is downloaded for pre-cached jobs and for LSZgen requests for these jobs. When a pre-cached job is created:
On the client side:
After running the wizard, Nomad clients that are registered with ActiveEfficiency and that were included in the selected device collection will get a pre-cache notification within 24 hours. This notification tells Nomad that it has to process a download job on the content to be cached. The default number of notifications a client processes in one pre-cache poll cycle is 20 but you can modify this by updating the PrecachePollBatchSize registry value.
Nomad clients normally start their polling cycle when the service starts, with a random delay to minimize the possibility of multiple simultaneous polls from different clients. However, polling will not start if any of the following is true:
To explicitly turn polling off for a Nomad client set the PrecachePollMinutes registry value to 0.
Nomad pre-caching is tightly integrated into Configuration Manager and honors the permissions and restrictions enforced by role-based access control (RBAC). The following rules are used to determine whether a particular user is allowed to pre-cache a particular content on a particular collection or not:
If an administrator does not have the necessary RBAC permissions, they will not be able to see or access any of the Nomad pre-cache features in the Configuration Manager Admin console. Similarly, if they do not have the right permissions to a device collection, that collection will not be available to them in the Targeting screen of the pre-cache wizard.
However, full administrators will see:
The following table provides an overview of the availability of Nomad pre-caching for the built-in Configuration Manager security roles:
Nomad pre-caching support based on the Configuration Manager security role | |||||||
Built-in Configuration Manager Security Roles | SOFTWARE LIBRARY | ||||||
APPLICATION MANAGEMENT | Operating System | ||||||
Applications | Packages | Driver Packages | Operating System Images | Boot Images | Task Sequences | ||
Nomad pre-caching Wizard | |||||||
Application Administrator | Pre-caching available (Access to Collection required) | Not available | |||||
Application Author | Pre-caching Not available (Access to Application Management only) | Not available | |||||
Application Deployment Manager | Pre-caching available (Access to Collection required) | Not available | |||||
Asset Manager | No access to Software Library | ||||||
Company Resource Access Manager | |||||||
Compliance Settings Manager | Pre-caching Not Applicable for Software Updates (No Access to Application Management & Operating System, Only Software Updates under Software Library available) | ||||||
Endpoint Protection Manager | No Access to Software Library | ||||||
Full Administrator | Pre-caching available (Access to Collection required) | ||||||
Infrastructure Administrator | Pre-caching not available (Access only to Windows Sideloading Keys in Application Management under Software Library) | ||||||
Operating System Deployment Manager | Pre-caching not available | Pre-caching available
| |||||
Operations Administrator | Pre-caching available (Access to Collection required) | ||||||
Read-only Analyst | Pre-caching not available (SCCM Console is in Read-Only mode) | ||||||
Remote Tools Operator | No access to Software Library | ||||||
Security Administrator | |||||||
Software Update Manager | Pre-caching not applicable for Software Updates (No access to Application Management & Operating System, Only Software Updates under Software Library available) |
The following limitations are part of the current implementation of the Nomad pre-caching feature:
Prior to this release, when a download is initiated, Nomad only used the credentials from the first Configuration Manager network access account it found to authenticate, and if that failed, the download stopped. From this release, Nomad cycles through all native Configuration Manager network access accounts to authenticate, thereby reducing the risk of failure.
Nomad won't use network access accounts for SMB downloads from Distribution share. It uses the SYSTEM$ account to connect to the package share location. |