Downloads

Disclaimer: As stated in our Terms of Use, Nintex is not responsible for any third-party content made available for download on Nintex Connect, whether or not this content has been reviewed and/or moderated by Nintex and regardless of who originated that content (including, but not limited to, Nintex employees, partners, affiliates, or moderators). Users shall assume all risks associated with applications and other content provided on Nintex Connect. Nintex does not provide support for any content and plugins provided for download at communities.nintex.com.

Great tool. But for enterprise use it's better to break general purpose PoSh activities into reusable but laser focused activities that cannot harm by inadvertently overburdening the infrastructure or outright doing bad things.

Considering the way the action works, I feel like the threat of that happening is low (the target executing machine must have WinRM enabled and the user specified must also be a local admin or be configured with least permissions to execute PS via WinRM.)

The only current pitfall I see with this action and system load is that it is a blocking action and is subject to the same batch timeouts as other sequential workflow activities. I do have this on the road map to be addressed however.

The game plan is to have a service (Windows or SharePoint) that actually performs the work so that the action can fire it up asynchronously and check up on the status of the PS session via a token system.

I welcome your thoughts opinions on that approach as it is still in development!

I can see this coming in very handy in a number of SP admin and overall infrastructure scenarios. Gosh how I hated doing all of that heavy lifting with AutoIT and other assorted scripts back in the day.

Good job on this, I got it installed properly.Your custom action workflow for PowerShell command works fine but has soon as I try to load the Add-PSSnapin "Microsoft.SharePoint.PowerShell" and run a SharePointShell command I recieve an error :

Are you running Server 2008 or 2008R2? The authentication type currently used by the action is Basic which works pretty much out of the box with Server 2012. The issue you are seeing is indeed a double hop authentication issue. I am currently looking at adding an option to change the authentication type from basic to CredSSP or Kerberos.

I do have a separate build of the action that supports CredSSP exclusively that you could use. I will upload a build to Codeplex and mark it CredSSP.

Unfortunately I cannot share the password for the key as it is there to uniquely identify myself as the developer/compiler. That said, it is just a self signed cert. Feel free to compile/sign with another certificate. If you wish to branch/fork the action feel free to do that as well.

Well, I can't change your mind, but that prevents you from received free help from the community who could be enhancing your initiative. You are and should always be identified as the person who started it, but if you want the community to give you the best input you should allow anyone compiling the solution.

By not providing it there is a need to change the strong name, which should be also followed by renaming the Action.

That is fine, I will fork it out and allow anyone compiling/improving it.

This is probably ignorance on my part again, but my workflow does not execute the script. I shared out the folder containing the script, and I can execute it from a powershell window on another server. I have the UNC path in the PowerShell Script box, and I have the servername with domain in the Server Name field. (servername.subdomain.domain.ext) I don't see anything in the ULS logs with the script name referenced. The wf, which has only the single step of the PowerShell action, completes without error. Any help greatly appreciated.

No worries at all! Do you see anything in the ULS logs at all that reference the NTX action? The correlation should step through each step of the action. You may need to flip on verbose momentarily to catch some of the messages.

Additionally, do you see anything in the event logs of the server that is executing the action (it could be any server running the workflow infrastructure service).

Legacy Workflow Infrastructure 00000 Unexpected Error Data: System.Management.Automation.Remoting.PSRemotingTransportException:Connecting to remote server servername.subd.dom.ext failed with the followingerror message : The client cannot connect to the destination specified in therequest. Verify that the service on the destination is running and is acceptingrequests. Consult the logs and documentation for the WS-Management servicerunning on the destination, most commonly IIS or WinRM. If the destination isthe WinRM service, run the following command on the destination to analyze andconfigure the WinRM service: "winrm quickconfig". For moreinformation, see the about_Remote_Troubleshooting Help topic. atSystem.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResultasyncResult) at System.Managemen... 5414bdb2-702c-48d1-bdc0-529f725cbc75

That would be the cause. You need to ensure that the machine you are connecting to has WinRM configured. To help isolate the issue a bit more (WinRM or NTXPS) you can check out this documentation: NTX - Documentation

Hi Adam Tobias, I tested it today with the last stable release, which I still had from Codeplex, on a freshly installed SharePoint 2016 on a Windows Server 2016 with Nintex 2016 installed and it worked like a charm.

Only thing I needed to do manually was the edit in the web.config and I needed to use a FQDN in the action itself, where you enter the computername. On my 2013 environment it was ok with computername only.

I enabled CredSSP only on my Web Frontendserver with role Server and Client for himself.

Hi Victor,we have deployed the wsp in the WFE and app server of SP 2016 but not able to see the option in the central admin powershell.could you please help us to how to deploy and get the executive power shell action in Sharepoint 2016

what exactly are you expecting in Central Admin? As soon as you deployed the .wsp it only shows the action inside your Workflow Designer and in Nintex Workflow Administration you will have a new action under "Manage allowed actions"... Hope this helps, if not please explain your problem further.

0
Kudos

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.