I'm trying to package iTunes for a Config Manager deployment and want to control the two iTunesPrefs.xml files that are distributed, idealy from the MSI/MST.  Using a script to copy the files after the install won't work because of the self heal that'll kick off when the users launches it for the first time.

I'm pretty sure these files are getting created during the install via Custom Actions but I can't figure out which one(s).  My goal is to delete the CU's and add the two XML files as files so Active Setup will install my 'correct' files.  Shouldn't be that difficult should it?  Can anyone confirm these files are created via CU?

0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


These files are not created by Custom Action. They are generated when you launch the itunes and get modified.

Answered 06/12/2012 by: piyushnasa
Red Belt

Please log in to comment



Piyushnasa is right (well since the last time I packaged itunes).  The xml files are created by the app if they are missing.

What I did, was used the self-heal to my advantage and included the xml files.

Also since in my case, it was the first time deploying a managed version of itunes (vs manual install), I used the removefile table to remove existing xml files.

Though be warned I had to build the folder structure in the directory table for both locations of the xml file since those folders are not in the msi.  I put my directory edits at the bottom.

Also if I remember correctly, itunes creates an alternative local directory for repairs, so if you include a cab or files via mst repairs will fail since the souce itunes creates does not copy those file over.  To get around this, I actually install the xml file (yes you can combine them into 1 universal version) to INSTALLDIR, then use the duplicatefiles table/action to install in proper location.  This way repairs will still work without having to mess with iTunes custom source, repair setup.

HC_W7_APPDATA                USERPROFILE            AppData

 HC_W7_APPLELOCAL          HC_W7_LOCAL       Apple~1|Apple Computer

HC_W7_APPLEROAM           HC_W7_ROAMING   Apple~1|Apple Computer

 HC_W7_ITUNESLOCAL        HC_W7_APPLELOCAL          iTunes

HC_W7_ITUNESROAM         HC_W7_APPLEROAM           iTunes

HC_W7_LOCAL                    HC_W7_APPDATA    Local

HC_W7_ROAMING               HC_W7_APPDATA    Roaming

HC_XP_APPDATA                 USERPROFILE            APPLIC~1|Application Data


HC_XP_APPLE           HC_XP_APPDATA   APPLEC~2|Apple Computer

 HC_XP_APPLE_LOC             HC_XP_APPDATA_LOC       APPLEC~2|Apple Computer

HC_XP_ITUNES                     HC_XP_APPLE           iTunes

HC_XP_ITUNES_LOC                      HC_XP_APPLE_LOC iTunes


Answered 06/13/2012 by: dandirk
Third Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity