Tag Archives: MMC

K2 blackpearl Installation: Configuring MSDTC properties

Disclaimer: in case you have no difficulties to say how to access Local DTC properties on Windows machine without googling or trying hard to remember it then you don’t need to read this post. ūüôā

I was building retro test environment with K2 4.6.2 installed and run into the following warning raised by K2 Setup Manager – “MSDTC Network Access options not set correctly”:

MSDTC Network Access 1 Warning

K2 Setup Manager quite explicitly tells you about what you have to do, detailing up to the level of exact check-boxes you have to have checked. Unfortunately 4.6.2 can’t repair this without your intervention (I assume recent versions too, bun need to double check this). But anyhow it is not difficult to guess that correct settings supposed to look like that:

MSDTC Network Access 2 Correct Settings

Once required check-boxes in place this warning resolved, just click “Analyze” after you have done these changes:

MSDTC Network Access 3 Warning Cleared

Looks straightforward enough, but what may be a question/issue here is that how to access these “Local DTC properties”? (maybe there is an answer in help hyperlink mentioned by Setup Manage in the same warning?)

Anyhow without looking/googling I keep forgetting how to access this dialog, so decided to jot this down. You have to run the Component Services MMC snap-in:

MSDTC Network Access 4 Component Services MSC

In this MMC snap-in you just locate “Local DTC” and select its properties from context menu. And to invoke this you just run this:




In case location matters for you it is located under: %SystemRoot%\System32

Windows Server 2008 administrative consoles shortcuts

I’ve posted similar list some time ago but it doesn’t include all Windows Server 2008 shortcuts (e.g. – Share And Storage Management and many others), so this list covers Server 2008 consoles (*.msc).\n

Command Line

Console Name

AdRmsAdmin.msc    Active Directory Rights Management Services
Adsiedit.msc    ADSI Edit
Azman.msc Authorization Manager
Certmgr.msc Certmgr (Certificates)
Certtmpl.msc Certificates Template Console
CluAdmin.msc Failover Cluster Management
Comexp.msc Component Services
Compmgmt.msc Computer Management
Devmgmt.msc Device Manager
Dfsmgmt.msc DFS Management
Dhcpmgmt.msc DHCP Manager
Diskmgmt.msc Disk Management
Dnsmgmt.msc DNS Manager
Domain.msc Active Directory Domains And Trusts
Dsa.msc Active Directory Users And Computers
Dssite.msc Active Directory Sites And Services
Eventvwr.msc Event Viewer
Fsmgmt.msc Shared Folders
Fsrm.msc File Server Resource Manager
Fxsadmin.msc Microsoft Fax Service Manager
Gpedit.msc Local Group Policy Editor
Lusrmgr.msc Local Users And Groups
Napclcfg.msc NAP Client Configuration
Nfsmgmt.msc Services For Network File System
Nps.msc Network Policy Server
Ocsp.msc Online Responder
Perfmon.msc Reliability And Performance Monitor
Pkiview.msc Enterprise PKI
Printmanagement.msc Print Management
Remoteprograms.msc TS RemoteApp Management
Rsop.msc Resultant Set of Policy
Secpol.msc Local Security Policy
ServerManager.msc Server Manager
StorageMgmt.msc Share And Storage Management
Services.msc Services
StorExpl.msc Storage Explorer
Tapimgmt.msc Telephony
Taskschd.msc Task Scheduler
Tmp.msc Trusted Platform Module (TPM) Management
Tsadmin.msc Terminal Services Management
Tsconfig.msc Terminal Services Configuration
Tsgateway.msc TS Gateway Manager
Tsmmc.msc Remote Desktops
Uddi.msc UDDI Services Console
Wbadmin.msc Windows Server Backup
Wdsmgmt.msc Windows Deployment Services
Winsmgmt.msc WINS Manager
WmiMgmt.msc WMI Control

Some thoughts on MMC in general & SCCM2007 console in particular

The MMC is technology which dates back to the point at which nobody thought about scale and sheer amount of objects like we have in products like SCCM 2007, and consequently it works really poor and limit this product manageability. Yes we shall admit that at the time of its introduction MMC was major step forward in unification of the way we perform administrative tasks, but this technology simply has reached the limits of its own capacity in terms of numbers of objects which needs to be managed in modern IT environments. Finally enough SCCM 2012 bring about total overhaul of SCCM management console and it is no longer based on MMC Рhooray!

But many firms will stick to SCCM 2007 as corporate environments quite unwilling to break their well tested approach of having 1-2 year gap when it comes to new¬†big¬†product adoption – and this is perfectly justifiable from economical stand point (it used to be so, and to some extent still relevant). Expertise around the product is built, potential problems are well known and support & implementation workforce widely available and cheaper than¬†it¬†used to be¬†during early adoption time – no one would argue with that. On the flip side – drawbacks in missed opportunities for your IT department to better serve your business and gain efficiencies – these are things which¬†are¬†notoriously difficult to measure in financial terms, and you may clearly¬†see the logic behind “follow the leader strategy”.

Many times I saw SCCM admins struggling with¬†“improved granular security / rights delegation” of SCCM 2007 – when they were trying to give somebody some limited rights but intended person didn’t not see the¬†objects to which they seemingly have all proper access rights granted. The thing is that quite often SCCM console could be a culprit here¬†and you need to restart it or perform console view clean up (see screenshot below) in cases if you don’t see things which you should be able to see there.

SCCM Console View Clean Up

The other day while working with SCCM 2007 console I for some reason was unable to see software packages created by me immediately after their creation and aforementioned measured didn’t help me too, even the multiple restarts ūüôā It was remove/reinstall of SCCM console which solved¬†this issue for me. So keep this in mind when you working with SCCM 2007 console.