My Findings around PowerShell in Project Server 2013

There are 53 new PowerShell cmdlets that operate on 24objects. Basically there are 10 cmdlets to configure Security and Resources, 8 for Installation and Initial Configuration and 6 for Monitoring. Each object has Get, Set, Mount etc Verbs for a total of 53 Verb/Noun cmdlets. If you wish to manage data such as add projects, tasks etc you need to use the .NET Programming interfaces. Full list and reference is here http://technet.microsoft.com/en-us/library/ee890097(v=office.15)

Security and Resources (10)
UserSync
UserSyncDisabledSyncThreshold
UserSyncFullSyncThreshold
UserSyncOffPeakSyncThreshold
PermissionMode
Permissions
ActiveDirectoryEnterpriseResourcePoolSync
ActiveDirectoryGroupSync
ActiveDirectorySyncSettings
AdministratorAccess
Installation and Initial Configuration (8)
Database
DatabaseQuota
DatabaseSQLCredentials
ServiceApplication
ServiceApplicationProxy
WebInstance
PCSSettings
OdataConfiguration
Monitoring (6)
DatabaseState
LogLevelManager
LogLevelManagerRefresh
QueueSettings
QueueStatsMonitoring
TimerJobDefaultSchedule

Using the Client Object Model to get at Project Server Data

Here is how to do it in SharePoint by Steve Peschka and here is MSDN article http://msdn.microsoft.com/en-us/library/ee857094.aspx

But how to do it in Project Server with PowerShell?

Other not that important but notable stuff

The GUID’s of OOB lookup tables and custom fields are then same in 2013

When customizing Views, you add a field to the view and want to move it to the top of the list, now you can single click to move, before it was double click. Cool

Advertisements