Microsoft cloud engineer - SharePoint, Office 365, Azure, DotNet, Angular, JavaScript.
Microsoft cloud engineer - SharePoint, Office 365, Azure, DotNet, Angular, JavaScript.

Administration

PowerShell – download all files in a Document Library

I needed to download the full contents of a Document Library to a local folder.   Explorer View, SharePoint Designer, and WebDAV simply weren’t fast enough for the large number of items needed.  So I wrote a quick script:

PowerShell – SOM (Server Object Model)

PowerShell – Remote HTTP (Client Side / Office 365)

NOTE – Remote HTTP (Client Side / Office 365) can recurse files from all sub-folders by updating the View to “Show all items (all folders)”

References

PowerShell – Always open default SharePoint site ($profile)

Recently I found myself starting each PowerShell window with the same predictable first command (Get-SPSite http://myportalurl).   Knowing that PowerShell supports a start up script ($profile) I thought it may be possible to automate this and save a few seconds each time I need to open a console.   Below is the source code with screenshots.   Hopefully this helps somebody else to save time also.

image
image
image

Configuring Workflow Manager 1.0 on SharePoint 2013 (screenshots)

During my first attempt to enable Workflow Manager 1.0 on a local VM I ran into the following error:

—> System.InvalidOperationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

The steps I took to resolve were:

  1. Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Remove from Farm     (not to be confused with SharePoint “farm”)
  2. Drop SQL databases for Workflow Manager.   (SbGatewayDatabase, SbManagementDB, SBMessageContainer01, WFInstanceManagementDB, WFManagementDB, WFResourceManagementDB)
  3. Start \ Programs \ Workflow Manager 1.0 \ Workflow Manager Configuration \ Configure Workflow Manager with Default Settings (Recommended)
  4. Two things I did differently on the next pass: 
    1. I used the SQL alias “SPSQL” instead of the FQDN machine names.   I’m using that for SharePoint and prefer SQL aliases for management flexibility.
    2. I formatted the user name as “DEMO\SPFARM” instead of “SPFARM@DEMO” (default text value).   That seems to make more sense for AD login credentials and I didn’t understand why the default was more of an email syntax.
    3. I commented out all of the HOSTS file entries.  While this may not be related, I wanted to simplify the connections as much as possible.   I had “127.0.0.1” entries for the local machine to ensure connectivity even as a change VM host network settings, but removed while running the WF configuration wizard.
  5. Ran the wizard just like before and it completed successfully this time.

 

Now I can continue the steps outlined at http://technet.microsoft.com/en-us/library/jj658588(v=office.15) and run the PowerShell cmdlet Register-SPWorkflowService

 

image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image
image

 

 

=========================================================================

Configuration for Workflow Manager
Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Management Database Name    WFManagementDB
Instance Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Instance Management Database Name    WFInstanceManagementDB
Resource Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Resource Management Database Name    WFResourceManagementDB
RunAs Account    spfarm@DEMO
RunAs Password    ***********
Certificate Generation Key    ***********
Workflow Manager Outbound Signing Certificate    Auto-generated
Service SSL Certificate    Auto-generated
Encryption Certificate    Auto-generated
Workflow Manager Management Port    12290
HTTP Port    Disabled
Enable firewall rules on this computer    True
Administrators Group    BUILTIN\Administrators
Configuration for Service Bus
Management Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Management Database Name    SbManagementDB
Gateway Database SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Gateway Database Name    SbGatewayDatabase
Message Container SQL Instance    SP15.demo.com
Enable SSL connection with SQL Server instance    False
Authentication    Windows Authentication
Message Container Database Name    SBMessageContainer01
RunAs Account    spfarm@DEMO
RunAs Password    ***********
Certificate Generation Key    ***********
Farm Certificate    Auto-generated
Encryption Certificate    Auto-generated
HTTPS Port    9355
TCP Port    9354
Message Broker Port    9356
Internal Communication Port Range    9000 – 9004
Enable firewall rules on this computer    True
Administrators Group    BUILTIN\Administrators

 

=========================================================================

=========================================================================

Configuration operation partially succeeded.  Use ‘Join an Existing farm’ to complete the configuration.

[Error] [3/27/2013 9:53:08 AM]: System.Management.Automation.CmdletInvocationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

—> System.InvalidOperationException: Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

 

   at Microsoft.ServiceBus.Commands.Common.ProcessHelper.RunCommandInProcess(String exeName, String arguments, String errorString)
   at Microsoft.ServiceBus.Commands.AddSBHost.ProcessRecordImplementation()
   at Microsoft.ServiceBus.Commands.ServiceBusBaseCmdlet.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   — End of inner exception stack trace —
   at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
   at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddSBNode(FarmCreationModel model, Boolean isFirstCommand)

=========================================================================

Starting
Validating input and configuration parameters.
Installing auto-generated certificate.
Granting ‘Log on as Service’ privilege to the run as account.
Windows Fabric configuration started.
Running Windows Fabric deployment.
Program C:\Program Files\Windows Fabric\bin\Fabric\Fabric.Code.1.0\FabricDeployer.exe exited with error: Windows Fabric deployment failed.DeploymentValidator: warning: The Fabric Data Collection Agent is disabled for this deployment.
None of the declared nodes is for the current machine.

WPI Offline Install – Workflow Manager 1.0 for SharePoint 2013

Earlier today I was trying to load Workflow Manager 1.0 to get the new “2013” flavor workflows running on my VM.   The Microsoft download links are tiny files which launch WPI (Web Platform Installer).   That’s fine for a hobby machine or one time install, but I need an offline install for real data centers.   Why?   Two reasons:   they often block internet access for security and I want to install via script (do many machines faster).

 

I watched Web Platform Installer download and install the various components I wondered where it was keeping all those nice download files.   Not %TEMP% and not C:\WINDOWS\TEMP\.  The obvious locations yielded nothing so I launched SysInternals PROCMON.EXE and watched open file handles for the install window  (click the target icon to select any active window).  That helped me find the right location and now I can copy those MSI files directly for offline installs.

If you need any Web Platform Installer items to run offline, just watch this folder while running on 1 PC and then you can copy to others.

 

C:\Users\spfarm\AppData\Local\Microsoft\Web Platform Installer\installers\

 

image
image

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