Archive for June 30, 2011

Upgrade of Nintex Workflow 2010 from V2.0.0.5 to V2.2

Author : Adriaan Steyn

Nintex has released a new version of Workflow 2010, version 2.2 at the end of May 2011.

*To complete the upgrade from the previous version of Nintex, ensure that you still have a valid license; otherwise this upgrade will not be possible.

Navigate to “Add/Remove Programs” on the server hosting Nintex Workflow 2010 and remove it.

(This will not affect the programs functionality in SharePoint 2010)

Do not retract the solutions from the Solutions Management, as this will disrupt users that are currently using the product.

Once this has been done, run the new installation “setup.msi” for Nintex. When it prompts to add the solutions, select “Yes”. This will attempt to automatically upgrade the WSP’s that are currently installed on your solution.

Once the installation has been completed, it will show the solutions page, with the status of “Deploying (timestamp of when this was initialized)”

This is where I ran into an issue, although everything in the supplied upgrade document stated that this will show up as deployed after a while, it was not the case.

After about 25minutes, the 2 solution files were still showing as deploying, with the same timestamp as when the software installation finish. I cancelled both “deployments”, both these files now showed as deployed, but with no Last Operation Time in either.

How to fix this?

Reset IIS, Start -> Run -> iisreset

This will release any threads that are holding onto the WSP files.

Make sure that the SharePoint 2010 Administration service is running, Start -> Run -> services.msc

You will now need to manually upgrade the solutions files.

Start the SharePoint 2010 Management Shell as an Administrator.

 Update-SPSolution –Identity nintexworkflow2010.wsp –LiteralPath “nintexworkflow2010.wsp” –GacDeployment 
 Update-SPSolution –Identity nintexworkflow2010enterprisefeatures.wsp –LiteralPath “nintexworkflow2010enterprisefeatures.wsp” –GacDeployment 

This will deploy your solutions correctly and add the needed DLL’s to the Global Assembly Cache.

You will now be able to access Nintex Workflow 2010 V2.2 from Central Administration.

Post to Twitter

SharePoint 2010 security token expiration date

In SharePoint 2010 when one uses Forms based authentication or NTLM and the popup box for credentials has a “Sign me in automatically” or “Remember my credentials” and one checks the tick box available you would think this would now log you on for the rest of time. However by default SharePoint 2010 security token expires on the client side machine after 24 hours.

To increase the security token expiration date on SharePoint 2010 one needs to run the following command from SharePoint PowerShell


$sts = Get-SPSecurityTokenServiceConfig
$sts.WindowsTokenLifetime = (New-TimeSpan -Day 365)
$sts.FormsTokenLifetime = (New-TimeSpan -Day 365)
$sts.Update()
Iisreset

Note that this will change the token to expire of 365 days for both Forms and NTLM.

Post to Twitter