4 Replies Latest reply on Jul 28, 2011 2:01 PM by historicalshavlikcustomer

    iTunes update rules

    Master
      I'm running an old version of itunes and the SCUPdate installable rules doesn't detect it.
      Present in my registry:
      HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall{23B45E10-0CA5-43E9-BD6D-C2BD6CBE11AC}
      DisplayVersion: 9.2.1.5

      Why not just do DisplayVersion less then 10.3.x for the rule?
        • 1. Re: iTunes update rules
          Master
          Work Around:

          There is a work around that can be done to fix these deployments. A
          package called "Apple Application Support" has been created in the
          SCUPdate package. This product will only show missing in SCCM when the
          appropriate version of iTunes, QuickTime or Safari is installed on the
          client system.

          In order to determine when it needs to be installed you must do the following:

          1) Deploy the latest program version to iTunes, QuickTime or Safari
          2) Rescan the systems and look for the Apple Application Support
          package missing.
          3) Deploy the missing Apple Application Support package to the client system.

          NOTE: The Apple Application Support MSI package is not available for
          download from the vendor. You must host the MSI package on a network
          share or internal IIS site. In addition, you will need to edit the
          download location in the Apple Application Support SCUPdate packages
          to reflect the network share or internal IIS site where you are
          hosting the MSE packages before they are published through the SCUP
          console.

          Obtaining the Apple Application Support MSI package.

          There are two way to acquire the Apple Application Support package.

          1. Launching the installer:
          a. Download the version of product that you are planning to deploy
          through SCCM. This download will contain the Apple Application Support
          package.
          b. On a machine, launch the installer by double clicking. Do not click
          on any of the installation wizard buttons.
          c. Navigate to your C:Documents and
          Settings
          insertcurrentlyloggedonuserLocal SettingsTempIXPxxx.tmp
          (xxx is a random number).
          d. The file will be in that directory called
          AppleApplicationSupport.msi. Copy this file to another location.
          e. Close the installer for the product.
          f. Rename the file to the appropriate name based off the following:
          Apple Application Support 1.0.0 -> AppleApplicationSupport100.msi
          Apple Application Support 1.0.1 -> AppleApplicationSupport101.msi
          Apple Application Support 1.1.0 -> AppleApplicationSupport110.msi

          2. Use either 7 zip or Winrar:
          a. Download the version of product that you are planning to deploy
          through SCCM. This download will contain the Apple Application Support
          package
          b. Open the installer with 7zip
          c. Copy AppleApplicationSupport.msi file to another location and Close 7zip.
          d. Right Click on the AppleApplicationSupport.msi and select properties.
          e. Click on the Summary Tab.
          f. Under Description > Comments the version of Apple Application
          Support is displayed.
          g. Close the AppleApplicationSupport.msi properties.
          h. Rename the file to the appropriate name based off the following:
          Apple Application Support 1.0.0 -> AppleApplicationSupport100.msi
          Apple Application Support 1.0.1 -> AppleApplicationSupport101.msi
          Apple Application Support 1.1.0 -> AppleApplicationSupport110.msi


          Changing the SCUPdate package
          1) In the System Center Updates Publisher, navigate to the appropriate
          package and edit the package.
          2) Click on <Next> until you get to the "Select Package" screen.
          3) Change the Download URL (or UNC) to a location your clients can connect.
          For example:
          \serverservershareAppleApplicationSupportxxx.msi
          -or-
          http://servername/AppleApplicationsSupportxxx.msi
          4) Click Finish
          5) Publish update to your SCCM console
          • 2. Re: iTunes update rules
            Master
            Useful information however this is concerning the iTunes update detection not AAS.
            The iTunes SCCM push for me doesn't latest AAS, I have a seperate task to install the latest AAS.
            • 3. Re: iTunes update rules
              Master
              We cannot use the "DisplayVersion less then 10.3.x" logic for the rule because each version of iTunes has a different registry key name.  It appears we have detection logic for 9.2.1.4 and not for 9.2.1.5.  I will look into adding the detection logic for 9.2.1.5 to the upcoming SCUPdates release.