Remove Nintex from Sharepoint 2013

Source:

https://community.nintex.com/servlet/JiveServlet/previewBody/1017-102-4-2295/Uninstalling%20Nintex%20Workflow%202013.pdf


Nintex Workflow 2013
Page | 1 of 2
Uninstalling Nintex Workflow 2013
The following are the steps to be taken for completely uninstalling Nintex Workflow 2013.
Removing the Nintex Workflow 2013 Solutions
1. Disable web level features on all webs that use Nintex Workflow 2013.
2. Disable site collection features on all site collections that use Nintex Workflow 2013.
3. Go to SharePoint Central Administration.
4. In the Nintex Workflow Management section, click the Web Application Activation link.
5. Check the All content web applications option.
6. Click Deactivate.
7. In the Quick Launch menu, click System Settings. In the Farm Management section, click the
Manage farm solutions link.
8. Retract and remove the solutions installed by Nintex Workflow 2013, in the following order:
nintexworkflow2013backwardscompatibility.wsp
nintexworkflow2013enterprisefeatures.wsp
nintexworkflow2013.wsp
nintexworkflow2013core.wsp
To retract and remove each solution, use the following steps.
a) Click the link for the solution and then click Retract solution.
b) Click the link for the solution again and then click Remove solution.
Remove the Nintex Workflow Database
1. Open Microsoft SQL Server Management Studio and delete the associated Nintex Workflow
database(s).
Removing entries from the Web.Config
1. On the server’s file system, navigate to the folder hoting the web application (by default
“C:\inetpub\wwwroot\wss\virtualdirectories\80”).
2. Open web.config with Notepad.
3. Verify there is no reference to “Nintex Workflow”. If there are any, delete them.
4. In the SharePoint 2013 Management Shell, use the following commands to remove the farm
properties added by Nintex Workflow:
$farm = get-spfarm
$farm.properties.remove(“NintexWorkflowServer2013License”)
$farm.properties.remove(“NW2007ConfigurationDatabase”)
$farm.update()
Note: The reference to the NW2007ConfigurationDatabase is correct.
Nintex Workflow 2013
Page | 2 of 2
5. You should also remove the following libraries and lists:
/NintexWorkflows
/Lists/NintexWorkflowHistory
/Workflows/NintexWorkflow
Note: The following are the Nintex Workflow content types that are installed by default:
a. Nintex Biztalk Task
b. Nintex Workflow Multi Outcome Task
c. Nintex Workflow Multi Outcome Task using InfoPath
d. Nintex Workflow Task
e. Nintex Workflow Task using InfoPath
f. Workflow
g. Workflow Snippet
h. Workflow Template

Comments

Post a Comment

Popular posts from this blog

Configure SharePoint Server to use Office Online Server

In a test environment that uses HTTP ======================================================================== Step 1: Create the binding between SharePoint 2016 and Office Web Apps Server New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP Step 2: View the WOPI zones for the SharePoint bindings Get-SPWOPIZone Step 3: Change the WOPI zone to internal-http Set-SPWOPIZone -zone "internal-http" Step 4: Change the AllowOAuthOverHttp setting in SharePoint 2016 to True (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp $config = (Get-SPSecurityTokenServiceConfig) $config.AllowOAuthOverHttp = $true $config.Update() (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp Step 5: Enable the Excel SOAP API $Farm = Get-SPFarm $Farm.Properties.Add("WopiLegacySoapSupport", "<URL>/x/_vti_bin/ExcelServiceInternal.asmx"); $Farm.Update(); Step 6: Verify that Office Web Apps is working In a production environment that uses H...
Read more

PowerShell command to import Module and Get-ADUser

PS C:\Users\adm_shahidul> Get-Module -ListAvailable     Directory: C:\Windows\system32\WindowsPowerShell\v1.0\Modules ModuleType Version    Name                                ExportedCommands ---------- -------    ----                                ---------------- Manifest   2.0.0.0    AppLocker                           {Get-AppLockerFile... Manifest   2.0.0.0    Appx                                {Add-AppxPackage, ... Manifest   1.0        BestPractices                       {Get-BpaModel, Get... Manifest   1.0.0.0   ...
Read more

Configure Office Web Apps for SharePoint 2013

copied from: https://technet.microsoft.com/en-us/library/ff431687.aspx Configure SharePoint 2013 to use Office Web Apps Server Choose one of the following sections depending on whether you want to use HTTP or HTTPS. HTTP is generally recommended only for test environments. In production environments, the more secure HTTPS protocol is the better choice. In a test environment that uses HTTP For this configuration, make sure you have set up Office Web Apps Server by following the steps in  Deploy a single-server Office Web Apps Server farm in a test environment . Be sure to configure the Office Web Apps Server farm to use an internal URL and HTTP. The Video: Configure Office Web Apps for SharePoint 2013  shows how to set up Office Web Apps Server and configure SharePoint 2013 to use Office Web Apps Server in a test environment. Step 1: Open an elevated SharePoint 2013 Management Shell Choose the procedure that corresponds to your server operatin...
Read more