5 Replies Latest reply on Mar 11, 2015 3:44 AM by jainsavan

    Active Package becomes Orphan

    Rookie

      With reference to the link, we've created a package with a similar approach for QL220+ which includes a selection criteria as "(!Custom.Test=1)", because we don't want it to be installed again and it  includes just one thing to update the property Custom.Test as 1 after it has been installed.

       

      Now the thing is,

      • The package is getting installed successfully
      • Property Custom.Test is being updated as 1 which is correct
      • After that, the package becomes Orphan(It should show as active as it has been installed correctly)

       

      Could somebody shed some light on what is wrong with the package or criteria?

       

      Creating a Fusion Package that installs silently and does not install over and over (loop).

        • 1. Re: Active Package becomes Orphan
          nrasmussen SupportEmployee

          If the criteria of the package is ! Custom.Test=1 and the package installs the property of Custom.Test=1 this would install then show orphaned as you are experiencing.  This is because as soon as you set the Custom.Test=1 property the device is no longer valid to download the package. 

           

          Regards,

          Nick R

          • 2. Re: Active Package becomes Orphan
            Rookie

            Agreed that it is no longer valid to download the package but the it is already an active package how it can become Orphan when it is installed and assigned!!


            Is there any other way to make the selection criteria where in I have different packages with Custom.Test set as 1,2,3,4,5 and I want to install 1 on store1 and 2 on store2 and so on. So if 1 is not installed on store 1 it will install the specific package and be active instead of Orphan.

            • 3. Re: Active Package becomes Orphan
              nrasmussen SupportEmployee

              Q:Agreed that it is no longer valid to download the package but the it is already an active package how it can become Orphan when it is installed and assigned!!

              A: This is what an orphaned package is.  It is a package the device received and installed, however it no longer fixes the criteria to have that package installed.  An orphaned package will not be removed unless you actively push down a update now and select the delete orphan option.


              Q: Is there any other way to make the selection criteria where in I have different packages with Custom.Test set as 1,2,3,4,5 and I want to install 1 on store1 and 2 on store2 and so on. So if 1 is not installed on store 1 it will install the specific package and be active instead of Orphan.

              A: If you wish for the package to be active after installation you need to ensure the device will fit the package criteria after it is installed.  So if you have 5 unique packages and you set a custom property to uniquely identify the device you could just use the criteria of "Custom.Store=1", this would then install the package and stay active.  Where you got in trouble was using the not. 

              1 of 1 people found this helpful
              • 4. Re: Active Package becomes Orphan
                Rookie

                If Custom.Store=1 is set as selection Criteria, even then it would re-install every time a force update is performed as it would check if Custom.Store=1 is satisfied and it will install over again.

                 

                But agreed for Orphaned Packages Got to know clearly why it becomes orphan.

                • 5. Re: Active Package becomes Orphan
                  Rookie

                  Is there any other way to do it? So it would not become orphan and also will not install over again if already installed?