8 Replies Latest reply on Nov 23, 2009 7:08 AM by aadesk

    Cannot install any software on a remote site (Solved)

    Apprentice

      Hello,

       

      I just discovered a strange issue which i cannot explain.

       

      We got a little working site with about 10 computers and i cannot install any software remotely only on this site.

       

      The packages are working on other sites, even very far sites where the ping response time is higher dan 500ms.

       

      Each computer from this site can ping the core server and the core server can ping any of these computer.

       

      I installed some software from one of these computer by clicking on the MSI which is located in the package folder on the core server.

       

      So i really don't get it.

       

      The only thing i can say is that i needed to add the dns name of the server into the host file or the computer cannot found the core server on the network.

       

      I really getting lost in this issue, any help is highly appreciated.

       

      Thanks.

        • 1. Re: Cannot install any software on a remote site
          Master

          Hi,

           

          This is a helpful document on troubleshooting software deployments:

           

          http://community.landesk.com/support/docs/DOC-5096

           

          Also, I would look to make sure your Scheduler Service login has admin rights on those machines.

           

          I hope the document helps you.

          • 2. Re: Cannot install any software on a remote site
            Employee

             

             

            Also, I would look to make sure your Scheduler Service login has admin rights on those machines.

             

             

            Scheduler needs admin rights on the target machine? Sorry for this unholy spectacle of two LANDesk employees fighting it out in public, but this is a popular enough belief that I thought it might climb onto my soapbox. The only time the scheduler service needs admin rights on the client is when you're rolling out the agent using the push method. That's the one and only time. Once the agent is installed, there is never again a situation where the scheduler service account(s)  specified in configure services matter.

             

            Warning: last time this came up, I accepted a bet on this and won a bottle of wine...

            • 3. Re: Cannot install any software on a remote site
              Apprentice

              In fact we have a build for all the laptops and desktops. So that is not the issue.

               

              Also, if i take a laptop from this site and connect it on another site. I will be able to push the packages from the core server.

               

              So it is definitavely related to this site, but why ? no any clue.

               

              I tested with a SWD package and with a https link to the package instead of a \\coreserver\packages link and that only works.

               

              But still, only with a SWD package, no msi or executable does work.

               

              i also tested to reinstall the Landesk Client. Landesk client and core server are on the same version (SP3)

               

              I am really lost now

               

               

              P.S : Here is the log i found about another attemp to install with i package i know works on all system and computers (MSI package)

               

              Fri, 20 Nov 2009 09:03:10 File (\\CORESERVER\Packages\Default Applications\Citrix Xenapphosted\Citrix11.msi) is not in cache
              Fri, 20 Nov 2009 09:03:11 MSI Client Thread
              Fri, 20 Nov 2009 09:03:11 PackagePath:     [\\CORESERVER\Packages\Default Applications\Citrix Xenapphosted\Citrix11.msi]
              Fri, 20 Nov 2009 09:03:15 Installing MSI package

              Starting the installation of the MSI package

              Installing MSI package from '\\CORESERVER\Packages\Default Applications\Citrix Xenapphosted\Citrix11.msi' using options ' ALLUSERS=1 REBOOT=ReallySuppress'

              Failed to install the MSI package.

              Installing MSI package (-1 seconds)

              Fri, 20 Nov 2009 09:03:15 MSI result 80070653
              Fri, 20 Nov 2009 09:03:15 processing of package is complete, result -2147023277 (0x80070653 - code 1619)

              • 4. Re: Cannot install any software on a remote site
                phoffmann SupportEmployee

                So it's really down to this site? Interesting.

                 

                So the #1 culprit here would be closed ports on switches / routers - but if you look at the SERVICEHOST.LOG file (in "C:\Program Files\LANDesk\Shared Files\") on the client in question, it *SOUNDS* as if you do still get the relevant commands sent to the client (i.e. "install this piece of software") does go through.

                 

                What you CAN do is to enable a bit of extra logging...

                 

                ... if you think the problem is related to downloading files (LANDesk side) - open up a support case, and we'll cover the relevant debug-enabling options with you from there.


                However (and this is me assuming things, always a bit dangerous), it SEEMS that the file-download does work, and the install does start.

                 

                So the thing to do might be to enable MSI debugging (since it seems that you're launching an MSI) -- which is done in the following way (and HOPEFULLY will give a bit more info on what happens, but MSI-logs are not always as helpful as one would hope):

                - http://support.microsoft.com/kb/223300

                 

                Using the "voicewarmup" string should cover you in most cases .

                 

                - Paul Hoffmann

                LANDesk EMEA Technical Lead

                • 5. Re: Cannot install any software on a remote site
                  Employee

                  Here's a good definition of the MSI error code you're seeing. I don't believe there's any more debug info to be had from MSI logs. MSI can't access the package and that's all there is to it. My guess would be access rights. When you installed some software from one of these computer by clicking on the MSI, you proved that the account under which you were logged in can access the package. But that doesn't mean the system account can. When the LANDesk agent is installing the package, it's using the system account (aka localsystem). And unless you configure proper credentials under Configure - Preferred Server, the agent won't be able to access the package(*). I can see in your log that no preferred server is mentioned. Therefore, if it takes credntials to access your package share, the agent doesn't have them. You might think that, if clients take packages from the core server anyway, there is no reason to configure a preferred server. Except, there is a reason: credentials.

                   

                  I don't know why other sites don't have this problem. Perhaps you have a preferred definition for them. Or perhaps there is some subtle difference in permissions. But is seems pretty clear that in the session that you logged, the agent didn't have read access to the package share.

                   

                  (*) Preferred Server is the most obvious mechanism by which the agent can get the rights it needs to access your package share. There are 2 less obvious mechanisms. One, you might have granted read access to "domain computer". Two, your package share might be a NullSessionShare (unlikely because your security people would probably object).

                   

                  ps 1 - One thing you say is that a url path works, but only for an swd package. The reason why a url path doesn't work for msi or for executable is probably that you use run from source and that the packages aren't single-file.

                   

                  ps 2 - As said, I believe you are installing with the "run from source" option. There may perfectly valid reasons for doing so, but I'll take the liberty to at least ask the question: the environment that you describe (small branch office without a local server?) is exactly the one where a feature known as peer download would be very valuable. If all 10 computers at that remote site need the same package, all 10 of them will download it from your main site. If you used "download from source" instead, one machine can do the downloading and the other 9 will pick it up from the first machine's cache.

                  • 6. Re: Cannot install any software on a remote site
                    Apprentice

                    Okay, i think i found the issue.

                     

                    On this site, for obvious reasons, the ping from the pc to the core server doesn't work if you don't have the record into the windows xp host file.

                     

                    And that is just the issue.

                     

                    Windows shows this message.

                     

                    Error Message: The Redirector Failed to Determine the Connection Type

                     

                    So, in other words, since my packages are running from source or download from source, the computers cannot recognise which type of connection it is and the package install doesn't start.

                     

                    http://support.microsoft.com/kb/267934/en

                     

                    I have passed the netwok issue to my colleague and we will test further.

                    • 7. Re: Cannot install any software on a remote site
                      Master

                      jan.buelens wrote:

                       

                       

                       

                      Also, I would look to make sure your Scheduler Service login has admin rights on those machines.

                       

                       

                      Scheduler needs admin rights on the target machine? Sorry for this unholy spectacle of two LANDesk employees fighting it out in public, but this is a popular enough belief that I thought it might climb onto my soapbox. The only time the scheduler service needs admin rights on the client is when you're rolling out the agent using the push method. That's the one and only time. Once the agent is installed, there is never again a situation where the scheduler service account(s)  specified in configure services matter.

                       

                      Warning: last time this came up, I accepted a bet on this and won a bottle of wine...

                      No worries Jan, Im on the Inventory Team so I am definatly not a Software Distribution specialist; I just recall it being said often

                      • 8. Re: Cannot install any software on a remote site
                        Apprentice

                        Okay, the solution is confirmed.

                         

                        There was an issue with with the DNS configuration. i cleaned the host files and testes again, i can distribute all software.

                         

                        So in other words, run from source doesn't work if the core server details is entered in the Windows host file.