Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Iain
    Senior Moderator

    We would like to update you with further information about this issue. This has proven to be a very challenging problem for us to reproduce, and extensive testing has taken place against a  range of deployment configurations of MyID including split application, web and database tiers, web tiers in DMZ configurations and different combinations/permutations of Distributed Component Object Model (DCOM) configuration both with and without ‘DCOM hardening’ (KB500442) enabled.

     

    Overall, we can be certain that many customers have applied these Windows server updates and not experienced any problem. Two customers had been affected but both were able to be resolved by reconfiguring DCOM settings on MyID Servers. In one case, the database server was affected but not other application server tiers.

     

    Intercede advise that should any further problem occur on installing windows updates, that MSDTC security configuration is verified to be in line with the information in your MyID product documentation in section Installation and Configuration Guide > Preparing your system > Timeouts, limits and other settings > MSDTC security configuration*.

     

    The System Interrogation Utility can also be used to verify these settings (tests SIU-083, SIU-084, SIU-218). Please see Intercede product documentation* for guidance on using this utility.

     

    If further problems persist, please create a support ticket quoting reference SUP-354.

     

    * Links provided are for MyID PIV v12.1 product documentation, please see equivalent sections in documents applicable to your product version on the Intercede customer portal

Viewing 1 post (of 1 total)