Publish-SilData
Publish-SilData
Initiates a point in time collection of Software Inventory Logging data and forwards it, along with any accumulated historical data, to the aggregation server. Windows Server 2012 R2 with KB3000850 applied. For more information, see https://support.microsoft.com/kb/3000850.
Syntax
Parameter Set: CollectThenFlush
Publish-SilData [[-FileName] <String> ] [-AsJob] [-CheckCollectionHistory] [-CimSession <CimSession[]> ] [-ThrottleLimit <Int32> ] [ <CommonParameters>]
Parameter Set: FlushOnly
Publish-SilData [-AsJob] [-CimSession <CimSession[]> ] [-ThrottleLimit <Int32> ] [-UseCacheOnly] [ <CommonParameters>]
Detailed Description
The Publish-SilData cmdlet initiates a point in time collection of all Software Inventory Logging data, and forwards the data over the network to an aggregation server, if one is specified. To identify the aggregation server, specify the TargetUri parameter of the Set-SilLogging cmdlet. If Software Inventory Logging was started by an administrator by using the Start-SilLogging cmdlet, hourly collection and forwarding of data to the aggregation server commences. In cases where Software Inventory Logging does not receive an acknowledgement from the aggregation server that data forwarding was successfully received, the feature stores that data locally and attempts to forward both cached and current data during the next scheduled forward attempt. Once the cached and current data has been forwarded successfully, the feature deletes all historical data from the local server.
Parameters
-AsJob
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-CheckCollectionHistory
Indicates that this cmdlet checks whether the current data set varies from the previous collection results. If it does vary, this cmdlet publishes a full set of the data to the aggregation server at the target uniform resource identifier (URI). If the data set does not vary, this cmdlet publishes a small package of data that identifies the computer to the aggregation server.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-CimSession<CimSession[]>
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
Aliases |
Session |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-FileName<String>
Specifies the name of a file. This file is used by Software Inventory Logging to define the data sources. Because Software Inventory Logging has an inherent default value, you do not usually need to specify this parameter.
Aliases |
none |
Required? |
false |
Position? |
1 |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-ThrottleLimit<Int32>
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
-UseCacheOnly
Indicates that the server can publish stored data to the aggregation server without triggering a point in time collection of all Software Inventory Logging data.
Aliases |
none |
Required? |
false |
Position? |
named |
Default Value |
none |
Accept Pipeline Input? |
false |
Accept Wildcard Characters? |
false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
Outputs
The output type is the type of the objects that the cmdlet emits.
- None
Examples
Example 1: Forward Software Inventory Logging data
This command initiates a point in time data collection of Software Inventory Logging data and forwards the data to an aggregation server. To identify the aggregation server, specify the TargetUri parameter of the Set-SilLogging cmdlet.
PS C:\> Publish-SilData