{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json","elmType": "a",
"txtContent": "=@currentField",
"attributes": {
"target": "_blank",
"href": "=@currentField"
}
}
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",SharePoint PowerShell Commands
Note: -
|
As per my knowledge the below SharePoint PowerShell commands will work below SharePoint Versions.
1. SharePoint 2010. 2. SharePoint 2013. 3. SharePoint 2016. 4. SharePoint 2019.
I don’t have any knowledge on SharePoint Server Subscription, hence not able to comment on the new version. |
|
Title |
SharePoint PowerShell Command Example |
Command Type |
|
Add-SPSolution |
Add-SPSolution "Path\Test.wsp" |
WSP |
|
Install-SPSolution |
Install-SPSolution -Identity Test.wsp -WebApplication http://SP2019Dev:100/ -GACDeployment -Force |
WSP |
|
Uninstall-SPSolution |
Uninstall-SPSolution -Identity Test.wsp –WebApplication http://SP2019Dev:100/ |
WSP |
|
Remove-SPSolution |
Remove-SPSolution -Identity Test.wsp |
WSP |
|
Backup-SPSite |
Backup-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak |
Backup a Site Collection |
|
Restore-SPSite |
Restore-SPSite https://server_name/sites/site_name -Path C:\Backup\site_name.bak |
Restore a Site Collection |
|
Import-SPWeb |
Import-SPWeb https://site -Path export.cmp -UpdateVersions Overwrite |
Backup a Particular SharePoint Site/Subsite |
|
Export-SPWeb |
Export-SPWeb https://site -Path "C:\Temp\export.cmp" |
Restore a Particular SharePoint Site/Subsite |
Add-SPSolution: -
The Add-SPSolution cmdlet adds a SharePoint solution package to the farm. This cmdlet does not deploy the uploaded SharePoint solution.
Install-SPSolution: -
The Install-SPSolution cmdlet deploys an installed SharePoint solution in the farm.
Uninstall-SPSolution: -
The Uninstall-SPSolution cmdlet retracts a deployed SharePoint solution in preparation for removing it from the farm entirely.
Remove-SPSolution: -
The Remove-SPSolution cmdlet deletes a SharePoint solution from a farm.
Please follow below steps to resolve this issue.
1.
Create a New Computer Account (Not Domain User).
a.
Example: - SQLUser
2.
Add it to your Administrators group.
3.
Now Shift + right click on SQL server setup.
4.
Run it as different user.
5.
Provide credentials of newly created account.
Now
the issue will get resolved and the SQL Server Setup will run without any
issue.
Protocol
|
Port
|
Usage
|
Comment
|
| TCP | 80 | http | Client to SharePoint web server traffic (SharePoint – Office Online Server/Office Web Apps communication) |
| TCP | 443 | https/ssl | Encrypted client to SharePoint web server traffic (Encrypted SharePoint – Office Online Server/Office Web Apps communication) |
| TCP | 1433 | SQL Server default communication port. | May be configured to use custom port for increased security |
| UDP | 1434 | SQL Server default port used to establish connection | May be configured to use custom port for increased security |
| TCP | 445 | SQL Server using named pipes | When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP port 445 |
| TCP | 25 | SMTP for e-mail integration | Cannot in 2016 be configured (Use SMTP ports other than the default (25).) |
| TCP | 16500-16519 | Ports used by the search index component | Intra-farm only Inbound rule Added to Windows firewall by SharePoint. (GPO may override this change) |
| TCP | 22233-22236 | Ports required for the AppFabric Caching Service | Used by the Distributed Cache… |
| TCP | 808 | Search – Query processing component Windows Communication Foundation communication |
Search – Query processing component (WCF) |
| TCP | 32843 | Communication between Web servers and service applications | http (default) To use custom port, see references section Inbound rule Added to Windows firewall by SharePoint |
| TCP | 32844 | Communication between Web servers and service applications | https Inbound rule Added to Windows firewall by SharePoint |
| TCP | 32845 | net.tcp binding: TCP 32845 (only if a third party has implemented this option for a service application) | Custom Service Applications Inbound rule Added to Windows firewall by SharePoint |
| TCP | 32846 | Microsoft SharePoint Foundation User Code Service (for sandbox solutions) | Inbound on all Web Servers Inbound rule Added to Windows firewall by SharePoint Outbound on all Web and App servers with service enabled. |
| TCP | 636 | User Profile Synchronization Service/Active Directory Import | Synchronizing profiles between SharePoint 2016 and AD using SLDAP (Secure LDAP) |
| TCP | 5725 | User Profile Synchronization Service | Synchronizing profiles between SharePoint 2016 and Active Directory Domain Services (AD DS) |
| TCP + UDP | 389 | User Profile Synchronization Service | LDAP Service |
| TCP + UDP | 88 | User Profile Synchronization Service | Kerberos |
| TCP + UDP | 53 | User Profile Synchronization Service | DNS |
| UDP | 464 | User Profile Service | Kerberos change password |
| TCP | 809 | Office Online Server/Office Web Apps | Office Online Server/Office Web Apps intra-farm communication. |