Deployment Solution

 View Only

Redhat 5.4 locking windows server 2008 account when deploying agent

  • 1.  Redhat 5.4 locking windows server 2008 account when deploying agent

    Posted Jan 31, 2012 03:39 PM

    We are using RHEL 5.4 and Windows Server 2008 R2. We have Lanman Authentication level in windows set to level 5, in Redhat its set to client ntlmv2 auth = yes.

    the account we are using is getting locked out. Here is a snippet of the error

    Log File Name: C:\ProgramData\Symantec\SMP\Logs\a.log

    Priority: 1

    Help and Support:

    Date: 1/31/2012 12:14:26 PM

    Tick Count: 11846871

    Host Name: 29-ALTIRIS

    Process: w3wp (5784)

    Thread ID: 214

    Module: w3wp.exe

    Source: Altiris.NS.Server.GroupMessaging_Trace

    Description: [w3wp.exe:/LM/W3SVC/1/ROOT/Altiris/Resource-19-129725135233971649] <_lm_w3svc_1_root_altiris_resource_19_129725135233971649_cf8454bf82274965be134bfc23b9f5b8> Failed to create security context for channel: Altiris.NS.Utilities.ImpersonationException: Could not logon as user "MC\altiris". Current user is "IIS APPPOOL\Classic .NET AppPool". Token=0, LastError=1909 (The referenced account is currently locked out and may not be logged on to). ---> System.ComponentModel.Win32Exception: The referenced account is currently locked out and may not be logged on to

       --- End of inner exception stack trace ---

       at Altiris.NS.Utilities.Impersonate.CreateUserLogonToken(String domain, String user, String password, Int32 logonType, Int32 logonProvider, IntPtr& token1)

       at Altiris.NS.Utilities.Impersonate.ImpersonateAsSvc()

       at Altiris.NS.Server.GetSecurityContextForNSChannel()

       at Altiris.GroupCommunications.Channel.CreateSecurityContextCallbackWrapper()

     

    V/R

     

    I will run a wireshark and find out the results