This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

iTunes - DISABLE CHECK FOR UPDATE OPTION - ACTIVE DIRECTORY ADMINISTRATIVE TEMPLATE

This Active Directory Administrative Template contains the Group Policy option to disable Automatic Update Notifications for iTunes. The policy is applied to an Organizational Unit under the “Current User Configuration”. The template has been tested with  iTunes 11.0.3.42 and is to be used at the discretion of the user.

attachments.zip
  • This doesn't work on iTunes 11.1.xxx. The menu options are all set according to the GPO, but it still prompts for updates. Also, the description says it's for User but when I open the ADM in notepad it says Class Machine at the beginning. Also, when I import the ADM it's only imported under Computer Configuration, which is it?

  • FormerMember
    0 FormerMember

    Be nice if there was a followup to this.

  • What kind of followup are you looking for, Rick?

  • FormerMember
    0 FormerMember

    Well the earlier comment reports several issues. Has it been fixed for ITunes 11.1? Has it been updated for clarity between User and Computer?

  • The template was posted as an as-is sample, tested for iTunes 11.0.3. It's entirely possible that Apple made changes that impacted the template's functionality with iTunes 11.1 or later versions. But, inasmuch as the attached ADM files are source code, any such changes that could be made, or might be necessary, are surely within the capability of any end-user who chooses to use the templates. I'm not aware of any plans, nor expectation, to maintain this template or any of the others posted from time to time.

  • FormerMember
    0 FormerMember


    There is a link from the 12.0.1 iTunes Patch that points to this article, so that certainly prvided the expectation it will work with 120. Unimpressed by the complete lack of support that comes with statements like "surely within the capability...". We purchased PM so we could transfer some of that work to PM, and the product links to it as a solution.

  • Hmm... I was unaware of the reference in the package description. I agree, if we're linking to it in current packages, then the template should work with current versions.

    I've inquired internally as to what the expectation actually is.


    I'm sympathetic to your concern about "lack of support", but generally speaking, content posted in *Thwack* is considered to be as-is and not supported. Supported content will ship with the product itself, and quite often we pull contributed content from Thwack and ship it with the product as supported content.