1 2 Previous Next 21 Replies Latest reply on Mar 12, 2010 2:56 PM by Alessandro Iacopetti

    Trying to automate RSCD Windows agent upgrade

    Vinnie Lima

      Hi,

       

      Trying to use BL to apply RSCD 7.6.0 hotfix 132 on all systems which are currently at RSCD 7.6.0 115.  I dont want to use the Bulk Agent Installer if I dont have to, rather create a deploy job via BL natively.

       

      I created the Install Shield silent response file (iss) per the instructions on the Bulk agent installer. It looks like the item below:

       

      [InstallShield Silent]
      Version=v7.00
      File=Response File
      [File Transfer]
      OverwrittenReadOnly=NoToAll
      [{10C11452-9CAD-4368-A826-41B486B85A0D}-DlgOrder]
      Dlg0={10C11452-9CAD-4368-A826-41B486B85A0D}-AskOptions-0
      Count=2
      Dlg1={10C11452-9CAD-4368-A826-41B486B85A0D}-SdFinish-0
      [{10C11452-9CAD-4368-A826-41B486B85A0D}-AskOptions-0]
      Result=1
      Sel-0=1
      Sel-1=0
      [Application]
      Name=BMC BladeLogic RSCD Agent
      Version=7.6.0
      Company=BMC BladeLogic
      Lang=0009
      [{10C11452-9CAD-4368-A826-41B486B85A0D}-SdFinish-0]
      Result=1
      bOpt1=0
      bOpt2=0

       

       

      The job ran  during staging and simulation, but then failed. Looking at the Transaction log, the following popped up:

       

      11/13/09 16:10:52.274 INFO     bldeploy - [1][] Executing command: ""1444.1\WindowsAgent-release_7.6.0_hotfix-132.exe\\setup.exe" /s /SMS /f1"C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\1444.1\WindowsAgent-release_7.6.0_hotfix-132-answer.iss" /f2"C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\\setup.log""
      11/13/09 16:10:52.274 DEBUG    bldeploy - [1][] chdir to PkgDir: 'C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\'
      11/13/09 16:10:52.274 DEBUG    bldeploy - Replacing parameters in file /C/temp/stage/Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1/1444.1/WindowsAgent-release_7.6.0_hotfix-132-answer.iss using tmp file C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\response.tmp
      11/13/09 16:10:52.337 DEBUG    bldeploy - [1][] exeFullPath = (null), CmdLine = "C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\bldeploycmd.bat", workingDir = NULL
      11/13/09 16:10:52.446 INFO     bldeploy - [1][] [stdout: 1]   

       

      C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1>chcp 1252  1>NUL

       


      11/13/09 16:10:52.759 INFO     bldeploy - [1][] [stdout: 1]   

       

      C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1>"1444.1\WindowsAgent-release_7.6.0_hotfix-132.exe\\setup.exe" /s /SMS /f1"C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\1444.1\WindowsAgent-release_7.6.0_hotfix-132-answer.iss" /f2"C:\temp\stage\Upgrade-Windows2003-RSCD-Agent-to-7.6.0.132-1445.1-304.1\\setup.log"

       


      11/13/09 16:10:52.759 WARN     bldeploy - [1][] [stderr: 1]     The directory name is invalid.

       

      Any suggestions before I start diving into this?  C:\temp exists. Obviously the temp directory structure has been wiped clean due to the job failing.

       

      Thanks,

      Vinnie.

        • 1. Re: Trying to automate RSCD Windows agent upgrade
          Bill Robinson

          You can check some options to leave the staging area on job failure.

           

          Also, try doing this as a file deploy per the BMCBladeLogicInstallation.pdf as opposed to a custom software deploy.

          • 2. Re: Trying to automate RSCD Windows agent upgrade
            Vinnie Lima

            That worked.  Get a funky error whenever the job is run:

             

            Info    Nov 13, 2009 4:59:21 PM    Copy //emda-nbp-uea26/E/DESIREFED/7.6/Hotfix/76-Agent/WindowsAgent-release_7.6.0_hotfix-132-answer.iss -> /c/tmp/WindowsAgent-release_7.6.0_hotfix-132-answer.iss ... Done
            Info    Nov 13, 2009 4:59:31 PM    Copy //emda-nbp-uea26/E/DESIREFED/7.6/Hotfix/76-Agent/WindowsAgent-release_7.6.0_hotfix-132.exe -> /c/tmp/WindowsAgent-release_7.6.0_hotfix-132.exe ... Done
            Info    Nov 13, 2009 4:59:31 PM    + /c/tmp/job_305.1_postcmd.bat
            Info    Nov 13, 2009 4:59:43 PM    Exit Code 0
            Error    Nov 13, 2009 4:59:32 PM    The filename, directory name, or volume label syntax is incorrect.

             

            Although it upgrades the agent just fine.

             

            Thanks!!!

            • 3. Re: Trying to automate RSCD Windows agent upgrade
              Bill Robinson

              That error looks like it's coming from the agent installer itself, not the bladelogic deploy, googling shows it to be a windows error, not a bladelogic error.

              • 4. Re: Trying to automate RSCD Windows agent upgrade
                Vinnie Lima

                Bill,

                 

                I am still trying to do this in a "proper" way of deploying an installshield package (even though your file deploy job works).  I am running into errors which seem strange.

                 

                1)  Created a Depot InstallShield package with the following parameters for install command:

                 

                "??SOURCE??" -a -s -f1"??_INSTALL_RESPONSEFILE??"

                 

                Where the response file is uploaded into the Depot from:

                 

                //emda-nbp-uea21.corp.csa.ic.gov/opt/bmc/bcas/storage/installables/1449.1/WindowsAgent-release_7.6.0_hotfix-132-answer.iss

                 

                2) Created a BLPackage from an Audit exception result for this one system.  Executed the BLPackage to be deployed on the target system.

                 

                3) The install failed. Looked at the transaction log detail on that system and found the following:

                 

                 

                11/16/09 10:58:22.011 DEBUG    bldeploy - [1][] exeFullPath = (null), CmdLine = "C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1\bldeploycmd.bat", workingDir = NULL
                11/16/09 10:58:22.462 INFO     bldeploy - [1][] [stdout: 1]   

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>chcp 1252  1>NUL


                11/16/09 10:58:23.013 INFO     bldeploy - [1][] [stdout: 1]   

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>"1449.1\WindowsAgent-release_7.6.0_hotfix-132.exe" -a -s -f1"C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1\1449.1\WindowsAgent-release_7.6.0_hotfix-132-answer.iss"


                11/16/09 10:59:42.702 DEBUG    bldeploy - [1][] In RunProcess: exitCode = -2147213312
                11/16/09 10:59:42.702 ERROR    bldeploy - [1][] Command returned non-zero exit code: -2147213312

                 

                 

                4) I chose as part of the job to leave the bits in place so I can research if it failed.  I manually executed the command per the reference above but the agent is still not upgraded with the hotfix:

                 

                C:\temp\stage>cd Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>dir
                Volume in drive C has no label.
                Volume Serial Number is B83E-B9A5

                 

                Directory of C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.
                11.16-10.55.21.508-0500-1452.1-316.1

                 

                11/16/2009  10:58 AM    <DIR>          .
                11/16/2009  10:58 AM    <DIR>          ..
                11/16/2009  11:07 AM    <DIR>          1449.1
                11/16/2009  10:58 AM               983 bldeploy.xml
                11/16/2009  10:58 AM               239 bldeploycmd.bat
                11/16/2009  10:58 AM                 0 doNOTdeleteSupportFilesUsed.txt
                11/16/2009  10:58 AM                 0 params.txt
                11/16/2009  10:58 AM               540 response.tmp
                11/16/2009  10:59 AM               393 Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0
                .132-@2009.11.16-10.55.21.508-0500-1452.1-316.1.cfg
                               6 File(s)          2,155 bytes
                               3 Dir(s)   3,963,793,408 bytes free

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1\bldeploycmd.bat

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>chcp 1252  1>NUL

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1>"1449.1\WindowsAgent-release_7.6.0_hotfix-132.exe" -a -s -f1"C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21.508-0500-1452.1-316.1\1449.1\WindowsAgent-release_7.6.0_hotfix-132-answer.iss"

                 

                C:\temp\stage\Upgrade-msfe-nbp-uea09-to-RSC-agent-7.6.0.132-@2009.11.16-10.55.21
                .508-0500-1452.1-316.1>

                 

                Thoughts??

                 

                Thanks,

                Vinnie

                • 5. Re: Trying to automate RSCD Windows agent upgrade
                  Bill Robinson

                  The file deploy job is the 'proper' method, meaning that it's the documented method of doing agent upgrades (per the installation pdf).

                   

                  because you are restarting the agent when you run the upgrade, you maybe cutting yourself off if you use another job type. It could also be that the installer exe does not like the long path.  if you leave the files there for the failed job, can you run the bldeploycmd.bat from a console/rdp login to the server?

                  • 6. Re: Trying to automate RSCD Windows agent upgrade
                    Vinnie Lima

                    Ok. Fair enough.

                     

                    Ended up trying to do a manual agent install to ensure it's not a local system issue. Ends up that the manual interactive install was complaining that a RSCD library was innacessible.

                     

                    I ended up having to manually kill the RSCD.exe process and then the install worked.

                     

                    Chalk this one up to platform issue.

                     

                    Thanks for your help.

                     

                    Vinnie

                    • 7. Re: Trying to automate RSCD Windows agent upgrade

                      Follow the instructions in the installation guide on how to create a silent install file:

                       

                      Creating a Response File for Windows Agents
                      Use this procedure to record your responses to prompts from the installation program. Your
                      responses are stored in a response file.
                      Procedure 1 Copy rscd<version>.exe (the RSCD agent installation program) to
                      <WINDIR>\Temp, where <WINDIR> is typically C:\winnt or C:\Windows.
                      2 From the command line, connect to <WINDIR>\Temp.
                      3 From the command line, enter
                      rscd<version> –a –r
                      –f1<WINDIR>\Temp\version-install_type.iss
                      where version-install_type.iss is the name of response file you are creating
                      (for example, specify 7.4.1-install.iss as the name of the response file for initial installs
                      of 7.4.1 or 7.4.1-upgrade for upgrades to 7.4.1 from earlier versions of the agent).
                      The installation program for the RSCD agent opens. Use the program to perform an
                      initial install or an upgrade of the RSCD agent, selecting the options that are appropriate
                      for your site.

                       

                      then there is a Knowledge Base article which explains the procedure to upgrade agents through Bladelogic: 20010817

                       

                      Question
                      What is the best way to upgrade Bladelogic windows RSCD agents for sure?
                      Product
                      Bladelogic
                      Environment
                      Windows
                      Answer
                      What is the best way to upgrade Bladelogic windows RSCD agents for sure?
                      Bladelogic
                      Windows
                      There are bugs with agentctl which could result in the agent not stopping  correctly and the upgrade to fail.
                      In particular, while agentctl is running, some libraries might still be  locked by Windows. Rebooting the  server after the upgrade might solve the issue, but the best solution is to make  sure the agent is really stopped.
                      The following steps will describe how to build a job to upgrade Windows Agents.
                      Please note, before building the job, you will need to record a  silent install  file.
                      1. Create a new File Deploy Job
                      2. Add the following files to the deploy job
                      RSCD.exe
                      RSCD.iss
                      Sleep.exe
                      Upgrade.bat
                      3. Add the following as the post command for the deploy job
                      "%PROGRAMFILES%\BladeLogic\RSC\agentctl" –b exec  <path_to_upgrade.bat>
                      Attached is a sample upgrade.bat script.
                      The upgrade.bat script will take care of stopping the agent using windows kill commands and make sure  the agent is really stopped, before running the upgrade.

                       

                      upgrade.bat:

                      -------------------

                      "%PROGRAMFILES%\BladeLogic\RSC\agentctl.exe" stop
                      "%SYSTEMDRIVE%\tmp\blade\sleep" 40

                       

                      :KILLMGR
                      VER | FIND "2000" > nul
                      IF %ERRORLEVEL% == 0 GOTO VER_2000
                      TASKKILL /IM RSCD.exe /F
                      GOTO UNINST

                       

                      :VER_2000
                      KILL -F RSCD.exe

                       

                      :UNINST
                      "%SYSTEMDRIVE%\temp\RSCD.exe  /NONETSTAT -a -s -f1”"%SYSTEMDRIVE%\temp\RSCD.iss
                      "%SYSTEMDRIVE%\tmp\blade\sleep" 40
                      "%PROGRAMFILES%\BladeLogic\RSC\agentctl.exe" start

                      -------------------

                      • 8. Re: Trying to automate RSCD Windows agent upgrade

                        Hi LB,

                         

                        I couldn't get it to work. I copied sleep from somewhere in OM, but I think that is an nsh sleep that requires cygwin libraries to work.

                         

                        Where did you get your sleep command from?

                         

                        Mark.

                        • 9. Re: Trying to automate RSCD Windows agent upgrade

                          C:\Documents and Settings\joe>cd C:\Program Files\BladeLogic\OM\bin

                           

                          C:\Program Files\BladeLogic\OM\bin>sleep.exe 2 && echo done
                          done

                          • 10. Re: Trying to automate RSCD Windows agent upgrade

                            Sorry, just re-read your message again, I see your point.

                             

                            sleep.exe was attached to the original KB article. It's now gone.

                             

                            You can get it from the windows resource kit.

                             

                            http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en

                            • 11. Re: Trying to automate RSCD Windows agent upgrade
                              Vinnie Lima

                              Hey Guys - revisiting this.

                               

                              I created a File Job to upgrade to 7.6.0.207 agent, incorporated the upgrade.bat file (some minor mods to reference the right location for sleep.exe).

                               

                              Here's what the job log says:

                               

                              Info    Feb 2, 2010 4:36:51 PM    Exit Code 0
                              Error    Feb 2, 2010 4:36:50 PM    The system cannot find the path specified.
                              Info    Feb 2, 2010 4:36:50 PM    + /C/temp/blade/job_171.4_postcmd.bat

                              Info    Feb 2, 2010 4:36:49 PM    Copy //emda-nbp-uea26/E/DESIREFED/7.6/Hotfix/76-207-Agent/upgrade.bat -> /C/temp/blade/upgrade.bat ... Done
                              Info    Feb 2, 2010 4:36:49 PM    Copy //emda-nbp-uea26/E/DESIREFED/7.6/Hotfix/76-207-Agent/WindowsAgent-release_7.6.0_hotfix-207-setup.iss -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207-setup.iss ... Done
                              Info    Feb 2, 2010 4:36:48 PM    Copy //emda-nbp-uea26/E/DESIREFED/7.6/Hotfix/76-207-Agent/WindowsAgent-release_7.6.0_hotfix-207.exe -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207.exe ... Done

                               

                              I can't find the /C/temp/blade/job_171.4_postcmd.bat for the life of me on the target server.  I can confirm that under /C/temp/blade the following files do exist:

                               

                              upgrade.bat

                              WindowsAgent-release_7.6.0_hotfix-207-setup.iss

                              WindowsAgent-release_7.6.0_hotfix-207.exe

                               

                              Am I missing something?  Seems like the app server is not deploying it's own bat file for a weird reason, so the "upgrade.bat" doesnt even get executed.

                               

                              Thanks.

                              Vinnie

                              • 12. Re: Trying to automate RSCD Windows agent upgrade
                                Bill Robinson

                                you've got a problem here: "*Error    Feb 2, 2010 4:36:50 PM    The system cannot find the path specified." w/ something. 

                                 

                                what's the STAGING_DIR set to on the target?

                                • 13. Re: Trying to automate RSCD Windows agent upgrade
                                  Vinnie Lima

                                  Ok corrected some errors on the "upgrade.bat" file (see below for content).  Seems that the instruction a few posts above for the Post Command option:

                                   

                                  "C:\Program Files\BMC BladeLogic\RSC\agentctl" –b exec C:\temp\stage\upgrade.bat

                                   

                                  Is invalid as I get the error:

                                   

                                  Info    Feb 2, 2010 5:56:02 PM    Exit Code 0
                                  Error    Feb 2, 2010 5:56:02 PM    list         List running agents
                                  Error    Feb 2, 2010 5:56:02 PM    exec cmd     Stop the agent, run cmd, and then start agent
                                  Error    Feb 2, 2010 5:56:02 PM    restart      Stop and then start the agent
                                  Error    Feb 2, 2010 5:56:02 PM    kill         Forcefully stop the agent and its sub-processes
                                  Error    Feb 2, 2010 5:56:02 PM    stop         Gently stop the agent and its sub-processes
                                  Error    Feb 2, 2010 5:56:02 PM    start        Start the agent if not already started
                                  Error    Feb 2, 2010 5:56:02 PM    -v           Verbose output
                                  Error    Feb 2, 2010 5:56:02 PM    -r           Pass -r flag (retry on busy) to agent starting (implies -f)
                                  Error    Feb 2, 2010 5:56:02 PM    -q           Quiet mode on starting
                                  Error    Feb 2, 2010 5:56:02 PM    -f           Force agent start even if already started
                                  Error    Feb 2, 2010 5:56:02 PM    -b           If restarting, restart in background
                                  Error    Feb 2, 2010 5:56:02 PM    list | start | stop | kill | restart | exec cmd [args]
                                  Error    Feb 2, 2010 5:56:02 PM    Usage: agentctl [-b] [-f] [-q] [-r] [-v]
                                  Info    Feb 2, 2010 5:56:00 PM    + /C/temp/blade/job_171.9_postcmd.bat
                                  Info    Feb 2, 2010 5:56:00 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/WindowsAgent-release_7.6.0_hotfix-207.exe -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207.exe ... Done
                                  Info    Feb 2, 2010 5:55:53 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/WindowsAgent-release_7.6.0_hotfix-207-setup.iss -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207-setup.iss ... Done
                                  Info    Feb 2, 2010 5:55:53 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/upgrade.bat -> /C/temp/blade/upgrade.bat ... Done

                                   

                                  So I changed it to be:

                                   

                                  "C:\Program Files\BMC BladeLogic\RSC\agentctl –b exec C:\temp\stage\upgrade.bat"

                                   

                                  And the log says:

                                   

                                  Info    Feb 2, 2010 5:58:20 PM    Exit Code 0
                                  Info    Feb 2, 2010 5:58:20 PM    + /C/temp/blade/job_171.10_postcmd.bat
                                  Error    Feb 2, 2010 5:58:20 PM    The filename, directory name, or volume label syntax is incorrect.
                                  Info    Feb 2, 2010 5:58:20 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/WindowsAgent-release_7.6.0_hotfix-207.exe -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207.exe ... Done
                                  Info    Feb 2, 2010 5:58:14 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/WindowsAgent-release_7.6.0_hotfix-207-setup.iss -> /C/temp/blade/WindowsAgent-release_7.6.0_hotfix-207-setup.iss ... Done
                                  Info    Feb 2, 2010 5:58:13 PM    Copy //emda-nbp-uea21/opt/bmc/bcas/storage/agents/windows/upgrade.bat -> /C/temp/blade/upgrade.bat ... Done

                                   

                                  But nothing is executed on the remote system. The files are placed, again, and If i run the "upgrade.bat" interactively on the target, the upgrade works just fine.  I still can't find the job_171.10_postcmd.bat script anywhere on the target....

                                   

                                  Below is the upgrade.bat script:

                                   

                                  "%PROGRAMFILES%\BMC BladeLogic\RSC\agentctl.exe" stop
                                  "%PROGRAMFILES%\Windows Resource Kits\Tools\sleep" 40

                                   

                                  :KILLMGR
                                  VER | FIND "2000" > nul
                                  IF %ERRORLEVEL% == 0 GOTO VER_2000
                                  TASKKILL /IM RSCD.exe /F
                                  GOTO UNINST

                                   

                                  :VER_2000
                                  KILL -F RSCD.exe

                                   


                                  :UNINST
                                  %SYSTEMDRIVE%\temp\blade\WindowsAgent-release_7.6.0_hotfix-207.exe /NONETSTAT -a -s -f1%SYSTEMDRIVE%\temp\blade\WindowsAgent-release_7.6.0_hotfix-207-setup.iss
                                  "%PROGRAMFILES%\Windows Resource Kits\Tools\sleep" 40
                                  "%PROGRAMFILES%\BMC BladeLogic\RSC\agentctl.exe" start

                                  • 14. Re: Trying to automate RSCD Windows agent upgrade
                                    Bill Robinson

                                    where'd you get the upgrade.bat file from, or did you just create it?

                                     

                                    I'm able to run the agentctl ok:

                                     

                                    C:\Documents and Settings\brobinson>"c:\Program Files\BMC BladeLogic\RSC\agentct
                                    l.exe" -b exec echo foo

                                    C:\Documents and Settings\brobinson>Bladelogic RSCD Agent service stopped
                                    foo
                                    The BladeLogic RSCD Agent service is starting.
                                    The BladeLogic RSCD Agent service was started successfully.

                                     

                                     

                                    I wonder if your stop in the update.bat is screwing stuff up

                                     

                                    can you take the update.bat out of there and make your post command:

                                     

                                    "%PROGRAMFILES%\BMC BladeLogic\RSC\agentctl.exe" -b exec "%SYSTEMDRIVE%\temp\blade\WindowsAgent-release_7.6.0_hotfix-207.exe" /NONETSTAT -a -s -f1"%SYSTEMDRIVE%\temp\blade\WindowsAgent-release_7.6.0_hotfix-207-setup.iss"


                                    and run that job?

                                    1 2 Previous Next