Skip to content
Merged
Show file tree
Hide file tree
Changes from 71 commits
Commits
Show all changes
84 commits
Select commit Hold shift + click to select a range
58714f6
Update Get-SPProjectEventServiceSettings.md
Apr 22, 2018
95824ec
Update Get-SPProjectEnterpriseProjectTaskSync.md
Apr 22, 2018
d133a48
Update Get-SPProjectDatabaseUsage.md
Apr 22, 2018
8a03f7c
Update Get-SPProjectIsEmailNotificationEnabled.md
Apr 22, 2018
f1d79eb
Update Get-SPSecureStoreApplication.md
Apr 22, 2018
1fee064
Update Get-SPService.md
Apr 22, 2018
347d8f8
Update Get-SPServiceApplication.md
Apr 22, 2018
4b68b98
Update Get-SPServiceInstance.md
Apr 22, 2018
18b2904
Update Get-SPSite.md
Apr 22, 2018
60a4e45
Update Get-SPSiteMapDatabase.md
Apr 22, 2018
87f8ec0
Update Get-SPSiteMaster.md
Apr 22, 2018
862489e
Update Get-SPUserSolutionAllowList.md
Apr 22, 2018
13e4b85
Update Get-SPWebApplicationAppDomain.md
Apr 22, 2018
00d395b
Update Get-SPWorkflowServiceApplicationProxy.md
Apr 22, 2018
7659356
Update Get-SPWebTemplatesEnabledForSiteMaster.md
Apr 22, 2018
d9803ff
Update Remove-SPAppPrincipalPermission.md
Apr 22, 2018
c5dbeba
Update Remove-SPCentralAdministration.md
Apr 22, 2018
bb7d408
Update Remove-SPClaimTypeMapping.md
Apr 22, 2018
b474cab
Update Remove-SPContentDatabase.md
Apr 22, 2018
03ca508
Update Remove-SPEnterpriseSearchComponent.md
Apr 22, 2018
2a576b7
Update Remove-SPEnterpriseSearchContentEnrichmentConfiguration.md
Apr 22, 2018
edff3b0
Update Remove-SPEnterpriseSearchCrawlContentSource.md
Apr 22, 2018
6ae22a7
Update Get-SPAccessServicesDatabaseServerGroup.md
Apr 22, 2018
2703a2f
Update Restore-SPODeletedSite.md
fselkirk Apr 26, 2018
9f2ee5b
Metadata Update as per VSO:BUG 2283348
v-srteeg Apr 27, 2018
55ec41d
Metadata Update as per VSO:BUG 2283348
v-srteeg Apr 27, 2018
871b390
Update Get-OfficeWebAppsExcelBIServer.md
andikrueger Apr 27, 2018
742da9f
Update Remove-SPOUserProfile.md
expiscornovus Apr 30, 2018
cdd93ce
Update mfa-connect-to-exchange-online-powershell.md
chrisda May 1, 2018
335bd04
Added loc metadata.
kenwith May 1, 2018
6a40001
fixed typo for ExcludeFromOrgHolds parameter name
markjjo May 1, 2018
f254308
- Split SYNTAX entries for Get-Whiteboard. Added short descriptions f…
TommyBrosman May 2, 2018
d573ee4
Adds more detail.
kenwith May 2, 2018
b1daaed
Update Export-QuarantineMessage.md
chrisda May 2, 2018
33e2bf8
Update Get-QuarantineMessage.md
chrisda May 2, 2018
6111c42
Update Release-QuarantineMessage.md
chrisda May 2, 2018
37a896d
Update Preview-QuarantineMessage.md
chrisda May 2, 2018
22bfd03
Merge branch 'master' into whiteboard-ps-minor-fixes
TommyBrosman May 2, 2018
150bba7
Minor fix to match schema.
TommyBrosman May 2, 2018
83140b6
Merge pull request #959 from tbrosman/whiteboard-ps-minor-fixes
kenwith May 2, 2018
228d764
Update New-SPConfigurationDatabase.md
FaganSC May 2, 2018
6b0f642
Merge pull request #960 from FaganSC/patch-1
Techwriter40 May 2, 2018
c81be45
Update Search-Mailbox.md
chrisda May 2, 2018
41c47da
Merge pull request #855 from tseward/patch-489
Techwriter40 May 2, 2018
3ebf6f3
Merge pull request #854 from tseward/patch-488
Techwriter40 May 2, 2018
53cc52d
Merge pull request #853 from tseward/patch-487
Techwriter40 May 2, 2018
48a8407
Merge pull request #852 from tseward/patch-486
Techwriter40 May 2, 2018
2218003
Merge pull request #843 from tseward/patch-477
Techwriter40 May 2, 2018
8688bd8
Merge pull request #844 from tseward/patch-478
Techwriter40 May 2, 2018
f42ede7
Merge pull request #845 from tseward/patch-479
Techwriter40 May 2, 2018
631abb5
Merge pull request #846 from tseward/patch-480
Techwriter40 May 2, 2018
dddda69
Merge pull request #847 from tseward/patch-481
Techwriter40 May 2, 2018
488698a
Merge pull request #848 from tseward/patch-482
Techwriter40 May 2, 2018
deaff88
Merge pull request #849 from tseward/patch-483
Techwriter40 May 2, 2018
c7240d4
Merge pull request #850 from tseward/patch-484
Techwriter40 May 2, 2018
afd941a
Merge pull request #851 from tseward/patch-485
Techwriter40 May 2, 2018
c166c36
Merge pull request #834 from tseward/patch-467
Techwriter40 May 2, 2018
df8fbe3
Merge pull request #835 from tseward/patch-468
Techwriter40 May 2, 2018
c1271b3
Merge pull request #836 from tseward/patch-469
Techwriter40 May 2, 2018
edb068e
Merge pull request #837 from tseward/patch-471
Techwriter40 May 2, 2018
b54b2c9
Merge pull request #838 from tseward/patch-472
Techwriter40 May 2, 2018
eb5b522
Merge pull request #839 from tseward/patch-473
Techwriter40 May 2, 2018
fc60517
Merge pull request #840 from tseward/patch-474
Techwriter40 May 2, 2018
46b743b
Merge pull request #841 from tseward/patch-475
Techwriter40 May 2, 2018
7a2b0be
Merge pull request #842 from tseward/patch-476
Techwriter40 May 2, 2018
67f58d8
Adds new cmdlets for TeamsUpgrade.
kenwith May 2, 2018
9e88ebd
Merge branch 'master' of github.com:MicrosoftDocs/office-docs-powershell
kenwith May 2, 2018
2b4e82f
Merge pull request #934 from fselkirk/patch-2
VesaJuvonen May 3, 2018
3032d4d
Merge pull request #947 from expiscornovus/patch-1
VesaJuvonen May 3, 2018
f5f15ce
Update Get-CsTeamsUpgradePolicy.md
bjwhalen May 3, 2018
78d2a8a
Merge pull request #963 from bjwhalen/patch-1
kenwith May 3, 2018
9cfccde
Merge remote-tracking branch 'upstream/master'
markjjo May 3, 2018
8af9a07
added new CaseType parameter
markjjo May 3, 2018
5fb0ea7
Merge pull request #955 from markjjo/master
chrisda May 3, 2018
bd16716
Merge branch 'master' into patch-2
kenwith May 4, 2018
2e56f1a
Merge branch 'master' into patch-1
kenwith May 4, 2018
fb80faa
Merge pull request #939 from andikrueger/patch-1
kenwith May 4, 2018
e40af51
Merge pull request #937 from v-srteeg/patch-2
kenwith May 4, 2018
e237a08
Merge pull request #936 from v-srteeg/patch-1
kenwith May 4, 2018
c5faaf6
Merge pull request #897 from tseward/patch-531
Techwriter40 May 4, 2018
a71cd81
Fixing Typo
nsshommo May 5, 2018
30ccef1
Update meeting room instructions
islubin May 7, 2018
f846597
Merge pull request #973 from islubin/master
kenwith May 7, 2018
f21316a
Merge pull request #968 from nsshommo/nasim
kenwith May 7, 2018
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,14 @@ If you want to use multi-factor authentication (MFA) to connect to Exchange Onli
4. In the verification window that opens, enter the verification code, and then click **Sign in**.

