FileNet to SharePoint – PowerStreamECM

It has been a very busy last few months!  I have built two major products both of which I now get to blog about before Ignite!  I have always been interested in building cool stuff and over the years I have done some pretty awesome things.  One of which was to migrate Oracle Portal to SharePoint for General Atomics here in San Diego.  Since then I have done other migrations, but have not had the exposure to some of the more popular ECM products out in the wild.  That has all changed since the beginning of the year.  Since being at ShareSquared I have got to see two more major ECM products in action:

FileNet was one of the more simple ones to figure out.  I can now use our PowerStreamECM product to migrate your old or new FileNet systems to SharePoint 2013/2016/O365 without any type of translation in-between. Just straight from the source to the target!

If you have a FileNet system that you want migrated, let me know!  We have done this so many times now we have the design, management and implementation of all the pieces down to an art form!

If you are interested in moving your old content to SharePoint, contact me at: chris@sharesquared.com

Chris

  

Installing Service Bus 1.0 and Service Bus 1.1 in Azure VM – Exit code: 15010 – Error 1722 – Installation success or error status: 1603

Have been doing a lot of Azure provisioning lately and ran across an interesting issue with the latest VMs in Azure.  Seems some registry keys are missing which will cause you to run across these errors:

MSI (s) (44:CC) [21:33:14:551]: Note: 1: 1722 2: DoFabricSetup 3: C:Program FilesWindows FabricinFabricFabric.Code.1.0MSIHiddenAppLauncher.exe 4: FabricSetup /operation:install /gac /trace:"C:ProgramDataWindows FabricFabriclog" /fabricDataRoot:"C:ProgramDataWindows Fabric\" /traceBufferSizeInKB:128 /traceFileSizeInMB:128 /fabricPrincipal:"contosos2admin" CustomAction DoFabricSetup returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox)

FabricSetup.EventLog,wevtutil failed to install manifest C:Program FilesWindows FabricinFabricFabric.Code.1.0WF.man. Exit code: 15010 

A partial solution was provided across a couple posts out there, but nothing that comprehensiving fixes it right away:

  • https://blogs.msdn.microsoft.com/distributedservices/2014/12/16/common-appfabric-1-1-installation-errors-with-and-without-sharepoint/ – Talks about various reasons why you might get these errors, none resolved my issue
  • http://sharepoint.stackexchange.com/questions/69320/error-installing-azure-workflow-server-during-2013-install – Talks about a service not being enabled, but in my case it was
  • http://blog.symprogress.com/tag/azure-worker-role/Shows that Channel "0" is missing in another instance
  • https://alasdaircs.wordpress.com/2014/08/15/azure-vm-agent-breaks-your-server– Shows that the Azure VM Agent causes an issue with installing and uninstalling things.  This partially fixes the problem, but was missing the "0" channel.  Adding it with the right values fixes the Service Bus install issue:

Here is the full registry file to get Service Bus 1.0 and Service Bus 1.1 to install in Azure VMs:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences]
"Count"=dword:00000004

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences]
@="Microsoft-WindowsAzure-Diagnostics/GuestAgent"
"Id"=dword:00000010
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences]
@="Microsoft-WindowsAzure-Diagnostics/Diagnostic"
"Id"=dword:00000010
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences1]
@="Microsoft-WindowsAzure-Diagnostics/Runtime"
"Id"=dword:00000011
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences2]
@="Microsoft-WindowsAzure-Diagnostics/Heartbeat"
"Id"=dword:00000012
"Flags"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWINEVTPublishers{9148c98f-152c-44d3-a496-26350c475d74}ChannelReferences3]
@="Microsoft-WindowsAzure-Diagnostics/Bootstrapper"
"Id"=dword:00000013
"Flags"=dword:00000000

Enjoy!
Chris

Videos – K2 vs Nintex – Want to know the real difference between the two? Here ya go!

Now that I have access to just about every 3rd party ISV software for SharePoint (K2, Nintex, VisualSP, ConceptSearch, Ephesoft, KnowledgeLake, etc, etc, etc), I have been able to install and configure all of them. And in most cases, I have automated the install of all of them (more on that in a later blog post after our new site goes live).  Due to this ISV software exposure, I was asked by some individuals to do a K2 vs Nintex comparison video.  Well, it takes more than just one video to really show the differences between the two.  So, here are a set of videos that you can review to see what the real differences are.  This is the list of videos that I will be posting in the next few days:

FYI: If you need Nintex Training or Nintex Subscription pricing, let me know! 

  • Headsup Install ( Videos : K2 vs Nintex)
    • Winner – Nintex
    • Why?
      • Nintex install takes around 10 minutes total for all components
      • Nintex install is simple .NET installer that adds solutions to your farm (and with Nintex Live, two windows services)
      • Nintex doesn't need a license key to install and configure
      • K2 install takes over an hour, and in many cases, up to 3 to get install properly
      • K2 requires a license to install it
      • K2 install has multiple components, each requiring much more time to install than the respective Nintex parts
  • Headsup ConfigurationAdmin UI (Videos – K2 vs Nintex)
    • Winner – Nintex
    • Why?
      • Nintex is SharePoint feature based – simply activate the features – all changes are inherited – no real updating of anything
      • Nintex is integrated into SharePoint Central Administration
      • Nintex has its own category of links, all of which are simple and easy to maneuver around
      • K2 requires you to leave SharePoint to configure anything admin
        related.  You can always put a link to the K2 admin UI in Central Admin,
        but you still have to leave SharePoint to get to it
      • The K2 admin UI is a bit slow and its not very intuitive.
      • K2 utilizes the App Model, this means extra work to deploy the app across web application boundaries (multiple app catalogs), and you have to "add" the app to each web you want to use it on
      • You must also ensure that you can connect to the K2 server for the app to function properly (mean properly setting up the SSL bindings on the K2 server).
      • K2 app updates mean you have to redeploy the app to each web (no easy automation available for this unless you are an old school SharePoint person)
  • Headsup Designer(s) (Videos – K2 vs Nintex)
    • Winner – Tie
      • Nintex has a very simple web based Designer for both workflows and forms.  It is integrated into the browser, no separate applications, all via a rich web client.
      • K2 has many ways to design "processes" aka workflows.  You can do it via the browser, or you can do it via Designer tools like K2 Studio, Visual Studio or a web based designer.
      • K2 is a bit more complex to work with and understand the various UIs versus the simple-ness of Nintex
  • Headsup Site and List Workflow (Videos – K2 vs Nintex)
    • Winner – Tie
    • Why
      • TODO
  • Headsup Actions (Videos – K2 vs Nintex)
    • Winner Nintex
    • Why
      • TODO
  • Headsup Forms (Videos – K2 vs Nintex)
    • Winner Nintex
    • Why?
      • TODO
  • Headsup Extensability (Videos – K2 vs Nintex)
    • Winner – Nintex
    • Why
      • TODO
  • Headsup O365 versions (Videos – K2 vs Nintex)
    • Winner – Nintex
    • Why?
      • Nintex just works.  Period.  Install the O365 Workflow and Forms apps, your up and running with a 30 day trial.  Easy.  After the trial, call your Nintex Partner (ACS of course) and we can get you activated same day.  Easy.
      • K2 takes a very complicated process of working with them to setup a backend tenant tied to your O365 tenant.  You must also be given the AppIt app to install into your app catalog in order to use it (it is not in the SharePoint store).
      • K2 also requires that you continue to use it or the OAuth token will expire and the system won't be able to talk back to your O365 instance.  You'll get a ton of emails notifying you of this until you click the link to refresh it.

