Friday, September 25, 2015

Find files with same content using powershell

Today I needed to find files with identical content within a folder. Inspired by a few examples out there I came up with this (will Work from ps 4.0):

Get-ChildItem|where { ! $_.PSIsContainer }|
Get-FileHash|Group-Object Hash|where{$_.Count -gt 1}|
foreach{write-host "-----------------------------------------------";$_.Group.Path}

Once again, the power of powershell proved itself, as I managed to get it right in less that 10 minutes

For reference:


Monday, August 3, 2015

BizTalk group SCOM discovery not working

The BizTalk group SCOM discovery will not work until a stopped first server is removed from the group unless you do the following the Computer Name property override for the discovery.

Go the SCOM Authoring pane, search for the object discovery called BizTalk Group Discovery and override this for a specific object of the BizTalk run-time role (select one of the running servers). 

Now, what exactly do you have to write as Override Value:

To be sure, execute the following SQL query against the BizTalk management database of the group:

select * from adm_Server srv with (NoLock) order by srv.Id asc

From the Name column of query result copy the exact server name (casing and all) matching the BizTalk Run-Time Role object for which you chose to override the discovery. 

Friday, May 8, 2015

Microsoft.BizTalk.ExplorerOM.PermissionException: Error in the application after upgrade to BizTalk Server 2013 R2

After upgrading to BizTalk Server 2013 R2 certain (service) accounts get this exception:

Microsoft.BizTalk.ExplorerOM.PermissionException: Error in the application

Running the BizTalk Server Administration Console using the same account you'll get this similar error:

Failed to load Group […BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)

Connecting to ExplorerOM failed. (Microsoft.BizTalk.SnapIn.Framework)

Error in the application. (Microsoft.BizTalk.ExplorerOM)

We saw the exact same problem back in 2013 when we installed BizTalk Server 2013. I've described a fix for the issue in this post: