2 Replies Latest reply on Nov 13, 2009 7:46 AM by Morad.Labachi

    custom script : can't wake on lan targeted devices (landesk 8.8 sp3)

    Rookie

      Hi all,

       

      i can't wawke up devices using a custom script, i read the how to and i think there no

      setting mistakes.

       

      here is the script

       

      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ;
      ;  LANDesk(R) Management Suite Custom Script
      ;
      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

       

      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; JOBPARAM = Controls various configuration options on a per script basis. 
      ; The following is a sample of what this section might look like:
      ;
      ;    [JOBPARAM]
      ;    MAX_CUST_JOB_THREADS=120
      ;    MAX_MULTICAST_THREADS=10
      ;    MAX_MC_FAILURE_THREADS=60
      ;    STEPS=1
      ;    TASK_COMPLETION_ENABLED=FALSE
      ;
      [JOBPARAM]
      MAX_CUST_JOB_THREADS=120
      MAX_MULTICAST_THREADS=1
      MAX_MC_FAILURE_THREADS=60
      STEPS=1
      TASK_COMPLETION_ENABLED=FALSE

       

      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; PREMACHINE - Processed once at start of job.  Only the local (LOCxxx)
      ; commands can be used in this section.  Use this section as well for
      ; jobs with no associated machines.
      [PREMACHINE]

       


      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; MULTICAST - This section is used to control the targeted multicast.
      [MULTICAST]
      http://s-eaci-ld01/packages/temp.txt
      FILE_TTL_TARGET=172800
      FILE_TTL_SUBREP=1209600
      MIN_SLEEP=1
      MAX_SLEEP=200
      WAKE_ON_LAN=1
      WAIT_FOR_WAKE_ON_LAN=120
      WRITE_DOMAINS=0
      USE_DOMAINS_IN_REGISTRY=0
      OUTPUT_TARGETS=d:\mctargets.txt

       

      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; MACHINES - This section is run once for each machine in the target set. 
      ; Commands in this section will be processed in the order they are listed
      ; in the custom script.  This section supports both local (LOCxxx) and remote
      ; (REMxxx) commands.
      [MACHINES]

      ;remexecx=(command to execute)

      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; MACHINES_95 - After the commands in the MACHINES section have been processed
      ; this section will be processed for each machine that is a Windows* 9x system. 
      ; The type of computer is determined by the information returned by PDS when
      ; the computer is discovered. Like the MACHINES section this section can include
      ; both local (LOCxxx) and remote (REMxxx) commands.
      [MACHINES_95]

       


      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; MACHINES_NT - After the commands in the MACHINES section have been processed
      ; this section will be processed for each machine that is a Windows NT* or
      ; Windows* 2000 system.  The type of computer is determined by the information
      ; returned by PDS when the computer is discovered. Like the MACHINES section
      ; this section can include both local (LOCxxx) and remote (REMxxx) commands.
      [MACHINES_NT]

       


      ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
      ; POSTMACHINE - After all of the individual machines have been processed the
      ; commands in this section are processed.  If there were no machines that can
      ; be run in the scheduled task this section will not be processed. This section
      ; only supports the local (LOCxxxx) commands.
      [POSTMACHINE]

       

       

      i used 2 ways to wake up the pc

       

      1 : set the wake on lan to 1 in [multicast] section in custom script.

       

      2 : set the wake on lan in the properties of scheduled task (target devices)

           by shecking the wake on lane option.

       

      nothing work.

       

      The scheduled tasks made with "distribution packages" work fine and wake up pcs.

       

       

      The multicast log file created by the "OUTPUT_TARGETS=d:\mctargets.txt" return this

       

      Custom Job Processor, Multicast Job Information
      Task ID              : 1342
      Custom Script        : C:\DOCUME~1\EACI-M~1\LOCALS~1\Temp\task_1342\FlashPlayer_10.0.32.18.ini
      TMC Log Directory    : C:\Program Files\LANDesk\ManagementSuite\log
      File to be multicast : {none}
      Multicast Job Parameters ( 0 indicates that the default will be used)
          Max Threads      : 1
          TTL Target / Rep : 172800 / 1209600
          Sleep Min / Max  : 1 / 200
          Write Domains    : 0
          Use Reg Domains  : 0

       

      Target List
          Machine Name, IP Address, IP Subnet Mask
          D02DI0509697ECI, 158.166.98.27, 255.255.255.0

       

      Representatives List
          Machine Name, IP Address, IP Subnet Mask
          D02IE0900021ECI, 158.166.98.4, 255.255.255.0
          D02IE0900039ECI, 158.166.165.99, 255.255.255.0
          D02IE0900005ECI, 158.166.98.20, 255.255.255.0
          D02IE0900030ECI, 158.166.165.22, 255.255.255.0

       

      is it strange nothin about wake on lan in the log ????

       

      i strongly appreciate a help to understand.

       

      Morad.

        • 1. Re: custom script : can't wake on lan targeted devices (landesk 8.8 sp3)
          Rookie

          WOL setup at my site works fine. And to achieve this is what I had done:

           

          1. Created a batch file which includes nothing.

          2. Created a batch file software distribution package.

          3. Schedule a task that refers to this batch file package and make sure that you select Multicast (Cache only) - Multicast WOL delivery method.

           

          Hope this makes sense. Let me know if you need furthur assistance regarding this.

          • 2. Re: custom script : can't wake on lan targeted devices (landesk 8.8 sp3)
            Rookie

            Hi Vinay,

             

            thank you to reply.

             

            i reinstalled the service pack 3 and now i can wake up pc with scheduled custom script

            but only if i check the wake on lan option in "taget devices" in sheduled task properties.

             

            if i leave wake on lan unchecked, it does'nt work. i see the "multicast custom script" progress

            windows on the core server but no wake on lan packet is sent.

             

            your suggestion is exatly what i do to wake up pcs.

             

            but i would like to know if someone can wake pc with this line in the custom script

             

            WAKE_ON_LAN=1

             

            under the [MULTICAST] section

            and without checking this wake on lan option in the scheduled task.

             

            it worked very fine with landesk 8.5.

             

             

             

            Morad.