Honored Contributor.. Brett Danalake Honored Contributor..
Honored Contributor..
330 views

Registering the TRIMSDK.dll via SCCM deployment

We are testing upgrading to Content Manager 9.3 Patch 1. We are using Kapish Easy Link which now requires us to run a command to register teh TRIMSDK.dll to validate the licence stored in CM.

REGSVR32 /S "C:\Program Files (x86)\Micro Focus\Content Manager\trimsdk.dll"

This command can be run from a command prompt with elevated priviliges with no problem. However, we will be rolling Content Manager and Easylink out using bat files via SCCM. Including the registration command in a bat file via SCCM does not appear to be successful.

Is there something different that needs to be done if registering the dll via SCCM? ALso, is there a way to confirm whether the dll has successfuly registered?

0 Likes
3 Replies
Super Contributor.. davros29 Super Contributor..
Super Contributor..

Re: Registering the TRIMSDK.dll via SCCM deployment

Hi, Brett. 

1. I don't *think* there's any difference when rolling it out via SCCM. 

2. We've used this snippet of PowerShell to test if it's registered or not. Just running it manually, but you should be able to adjust it to run with SCCM, I guess? Can't find the code tag so this is going to look messy...

Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss")`tINFO`tChecking if TRIMSDK is registered."

try {
$trim = New-Object -ComObject TRIMSDK.Database
Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss")`tINFO`tTRIMSDK is registered." -ForegroundColor Green
}
catch {
Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss")`tERROR`tTRIMSDK is NOT REGISTERED." -ForegroundColor Red
if ([Environment]::Is64BitProcess) {
Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss")`tWARN`tTesting from a 64-bit instance of PowerShell. This may have caused this test to fail." -ForegroundColor Black -BackgroundColor Yellow
Write-Host "$(Get-Date -Format "yyyy-MM-dd HH:mm:ss")`tWARN`tRun test again from a 32-bit instance of PowerShell if this was unintentional." -ForegroundColor Black -BackgroundColor Yellow
}
}

Highlighted
Honored Contributor.. Brett Danalake Honored Contributor..
Honored Contributor..

Re: Registering the TRIMSDK.dll via SCCM deployment

Thanks for this. It has helped us identify if the registration was successful. Now just have to work out why it will work manually but not via SCCM.
Honored Contributor.. Brett Danalake Honored Contributor..
Honored Contributor..

Re: Registering the TRIMSDK.dll via SCCM deployment

Hi, Forgot to update this for the curious. We found the issue was in the way our SCCM deployment was written. It had a command to look for a file that wasn't there until after the deployment was run. Once that was removed it all worked successfully.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.