User Agent (DC 5.3, Agent 2.2)

Having problems with the user agent/AD integration.  I have installed the user agent on a Windows 2008 box, it seems to be communicating with the DC servers fine.  When going from the agent to the DC is where it seems the problem is.  I added the IP on the DC, added the DC on the agent...get nothing.  I can telnet to port 3306 on the DC from the user agent machine fine and get the Got packets out of order message like is said in the troubleshooting guide.
Any suggestions?  I turned on debugging and logging on the agent and there are no errors listed and it says start DC chk, end DC chk...

Hi ,
Not sure if this helps but there is a known bug with v2.2.18 of the UA software which doesn't populate events unless the Date format is set to US Locale on the Domain Controller. I've seen it where events aren't logged at all, or events are generated but only on the first 12 days of the month (I assume theres an issue with the logic on the parser for the logs, once you hit the 13th it bugs out - UK Locale anyway, depends on your date format)
Info here:
If you use the dd/mm/yyyy date format on your Microsoft Active Directory (AD) server, the system sets the Active Directory server status to pending and fails to generate events. As a workaround, use the mm/dd/yyyy format on your AD server. (137315)
Other common issues are as you have correctly stated. Ensure the relevant Windows EventIDs for logon/logoff events are generated in the Windows security event logs.
Also if the agent and DC/FSM are seperated by a NAT device, you need 2 entries in the User Agents section on the DC/FSM. One for the Pre-NAT address and one for the Post-NAT Address.
Thanks,

