Install SSL trusted root Intermediate certificate

Install SSL certificate trusted root certificate Intermediate certificate is required on sharepoint servers which is provided by Certification Authority. SSL is a security protocol that establishes a secure connection by providing encrypted connection between server and client, typically between server and client browser. So, its mandatory to install ssl certificate in servers. Normally we create .pem file for SSL certificate. PEM file with full form “Privacy-enhanced Electronic Mail” is nothing but a file format, act as certificate container files. It stores cryptographic data, like “Keys” and “Digital Certificates“. Follow the step by step below to Install SSL certificate trusted root certificate Intermediate certificate on sharepoint web servers.

Advertisements
  1. Generate CSR file
  2. Create .pem file for SSL certificate
  3. Install Certificate on Web Server from which CSR file is created
  4. Install Certificate on Web Server from which CSR file is not created
    • Export certificate from server where CSR files is created and installed
    • Install PFX file certificate
  5. Install Internal Certificates
    • Install Global Root CA
    • Install Intermediate Certificates RapidSSL RSA CA
Advertisements

Generate CSR file

Before requesting certificate, first generate csr file for ssl certificate from web server. Follow the step by step procedure below for CSR file (Certificate Signing Request file) generation.

  • Log in to one of the WFE server.
  • Open IIS Manager.
  • Click on the server name present under Connections from left navigation.
  • Click on “Server Certificates” present in “Center Pane” under IIS in “Feature view“.
  • Double click on “Server Certificates“.
  • Click on “Create Certificate Request” from right pane.
  • You will get a dialogue box “Request Certificate” wizard to fill “Distinguished Name Properties” like Common name, Organization, Organizational Unit, City/locality, State, Country/Region.
Advertisements
Common namefully qualified domain name (FQDN)
Organizationcompany registered legal name
Organizational unitDepartment name in organization like “IT”, “Web Security” etc.
City/localitycompany location legally
State/province
Country/region
Common name: SharePoint2019.spmcse.com
Organization: SPMCSE
Organizational unit: IT
City:
State:
Country/region: US
Advertisements
  • Click on “Next” once filled all details.
  • You will get next window “Cryptographic Service Provider Properties“.
  • Select the option “Microsoft RSA SChannel Cryptographic Provider” from drop down option “Cryptographic service provider“.
  • Select “Bit length” as “2048” from drop down and click on “Next“.
Cryptographic Service Provider PropertiesMicrosoft RSA SChannel Cryptographic Provider
Bit length2048
Advertisements
  • Next window “File Name” will appear.
  • Under “Specify a file name for the certificate request“, choose “saved location for your CSR file ex. C:\certs\CsrFile.txt“. Default saved location is “C:\Windows\System32“.
  • Click on “Finish” once saved location of the CSR file is selected.
  • Create csr file for ssl certificate process completed.
  • Open CSR file with notepad. You will see information in CSR starts with “BEGIN NEW CERTIFICATE REQUEST” and at the end you will notice “END NEW CERTIFICATE REQUEST“. This is the format of CSR file created.
Advertisements

Create .pem file for SSL certificate

Next process is to request SSL trusted certificate from third party digital certificate authority provider. We will create .pem file for SSL certificate.

  • Login to any third party certificate authority site that provides digital certificate. Let me share one third party certificate authority provider “https://www.venafi.com“.
  • Under “Policy” from left navigation, expand “Certificate Under Management“.
  • Expand “External Facing Certificate“.
  • Expand “Enrollment Management Type“. You will find your server folder (Ex. SPMCSE) under that. Right click on “SPMCSE“.
  • Navigate to Add -> Certificate -> Certificate.
  • Fill details like “Certificate Name” and “Description” under the tab “General Information“.
Advertisements
  • Under the tab “CSR Handling“, select “CSR Generation” option as “User Provided CSR“. Below that there is a option “Upload CSR“. Click on “Upload CSR“.
  • Click on “Browse“, select the CSR files generated and saved as discussed in previous steps and click on “Upload“. Click on “OK“.
  • From next window under the tab “Subject Alt Name“, click on “Add/Remove“.
  • Select “SAN Type” as “DNS“.
  • Enter extra URL in “SAN Value (SharePoint2019.spmcse.com, MySite.spmcse.com)“.
  • Click on “Add“. URLs under “SAN Value” will be moved to “SAN“. Click on “Done“.
Advertisements
  • From next tab “Symantec MPKI Owner“, Enter manager information like “First Name“, “Last Name“, “Email“.
  • Click on “Save“.
  • From top navigation click on “Settings” and then click on “Renew Now“. Click on “Yes“.