![Enter your verification code in the Exchange Online Remote PowerShell window](../../media/d3a405ce-5364-4732-a7bb-2cc9c678da2d.png)


> [!NOTE]
> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Exchange Online Remote PowerShell Module window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect all currently open PowerShell sessions in the current window, run the following command:

```
Get-PSSession | Remove-PSSession
```

## How do you know this worked?

After Step 4, the Exchange Online cmdlets are imported into your Exchange Online Remote PowerShell Module session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange Online cmdlet, for example, **Get-Mailbox**, and see the results.
Expand All @@ -105,5 +112,3 @@ If you receive errors, check the following requirements:
- The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../disable-access-to-exchange-online-powershell.md).

- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.


Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,9 @@ monikerRange: "exchonline-ps || eop-ps"
## SYNOPSIS
This cmdlet is available only in the cloud-based service.

Use the Export-QuarantineMessage cmdlet to export quarantined messages from your cloud-based organization to .eml message files. You can then open the .eml files in Outlook.
Use the Export-QuarantineMessage cmdlet to export quarantined messages and files from your cloud-based organization. Messages are exported to .eml message files so you can open them in Outlook.

For files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, the files are exported in Base64 format.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

Expand Down Expand Up @@ -43,6 +45,13 @@ Notes:

- You need to use the Out-File cmdlet to write the .eml message file with the required encoding. If you use the default PowerShell redirection operator ">" to write the output file, the default encoding is Unicode, which might not match the actual message encoding.

