Get-SPPerformancePointSecureDataValues
Published: May 12, 2010
Displays unattended service account settings.
Get-SPPerformancePointSecureDataValues [-ServiceApplication] <SPPerformancePointMonitoringServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
|
ServiceApplication |
Required |
Microsoft.PerformancePoint.Scorecards.SPPerformancePointMonitoringServiceApplicationPipeBind |
Specifies the PerformancePoint Service application that is associated with the unattended service account. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a PerformancePoint Service application (for example, PerfPointApp1); or an instance of a valid SPPerformancePointServiceApplication object. |
||
|
AssignmentCollection |
Optional |
Microsoft.SharePoint.PowerShell.SPAssignmentCollection |
Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
|
Detailed Description
The Get-SPPerformancePointSecureDataValues cmdlet displays global settings for the unattended service account.
Input Types
Return Types
------------------EXAMPLE 1---------------------
Get-SPPerformancePointServiceApplication | Get-SPPerformancePointSecureDataValues
This example shows how to get the unattended service account settings using a service application pipe bind.
------------------EXAMPLE 2---------------------
Get-SPPerformancePointSecureDataValues –ServiceApplication "PerformancePoint Service Application"
This example shows how to specify the service application by using the service application name.
Change History
| Date | Description | Reason |
|---|---|---|
|
May 12, 2010 |
Initial publication |
|

Note: