If you are looking to move off of Documentum to SharePoint, let me know! PowerStreamECM supports migrating off of Documentum and to SharePoint 2013/2016/O365!
Chris
chris@sharesquared.com
If you are looking to move off of Documentum to SharePoint, let me know! PowerStreamECM supports migrating off of Documentum and to SharePoint 2013/2016/O365!
Chris
chris@sharesquared.com
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
If you are looking to move off of Questys to SharePoint, let me know! PowerStreamECM supports migrating off of Questys and to SharePoint 2013/2016/O365!
Chris
chris@sharesquared.com
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:
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