### -------------------------- Example 2 --------------------------
```
$e = Export-QuarantineMessage -Identity 9c6bb3e8-db9e-4823-9759-08d594179bd3\7fec89fe-41b0-ae67-4887-5bede017d111; $bytes = [Convert]::FromBase64String($e.eml); [IO.File]::WriteAllBytes("C:\My Documents\Export1.txt", $bytes)
```

This example exports the quarantined file with the specified Identity value. The first command exports the file to a Base 64 string. The next two commands convert the string to byte format and write it to the output file.

## PARAMETERS

### -Identity
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,9 @@ monikerRange: "exchonline-ps || eop-ps"
## SYNOPSIS
This cmdlet is available only in the cloud-based service.

Use the Get-QuarantineMessage cmdlet to view quarantined messages in your cloud-based organization.
Use the Get-QuarantineMessage cmdlet to view quarantined messages and files in your cloud-based organization.

**Not**: Quarantined files are files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

Expand Down Expand Up @@ -62,6 +64,15 @@ This example returns the quarantined message with the Message-ID value \<5c695d7
Get-QuarantineMessage -Identity c14401cf-aa9a-465b-cfd5-08d0f0ca37c5\4c2ca98e-94ea-db3a-7eb8-3b63657d4db7 | Format-List
```

This example returns detailed information for the quarantined message with the specified Identity value.

### -------------------------- Example 5 --------------------------
```
Get-QuarantineMessage -QuarantineTypes SPOMalware | Format-List
```

This example returns detailed information for the files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams.

## PARAMETERS

### -Identity
Expand Down Expand Up @@ -216,12 +227,16 @@ The QuarantineTypes parameter filters the results by what caused the message to

- Spam

- SPOMalware

- TransportRule

You can specify multiple values separated by commas.

You don't need to use this parameter with the Type parameter.

For files protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, the detection information can be found in CustomData field in the output.

```yaml
Type: QuarantineMessageTypeEnum[]
Parameter Sets: Set1
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ This cmdlet is available only in the cloud-based service.

Use the Preview-QuarantineMessage cmdlet to preview the contents of quarantined messages in your cloud-based organization.

**Note**: This cmdlet isn't available for files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business, and Microsoft Teams.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

## SYNTAX
Expand Down
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@


---
external help file: Microsoft.Exchange.ServerStatus-Help.xml
applicable: Exchange Online, Exchange Online Protection
Expand All @@ -13,6 +15,8 @@ This cmdlet is available only in the cloud-based service.

Use the Release-QuarantineMessage cmdlet to release messages from quarantine in your cloud-based organization. You can release messages to all original recipients, or to specific recipients.

For files that are protected by Office 365 Advanced Threat Protection in SharePoint Online, OneDrive for Business and Microsoft Teams, you can unblock the files in the respective team sites and document libraries by using the Release-QuarantineMessage cmdlet so users can access, share, and download the files.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

## SYNTAX
Expand Down Expand Up @@ -133,6 +137,8 @@ Accept wildcard characters: False
### -ReleaseToAll
The ReleaseToAll switch releases the quarantined message to all original recipients. You don't have to specify a value with this switch.

This parameter is required for the quarantine type SPOMalware.

If you previously used the User parameter or the ReleaseToAll switch to release the quarantined message to some or all of the original recipients, those recipients are skipped when you use the ReleaseToAll parameter again. You don't have to specify a value with the ReleaseToAll switch.

You can't use the ReleaseToAll switch and the User parameter in the same command.
Expand Down
2 changes: 0 additions & 2 deletions exchange/exchange-ps/exchange/mailboxes/Search-Mailbox.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,6 @@ You can use the Search-Mailbox cmdlet to search messages in a specified mailbox

- Delete messages from the source mailbox. You have to be assigned the Mailbox Import Export management role to delete messages.

