8 Replies Latest reply on Mar 16, 2011 9:40 AM by Steffen Kreis

    Automation Principals and Windows Patching

    Jim Campbell

      Has anyone else run into a problem with Automation Principal usage specific to Windows Patching?  After setting up an NSH proxy and configuring the appservers to use it, I can run file deploys, NSH script jobs, extended objects that use NSH scripts, etc.  They all use the automation principal.  However, when I try to run a Windows Patch Analysis job one portion of the job attempts to use mapping on these same servers that in all other respects use the automation principal as they should (this is from a successful analysis in which the local mapping was enabled, the patch analysis fails at this step when the local mapping is removed):

       

      01/03/11 12:10:22.617 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: ***** New connection *****

      01/03/11 12:10:22.617 INFO2    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: remote command: BLPatchCheck2 0 -pt 1 -pt 13 -qf "C:/Program Files/BMC Software/BladeLogic/8.0/RSCD/tmp/WindowsCatalog_23606_92_SERVERNAME/windows-includes.lst"  -s "C:/Program Files/BMC Software/BladeLogic/8.0/RSCD/tmp/WindowsCatalog_23606_92_SERVERNAME/hfnetchk6b.xml" "C:/Program Files/BMC Software/BladeLogic/8.0/RSCD/tmp/WindowsCatalog_23606_92_SERVERNAME/shavlik_results.xml"

      01/03/11 12:10:22.633 DEBUG    rscd -  SERVERNAME 4628 SYSTEM (???): ???: Workstation name: WinSta0

      01/03/11 12:10:22.633 DEBUG    rscd -  SERVERNAME 4628 SYSTEM (???): ???: Desktop name: Default

      01/03/11 12:11:06.710 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: ReadPipe: Read = 57 Buf =  1Info: Started Scanning Machine Group.  Machine Count: 1 

      01/03/11 12:12:06.647 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: ReadPipe: Read = 91 Buf =  1Info: Started Scanning Machine SERVERNAME  Info: Completed Scanning Machine SERVERNAME  success 

      01/03/11 12:12:07.522 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

      01/03/11 12:12:07.522 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

      01/03/11 12:12:07.631 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

      01/03/11 12:12:07.631 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

      01/03/11 12:12:07.631 DEBUG    rscd -  1.2.3.4 4628

      BladeLogicRSCD@SERVERNAME->LocalAdministratorAccount@SERVERNAME:PrivilegeMapped

      (BLAdmins:BLAdmin): CM: win_nexec Process exit status 0