Advertisements
  • Once security team approves the request, certificate is created and ready to be downloaded.
  • Log in to the CA provider. From “Settings” present at the top navigation, click on “Download“, choose certificate.
  • From pop up window “Download Certificate“, select the checkbox “Include Root Chain“.
  • Select “Chain Order” as “End-entity first“. “Format” as “Base64 (PKCS#8)“. Click on “Download“.
Advertisements

Install Certificate on Web Server from which CSR file is created

Now we need to install certificate on web server. Web server includes the server from which CSR file got generated and other servers from which CSR file is not generated. First we will discuss about how to install certificate on server from which CSR file is generated.

  • Log in to one of the WFE server.
  • Open IIS Manager.
  • Click on the server name present under Connections from left navigation.
  • Click on “Server Certificates” present in “Center Pane” under IIS in “Feature view“.
  • Double click on “Server Certificates“.
  • Click on “Complete Certificate Request” from right pane.
  • You will get a dialogue box “Complete Certificate Request” wizard. Browse and select the certificate (.pem file) from the field “File name containing the certificate authority’s response“.
  • Populate next field “Friendly name” as “SharePoint2019.spmcse.com“.
  • From next field “Select a certificate store for the new certificate“, choose “Personal” from drop down. Click “OK“.
  • Now you can see the certificate under “Server Certificates” in “Features View“. This indicates that certificate is successfully installed.
Advertisements

Install Certificate on Web Server from which CSR file is not created

Installation of certificate on servers from which CSR file is not generated is a 2 step process as below.

  1. Export certificate from server where CSR files is created and installed.
  2. Install PFX file certificate.
Advertisements

Export certificate from server where CSR files is created and installed

  • Open the server from which SSL trusted digital certificate from certificate authority is generated.
  • From keyword shortcut keys, type “WINKEY+R” to open “run” window.
  • Type “mmc” and press “Enter“.
  • Navigate to “Console Root -> Certificates (Local Computer) -> Personal -> Certificates“.
  • You will find the installed certificate (SharePoint2019.spmcse.com) under it.
  • Select the certificate, right click on it.
  • Click on “All Tasks” and then select “Export“.
  • You will get the window “Certificate Export Wizard“. Click on “Next“.
  • From the next windows select the radio button “Yes, export the private key” and click on “Next“.
  • From next window, select the radio button “Personal Information Exchange – PKCS #12 (.PFX)“. Under that, make sure the check boxes related to options “Include all certificates in the certification path if possible” and “Export all extended properties” are selected. Click on “Next“.
  • From next window, select the checkbox “Password” and insert “New Password“. Click on “Next“.
  • FInally you will get the window “Completing the Certificate Export Wizard” with all selected settings. Click on “Finish“. You will get pop up like “The export was successful“. Click on “OK“.
Advertisements

Install PFX file certificate

  • Copy the exported certificate (.PFX) file to other servers where you need install this certificate.
  • Navigate to the .PFX file and right click on it.
  • Select on “Install PFX“.
  • You will get the window “Certification Import Wizard“.
  • Select the ration button option “Local Machine” present under “Store Location“. Click on “Next“.
  • From next window, browse to the stored location of .PFX file and select the certificate. Click on “Next“.
  • From next window, enter the same password that was set while exporting the certificate in previous steps.
  • Make sure the checkbox “Include all extended properties” selected present under “Import Options“. Click on “Next“.
  • From next window, browse “Place all certificate in the following store” as “Personal“. Click on “Next”.
  • From next window “Completing the Certificate Import Wizard“, you will see all selected options. Click on “Finish“.
Advertisements

Install Internal Certificates

Next process on Install SSL trusted root Intermediate certificate is to install internal certificates like “Global Root CA” and “RapidSSL RSA CA” in all servers that are using SSL certificate.

Install Global Root CA

  • Copy the folder “Global Root and intermediate CA – RapidSSL (internal certs)” to the server in which needs to be installed.
  • Open the folder, you will see 2 security certificates like “Global Root CA” and “RapidSSL RSA CA“.
  • Select and right click on the security certificate “Global Root CA“, click on “Install Certificate“.
  • You will get the window “Certification Import Wizard“.
  • Select the ration button option “Local Machine” present under “Store Location“. Click on “Next“.
  • From next window, browse to the stored location as “Trusted Root Certification Authorities“, click “OK” and move to “Next“.
  • From next window “Completing the Certificate Import Wizard“, you will see all selected options. Click on “Finish“. Finally click on “OK” from pop up window.
Advertisements

Install Intermediate Certificates RapidSSL RSA CA

  • Similarly select and right click on the security certificate “RapidSSL RSA CA“, click on “Install Certificate“.
  • You will get the window “Certification Import Wizard“.
  • Select the ration button option “Local Machine” present under “Store Location“. Click on “Next“.
  • From next window, browse to the stored location as “Intermediate Certification Authorities“, click “OK” and move to “Next“.
  • From next window “Completing the Certificate Import Wizard“, you will see all selected options. Click on “Finish“. Finally click on “OK” from pop up window. Rapidssl certificate installation completed.
  • Finally do an “IISRESET“.
Advertisements
Advertisements

Delete SharePoint site subsite permanently

Delete SharePoint site subsite on premise environment is a common task for administrator. You might be thinking how to permanently delete a SharePoint site collection in production server. There are difference scenarios, you might face while trying to delete a site SharePoint. After sharepoint site migration, we need to delete old site, exactly where its helpful, as per current situation.

Advertisements

Permanently delete a subsite in SharePoint from site settings

You can follow UI method for sharepoint subsite deletion following step by step procedure below.

  • Navigate to sharepoint subsite.
  • Open site settings.
  • Click on Delete this site present under Site Actions.
Delete SharePoint subsite from site settings
Advertisements
  • Click on Delete option present at bottom right.
  • Pop up will appear for confirmation.
  • Click on OK to delete.
delete this site in site settings
Advertisements

Permanently delete a site in SharePoint from site settings

Follow the same procedure to delete site collection as well. Navigate to site collection settings and click on delete this site. After that click on delete and OK to apply the change.

Same steps are also applicable to delete sharepoint online site in office 365.

Advertisements

Delete a Site Collection from Central Admin

You can follow another way to delete site collection from central admin without navigating to site settings.

  • Navigate to central admin
  • Click on Application Management.
  • Click on Delete a site collection present under option Site Collections.
delete a site collection in sharepoint from central admin
Advertisements
  • Select site collection from any one web application, from the drop down, that you want to delete and click on Delete.
  • Click on OK for confirmation to apply changes.
delete site collection
Advertisements

Delete SharePoint site collection powershell

Follow Remove-SPSite, the powershell command to delete site collection in SharePoint.

Remove-SPSite -Identity "<Site Collection Url>" -GradualDelete -Confirm:$False
Remove-SPSite -Identity "http://win-q2repghf9du:44179/sites/SharePointTech" -GradualDelete -Confirm:$False
Remove-SPSite
Advertisements

Delete SharePoint subsite powershell

If you need to delete SharePoint subsite using powershell command, follow Remove-SPWeb.

Remove-SPWeb -Identity "<Subsite Url>"
Remove-SPWeb -Identity "http://win-q2repghf9du:44179/sites/SharePointTechnicalSupport/Subsite1/"
Remove-SPWeb
Advertisements

Delete all site collections present under web application

If you want to delete all site collections present under one web application, follow the command below.

$WebApplicationURL="http://win-q2repghf9du:24072/"
Get-SPWebApplication $WebApplicationURL | Get-SPSite -Limit ALL | Remove-SPSite -Confirm:$false
Delete all site collections present under web application
Advertisements

Delete all site collections present under specific managed path

Specific requirement might come when user need to delete all site collections part of one specific sharepoint managed path, in a web application, using powershell.

Get-SPSite "<web application url>/<managed path>*" -Limit ALL | Remove-SPSite -Confirm:$false
Get-SPSite "http://win-q2repghf9du:27315/sites*" -Limit ALL | Remove-SPSite -Confirm:$false
Delete all site collections present under specific managed path
Advertisements
Advertisements

Similar Article

Advertisements

Nintex feature id in SharePoint

Nintex feature id error messages in SharePoint related to nintex workflow features, you may face. Similar to SharePoint feature id, you need the nintex feature id to get understand the error more.

Nintex FeatureNintex Feature ID
NintexFormsAdminWeb70f4f7da-4fb4-4e30-ba1a-a733efb2e1ac
NintexFormsFarmada0910e-a663-4db4-a19c-d8a097317b87
NintexFormsListSite202afc3c-7384-4700-978d-6da3d3cce192
NintexFormsLiveSite23fce797-ac15-4451-b8da-cf8ac6de6912
NintexFormsSitePrerequisites716f0ee9-e2b0-41f0-a73c-47ed73f135de
NintexFormsWebApplication0cdf436f-61b0-43d2-b250-4360f0353b63
NintexFormsWorkflowSiteac8addc7-7252-4136-8dcb-9887a277ae2c
NintexLiveAdminLinks29e9a673-31a4-46a3-b0d2-d8e1db1dbd92
NintexWorkflow0561d315-d5db-4736-929e-26da142812c5
NintexWorkflowAdminf7937973-0cf9-4f2d-a549-be2d3c25b772
NintexWorkflowClaimsMigration4db97f4c-e643-4b1b-9f6a-43a9d817e6a2
NintexWorkflowContentTypeUpgrade86c83d16-605d-41b4-bfdd-c75947899ac7
NintexWorkflowEnterpriseAdminaa61ef91-ee2b-42d5-9911-7c6557ad90c2
NintexWorkflowEnterpriseWeb2fb9d5df-2fb5-403d-b155-535c256be1dc
NintexWorkflowEnterpriseWebParts53164b55-e60f-4bed-b582-a87da32b92f1
NintexWorkflowInfoPath80bf3218-7353-11df-af9f-058bdfd72085
NintexWorkflowLiveAdminWeb485f5158-4b8a-453f-9eeb-7b33f5112adf
NintexWorkflowLiveSite54668547-c03f-4bb5-aaab-d9568ebaf9c9
NintexWorkflowWeb9bf7bf98-5660-498a-9399-bc656a61ed5d
NintexWorkflowWebPartseb657559-be37-4b91-a369-1c201183c779
Advertisements

Nintex Content Types ID

Below are the ID of nintex content types. Like nintex feature id, nintex content types id are import for resolving any issue in SharePoint.

Nintex Content TypeContent Type ID
Nintex Biztalk Task0x010801005CC0A86910A24687A76ECAC954D3E3F3
Nintex Workflow Multi Outcome Task0x0108010064E42B14ADA442C78E98D686760A8493
Nintex Workflow Multi Outcome Task using InfoPath0x0108010064E42B14ADA442C78E98D686760A8493006EBD0FA4731041D9804386A7FEA568DC
Nintex Workflow Multi Outcome Task using Nintex Forms0x0108010064E42B14ADA442C78E98D686760A8493000568DBB766D0491684897A230753AAF9
Nintex Workflow Task0x0108010079DBDE612F7B46928C6A2516BA2CAE37
Nintex Workflow Task using InfoPath0x0108010079DBDE612F7B46928C6A2516BA2CAE3700E0B65C5281234030AA8CA4D8F8910E72
Nintex Workflow Task using Nintex Forms0x0108010079DBDE612F7B46928C6A2516BA2CAE3700D4A837248A47E040ABD1A569613E898B
Workflow0x01010024055591300C45C3B4C2854A24EF05CE
Workflow Snippet0x010100F815D979DC2B4F48A9DBCA64AED3C636
Workflow Template0x010100F8376F5313D041EF85718B229F4FBFA8
Advertisements

Nintex Fields Site Columns ID

Below are the ID of nintex fields.

Nintex Fields Internal NameIDGroup
NFLiveAuthorce8c2faf-1a10-4e3a-be01-8b2e954f2d62Nintex
NFLiveEditor8866de2b-711d-4c36-812f-68c2fb9593e5Nintex
ApproverComments819e6cf2-36c3-4013-8aef-c99712c26036Nintex Workflow
AssociatedContentType4a07d815-9c92-4b43-a527-29c3b76a65bfNintex Workflow
NintexWorkflowDescriptiond97c0a58-77fd-48cf-8a7a-9ffdfdd11a6eNintex Workflow
TemplateCategory6abeaa08-87c5-4385-9c81-39cbb72f99a6Nintex Workflow
TemplateLcid837c2b97-e338-446d-a993-c96fd0c4b5d7Nintex Workflow
WorkflowCategoryd0d7bbf9-95cb-4661-b7a0-9bec8e968c3eNintex Workflow
WorkflowPartDescription607ec2f6-48eb-4a14-9e1e-bc48043e157eNintex Workflow
WorkflowPartID7f3814a0-6ef1-4856-bf1d-1a06f8437dc4Nintex Workflow
ApprovalOutcome6765859b-8902-469f-a8b6-faa121304602NintexHidden
ApproverTaskID9cf1474e-c190-4d8d-ad6e-e26cbcbd587bNintexHidden
AssociatedListIDca9e1feb-0014-46b0-87c8-08fb9e2fe003NintexHidden
DatabaseID1e39a08d-5f96-494b-ad5a-9096a323b1daNintexHidden
Decisiona7ae99d0-e5df-47f4-9d75-560e3f608006NintexHidden
HumanWorkflowIDcaba3010-7526-43c2-b05f-786037b1dcdfNintexHidden
MultiOutcomeTaskInfof9c2546c-f40b-46d5-8bac-9ab11cc7d640NintexHidden
NintexWorkflowIDbb2af572-4d2c-4780-9bb9-a7cd8106e874NintexHidden
NWAssociatedWebID1d5afadd-d013-4d88-b3b2-38b570da9b6fNintexHidden
WaitingMessageIdcaca9759-3b72-4bf1-8927-7e101337ecf1NintexHidden
Xsdcb2eae1e-cab5-44dc-a9dc-84641eb2ada6NintexHidden
MessageDatabe604058-3251-4088-aad6-e702c4ff1905NintexHidden
Advertisements
Advertisements