Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager Desired Configuration Management > DCM - Access check failed against user 'domainaccount'
Ask a questionAsk a question
Search Forums:
 

QuestionDCM - Access check failed against user 'domainaccount'

  • Monday, November 02, 2009 4:33 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi, After I evaluated, I click on View Report, I can see all configuration items also "not detected". It's Windows Server 2008. In DCMAgent.log, it got this error >> Access check failed against user 'domainaccount'. CLR has been enabled on the Microsoft SQL Server.  What else I need to set?

     

All Replies

  • Tuesday, November 03, 2009 7:55 AMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    You should provide more details. Which CI are you talking about etc...
     
  • Tuesday, November 03, 2009 8:21 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    I am using Windows server 2008 EC Configuration Item. All Configuration Items and Configuration Baseline also show the Actual Compliance State "not detected".


    Then in DCMAGent.log, it shows the following:
    CDCMSDK::EvaluateBaseline DCMAgent 3/11/2009 11:37:07 AM 4308 (0x10D4)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): State - Downloading DCMAgent 3/11/2009 11:37:07 AM 3300 (0x0CE4)
    CDCMSDK::GetBaselineComplianceReport DCMAgent 3/11/2009 11:37:11 AM 2536 (0x09E8)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): NotifyComplete DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): NotifyComplete (download complete) - Job queued for discovery DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): State - Detecting DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): ProcessDiscovery - Baseline - ScopeId_EDEFCFFF-53CD-437F-B16C-84DA40504545/ClonedCI_f4ddcf0b-aa00-4b5a-b1f9-bfa0145b7ba6 DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): ProcessDiscovery (discovery not required) - Released discovery semaphore DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    DCMAgentJob({E92BFF18-6577-441F-882F-6AC60B980A55}): State - Complete DCMAgent 3/11/2009 11:37:17 AM 3676 (0x0E5C)
    CDCMSDK::GetAssignedBaselines DCMAgent 3/11/2009 11:37:17 AM 4308 (0x10D4)
    CDCMAgent::EnumCIs DCMAgent 3/11/2009 11:37:17 AM 2348 (0x092C)
    CDCMSDK::GetBaselineComplianceReport DCMAgent 3/11/2009 11:37:38 AM 2108 (0x083C)
    DCM Agent starting up... DCMAgent 3/11/2009 11:50:37 AM 5060 (0x13C4)
    Updated DCM agent configuration Enabled='true', PerProviderTimeout='120', PerScanTimeout='360', PerScanTTL='15', PerScanDefaultPriority='0' DCMAgent 3/11/2009 11:50:37 AM 5060 (0x13C4)
    CDCMAgent::Initialize succeeded. DCMAgent 3/11/2009 11:50:37 AM 5060 (0x13C4)
    DCM Agent successfully started up. DCMAgent 3/11/2009 11:50:37 AM 5060 (0x13C4)
    CDCMSDK::GetAssignedBaselines DCMAgent 3/11/2009 12:33:02 PM 3248 (0x0CB0)
    CDCMAgent::EnumCIs DCMAgent 3/11/2009 12:33:02 PM 3164 (0x0C5C)
    Access check failed against user 'sccmadmin' DCMAgent 3/11/2009 12:33:02 PM 3164 (0x0C5C)
    CDCMSDK::GetBaselineComplianceReport DCMAgent 3/11/2009 12:33:08 PM 1792 (0x0700)
     
  • Tuesday, November 03, 2009 9:21 AMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote
    Have you already found that thread? http://social.technet.microsoft.com/Forums/en-US/configmgrdcm/thread/3659f76f-6f68-4188-b7c7-2dc461f65d40/
     
  • Tuesday, November 03, 2009 9:41 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Yes, I found that thread and tried to check the CLR setting. It's now CLR enabled for the SQL database.
     
  • Tuesday, November 03, 2009 10:17 AMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote
    And what about Sherry's suggestion? "The Access Check in the log is specifically when UAC is on in Vista or Server08.  If you do a runas on the control panel applet, you don't get the error."
     
  • Tuesday, November 03, 2009 11:23 AMMicrosoft Gal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Yes, I did do a runas on the control panel applet, I still get the error.

    Anyway UAC is enabled and cannot be disabled due to the AD policy. How could I get the status without disable the UAC?