DCOM, XenApp, IMAService, MFCOM,

See this error repeatably  DCOM got error "2148007941" from the computer SERVER-123 when attempting to activate the server:
{D66B68BD-9B5B-41CB-B692-A4D44DA3DC20}  --> XenAppCOM.XenAppIMACOM 1.0
AppID ---> {7BB98CBB-42E7-402B-994B-C21141D252DB} The keys identified with this AppID are as follows:
In a previous post i was instructed to add Domain Computers Full control to that single Key. This particular App ID points to several XenAPP components, do i need to set this permission on keys?

(Default) REG_SZ          MFCom
LocalService  REG_SZ   MFCom
Service Parameters  REG_SZ   -Service
MFCom.exe  ---> Value not set
XenAppCOM.XenAppPrivileges 1.0   --->   {DA037D58-B730-41D2-9EE2-083E0751823B}
XenAppCOM.XenAppUser 1.0   ---> {DD80DF53-9ABB-4E75-BF7E-585A7C53D6CF}
XenAppCOM.XenAppZone 1.0   --->   {DE9B3C54-B189-4809-9D1C-134A8BFEE2D3}
XenAppCOM.XenAppIPRanges 1.0  --->   {D0284C5E-7889-4024-9885-FE1BE5A01A71}
                                                                    {E80D1888-0A1A-479A-9E07-0FEC40CC994F}
XenApp.COM.XenAppID 1.0  --> {F3F409D5-1AE3-4A31-AB6B-992025FACD32}
XenAppCOM.XenServer 1.0   ---> {7C01FC2F-2091-4A23-AD2D-C9994A077348}
XenAppCom.XenAppAdministrator 1.0 ---> {037ADFEA-8565-4501-826C-4D491BC7EB10}
XenAppCOM.XenAppConfigLogging 1.0 --> {0ACFE8A7-FF54-4968-BF53-B076EE9D70D0}
XenAppCOM.XenAppLMRules 1.0 -->  {0E2DCD9D-9F84-4A2C-8CAE-33945D2F135F}
                                                             {2E715117-5620-43E6-AFDC-FC214297D405}
XenAppCOM.XenAppApplication 1.0 ---> {11724163-BE50-4B2B-B2BD-E739CA4822AF}
XenAppCOM.XenAppSession 1.0 ---> {1B41563C-6DBD-4213-ABDD-5F1B9AF02CB3}
XenAppCOM.XenAppAccountAuthority 1.0 ---> {42665BF8-BF70-414B-89F0-7851BF0CC75C}
XenAppCOM.XenAppAccounts 1.0 ---> {463484D4-C933-4A13-81A8-303D35D0D6F4}
                                                                 {5E342770-E8BD-49E0-BE97-5B955EFC386E}
XenAppCOM.XenAppGroup 1.0 ---> {62FC3310-1DC7-409A-82E4-2AA85F132652}
XenApp.XenAppProcess 1.0 ---> {6AE19245-CCCB-4853-B45C-04AC344A2303}
XenAppCOM.XenAppAppPackage 1.0 ---> {70B4A1E3-71FE-4475-806A-B5EB6DF046A6}
XenAppCOM.XenAppTime 1.0 ---> {80B593E4-961B-4F22-945E-2E179C6E81FD}
XenAppCOM.XenAppCredential 1.0 --> {8A9DA345-DEEB-4A2D-8406-3C219DADABD5}
XenAppCOM.XenAppFileTypes 1.0 --->   {A35260AC-0E93-4252-B785-589CC03B4EAA}
                                                                  {B0629CFC-5778-41C3-A008-6CBB151333F0}
XenAppCOM.XenAppFolder 1.0 ---> {AD793A9D-3453-4B77-B0BA-4D0FF6E8AEA7}
                                                           {B9E1AF0B-CF27-4835-AB89-39372D7E4DDA}
XenAppCOM.XenAppFarm 1.0 ---> {BE110642-8F5D-425D-8677-389E35CAACD4}
XenAppCOM.XenAppPolicy 1.0   --->  {BF58C748-355E-4E06-BC40-6FDE0B139B6E}
XenAppCom.XenAppLoadEvaluator 1.0 --->   {CF6FFC5C-F5D9-40D4-B289-6031E36DFCE2}
XenAppCOM.XenAppWorkerGroup 1.0 --->   {D02B0BD2-6C0D-4AE0-A92D-E49F1773C75E}

This all in regards to IMA Serivce MFCom service failing to start.