Similar Messages

  • Skipping request for user policy assignments due to agent configuration for authority

    Hello all,
    Symptoms:
    The Configuration Manager only shows the following actions:
    Application Deployment Evaluation Cycle
    Machine Policy Retrieval & Evaluation Cycle
    Software Updates Deployment Evaluation Cycle
    User Policy Retrieval & Evaluation Cycle
    In Software Center there are no applications visible. Also the default 'IT Organization' is shown instead of the 'real' name.
    The Confugration Manager:
    shows in the tab 'General' the correct Management point. Connection type is 'currently intranet' (ok)
    shows in the tab 'Site' the correct site code.
    shows in the tab 'Components' all components as either 'installed' or 'enabled'. Only CCM Notification Agent shows 'Disabled'.
    In SCCM 2012 under 'Client Settings' -> 'Default Settings' -> 'Client Policy' the setting 'Enable User policy on clients' has been enabled.
    Done so far (without success):
    Re-installed the MP
    Run a query on the SCCM Database to check if there are any corrupt records. There are not.
    Installed version 5.00.7958.1000
    CCM Framework: 5.00.7958.1203
    The computer is installed with a task sequence. There is a reboot after 'Setup Windows and ConfigMgr (CM2012 R2 CU1)'.
    Installation command of the SCCM Client (during OSD deployment):
    SMSCACHEFLAGS=PERCENTDISKSPACE SMSCACHESIZE=10 SMSSLP=demo-sccm.demoforest.local SMSMP=demo-sccm.demoforest.local PATCH="%_SMSTSMDataPath%\OSD\TDS00020\KB2938441\configmgr2012ac-r2-kb2938441-i386.msp"
    Content log files on the client:
    PolicyAgent.log:
    Processing PreShutdown event PolicyAgent_RequestAssignments 8/4/2014 11:56:52 PM 2204 (0x089C)
    Processing PostStartup event PolicyAgent_RequestAssignments 8/4/2014 11:57:37 PM 2436 (0x0984)
    Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/4/2014 11:57:37 PM 2436 (0x0984)
    Registered for MP notifications. PolicyAgent_PostStartup 8/4/2014 11:57:37 PM 2436 (0x0984)
    Not rerequesting policy on site code change in provisioning mode. PolicyAgent_ReRequestPolicy 8/5/2014 12:01:55 AM 3212 (0x0C8C)
    Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 12:02:48 AM 2352 (0x0930)
    Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 12:02:48 AM 2352 (0x0930)
    Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 12:02:48 AM 2352 (0x0930)
    Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 12:11:36 AM 2720 (0x0AA0)
    Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 12:11:36 AM 2720 (0x0AA0)
    Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 12:11:36 AM 2720 (0x0AA0)
    Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 1:25:02 AM 3164 (0x0C5C)
    Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 1:25:02 AM 3164 (0x0C5C)
    Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 1:25:02 AM 3164 (0x0C5C)
    Processing PostStartup event PolicyAgent_RequestAssignments 8/5/2014 1:26:05 AM 2652 (0x0A5C)
    Policy Download Endpoint's message queue is empty; proceeding with maintenance work PolicyAgent_Cleanup 8/5/2014 1:26:05 AM 2652 (0x0A5C)
    Registered for MP notifications. PolicyAgent_PostStartup 8/5/2014 1:26:05 AM 2652 (0x0A5C)
    Triggered update of user S-1-5-21-1840543543-1948091412-3654635223-1109 settings PolicyAgent_RequestAssignments 8/5/2014 9:00:57 AM 3232 (0x0CA0)
    Requesting User policy assignments for 'S-1-5-21-1840543543-1948091412-3654635223-1109' PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
    Requesting User policy from authority 'SMS:TDS' PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
    Skipping request for user policy assignments due to agent configuration for authority 'SMS:TDS'. PolicyAgent_RequestAssignments 8/5/2014 9:02:34 AM 2484 (0x09B4)
    ClientIDManagerStartup.log:
    [----- STARTUP -----] ClientIDManagerStartup 8/5/2014 1:24:34 AM 372 (0x0174)
    Read SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
    Evaluated SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
    No SMBIOS Changed ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
    SMBIOS unchanged ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
    SID unchanged ClientIDManagerStartup 8/5/2014 1:24:52 AM 2932 (0x0B74)
    HWID unchanged ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Computed HardwareID=2:0760033F87CBB92FC5D6343C630C99002655F937
     Win32_SystemEnclosure.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_SystemEnclosure.SMBIOSAssetTag=2522-6626-0190-0004-7023-0906-91
     Win32_BaseBoard.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_BIOS.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:00:2A:0C ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
     HardwareID1=2:0760033F87CBB92FC5D6343C630C99002655F937
     HardwareID2=98130500010000EE ClientIDManagerStartup 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Failed to open to WMI namespace '\\.\root\ccmvdi' (8007045b) ClientIDManagerStartup 8/5/2014 1:25:02 AM 372 (0x0174)
    [----- SHUTDOWN -----] ClientIDManagerStartup 8/5/2014 1:25:02 AM 372 (0x0174)
    [----- STARTUP -----] ClientIDManagerStartup 8/5/2014 1:25:42 AM 2012 (0x07DC)
    Read SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
    Evaluated SMBIOS (encoded): 31003800300035002D0030003700310038002D0035003700330038002D0035003500350033002D0034003800350030002D0038003000390030002D0032003800 ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
    No SMBIOS Changed ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
    SMBIOS unchanged ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
    SID unchanged ClientIDManagerStartup 8/5/2014 1:25:51 AM 2504 (0x09C8)
    HWID unchanged ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
    GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Windows To Go requires a minimum operating system of Windows 8 ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Computed HardwareID=2:0760033F87CBB92FC5D6343C630C99002655F937
     Win32_SystemEnclosure.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_SystemEnclosure.SMBIOSAssetTag=2522-6626-0190-0004-7023-0906-91
     Win32_BaseBoard.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_BIOS.SerialNumber=1805-0718-5738-5553-4850-8090-28
     Win32_NetworkAdapterConfiguration.MACAddress=00:15:5D:00:2A:0C ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Persisted hardware IDs in CCM_ClientIdentificationInformation=@:
     HardwareID1=2:0760033F87CBB92FC5D6343C630C99002655F937
     HardwareID2=98C70600010000EE ClientIDManagerStartup 8/5/2014 1:25:53 AM 2504 (0x09C8)
    ClientAuth.log:
    Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:01 PM 1612 (0x064C)
    Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:01 PM 1612 (0x064C)
    Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:02 PM 1612 (0x064C)
    Error signing client message (0x80004005). ClientAuth 4/22/2014 9:25:02 PM 1612 (0x064C)
    ClientLocation.log:
    Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:24:34 AM 372 (0x0174)
    Domain joined client is in Intranet ClientLocation 8/5/2014 1:24:34 AM 372 (0x0174)
    Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Domain joined client is in Intranet ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
    1:24:53 AM 2932 (0x0B74)
    Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:24:53 AM 2932 (0x0B74)
    Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
    1:24:54 AM 2932 (0x0B74)
    Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:24:54 AM 2932 (0x0B74)
    Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:25:42 AM 2012 (0x07DC)
    Domain joined client is in Intranet ClientLocation 8/5/2014 1:25:42 AM 2012 (0x07DC)
    Current AD forest name is demoforest.local, domain name is demoforest.local ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Domain joined client is in Intranet ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
    1:25:53 AM 2504 (0x09C8)
    Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Rotating assigned management point, new management point [1] is: DEMO-SCCM.demoforest.local (7958) with capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities> ClientLocation 8/5/2014
    1:25:53 AM 2504 (0x09C8)
    Assigned MP changed from <DEMO-SCCM.demoforest.local> to <DEMO-SCCM.demoforest.local>. ClientLocation 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Getting Assigned Site ClientLocation 8/5/2014 9:02:38 AM 2264 (0x08D8)
    Assigned Site is TDS ClientLocation 8/5/2014 9:02:38 AM 2264 (0x08D8)
    Getting Assigned Site ClientLocation 8/5/2014 1:19:20 PM 2604 (0x0A2C)
    Assigned Site is TDS ClientLocation 8/5/2014 1:19:20 PM 2604 (0x0A2C)
    execmgr.log (with errors):
    Requesting MTC to delete task with id: {C5DCEE82-C903-4CBD-98CC-534646B3EFD7} execmgr 4/22/2014 7:14:28 PM 1872 (0x0750)
    This execution request does not own the corresponding task in MTC, returning without deleting it from MTC. execmgr 4/22/2014 7:14:28 PM 1872 (0x0750)
    Service startup. execmgr 4/22/2014 7:16:09 PM 2332 (0x091C)
    Service startup. execmgr 4/22/2014 9:17:36 PM 2216 (0x08A8)
    Service startup. execmgr 4/22/2014 9:23:02 PM 2348 (0x092C)
    Service startup. execmgr 4/22/2014 9:24:53 PM 1000 (0x03E8)
    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:56:52 PM 3224 (0x0C98)
    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:56:52 PM 1292 (0x050C)
    Service startup. execmgr 8/4/2014 11:57:32 PM 3696 (0x0E70)
    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 8/4/2014 11:57:33 PM 3696 (0x0E70)
    Software distribution agent was enabled execmgr 8/5/2014 12:01:55 AM 3448 (0x0D78)
    Service startup. execmgr 8/5/2014 12:02:44 AM 2272 (0x08E0)
    ExecMgr::GetTaskState - GetTaskState Failed with error code 0x87d00317 execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
    Policy arrived for child program Install execmgr 8/5/2014 12:03:02 AM 1648 (0x0670)
    Creating mandatory request for advert TDS20014, program Install, package TDS00014 execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
    An existing MTC token was supplied, this execution request is not owner of MTC object. execmgr 8/5/2014 12:03:02 AM 1652 (0x0674)
    CertificateMaintanance.log:
    HTTP is selected for Client. The current state is 0. CertificateMaintenance 4/22/2014 6:49:04 PM 604 (0x025C)
    Raising pending event:
    instance of CCM_ServiceHost_CertRetrieval_Status
     DateTime = "20140422164904.539000+000";
     HRESULT = "0x00000001";
     ProcessID = 3320;
     ThreadID = 604;
     CertificateMaintenance 4/22/2014 6:49:04 PM 604 (0x025C)
    Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
     ClientID = "GUID:7ff40832-4c01-456f-9705-096da67985b3";
     DateTime = "20140422164946.336000+000";
     HRESULT = "0x00000001";
     ProcessID = 3320;
     ThreadID = 3216;
     CertificateMaintenance 4/22/2014 6:49:46 PM 3216 (0x0C90)
    HTTP is selected for Client. The current state is 0. CertificateMaintenance 8/4/2014 11:56:39 PM 2212 (0x08A4)
    Raising pending event:
    instance of CCM_ServiceHost_CertRetrieval_Status
     DateTime = "20140804215639.612000+000";
     HRESULT = "0x00000001";
     ProcessID = 2144;
     ThreadID = 2212;
     CertificateMaintenance 8/4/2014 11:56:39 PM 2212 (0x08A4)
    Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804215651.440000+000";
     HRESULT = "0x00000001";
     ProcessID = 2144;
     ThreadID = 3348;
     CertificateMaintenance 8/4/2014 11:56:51 PM 3348 (0x0D14)
    Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/4/2014 11:56:56 PM 1096 (0x0448)
    Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 12:02:33 AM 1656 (0x0678)
    Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 12:11:17 AM 384 (0x0180)
    Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 1:24:34 AM 372 (0x0174)
    Client is set to use HTTPS when available. The current state is 480. CertificateMaintenance 8/5/2014 1:25:42 AM 2012 (0x07DC)
    smscliui.log:
    Perform Action: Request & Evaluate User Policy - {3A88A2F3-0C39-45fa-8959-81F21BF500CE}. Message sent, id={FC736B58-2635-45B8-8002-E7C8D6CCEB8D} smscliui 8/5/2014 9:02:34 AM 2484 (0x09B4)
    Current Assigned Site: TDS smscliui 8/5/2014 9:02:38 AM 868 (0x0364)
    Currently assigned FQDN:  smscliui 8/5/2014 9:02:41 AM 868 (0x0364)
    Failed to set DNSSuffix value to the registry. smscliui 8/5/2014 9:02:58 AM 868 (0x0364)
    SMS Site code has not been changed. smscliui 8/5/2014 9:02:58 AM 868 (0x0364)
    Current Assigned Site: TDS smscliui 8/5/2014 1:19:20 PM 2160 (0x0870)
    CcmMessaging.log:
    Queue 'StateMessageManager' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'StateMessageManager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'CTMDTSReply'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'CTMDTSReply' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'CTMDTSReply'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'execmgr'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'execmgr' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'execmgr'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'PolicyAgent_RequestAssignments'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'PolicyAgent_RequestAssignments' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'PolicyAgent_RequestAssignments'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'ClientRegistration'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'ClientRegistration' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'ClientRegistration'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'EndpointProtectionAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'EndpointProtectionAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'EndpointProtectionAgent'. Enabled=true Concurrency=20 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'LS_ScheduledCleanup'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'LS_ScheduledCleanup' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'LS_ScheduledCleanup'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'PolicyAgent_Cleanup'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'PolicyAgent_Cleanup' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'PolicyAgent_Cleanup'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'DCMAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'DCMAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'DCMAgent'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'CertEnrollAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'CertEnrollAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'CertEnrollAgent'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'ExternalEventAgent'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'ExternalEventAgent' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'ExternalEventAgent'. Enabled=true Concurrency=20 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'UpdateStore'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'UpdateStore' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'UpdateStore'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'PolicyAgent_ReplyAssignments'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'PolicyAgent_ReplyAssignments' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'PolicyAgent_ReplyAssignments'. Enabled=true Concurrency=5 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'SMSSHA'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'SMSSHA' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'SMSSHA'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'lmp_[http]mp_locationmanager'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'lmp_[http]mp_locationmanager' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'lmp_[http]mp_locationmanager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'mp_statusreceiver'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'mp_statusreceiver' initialized with 0 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'mp_statusreceiver'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initializing queue 'mp_[http]mp_locationmanager'... CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Queue 'mp_[http]mp_locationmanager' initialized with 1 messages. CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Initialized queue processor 'mp_[http]mp_locationmanager'. Enabled=true Concurrency=1 CcmMessaging 8/5/2014 1:25:50 AM 2192 (0x0890)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232553.423000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2504;
     CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232553.485000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2504;
     CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232553.563000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2504;
     CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232553.657000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2504;
     CcmMessaging 8/5/2014 1:25:53 AM 2504 (0x09C8)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232606.048000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2508;
     CcmMessaging 8/5/2014 1:26:06 AM 2508 (0x09CC)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232606.110000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2188;
     CcmMessaging 8/5/2014 1:26:06 AM 2188 (0x088C)
    Raising event:
    instance of CCM_CcmHttp_Status
     ClientID = "GUID:b8d72095-2590-4724-9db9-b721efc05007";
     DateTime = "20140804232606.188000+000";
     HostName = "DEMO-SCCM.demoforest.local";
     HRESULT = "0x00000000";
     ProcessID = 1996;
     StatusCode = 0;
     ThreadID = 2504;
     CcmMessaging 8/5/2014 1:26:06 AM 2504 (0x09C8)
    CcmNotificationAgent.log:
    Bgb client agent is starting... BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
    Bgb client agent is disabled BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
    TCP Listener is disabled. BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
    BgbController main thread is started with settings: {bgb enable = 0}, {tcp enabled = 0}, {tcp port = 0} and {http enabled = 0}. BgbAgent 8/5/2014 1:26:05 AM 2504 (0x09C8)
    Wait 3600 seconds for event notification. BgbAgent 8/5/2014 1:26:05 AM 3076 (0x0C04)
    Wait 3600 seconds for event notification. BgbAgent 8/5/2014 2:26:05 AM 3076 (0x0C04)
    Any help is appreciated and with kind regards,
    Willem-Jan

    Hello all,
    I modified the TS, but the problem is still there.
    smsts.log:
    ==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
    Executing task sequence OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
    Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} OSDSetupHook 8/5/2014 4:51:30 PM 856 (0x0358)
    Debug shell is enabled OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Successfully enabled debug command shell support. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Configuring local administrator account OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Re-assign all drive letters... OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Could not open drive Q:\ (80070005) OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Ignoring inaccessible volume 'Q:' with error 0x80070005 OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    No partition needs to be udpated. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Installing SMS client OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Client already installed. OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Moving logs to SMS client directory OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Successfully moved logs to SMS client log directory: C:\Windows\CCM\Logs\SMSTSLog OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Executing task sequence manager bootstrap OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    Executing command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5 OSDSetupHook 8/5/2014 4:51:39 PM 856 (0x0358)
    ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Current OS version is 6.1.7601.1 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Logging successfully initialized. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Resuming Task Sequence in Full OS TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    We are going in GINA and potentially need to set the authenticator TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    setting the authenticator TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    ==========[ TsProgressUI started in process 2196 ]========== TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    Command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    Registering COM classes TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    Unregistering class objects TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    Shutdown complete. TsProgressUI 8/5/2014 4:51:39 PM 2200 (0x0898)
    Process completed with exit code 0 TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Successfully registered TS Progress UI. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Found network adapter "Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)" with IP Address 5.5.5.101. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Starting Task Sequence Manager. TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    executing TS Manager not in full media TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    executing TS Manager in c:\windows\ccm TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Executing command line: "TsManager.exe" TSMBootstrap 8/5/2014 4:51:39 PM 2152 (0x0868)
    Successfully intialized Logging for TS Manager. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Commandline: "TsManager.exe" TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    /service parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    /standalone parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    /noclient parameter found at index: -1 TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Successfully registered Task Sequencing COM Interface. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Executing as a standalone exe TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Initializing TS Environment TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Opening Task Sequencing Environment TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,228) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    NOT executing in WinPE TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling Config policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling config policies... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling SysHealthConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSSysHealthClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 684, uncompressed size 4652. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling SoftUpdConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSSWUpdateClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 1922, uncompressed size 19242. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling SoftDistClientConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSSoftDistClientConfig' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 1327, uncompressed size 13740. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling NAAConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSNAAConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 1022, uncompressed size 6494. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_NetworkAccessAccount.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling RebootSettingsConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSRebootSettingsConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 433, uncompressed size 1556. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_RebootSettings.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Compiling AppManClientConfig policy... TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Retrieving value from TSEnv for '_SMSTSAppManClientConfigPolicy' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    ::DecompressBuffer(65536) TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Decompression (zlib) succeeded: original size 982, uncompressed size 6358. TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Instance path = 'CCM_ApplicationManagementClientConfig.SiteSettingsKey="1"' TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Start to compile TS policy TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Failed to find property 'AutoApplyDeployment' in 'CCM_ApplicationManagementClientConfig' class defintion. Error 0x80041002. Default value will be used for this property TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    End TS policy compilation TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Get Install Directory for SMS Client TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    Updating settings in \\.\root\ccm\policy\machine\actualconfig TSManager 8/5/2014 4:51:40 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 435 TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
    Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
    Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3}") AND (PolicyState
    = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
    There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
    Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:Client:Default:{BFDADC41-FDCD-4B9C-B446-8A818D01BEA3} successfully TSManager 8/5/2014 4:51:49 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
    Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:TDS successfully TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
    Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "SMS:TDS") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
    4:51:50 PM 2244 (0x08C4)
    There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
    Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source SMS:TDS successfully TSManager 8/5/2014 4:51:50 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
    Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmPortal successfully TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
    Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmPortal") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
    4:51:51 PM 2244 (0x08C4)
    There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
    Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmPortal successfully TSManager 8/5/2014 4:51:51 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 0 TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
    Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source Local successfully TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 9 TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
    Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source Local successfully TSManager 8/5/2014 4:51:53 PM 2244 (0x08C4)
    RequestedConfig policy instance(s) : 11943 TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
    Locked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmTaskSequence successfully TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
    Namespace: \\.\ROOT\ccm\policy\machine\RequestedConfig, Query: SELECT PolicyID FROM CCM_Policy_Policy5 WHERE (PolicySource = "CcmTaskSequence") AND (PolicyState = "Active") AND (PolicyType = "Machine") TSManager 8/5/2014
    4:51:57 PM 2244 (0x08C4)
    There is no ccm_policy_policy instance, skipping addition to realinst map TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
    Unlocked \\.\ROOT\ccm\policy\machine\RequestedConfig for source CcmTaskSequence successfully TSManager 8/5/2014 4:51:57 PM 2244 (0x08C4)
    Total RequestedConfig policy instance(s) : 12387 TSManager 8/5/2014 4:52:00 PM 2244 (0x08C4)
    New/Changed ActualConfig policy instance(s) : 0 TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Policy evaluation initiated TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace  TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Query = 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"'  TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Verified policy for instance path 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Query = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"'  TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Verified policy for instance path 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine' namespace TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Query = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"'  TSManager 8/5/2014 4:52:04 PM 2244 (0x08C4)
    Verified policy for instance path 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"' compiled in 'root\ccm\policy\machine'
    The Powershell command as described by NPerson give the output:
    C:\Windows\system32>powershell Invoke-WmiMethod -Namespace root\CCM -Class SMS_C
    lient -Name SetClientProvisioningMode -ArgumentList $false
    __GENUS          : 1
    __CLASS          : __PARAMETERS
    __SUPERCLASS     :
    __DYNASTY        : __PARAMETERS
    __RELPATH        : __PARAMETERS
    __PROPERTY_COUNT : 1
    __DERIVATION     : {}
    __SERVER         : DEMO-CAPTURE
    __NAMESPACE      : ROOT\ccm
    __PATH           :
    \\DEMO-CAPTURE\ROOT\ccm:__PARAMETERS
    ReturnValue      :
    PSComputerName   : DEMO-CAPTURE
    It is about the PSComputerName: that is the name of the machine on which the capture was made. So I suppose the problem is already in the image. Is my statement correct or is it not relevant?
    With kind regards,
    Willem-Jan

  • SMD agents goes offline in agent administration

    Hi,
    In my landscape all the SMD agents are directly registered to Solman SPS27.
    Each time my solman is restarted, all teh agents in agent administration goes offline. but in actual its runing at OS lvl.
    After we take seperate Java stack restart of solman, agents come online in agent admin. This scenario is confusing
    Any idea as to how can we overcome this issue ?
    Regards,
    Shyam

    Thanks Guilherme for this very good clearification!
    I have a simular problem at the moment and can confirm that the agent connection get disabled because they are not able to authentificate. I will try to implement the workaround with the telnet command to bring the agents in MM... This should help to solve the issue.
    Anyway what I don´t understand is that not all agents get disconnected!
    For example:
    SMDsystem.log of Agent which is offline:
    Aug 20, 2011 1:01:15 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
    Aug 20, 2011 1:01:16 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
    Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Failed to connect to SMD server - user: SMD_ADMIN
    Aug 20, 2011 1:02:07 AM [Thread[Connector,5,main]] Error      Connecting to SMD server ms://jusmp00:8104/P4 failed
    com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException: Exception during getInitialContext operation. Wrong security principle/credentials. Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
    Aug 20, 2011 1:02:08 AM [Thread[Connector,5,main]] Warning    Access denied occurs during the registration, smd connector has been disabled (waiting new SLD GUID).
    Aug 20, 2011 1:43:20 AM [Thread[SLD-Registration,1,main]] Info       Next try to push instance data in SLD is  Sat Aug 20 13:43:06 AST 2011
    SMDsystem.log of Agent which is online:
    Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Error      ms://jusmp00:8104/P4 Ping failed : com.sap.smd.server.exec.asio.TimeOutError - null
    Time out occurred when calling method 'ping' on object com.sap.smd.api.ISMDServerHandle_Stub@54bf219b after 30001 ms.
    possible cause: com.sap.smd.server.util.concurrent.TimeoutException
         at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:130)
         at $Proxy1.ping(Unknown Source)
         at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.updateConnectionStatus(SMDConnector.java:230)
         at com.sap.smd.agent.connection.SMDConnector$SMDConnectionTask.run(SMDConnector.java:189)
         at java.lang.Thread.run(Thread.java:664)
    Caused by: com.sap.smd.server.util.concurrent.TimeoutException
         at com.sap.smd.server.util.concurrent.FutureResult.timedGet(FutureResult.java:159)
         at com.sap.smd.server.exec.asio.AsioInvocationHandler.invoke(AsioInvocationHandler.java:122)
         ... 4 more
    Aug 20, 2011 1:01:12 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Checking server availability...
    Aug 20, 2011 1:40:27 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Authentication in progress ...
    Aug 20, 2011 1:40:29 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Connection established .
    Aug 20, 2011 1:40:30 AM [Thread[Connector,5,main]] Info       ms://jusmp00:8104/P4 Registering agent on server ...
    So you see that the secound agents waits the 40 minutes and start the authentication process after than.
    Both agents are 7.11 and application version 7.01.7.3.20110311130810.
    Any idea about that?

  • CDSSO Invalid Agent: Could not get agent for realm

    Hi,
    This post follows on from a previous post (http://forum.java.sun.com/thread.jspa?threadID=5276012) but describes a subsequent problem.
    I'm getting the following error in my amCDC log. I believe it is related to the post (http://forum.java.sun.com/thread.jspa?threadID=5162908&messageID=9623898)
    03/18/2008 10:17:58:826 AM GMT: Thread[httpSSLWorkerThread-443-0,10,Grizzly]
    CDCServlet.doGetPost: Query String received: goto=http%3A%2F%2Fbonecrusher.test.local%3A80%2F%3FsunwMethod%3DGET&RequestID=20798&MajorVersion=1&MinorVersion=0&ProviderID=http%3A%2F%2Fbonecrusher.test.local%3A80%2Famagent&IssueInstant=2008-03-18T10%3A18%3A09Z
    03/18/2008 10:17:58:826 AM GMT: Thread[httpSSLWorkerThread-443-0,10,Grizzly]
    SSOException caught: com.iplanet.sso.SSOException: Invalid session ID.
    03/18/2008 10:17:59:091 AM GMT: Thread[httpSSLWorkerThread-443-0,10,Grizzly]
    Forwarding for authentication to: /UI/Login?goto=%2Famserver%2Fcdcservlet%3FTARGET%3Dhttp%253A%252F%252Fbonecrusher.test.local%253A80%252F%253FsunwMethod%253DGET%26RequestID%3D20798%26MajorVersion%3D1%26MinorVersion%3D0%26ProviderID%3Dhttp%253A%252F%252Fbonecrusher.test.local%253A80%252Famagent%26IssueInstant%3D2008-03-18T10%253A18%253A09Z
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    CDCServlet.doGetPost: Query String received: TARGET=http%3A%2F%2Fbonecrusher.test.local%3A80%2F%3FsunwMethod%3DGET&RequestID=20798&MajorVersion=1&MinorVersion=0&ProviderID=http%3A%2F%2Fbonecrusher.test.local%3A80%2Famagent&IssueInstant=2008-03-18T10%3A18%3A09Z
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    WARNING: Advice List is : null
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    CDCServlet.doGetPost: targetURL = http://bonecrusher.test.local:80/?sunwMethod=GET
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    CDCServlet.doGetPost: gotoURL = http://bonecrusher.test.local:80/?sunwMethod=GET
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    CDC Servlet: Directory matches for http://bonecrusher.test.local:80/ is:{AMIdentity object: id=TestCDSSOAgent,ou=agent,dc=test-sun,dc=local={objectclass=[person, inetorgperson, organizationalperson, inetuser, top], sunIdentityServerDeviceKeyValue=[agentRootURL=http://bonecrusher.test.local:80/, agentRootURL=http://bonecrusher.test.local/], sunIdentityServerDeviceStatus=[Active], userpassword=[Q8Ea8sKa1CMyUaxgkqhC0PVeKV8=]}}
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    CDC Servlet: Restriction string for: http://bonecrusher.test.local:80/ is: id=TestCDSSOAgent,ou=agent,dc=test-sun,dc=local [bonecrusher.test.local, bonecrusher.test.local]
    03/18/2008 10:18:04:482 AM GMT: Thread[httpSSLWorkerThread-443-2,10,Grizzly]
    ERROR: CDCServlet.doGetPost:Exception occured
    java.lang.Exception: Invalid Agent: Could not get agent for the realm
    at com.iplanet.services.cdc.LdapSPValidator.validateAndGetRestriction(LdapSPValidator.java:200)
    at com.iplanet.services.cdc.CDCServlet.redirectWithAuthNResponse(CDCServlet.java:303)
    at com.iplanet.services.cdc.CDCServlet.doGetPost(CDCServlet.java:262)
    at com.iplanet.services.cdc.CDCServlet.doGet(CDCServlet.java:208)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    Based on the previous post I believe it has something to do with the validity checks performed by the CDC. The post describes 3 checks and I believe my solution is failing one of these, however I am not sure which.
    As far as I understand it my logs above demonstrate that the agentRootURL is correctly set, but I'm not sure what other values are needed.
    Any advice would be greatly received.
    R

    Quick follow up :)
    This problem was caused by the Access Manager instance not being able to resolve the IP address for 'bonecrusher.test.local'
    After I added the entry for this into the hosts file everything worked.
    R

  • Cisco Supervisor Desktop show "Agent Logs - call" and "Agent Logs - state" in N/A ::: UCCX 8.5.1

    Hi team.
    The Cisco Supervisor Desktop don't show any logs in the "Agent Logs - State" and "Agent Logs - Call" in some agents.
    I restarted the Cisco Desktop Services in CCX Serviceability but the issue continue.
    I appreciate any help respect this case.
    Thanks a lot.
    ErnestoG

    Hi Ernesto,
    Did you click or selct the Specific Agent\Inbound call which is currently being handled by the Agent. From the Screenshot you have attached (first one) doesn't look like the call has been selected.
    Please select or click on that Specific Agent\Inbound call from CSD and check these values.
    Hope this helps.
    Anand
    Please rate helpful posts !!

  • Weblogic SNMP Agent with WindowsNT SNMP Agent

    Can I setup Weblogic SNMP agent as a sub-agent to Windows NT SNMP agent (Microsoft's version)? According to documentation, sub-agents for Microsft's SNMP agent need to be implemented as 32-bit multithreaded DLLs using the Microsoft SNMP API. Does Weblogic have DLLs that we could use for this purpose?
    If that is not possible, is there a roadmap on how to provide the same support as the Microsoft's SNMP agent under Weblogic SNMP agent so that the Weblogic agent would provide the same visibility into the system that the Microsoft's agent does by default? Is this even possible?
    Thanks.

    "Sanjeev Mishra" <[email protected]> wrote:
    >
    Does anyone know how to make Microsoft's SNMP Master Agent run on a different port?
    I figured this out. It uses the 'snmp' setting from the services file. Just changing that works. Would have been more convenient if there was also a command line flag for that purpose.
    Thanks.
    "Sanjeev Chopra" <[email protected]> wrote:
    Sanjeev Mishra <[email protected]> wrote in message
    news:39fde7f2$[email protected]..
    Can I setup Weblogic SNMP agent as a sub-agent to Windows NT SNMP agent(Microsoft's version)? According to documentation, sub-agents for Microsft's
    SNMP agent need to be implemented as 32-bit multithreaded DLLs using the
    Microsoft SNMP API. Does Weblogic have DLLs that we could use for this
    purpose?
    No.
    However, you can have the WLS agent proxy for the NT agent. e.g. you can run
    the NT agent on a non-standard port and the WLS agent on 161 and then use
    '-otherAgents' option so that the WLS agent will forward any reqs for the NT
    agent MIB to that agent. In this setup the SNMP Manager can view that node
    as one SNMP entity which supports the WLS MIB + NT MIB
    See http://www.weblogic.com/docs51/admindocs/snmpagent.html#use_agent for
    details.
    If that is not possible, is there a roadmap on how to provide the samesupport as the Microsoft's SNMP agent under Weblogic SNMP agent so that the
    Weblogic agent would provide the same visibility into the system that the
    Microsoft's agent does by default? Is this even possible?
    Thanks.

  • Difference between web policy agent and j2ee Policy agent ?

    Difference between web policy agent and j2ee Policy agent ?

    http://docs.sun.com/app/docs/doc/820-5816/ghscr?a=view

  • UCCE maximum agents with ICM/UCCE agent mix

         hello
    I saw in the UCCE 9 BOM that ICM can support up to 28800 agents and UCCE 12000 concurrent agents.
    Is it possible to support beyond 12000 with a mix of ICM agents (10000) and UCCE agents (4800) concurrent?
    Thanks
    Mike Kana

    Out of the check mark in the queue to skill group node you go to another run external script node, then you loop into that over and over again until the call is answered.
    david

  • User cannot log into ZCM Agent 11.3.1

    We just went through a domain migration. All PCs were unregistered from the old ZCM 11.2 server in the old domain before they were migrated. When we went to re-register them to the 11.3.1 ZCM server, we ran into 2 issues. Some of the systems successfully upgraded to 11.3.1 BUT users cannot log onto the ZCM 11.3.1 Agent. It's giving an error of "unable to log into the network because the login credentials or the server certificate is incorrect". The PCs that didn't not upgraded to ZCM 11.3.1 and are running 11.2.0 do not have this problem. They get authenticated appropriately. The User configuration is set to eDirectory (just like on the ZCM 11.2 server in the old domain).
    I ran "zac ci" and noticed there are old certificates from ZENworks servers that are no longer around. How do you get rid of these old references? It's picking up the new server's certificates. I ran this on my PC ZCM Agent 11.2 (won't upgrade and can authenticate into the ZCM 11.2 agent just fine) and I do not see the old certificates. I'm only seeing certificates for the new ZCM 11.3.1 server in the new domain and the eDirectory master server that the ZCM server is referencing.

    The old Trusts can be cleared using IE to managed the Trusted Root
    Stores. There are some other ways too.
    However, Having old ones should not be an issue unless the old and new
    Servers have the same name. Not 100% sure matching will cause an issue,
    but I think I have seen that before.
    It may be possible to automate the removal of the old trusts, but I
    would not worry about that until you verify it is an issue by manually
    fixing a couple and see if resolves your issue.
    Your issue may be something else.
    Reinstalling CASA is something else to try.
    On 10/9/2014 5:16 AM, hfr63 wrote:
    >
    > We just went through a domain migration. All PCs were unregistered from
    > the old ZCM 11.2 server in the old domain before they were migrated.
    > When we went to re-register them to the 11.3.1 ZCM server, we ran into 2
    > issues. Some of the systems successfully upgraded to 11.3.1 BUT users
    > cannot log onto the ZCM 11.3.1 Agent. It's giving an error of "unable
    > to log into the network because the login credentials or the server
    > certificate is incorrect". The PCs that didn't not upgraded to ZCM
    > 11.3.1 and are running 11.2.0 do not have this problem. They get
    > authenticated appropriately. The User configuration is set to
    > eDirectory (just like on the ZCM 11.2 server in the old domain).
    >
    > I ran "zac ci" and noticed there are old certificates from ZENworks
    > servers that are no longer around. How do you get rid of these old
    > references? It's picking up the new server's certificates. I ran this
    > on my PC ZCM Agent 11.2 (won't upgrade and can authenticate into the ZCM
    > 11.2 agent just fine) and I do not see the old certificates. I'm only
    > seeing certificates for the new ZCM 11.3.1 server in the new domain and
    > the eDirectory master server that the ZCM server is referencing.
    >
    >
    Going to Brainshare 2014?
    http://www.brainshare.com
    Use Registration Code "nvlcwilson" for $300 off!
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Technical Support Engineer
    Novell does not officially monitor these forums.
    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.

  • User exit for workflow WS20000075  agent determination for PO

    Hi,
    I have requirement to determine agents for workflow WS20000075 for PO from Ztable entry.  Is that customer exit EXIT_SAPLEBNF_005 will work ?

    Hi ,
    Try assigning a new Agent Rule in the Task TS20000166.
    You will have to create a custom rule using transaction PFAC. Choose option "F - Agent dertermination function to be executed" and assign a new Z function module which will determine your agent.
    You can refer to function module ME_REL_GET_RESPONSIBLE while creating your own function module.
    Cheers!!!
    Gautam

  • SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

    Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege.  I have a SQL server 2012 instance whose Agent service is configured to run
    under an AD user account named 'SQLServices'.  The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'.  The jobs are set up to execute SSIS packages which read and
    write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server).  The jobs are currently executing without error and are reading writing data correctly.  Upon close examination, it turns out the
    SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server.  How are these jobs working?  I verified in profiler that the login name indeed is 'SqlServices'.  I also verified
    that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected.  According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
    some cases where that is not necessarily the case.  So this is not so concerning.  What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does. 
    The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access.  What am I missing here?  Any input would be helpful.

    After 2 days on this forum I found the answer to my own question.  In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
    The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed.  This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
    role.  This is the login that Agent uses to connect to the local instance of SQL server.  If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
    used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server. 
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

  • SCOM 2012 R2 agent upgrade fails crippling agents

    Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues.  Warning this issue is not for the faint of heart. 
    Plan:
    I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2.  I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters. 
    Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
    Problem:
    I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state.  At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
    be done.  What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate.  This is no problem and I am able to do this.  (Note: all other methods of agent removal did not work ie:
    Cleanmom.exe utility or add remove)
    Task:
    Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
    Notes:
    Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down. 
    Looking at the MSI log, I see a common issue among systems that had this problem.
    ******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
    MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2:  3: -2147287037
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2:  3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
    MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
    CustomAction  returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
    Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
    Action ended 8:08:44: RemoveExistingProducts. Return value 3.
    Action ended 8:08:44: INSTALL. Return value 3.
    Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
    387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine.  Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent. 
    Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
    Action ended 8:08:11: FindRelatedProducts. Return value 1.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    Action start 8:08:11: _Set_OM_AGENT_FOUND.
    MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
    Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
    Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a  64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
    the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE).  This is the point of my confusion and my suspicion as the cause of the problem I am having. 
    Concluding thoughts:
    Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log?  Would this
    cause my agents to fail the upgrade?  I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
    Thanks in advance if you took the time to read this and think about it.  Extra points if you have any extra thoughts!
    Keith

    Hi,
    Have you used Requirement to limit the platform when you deploy application with SCCM.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Agent Assignment - if no agent found

    Hi,
      I have created a dialog work item. i have done agent assignment with position id.
      My problem is  if  position id is not having users( in some cases)  then the workitem will go to whom? ,  how  can i resolve this .
    Thanks & Regards
    Sankar.

    Hi Sankar,
    The work item is sent to the position, so If the position is empty then it will go to no one (well... that's what happens on 4.6C - unfortunately, no warnings or errors are produced to indicate this work item is without an agent).
    Note: If the "Position" doesn't Exist on the runtime environment - then your Workflow Will go into Error when "establishing the agent".
    However... run tx. SWI2_ADM1 to get a list of "Work Items Without Agents" and... Your Work item is there... And you can reserve the work item and forward it to an agent
    To resolve this:
    Check your "Agent Assignment" on that dialog task...
    You can specify the "Possible Agents", so that the work item will be sent to the "Position" and all "Possible Agents" (not 100% ideal - but will ensure that an Agent is found). Make sure it's Not a General Task to do this.
    Alternatives:
    You might want to reconsider applying a "position" directly to a task in the workflow. Instead, try using "Roles" - it gives you more flexibility in runtime.
    Hope it helps.
    Tom

  • Cisco Agent Desktop incorrect stats Agent Statistics Display

    Hi,
    I have a very strange problem with a cisco agent desktop user. The times/numbers as displayed in the Agent Statistics Display are incorrect. As you can see from image 1, the agent was presented with 14 calls. The total talking time is 7:22. However if you look at the actual times from image two, and add those numbers you will have a total of 54:42 minutes:seconds. Also the Max talking is incorrect since this filed should display the longest call which has a length of 14:22 min:sec. Also the ready times max/avg and so are incorrect. It's like it's displaying numbers from a different agent however the number of calls presented is correct. If i look at this specific user from the supervisor tool the numbers are correct, see image 3. (in this image a 15th call was placed) I have reinstalled the agent desktop software but this has not solved this problem. I've done some googling but can't seem to find anyone with the same issue and/or a way to troublshoot this. Anyone have a clue?
    Image 1:
    Image 2:
    Image 3:

    Hi Anand,
    I've looked at the historical reports. Nothing weird there. The 14 minute call came directly from outside, no transfeer or anything. And even if this was the case then the 2nd longest inbound call is 8:30 and not 3:08. Also if you take the sum of all inbound call times you get almost 55 minutes. The difference is too much as the Toal Talking time displayed is 7:22. Also from the supervisor tool I do see the correct numbers.
    Thanks again.
    Regards,

  • Error: No selected agent. Actually the agents are defined

    Hi Experts,
    In my workflow at one of the steps, the work item does not come to agents'  inbox. In the LOG when i try to check agents I get the message "No selected agents".
    In WF definition nothing is defined as responsible agents. the field is empty. 
    I tried to define the task as general task or to write down some user or org unit as possible agents. The result is the same.
    There are no selected agents in the log.
    Do anyone have any idea?
    Thanks a lot,
    Nina

    hi,
    "No selected agents".comes when for a dialog task have no agent assigned or when possible agent is not configured means you hav not make general task  . 
    if after doing this too the dialog task show the same error , then run "SWU_OBUF" , this will refresh the system.
    let me know if it helps
    kakoli

Maybe you are looking for

  • SAP BPC 7.5 (MS) - The members are locked.

    Problem occured when the processing time to clear down one TIME period of data took 3 hours on Fri pm. On Monday morning, I executed a Run Package > Clear > on the same segment.  It ran for 1hr and 10 minutes and I escalated to our Helpdesk for a ser

  • The hyperlink manager in the case messages section doesn't work

    Hi One of my clients uses the messages section in cases to respond to customer enquiries to keep track od communications (as it's set up for). However, you can't add a hyperlink to a message. If you open the Hyperlink Manager, the pop up box just sho

  • Channel allocation in rman at the time of backup

    what happens when one channel of five channels allocated for taking backup got corrupt at the time of backup process is still going on? does the backup will continue if so is that backup is consistent or inconsistent?

  • InDesign PDF Exports not as small as Quark

    Anybody know why inDesign PDFs are double the size of Quark's? I choose the smallest file size setting and the PDFs still come out twice the size of Quark's. Thanks!

  • Programmatically inserting row in ViewObject

    I have created Entity Object based on table and updatable VO based on the Entity. Now i need to add a new row in the table. I have a button Add new row , on button click a popup will open with the fields in the row. Entering the field ,clicking on OK