Overall, I prefer Nintex over K2.  I'll get flak for that statement (but most of my friends have left K2 for various reasons I'm not at liberty to share at this point so maybe not).  Some will say, but have you seen the extensibliliy and architecture of K2 behind the scenes?  I'll simply say yes, but customers don't care about that.  They want something that is easy to install, easy to get started with and productive out of the box.  Nintex does that perfectly.

Enjoy,
Chris

SP2013 vs SP2016 RTM – Diff at assembly level

Here is the latest diff on the SP2016 vs SP2013 code base.  From here you can explore what were some of the more deeper changes in the code.  Biggest changes:

  • All legacy Office Web Apps dlls are now removed
  • Previously I mentioned that silverlight dlls looked to be removed, they are in fact still around
  • Similarly, all the Ceres Search Flow resource dlls are still around
  • Same as last post – All Education dlls are finally removed
  • Still have dependencies on some 3rd party installed dlls:
    • Reporting Services 10.0+
    • Windows Azure Storage
    • Microsoft.Azure.GraphClient.FirstClient – still have no idea where to get this one
    • NewtonSoft.Json 6.0 – used in Search
    • System.Web.Http 5.2.2.0 – used in Search
    • Microsoft.Data (5.3 and 5.6) – seems some dlls have old 5.3 references that have not been updated
  • ChicagoIntegration is gone from RTM – *LOL* [:D]
  • All new Ceres Push API code now exists:
    • Microsoft.Ceres.ContentEngine.ContentPush
    • Microsoft.Ceres.ContentEngine.Operators.ContentPush
    • Microsoft.Ceres.ContentEngine.Processing.ContentPush
    • Microsoft.ContentPushFlow
    • Microsoft.ContentPushHybridFlow
  • New Ceres Flows (for more information on what flows are – see my other post):
    • Microsoft.ContentPushFlow
    • Microsoft.ContentPushHybridFlow
    • Microsoft.ConversationalLatencyFlow
    • Microsoft.CrawlerPropertyReportingSubFlow
    • Microsoft.CrawlerSecurityInsertHybridSubFlow
    • Microsoft.DataLossPreventionSubFlow
    • Microsoft.DeleteTenantFromIndexSystemFlow
    • Microsoft.DocumentPreviewMetadataFeederFlow
    • Microsoft.ExplorerFlow
    • Microsoft.GraphSearchProviderFlow
    • Microsoft.IndexingSubFlow
    • Microsoft.PeopleSuggestionDictionaryDeploymentFlow
      Microsoft.PropertyRetrievalSearchFlow
      Microsoft.QueryCompletionPeopleOutputFlow
      Microsoft.QueryCompletionPersonalizedQueryLogsOutputFlow
      Microsoft.QueryCompletionPreFetchOutputFlow
      Microsoft.QueryCompletionQueryLogsInputFlow
      Microsoft.QueryCompletionQueryLogsOutputFlow
      Microsoft.QuerySuggestionsQueryLogsFlow
      Microsoft.SearchAnalyticsBuzzFeederFlow
      Microsoft.SearchAnalyticsBuzzImportFlow
      Microsoft.SearchAnalyticsBuzzInputFlow
      Microsoft.SearchAnalyticsBuzzOutputFlow
      Microsoft.SearchAnalyticsExternalContentMapFlow
      Microsoft.SearchAnalyticsExternalContentPushFlow
      Microsoft.SearchAnalyticsFollowsImportFlow
      Microsoft.SearchAnalyticsFollowsInputFlow
      Microsoft.SearchAnalyticsGraphIndexFeederFlow
      Microsoft.SearchAnalyticsInFeedInputFlow
      Microsoft.SearchAnalyticsTagsImportFlow
      Microsoft.SearchAnalyticsTagsInputFlow
    • Microsoft.SignalStoreInputFlow
    • Microsoft.UsageAnalyticsImportFlow
  • OfficeGraph API exists:
    • Microsoft.Ceres.External.ContentApi.GraphExtensions
    • Microsoft.Ceres.SearchCore.GraphModel
    • Microsoft.Ceres.SearchCore.GraphQueryModel
    • Microsoft.Ceres.SearchCore.GraphSeedingModel
    • Microsoft.Ceres.SearchCore.GraphServer.Managed
    • Microsoft.Ceres.SearchCore.GraphStatusModel
    • Microsoft.Ceres.SearchCore.Indexes.GraphServerIndex
  • Microsoft.SharePoint.Client.Directory
    • CSOM for the new UserProfile sync stuff
  • Interesting new dll – Microsoft.Office.BigData.DataLoader.*
    • Have no idea what this is, but it looks interesting…
  • New compliance assemblies:
    • Microsoft.Office.CompliancePolicy.Platform