- Copy messages from the source mailbox and delete them from the target mailbox.

- Perform single item recovery to recover items from a user's Recoverable Items folder.

- Clean up the Recoverable Items folder for a mailbox when it has reached the Recoverable Items hard quota.
Expand Down
2 changes: 1 addition & 1 deletion exchange/exchange-ps/exchange/mailboxes/Set-Mailbox.md
Original file line number Diff line number Diff line change
Expand Up @@ -1663,7 +1663,7 @@ Accept wildcard characters: False
### -ExcludeFromOrgHolds
This parameter is available only in Exchange Online.

The ExcludeFromHolds parameter excludes the mailbox from one or more organization-wide Office 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Office 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Office 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'.
The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Office 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Office 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Office 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'.

You can specify multiple values for this parameter by using the syntax “GUID1”,”GUID2”,…”GUIDX”.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,14 @@ monikerRange: "o365scc-ps"
## SYNOPSIS
This cmdlet is available only in the Office 365 Security & Compliance Center. For more information, see Office 365 Security & Compliance Center PowerShell (https://technet.microsoft.com/library/mt587091.aspx).

Use the Get-ComplianceCase cmdlet to view eDiscovery cases in the Security & Compliance Center. You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization.
Use the Get-ComplianceCase cmdlet to view eDiscovery cases and DSR (data subject request) cases in the Security & Compliance Center. You use eDiscovery cases to control who can create, access, and manage compliance searches in your organization.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

## SYNTAX

```
Get-ComplianceCase [[-Identity] <ComplianceCaseIdParameter>] [-DomainController <Fqdn>] [-RoleGroup <String>]
Get-ComplianceCase [-Identity] <ComplianceCaseIdParameter>] [-CaseType <eDiscovery | DSR>] [-DomainController <Fqdn>] [-RoleGroup <String>]
[<CommonParameters>]
```

Expand All @@ -43,6 +43,25 @@ This example returns detailed information for the eDiscovery case named Contoso

## PARAMETERS

### -CaseType
The CaseType parameter specifies the type of eDiscovery case that you want to view. Valid values are:

- eDiscovery: eDiscovery cases are used to manage legal or other types of investigations. In the Security & Compliance Center, eDiscovery cases are displayed under Search & investigation \> eDiscovery. This is the default value.

- DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Security & Compliance Center, DSR cases are displayed under Data privacy \> DSR cases.

```yaml
Type: eDiscovery | DSR
Parameter Sets: (All)
Aliases:
Applicable: Office 365 Security & Compliance Center
Required: False
Position: Named
Default value: eDiscovery
Accept pipeline input: False
Accept wildcard characters: False
```

### -DomainController
This parameter is reserved for internal Microsoft use.

Expand Down
25 changes: 20 additions & 5 deletions repo_docs/NEW_CMDLETS.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,31 @@
# Generate Your Own Markdown
**SECTION IN PROGRESS**

Use PlatyPS to generate Markdown. See, https://github.com/PowerShell/platyPS.
1. Open PowerShell as Administrator.
2. Import the module you want to document.
- Skype for Business Online: https://technet.microsoft.com/en-us/library/dn362795(v=ocs.15).aspx
- Microsoft Teams: https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/
Hint: Might need to use Upgrade-Module and also Uninstall-Module depending on version and if you already have a version installed.
3. Use PlatyPS to generate Markdown.
- Skype for Business Online: `New-MarkdownHelp -module tmp_byivwzpq.e1k -OutputFolder .\docs`.
4. Find the new cmdlet and you will see the stubbed markdown.
5. Add correct metadata, see other similar cmdlets for examples.
6. Add the correct Applicable tags to the top metadata and also the parameters for the cmdlet. See others for details.
This is important since when the XML is generated to go back into the product the applicable is what is used for which content goes into which product.
7. Add the cmdlet to TOC. TOC file is the name of the module.
For example, for all Skype cmdlets the TOC file is skype.md.
8. Submit a Pull Request into the repo in appropriate place with adding the new cmdlet. aka.ms/office-powershell

Install PlatyPS.

Get to where you can run Get-Help and see cmdlets.

Generate help with PlatyPS.

If you want to merge multiple versions into a single version then use the PlatyPS merge command.

Make sure to update the TOC file. Exact format required so that the template text doesn't show up.

Add metadata to the file so it shows in the correct reports. See these scripts to do it or you can do it manually too.


References:
https://docs.microsoft.com/en-us/powershell/module/powershellget/install-module?view=powershell-6
https://docs.microsoft.com/en-us/powershell/module/powershellget/update-module?view=powershell-6
https://github.com/PowerShell/platyPS
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@ Remove-SPOUserProfile -LoginName <String> [<CommonParameters>]
## DESCRIPTION
Can be used to remove the SharePoint user profile from the tenant.

> [!NOTE]
> The User must be first be deleted from AAD before the user profile can be deleted. You can use the Azure AD cmdlet Remove-AzureADUser for this action

## EXAMPLES

### ------------ Example 1 --------------------
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ For permissions and the most current information about Windows PowerShell for Sh
```
Restore-SPODeletedSite -Identity https://contoso.sharepoint.com/sites/arecycledsite
```
This example restores a SharePoint Online deleted site collection named HYPERLINK "https://contoso.sharepoint.com/sites/arecycledsite" https://contoso.sharepoint.com/sites/arecycledsite from the Recycle Bin.
This example restores a SharePoint Online deleted site collection named "https://contoso.sharepoint.com/sites/arecycledsite" from the Recycle Bin.


## PARAMETERS
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ schema: 2.0.0
# Get-SPProjectDatabaseUsage

## SYNOPSIS
{{Fill in the Synopsis}}
Returns an approximate size, in megabytes (MB) of the Project Web App data used in the content database.

## SYNTAX

Expand All @@ -17,21 +17,23 @@ Get-SPProjectDatabaseUsage [-AssignmentCollection <SPAssignmentCollection>] -Url
```

## DESCRIPTION
{{Fill in the Description}}
Returns an approximate size, in megabytes (MB) of the Project Web App data used in the content database.

## EXAMPLES

### Example 1
```
PS C:\> {{ Add example code here }}
PS C:\>Get-SPProjectDatabaseUsage -Url http://contoso.com/sites/pwa
```

{{ Add example description here }}
This example shows the size of the Project Web App data in the content data for the Project Web App site at http://contoso.com/sites/pwa.

## PARAMETERS

### -AssignmentCollection
{{Fill AssignmentCollection Description}}
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.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

```yaml
Type: SPAssignmentCollection
Expand All @@ -47,7 +49,7 @@ Accept wildcard characters: False
```

### -Url
{{Fill Url Description}}
The URL of the Project Web App site collection.

```yaml
Type: Uri
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ schema: 2.0.0
# Get-SPProjectEnterpriseProjectTaskSync

## SYNOPSIS
{{Fill in the Synopsis}}
Returns whether the task list sync between Project Web App and project sites is enabled or disabled. This cmdlet returns a value only if the feature has previously been enabled or disabled.

## SYNTAX

Expand All @@ -18,21 +18,23 @@ Get-SPProjectEnterpriseProjectTaskSync [-AssignmentCollection <SPAssignmentColle
```

## DESCRIPTION
{{Fill in the Description}}
Returns whether the task list sync between Project Web App and project sites is enabled or disabled. This cmdlet returns a value only if the feature has previously been enabled or disabled.

## EXAMPLES

### Example 1
```
PS C:\> {{ Add example code here }}
PS C:\>Get-SPProjectEnterpriseProjectTaskSync -Url http://contoso/sites/PWA
```

{{ Add example description here }}
This example shows the syntax for getting the task sync status for the Project Web App site at http://contoso/sites/PWA.

## PARAMETERS

### -AssignmentCollection
{{Fill AssignmentCollection Description}}
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.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

```yaml
Type: SPAssignmentCollection
Expand All @@ -48,7 +50,7 @@ Accept wildcard characters: False
```

### -Url
{{Fill Url Description}}
The URL of the PWA site.

```yaml
Type: Uri
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ schema: 2.0.0
# Get-SPProjectEventServiceSettings

## SYNOPSIS
{{Fill in the Synopsis}}
Returns the settings for the Microsoft Project Server Events Service. There is currently only one setting which is the port that the service listens on for requests.

## SYNTAX

Expand All @@ -17,21 +17,23 @@ Get-SPProjectEventServiceSettings [-AssignmentCollection <SPAssignmentCollection
```

## DESCRIPTION
{{Fill in the Description}}
Returns the settings for the Microsoft Project Server Events Service. There is currently only one setting which is the port that the service listens on for requests.

## EXAMPLES

### Example 1
```
PS C:\> {{ Add example code here }}
PS C:\>Get-SPProjectEventServiceSettings
```

{{ Add example description here }}
This example shows what port the service is listening on.

## PARAMETERS

### -AssignmentCollection
{{Fill AssignmentCollection Description}}
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.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

```yaml
Type: SPAssignmentCollection
Expand Down
Loading