16 Replies Latest reply on Oct 13, 2016 11:33 AM by bkilbourne

    Custom Package Help

    dv1

      i'm trying to use Patch Manager to install a couple of packages. I get as far as the Install folder getting onto the client, but the exe or msi never installs. Help?

        • Re: Custom Package Help
          I LIKE EGGS

          Hi there, iv never used patch manager but you might just need to run this as administrator to install wsi file types

          • Re: Custom Package Help
            I LIKE EGGS

            Ok, done alittle digging and you might find your answerrs here: [VIDEO] Package Creation Using Patch Manager

            around 13 minutes in I could be wrong through

              • Re: Custom Package Help
                dv1

                I've watched this video a couple of times and it has helped in moving along, but i just cant get the file to install. i see it download, then i see it launch in task manager, but that's it. the file never installs.

              • Re: Custom Package Help
                I LIKE EGGS

                have you checked the event viewer

                And check the events when you tired to install the msi file?

                • Re: Custom Package Help
                  dv1

                  i tried installing the msi using msiexec and it installs when i use the /i command. i've been reading the threads and in Patch Manager the /i shouldn't be needed.

                   

                   

                   

                  i went thru the event log and this is what i see

                   

                   

                  - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

                   

                   

                  - <System>

                   

                   

                  <Provider Name="Windows Error Reporting" />

                   

                   

                  <EventID Qualifiers="0">1001</EventID>

                   

                   

                  <Level>4</Level>

                   

                   

                  <Task>0</Task>

                   

                   

                  <Keywords>0x80000000000000</Keywords>

                   

                   

                  <TimeCreated SystemTime="2016-03-02T04:07:54.000000000Z" />

                   

                   

                  <EventRecordID>11732</EventRecordID>

                   

                   

                  <Channel>Application</Channel>

                   

                   

                  <Computer>xxxxxxxxxxxxx</Computer>

                   

                   

                  <Security />

                   

                  </System>

                   

                  - <EventData>

                   

                   

                  <Data />

                   

                   

                  <Data>0</Data>

                   

                   

                  <Data>WindowsUpdateFailure3</Data>

                   

                   

                  <Data>Not available</Data>

                   

                   

                  <Data>0</Data>

                   

                   

                  <Data>7.6.7601.19116</Data>

                   

                   

                  <Data>80070667</Data>

                   

                   

                  <Data>140C2306-2CDD-45B5-81C4-9DA74F687E01</Data>

                   

                   

                  <Data>Install</Data>

                   

                   

                  <Data>2</Data>

                   

                   

                  <Data>0</Data>

                   

                   

                  <Data>80070667</Data>

                   

                   

                  <Data>EminentWare Extension Pack - CB</Data>

                   

                   

                  <Data>{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}</Data>

                   

                   

                  <Data>0</Data>

                   

                   

                  <Data />

                   

                   

                  <Data />

                   

                   

                  <Data />

                   

                   

                  <Data>0</Data>

                   

                   

                  <Data>565780d2-e02c-11e5-800a-5c260a0c68c4</Data>

                   

                   

                  <Data>0</Data>

                   

                  </EventData>

                  </Event>

                   

                  i

                  • Re: Custom Package Help
                    jbaits

                    More information is needed to find the cause of your problem. If you are seeing the installer launch but install does not complete it usually indicates that the installer is encountering an error. This could be due to incorrect switches being passed for the silent install, missing prerequisites, or any number of other problems depending on application.

                     

                    Are you installing an MSI or EXE?

                    Have you tested your silent install switches from the command line successfully?

                    Have you tried the above running as SYSTEM? I have seen some applications fail when running as SYSTEM.

                     

                    For MSI packages that only require the standard /qn /norestart switches you can leave the install parameters blank as those are included by default with all MSI packages.

                    • Re: Custom Package Help
                      dv1

                      i'm installing an MSI. when i try to install it from the command line, i'm only successful if i use the /i switch. i cant get it to install with the /S. i was instructed by the vendor that the /S was needed.

                       

                      what do you mean by running as SYSTEM?

                        • Re: Custom Package Help
                          jbaits

                          When patch manager calls an msi without any additional parameters specified it is actually running "msiexec.exe /i myapp.msi /qn /norestart". Anything you put in the install parameters field will be added to the end. If you add /S it will run "msiexec.exe /i myapp.msi /qn /norestart /S". You need to find the proper parameter set that will let your msi run from a command line and then put that in your custom package.

                           

                          When Windows Update runs your packages it will be running as the SYSTEM account. As I mentioned I have seen this break poorly written installers. You can use PSExec to run commands as SYSTEM to test. Based on your response this is likely not your issue.

                            • Re: Custom Package Help
                              dv1

                              so far i'm only able to get the msi to install with the /i I will go back to the package and try to remove all the other stuff

                                • Re: Custom Package Help
                                  jbaits

                                  To be clear, you do not need to specify anything in the package to achieve the standard install command of "msiexec.exe /i myapp.msi /qn /norestart". You also cannot remove those switches. I would test the install outside of patch manager in the command line and get that working before you proceed. Use that command as a starting point and find out from your vendor's documentation what switches need to be added.

                                   

                                  Once again, knowing what msi you are trying to install could be helpful.

                                    • Re: Custom Package Help
                                      dv1

                                      reached out to our contact, but i thought i was doing something wrong within PM... Thats the reason for me reaching out thru this.. Carbon Black is the package i'm trying to push out..

                                        • Re: Custom Package Help
                                          jbaits

                                          No problem. Half the fight with creating custom packages is crafting the unattended install command line. The other half is your detection rules for prerequisites, applicability, and installed status. The first step when creating a package is to make sure you can successfully install the msi or exe completely unattended from a command line.

                                          2 of 2 people found this helpful
                                • Re: Custom Package Help
                                  I LIKE EGGS

                                  Are you able to install the file on a diffrent/standalone PC? just to eliminate any issuse with the current set up? Not doughting your setup just checking all avenues:)