4 Replies Latest reply on Nov 26, 2010 7:56 AM by suderman

    Problems with Software deployment

    Rookie

      Hello,

       

      I've been trying to use Landesk 9 for Software deployment but each time I create a package and schedule it to install it doesn't work as expected.

      On some devices it works but on most devices it returns error after I start the task.

       

      first I've made a distribution package which in this case is simple MSI package then I've scheduled a task and assign divices to it. 

      In task properties I'm using Standard policy-supported push distribution as delivery method.

       

      Task is starting and on client devices task log I see errors like these:

       

      Thu, 25 Nov 2010 09:01:45 Checking preferred server path \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi instead of \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi
      Thu, 25 Nov 2010 09:01:46 Path \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi was redirected to \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi
      Thu, 25 Nov 2010 09:01:46 File (\\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi) is not in cache
      Thu, 25 Nov 2010 09:01:46 Checking preferred server path \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi instead of \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi
      Thu, 25 Nov 2010 09:01:46 Path \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi was redirected to \\fileserver\gpo\Java\1.6_20\x32\jre1.6.0_20.msi
      Thu, 25 Nov 2010 09:01:48 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 25 Nov 2010 09:01:48 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 25 Nov 2010 09:01:51 Connect failed (0) in ConnectToValidAddress (10.213.14.69:19074)
      Thu, 25 Nov 2010 09:01:51 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 25 Nov 2010 09:01:51 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 25 Nov 2010 09:01:54 Connect failed (0) in ConnectToValidAddress (10.213.14.69:19074)
      Thu, 25 Nov 2010 09:01:54 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 25 Nov 2010 09:01:54 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 25 Nov 2010 09:01:57 Connect failed (0) in ConnectToValidAddress (10.213.14.69:19074)
      Thu, 25 Nov 2010 09:01:57 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 25 Nov 2010 09:01:58 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 25 Nov 2010 09:02:00 Connect failed (0) in ConnectToValidAddress (10.213.14.69:19074)
      Thu, 25 Nov 2010 09:02:00 Performing TCP connection with a timeout of -1 milliseconds
      Thu, 25 Nov 2010 09:02:01 Performing TCP connection with a timeout of 2500 milliseconds
      Thu, 25 Nov 2010 09:02:03 Connect failed (0) in ConnectToValidAddress (10.213.14.69:19074)
      Thu, 25 Nov 2010 09:02:03 processing of package is complete, result -2147467259 (0x80004005 - code 16389)

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

       

      What is strange that ip address that the client is trying to connect to: ConnectToValidAddress (10.213.14.69:19074)
      is not the correct one. This ip address belongs to completely other workstation which is also managed by Landesk but have nothing to do with deployment of packages.

      As I understand it should connect to Server where MSI package is located, in my case \\fileserver but instead it's connecting to some other computer.

      Is there some property in Landesk that may redirects the client to other computer ? Fileserver with msi package is in different Vlan but I think it shoudn't be a problem.

       

      Can anyone could help me to make it work ?

       

      Thanks.

        • 1. Re: Problems with Software deployment
          zman Master

          It is trying to obtain the file from a peer. LANDesk first looks in the local workstation cache, then a peer, then preferred server, then original server. It appears that it is having a problem with the peer. You could reinstall the client on the peer 10.213.14.69, delete the file from the peer's cache, or change the delivery method to run from source.

          1 of 1 people found this helpful
          • 2. Re: Problems with Software deployment
            Rookie

            Hello,

             

            thanks for Your answer.

             

            After changing in delivery method to run from source it's still the same. It's still trying to connect to peer .

            Our network configuration (firewall) disllaows connections between workstations so anyway it won't work .

             

            Is it possible to change completely this behaviour ? to force always to connect to the preffered server first ?

            • 3. Re: Problems with Software deployment
              zman Master

              My bad it will still try and download from peer.  When you say firewall won't allow connections between workstations is this a workstation based firewall? You could trust sdclient.exe and rainstall.exe, If you can't have workstations communicating ???? then I'm wondering if you just disable the LANDesk Targeted Multicast service on your clients it may work.

              • 4. Re: Problems with Software deployment
                Rookie

                It seems to be better after I have upgraded all clients to 9 SP2. Before only Core and Console has been upgraded.

                What I have done also was adding a range of IP addresses into Preffered Server properties.

                 

                Thanks.