2 Replies Latest reply on Oct 19, 2009 9:50 AM by Admddi

    WSH packages not being pushed to clients

    Rookie

      Hi there,

       

      I'm getting a weird issue with WSH packages all of a sudden and could use some brain power.

       

      Core server : 8.8 SP3

      Clients : same as core

      Delivery method : tried both Run from source and Download from source

       

      Up until this morning, I've had no issue pushing WSH packages with vbs scripts. However, it seems that my server is refusing to push any WSH package.

      I was trying to add a very simple WSH package containing one VBS file which just creates a Registry key in HKLM, nothing fancy. The scripts is as follows :

       

      Dim WSHShell

      Set WSHShell = WScript.CreateObject("WScript.Shell")

      WSHShell.RegWrite "HKLM\Software\McNeel\RhinoLM\Zoo4", "Zoo4"

       

      Coudln't be any simpler really.

       

      When I push the package to a client, it fails and goes to "The client does not support the features required by the specified package and cannot be downgraded".

      The task log on the core server is as follows :

       

      10/19/2009 5:03:14 PM : loading distribution task (189) for global scheduler client.
      10/19/2009 5:03:14 PM : performing hash calculations on package : Reg_Rhino
      10/19/2009 5:03:15 PM : Information: client version LDMS7_or_earlier does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8_5 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8_6_1 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8_7 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8_7_5 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Information: client version LDMS8_7_7 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Core name obtained from database : WALDECK2
      10/19/2009 5:03:15 PM : Information: client version LDMS8_8 does not support Windows Script Host packages
      10/19/2009 5:03:15 PM : Core name obtained from database : WALDECK2
      10/19/2009 5:03:17 PM :          189 : Updating allowed machines if needed.
      10/19/2009 5:03:17 PM :          189 : Calling method to perform remote operations.
      10/19/2009 5:03:17 PM :          189 : Before hasherize of C:\Program Files\LANDesk\ManagementSuite\landesk\files\WALDECK2-task-189.pmf
      10/19/2009 5:03:17 PM :          189 : After hasherize
      10/19/2009 5:03:17 PM : Core name obtained from database : WALDECK2
      10/19/2009 5:03:17 PM :          189 : Troubleshooting guidelines
      The global scheduler has delegated task 189.
        The task was delegated by (source): WALDECK2
        This task was delegated to (dest) : WALDECK2
        Using GlobalTask_Idn              : 53
      This delegation was done by creating an entry in the GlobalTask table on the destination core (the task id is provided above).
      The Entry in the GlobalTask should have set to state column to 1 to indicate that it is a new task and should be processed.
      The scheduler service should detect and process this delegated task, please check scheduler service log on the destination core to see if it successfully detected the GlobalTask entry.

      10/19/2009 5:03:17 PM :          189 : Waiting for task 189 from WALDECK2 to complete on WALDECK2.  Checking every 10 seconds, inactivity timeout after 1200 seconds.
      Mon, 19 Oct 2009 17:03:19 Using user specified port 12174 for remote execute
      Mon, 19 Oct 2009 17:03:19 Using user specified read timeout 300000 for remote execute
      Mon, 19 Oct 2009 17:03:19 1 machines targeted to task
      Mon, 19 Oct 2009 17:03:22 Creating a pool of 1 worker threads
      Mon, 19 Oct 2009 17:03:22 Worker thread started
      Mon, 19 Oct 2009 17:03:22 Thread pool created
      Mon, 19 Oct 2009 17:03:22 Processing package
      Mon, 19 Oct 2009 17:03:22 Item placed in the Machine Node Queue
      Mon, 19 Oct 2009 17:03:22 Thread is activating, 1 active threads
      Mon, 19 Oct 2009 17:03:22 Queue Item 77480640: Preparing to process node
      Mon, 19 Oct 2009 17:03:22 processing machine STARCK
      Mon, 19 Oct 2009 17:03:28 Remote execute of application 'C:\Program Files\LANDesk\LDClient\fileversion.exe', params '"C:\Program Files\LANDesk\LDClient\sdclient.exe"' on STARCK (b93add0a)
      Mon, 19 Oct 2009 17:03:31 sdclient file version characterized as LDMS8_8
      Mon, 19 Oct 2009 17:03:31 [STARCK] : 1078
      Mon, 19 Oct 2009 17:03:31 Thread has completed processing, 0 active threads remaining
      Mon, 19 Oct 2009 17:03:31 The Machine Node Queue is now empty
      Mon, 19 Oct 2009 17:03:31 Shutting down thread pool
      Mon, 19 Oct 2009 17:03:31 The Machine Node Queue is now empty
      Mon, 19 Oct 2009 17:03:31 Thread pool shutdown
      Mon, 19 Oct 2009 17:03:31 Task complete, status 8
      10/19/2009 5:03:37 PM :          189 : WALDECK2 has completed task with status 5 (Delegated task complete.)
      10/19/2009 5:03:37 PM :          189 : Proxy work thread for core WALDECK2 is complete.
      10/19/2009 5:03:37 PM :          189 : Thread is complete, synchronizing status information.
      10/19/2009 5:03:37 PM : Warning: No link entries were returned.  No tasks will be synchronized
      10/19/2009 5:03:37 PM : Warning: No link entries were returned.  No tasks will be synchronized
      10/19/2009 5:03:37 PM :          189 : Remote operations complete, synchronizing status information.
      10/19/2009 5:03:37 PM :          189 : Task complete, returning status 7

       

      The client as we can see is indeed recognized as a 8.8 client, but this is what is bothering me : "Information: client version LDMS8_8 does not support Windows Script Host packages" O_o

       

      If anyone has an idea on this one, I'll gladly take it, doesn't make any sense to me, especially since it was still working fine this morning.