Skip to content
This repository was archived by the owner on Dec 27, 2017. It is now read-only.

Commit fb1b0cc

Browse files
committed
fix link for overview.md.
1 parent 23dd23d commit fb1b0cc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

sharepoint/docs-conceptual/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Before you can use the Add-SPShellAdmin cmdlet to grant permissions for users to
3030

3131
**NOTE:** If these permissions are not satisfied, contact your Setup administrator or SQL Server administrator to request these permissions.
3232

33-
For additional information about PowerShell permissions, see [Add-SPShellAdmin](../../sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md).
33+
For additional information about PowerShell permissions, see [Add-SPShellAdmin](../sharepoint-ps/sharepoint-server/Add-SPShellAdmin.md).
3434

3535
If you do not have membership in the **SharePoint_Shell_Access** role or **WSS_Admin_WPG** local group, use the **Add-SPShellAdmin** cmdlet to add the **WSS_Admin_WPG** group in all front-end web servers in the SharePoint farm and the **SharePoint_Shell_Access** role. If the SQL Server database does not have a **SharePoint_Shell_Access** role, the role is automatically created when you run the **Add-SPShellAdmin** cmdlet. After you run the **Add-SPShellAdmin** cmdlet, users can run SharePoint PowerShell cmdlets in a multiple-server farm environment.
3636

0 commit comments

Comments
 (0)