...
Use-JobSchedulerMaster
SYNOPSIS
This cmdlet has to can be used as the first operation with JobScheduler Master cmdlets and identifies the JobScheduler Master that should be usedto import settings from a local JobScheduler Master installation for Windows. The cmdlet is not related to the JobScheduler REST Web Service. Optionally applies settings from a JobScheduler Master location. A Master is identified by its JobScheduler ID and URL for which it is operated.
...
Use-JobSchedulerMaster [[-Url] <Uri>] [-Id] <String> [[-InstallPath] <String>] [[-BasePath] <String>] [[-EnvironmentVariablesScript] <String>] [[-Credentials] <PSCredential>] [[-ProxyUrl] <Uri>] [[-ProxyCredentials] <PSCredential>] [-NoCache] [<CommonParameters>]
DESCRIPTION
During installation of a JobScheduler Master a number of settings are specified.
Such settings are imported for use with subsequent cmdlets.
* For a local Master that is installed on the local Windows computer the cmdlet reads
settings from the installation path.
* For a remote Master operations for management of the
Windows service are not available.
...
| Required? | false |
| Position? | 8 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
NoCache
-NoCache <SwitchParameter>
Specifies that the cache for JobScheduler objects is ignored.
This results in the fact that for each Get-JobScheduler* cmdlet execution the response is
retrieved directly from the JobScheduler Master and is not resolved from the cache.
| Required? | false |
| Position? | named |
| Default value | False |
| Accept pipeline input? | false |
| Accept wildcard characters? | false |
RELATED LINKS
EXAMPLES
-------------------------- EXAMPLE 1 --------------------------
...