This supplements the following blog posts:

    Enjoy!
    Chris 

    Introducing codename PowerStream!

    Well, I can't keep stuff under wraps too long.  Sooo, a small little announcement about something I built in the past few months.  A tool code-named called "PowerStream" that will be officially announced with the new ShareSquared site in a few weeks.  This tool allows for the migration from anything (literally) to SharePoint with very little effort.  So far, I have tested the tool with several ECM systems (Documentum, oracle, custom, blah) and everything works perfectly!  In addition this tool integrates with another tool which I can't announce at the moment, but if you do anything around file plans, this will integrate with tools like Gimmal very easily.

    A lot of code came from the design of my Oracle to SharePoint tool that was developed at General Atomics, but this version adds in some of the other code I had from ACS days and some new stuff including:

    • Dynamic property setting
    • Managed Metadata leveling
    • OCR of TIFF and any other image formats
    • TIFF page/file merge
    • TIFF to OCR'd PDF/A
    • Really true awesome redaction capabilities

    Want to move your old redundant no featured ECM to SharePoint (on-premises or O365, yeah its CSOM based!)?  Let me know, I'll do it really quickly!

    Chris

     

    NEW SharePoint 2016 CSOM Rest EndPoints

    Here are the new end points segments and all new class methods and properties in SharePoint 2016:

    New endpoints:

    • /Me
      • /User
      • /Current
    • /GroupSiteManager
      • Create
      • GetSiteStatus
      • Notebook

    Out of the 529 new methods and properties available via CSOM/REST, here are some of the major changes I see:

    • Ability to interface with the new directory features (Microsoft.Office.Server.Directory.SharePoint.Provider.Remote)
    • A SharedWithMeDocument properties on the UserProfiles endpoint
    • TenantAdministration features for DeletedSiteProperties and SiteCreationProperties as well as SiteProperties; Tenant level methods for  (Microsoft.Online.SharePoint.Dedicated.TenantAdministration)
    • IRM properties – Microsoft.SharePoint.SPEffectiveInformationRightsManagementSettings and Microsoft.SharePoint.SPInformationRightsManagementFileSettings
    • Ability to get App Info – Microsoft.SharePoint.SPTenantAppInformation

    New clientcallable classes:

    • Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteDirectoryObjectData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemotePropertyCollectionData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemotePropertyData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteRelationData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteRelationSetData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteResourceData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteSchemaData
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteSharePointDirectoryProvider
      Microsoft.Office.Server.Directory.SharePoint.Provider.RemoteStateData
      Microsoft.Office.Server.Directory.SharePointInterfaceConversation
      Microsoft.Office.Server.Directory.SharePointInterfaceDirectorySession
      Microsoft.Office.Server.Directory.SharePointInterfaceGroup
      Microsoft.Office.Server.Directory.SharePointInterfaceGroupAndUserStatus
      Microsoft.Office.Server.Directory.SharePointInterfaceGroupCollection
      Microsoft.Office.Server.Directory.SharePointInterfaceLinkRequestSchema
      Microsoft.Office.Server.Directory.SharePointInterfaceMembershipResult
      Microsoft.Office.Server.Directory.SharePointInterfaceMembersInfo
      Microsoft.Office.Server.Directory.SharePointInterfaceMyGroupsResult
      Microsoft.Office.Server.Directory.SharePointInterfaceProperty
      Microsoft.Office.Server.Directory.SharePointInterfacePropertyDictionary
      Microsoft.Office.Server.Directory.SharePointInterfaceSPHelper
      Microsoft.Office.Server.Directory.SharePointInterfaceUser
      Microsoft.Office.Server.Directory.SharePointInterfaceUserCollection
      Microsoft.Office.Server.Directory.SharePointInterfaceUserRequestSchema
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationDeletedSiteProperties
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationSiteCreationProperties
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationSiteProperties
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationSpoOperation
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationSPOWebTemplate
      Microsoft.Online.SharePoint.Dedicated.TenantAdministrationTenant
      Microsoft.SharePoint.IdentityModel.OAuth2SPOAuthNativeClientAuthenticationService
      Microsoft.SharePoint.JSGridHierarchyTaskListSPFieldUserValue
      Microsoft.SharePoint.PackagingSPAppDetails
      Microsoft.SharePoint.PackagingSPAppIcon
      Microsoft.SharePoint.Portal.UserProfilesSharedWithGroupViewWorker
      Microsoft.SharePoint.Portal.UserProfilesSharedWithMeDocument
      Microsoft.SharePoint.Portal.UserProfilesSharedWithMeDocumentUser
      Microsoft.SharePoint.Portal.UserProfilesSharedWithPersonViewWorker
      Microsoft.SharePoint.Portal.WebControlsMruDocsData
      Microsoft.SharePoint.PortalGroupSiteInfo
      Microsoft.SharePoint.PortalGroupSiteManager
      Microsoft.SharePoint.PortalSuiteNavData
      Microsoft.SharePoint.SharingSPWebSharingManager
      Microsoft.SharePoint.UtilitiesSPWOPIHostUtility
      Microsoft.SharePoint.UtilitiesSPWOPIProperties
      Microsoft.SharePoint.WebControlsModuleLink
      Microsoft.SharePoint.WebControlsResourceManifestInformation
      Microsoft.SharePoint.WorkflowServicesWorkflowDefinitionCollection
      Microsoft.SharePoint.WorkflowServicesWorkflowSubscriptionCollection
      Microsoft.SharePointCreatableItemInfo
      Microsoft.SharePointCreatablesInfo
      Microsoft.SharePointIngestionTaskKey
      Microsoft.SharePointObjectSharingSettings
      Microsoft.SharePointPickerSettings
      Microsoft.SharePointSharePointSharingSettings
      Microsoft.SharePointSharingLinkInfo
      Microsoft.SharePointSharingPermissionInformation
      Microsoft.SharePointSharingResult
      Microsoft.SharePointSPAppTile
      Microsoft.SharePointSPAudit
      Microsoft.SharePointSPCommonListTile
      Microsoft.SharePointSPDataLeakagePreventionStatusInfo
      Microsoft.SharePointSPDlpPolicyTip
      Microsoft.SharePointSPDocLibTile
      Microsoft.SharePointSPDocumentLibraryInformation
      Microsoft.SharePointSPEffectiveInformationRightsManagementSettings
      Microsoft.SharePointSPFeatureAppTile
      Microsoft.SharePointSPFilePropertyValues
      Microsoft.SharePointSPInformationRightsManagementFileSettings
      Microsoft.SharePointSPInstanceAppTile
      Microsoft.SharePointSPInvitationCreationResult
      Microsoft.SharePointSPListTile
      Microsoft.SharePointSPMigrationJobStatus
      Microsoft.SharePointSPMountedFolderInfo
      Microsoft.SharePointSPMountPointClientApi
      Microsoft.SharePointSPMountPointInfo
      Microsoft.SharePointSPMoveCopyUtil
      Microsoft.SharePointSPRemoteWeb
      Microsoft.SharePointSPRenderListContextMenuDataParameters
      Microsoft.SharePointSPRenderListDataOverrideParameters
      Microsoft.SharePointSPRenderListDataParameters
      Microsoft.SharePointSPRenderListFilterDataParameters
      Microsoft.SharePointSPRequestUserContext
      Microsoft.SharePointSPStorageMetrics
      Microsoft.SharePointSPTenantAppInformation
      Microsoft.SharePointSPTenantAppInstance
      Microsoft.SharePointSPTenantAppTile
      Microsoft.SharePointSPUserResource
      Microsoft.SharePointTenantAppUtility
      Microsoft.SharePointTenantSettings

    The http://sprest.architectingconnectedsystems.com tool will be updated soon with a 2013/2016 mode so you can browse the new 2016 endpoints.

    Enjoy, 
    Chris 

    Getting K2 System Key without using the installers

    Yeah, you know if you have ever done a K2 install, you know what I'm talking about.  Well, the days of waiting to get the system key to request the license is over.  You can run the following script to get your system keys for BlackPearl, BlackPoint and SmartForms:

    $scriptPath = "C: empK2 for SharePoint 4.6.11 (4.13350.1734.1)Installation"
    $scriptPath = "C:TempK2 blackpearl 4.6.11 (4.12060.1731.1)Installation"

    cd $scriptPath

    [System.Reflection.Assembly]::LoadFile("$scriptpathSourceCode.Install.Logging.dll")
    [System.Reflection.Assembly]::LoadFile("$scriptpathSourceCode.Install.Licensing.dll")
    [System.Reflection.Assembly]::LoadFile("$scriptpathLicensingx64SourceCode.HostServerInterfaces.dll")

    [System.Environment]::CurrentDirectory = $scriptPath;
    $installpath = "M:Program Files (x86)K2 blackpearl";

    $license = new-object SourceCode.Install.Licensing.Licensing($installPath + "host serverin");
    "BlackPearl " + $license.MachineKey;

    $license = new-object SourceCode.Install.Licensing.Licensing($installPath);
    "SmartForms " + $license.MachineKey;

    Enjoy!
    Chris 

    Internet Information Service not installed

    Got bit by this on my personal servers in the past week.  A very helpful post pointed me to the issue: 

    SharePoint 2013 CU August 2013 – “Internet Information Services not installed”

    Except…mine was a tad bit different.  The IISADMIN service was completed removed from the WFE!  This was due to a SharePoint Server windows update not completing and failing.  In order to get it back, I simply re-ran the pre-req installer and once the service came back, I was able to load the Central Admin and continue with windows updates.

    Enjoy,
    Chris 

    Welcome to ShareSquared Shannon Bray!

    Yep…Shannon Bray has decided to join ShareSquared!

    Amazingly, it had nothing *directly* of my doing, although a few people would disagree.  It just happened that David K. hit up Shannon like he always does and happened to get a bit more "response" back because of my move a few months ago.  This latest move certainly peaked Shannon's interest as he knows me really well and working for someone has never been something he thought I would do again.  After a couple quick convo's, Shannon had some serious stuff to think about.  Certainly his Planet Technology co-workers are going to miss him, as I deduced from the Facebook and SMS messages [:)]. 

    I have known Shannon longer than I have known David (10+ years).  It all started back in the truely good old MCT days of everyone getting started with SharePoint via my famous (infamous?) 50064 SharePoint 2007 Developer course.  It was a tough course and those that could handle teaching it over a week were certainly complete and total rockstars.  Shannon was one of these people.  As he taught the course and grew over the years, he distinguished himself in many many ways. Husband, Father, Leader, Consultant, Cool Dude, Best Friend…etc etc.

    I'm excited that Shannon has decided to join myself and the ShareSquared team.  It means that he'll be around for my next round of cloud startup's in the next couple of years (yeah, those are still in the works) and I couldn't imagine it any other way!  

    Welcome Shannon, this is going to be a blast my friend!

    Chris