Answers

0

Hi, Bill.

There's a ton of stuff in the forum about QT. There's a file - the name of which escapes me - which you need to edit to turn this off. Use the 'Search' and/or 'Package KB' links at the top of the page.

I tried using the SCHEDULE_ASUW and ASUSWISINSTALLED settings but could not get them to work. After searching online, here at appdeploy and other places, I still had no idea as to how I could prevent apple update from running. I found it was a scheduled task, and searched for a means of disabling this to no avail. The most I could think of was making it an impossible schedule, but I did not go through with this. I had found an article about disabling the updates for safari and itunes, however they were CURRENT_USER based, and I need them for the local machine. I used Orca, searching through to see if I might change the registry that update searches for. Instead, I found a much easier solution. Open the Quicktime 7.4.5 with Orca, and expand the caPackage Table. Drop down the only PackageKey, AppleSoftwareUpdate. Now, run the msi. Check for automatic updates will still be opted, but the Software Update does not install, making the checkmark obsolete. I searched through the task scheduler, the registry, and even add/remove programs, there is no Software Update to be found. I ran a search to see why this had not been listed before, I found that in previous versions I.E. 7.1, this Table edit did NOT work, still installing Software Update. For some reason Apple must have changed the way the msi is configured, or perhaps not editing the SCHEDULE_ASUW and ASUWISINSTALLED has something to do with this deletion. Either way, this method removes the problem with Software Updates. making it safer and easier to deploy. I will post if any problems arise, hopefully Software Update is not hidden somewhere, and ask that if anyone finds any problems to post as well. I'd like to see this msi through to satisfaction, if this method does not meet the criteria.

I just used Orca to edit the msi. By the way I'm just a student assistant, I'm just getting into this kind of work, haven't even had any classes yet, so some things I say may not make sense, or I might not understand fully what's going on.

ORIGINAL: JPerez
I just used Orca to edit the msi. OK, well, welcome to the wonderful world of application packaging.

Your first lesson: always, ALWAYS use a tranform on vendor MSIs unless you absolutely cannot avoid editing the MSI directly, a situation I have yet to encounter after who knows how many thousand packages.

Your second lesson: use the Search facility here (with intelligent search terms) and of course the usual Web search engines first before posting. You'll find us a helpful group, particularly to those who have obviously tried to help themselves first.

I've used this site quite a bit in the last few months for a deployment project. It's been helpful with the packages, but the information on 7.4.5 wasn't meeting the specifications of our needs. Editing the msi with Orca was the last resort option, the past few weeks being spent on trying to get it to work. With 7.4.5, I've noticed many differences that do not apply to it. I was able to use commands listed here for 7.4.1, and overall had a successful package from that, but the same couldn't be done with 7.4.5. I spend my hours at work experimenting with this one, and yesterday I've discovered new settings that are more efficient to our standards. I will research these transforms as you mentioned later today.

I was able to turn off the Apple Update by creating the admin install point.
[blockquote]
msiexec /a <your.msi> SCHEDULE_ASUW=0 ASUWISINSTALLED=0 ALLUSERS=1 LIMITUI=1 TARGETDIR=D:\QUICKTIME SHORTFILENAMES=TRUE[/blockquote]
The key parts for turning off the update are "SCHEDULE_ASUW=0" and "ASUWISINSTALLED=0". Then, just deploy the MSI and files that reside in D:\QuickTime (you may want to use another directory like c:\QuickTime_Install).

I liked your solution best as Admin Install Points have worked so well for me in the past. I did use SMS install to try to capture any files or keys that may be relevent when I turn off the auto update box after reading VBScab's post of a needed file. but did not find any relevent file. One looked promising I found at All Users\Application Data\Apple Computer\QuickTime\QuicktIME.qtp but when I reviewed the file its contents never changes when I toggled between turing auto updates on or off even though its date modified did change. So after reading other post here I choose to try your solution as it was more straight forward. However, when I used the Properties I found in the information you listed in your post and launching the new msi created from the Admin Install Point I found I still had the box checked under the Update tab\Check For Updates Automatically. You say you got yours to work. Can you add more information on how you were successful, or see where I may have errored when I created my new Admin Install Point? This is what I used:
msiexec /a Path to our network share\QuickTime.msi SCHEDULE_ASUW=0 ASUWISINSTALLED=0 ALLUSERS=1 LIMITUI=1 TARGETDIR=C:\Quicktime

It seems that 7.4.5 is very different from the previous versions of Quicktime. Most of the tips and tricks that have worked with past versions, no longer work. It would be very helpful if questions regarding 7.4.5 were treated with renewed interest.

Hi folks,
to clarify some stuff:
I can't see big changes in 7.4.5 at all!
- The SCHEDULE_ASUW + ASUWISINSTALLED public properties affect only the installation of the Apple Update MSI
- The update check in Quicktime is still done from the main exe. And this is switched off/on with the update checkbox!
The value of the update checkbox is still saved in the notorious "Quicktime.qtp" file!

There are a lot of instructions on this forum:
See: http://www.appdeploy.com/messageboards/tm.asp?m=31346
And: http://itninja.com/question/how-do-you-roll-out-new-machines?7774

What I am seeing is that those items you litsted affect only the user they are applied to. In the past you could copy the qtp file to a location on the HD or you could make an MST with those changes and have it provide the same user preferences for all users. With the 7.4.5 product something changed and that no longer seems to work.

The update check in Quicktime is still done from the main exe. And this is switched off/on with the update checkbox!
The value of the update checkbox is still saved in the notorious "Quicktime.qtp" file!

With the 7.4.1 product I have a very successful AS scirpt that would copy a custom Quicktime.qtp file into the proper folders for each present/past/future user that logged on to the machine, now with the 7.4.5 product that file is overwritten by Quicktime which creates a new Quicktime.qtp each time a user runs Quicktime for the first time, over-writing my custom qtp with the basic settings. Maybe I missed something, but it seems as though something has changed, because I used the same script for the last 3 or 4 iterations of Quicktime without a problem. Only needing to recreate a new qtp file for some version checking. But, if someone has created a Quicktime 7.4.5 version that maintaines the settings in the qtp for all users, past/present/future, I would be very interested in seeing it.

All of the links you have shown apply to PRE-7.4.5 versions. I have no problem with anything previous to 7.4.5. and have used all of the great information provided here to find a solution each time I needed to package Quicktime. Have you packaged 7.4.5?

I have to agree with Mean Geneious. I have the exact same issue and I appreciate the suggestions from VBScab, nheim and others. But I have had no joy as of yet even after following the suggestions contained here. If someone has sucessfully packaged 7.4.5 with AutoUpdate Disabled for all users, and can provide input as to what was successful, that would be great. Thanks to all.

Hi folks,
i don't know, what you are looking at, but i can't see big changes in this version.

@Gene: Yes, finished our customizations for 7.4.5 last week.
All the things in my links apply to 7.4.5.

@Adam: QT7 is already packaged, we are discussing some customizations here.

Allmost all important settings of QT are lying in the notorious 'Quicktime.qtp' file.
But this file is not part of the package, it will be created either by the 'QuickTimePostInstallMSIProc_deferred' custom action or by 'Quicktime.exe' on the fly.
So we have to distribute this file with the installation.
There quite a few aproaches to this. See: http://www.appdeploy.com/packages/detail.asp?id=520
I do the things on the links above:
- Extra feature for User Data.
- Use Acitve Setup with the DuplicateFiles action to make sure the the settings are installed in each profile.
- To prevent 'Quicktime.qtp' from being overwritten, i install it "read only" and remove the RO bit with a simple deferred custom action at the very end of the 'InstallExecuteSequence'.
- We use a custom action to write UN/Serial to 'com.apple.QuickTime.plist'
- Some smaller cosmetic changes.

This approach emerged over time and works quite well now.
QT 7.4.5 was done in about half an hour.
Regards, Nick

Thanks Nick,
Your summary was very helpful. Im having a bit of trouble with the removal of the Read Only bit. Would you be able to expand on how you did that a bit? (pun intended). Maybe I am making this to hard?
Many Thanks.

Couple things to put out upfront:
This is only going on VISTA!!! Don't care about Windows 2000 or Windows XP.
We do not need to worry about a serial number as we are using the free version and have an agreement with Apple to do so.

This is what I have done so far.
I took the Quicktime MSI, the only mods I made to this was entering our support info as far as ARP. I modified the support contact, support URL, Support phone number, and the comments to reflect our support system here since that is who the enduser would be contacting for support. I then resaved the MSI.

I then created an MST called simply FBIQT745MST and Installshield 2008 selected File>New and then Transform. In the Open Transform Wizard I pointed to the Quicktime 7.4.5 MSI saved in the previous step. I did not point to any additional transforms I just hit next at that screen. I then chose to create a response transform at the next screen, leaving the command line parameters blank and clicked finish.

The quicktime installer screen comes up to which I clicked Next.

License Agreement comes up, clicked yes

Destination Folder accepted the defaults and clicked Install

At that point I got a message from Installshield 2008 telling me my mst was successfully created and that Installshield will now open this transform file. Obviously I clicked okay.

This brings up the project assistant, first screen is nothing just clicked yes.

Next screen I put in our help desk title, quicktime 7.4.5 for app name, leave the versioning at default, and then specified our support site.

Under Operating systems I ensured Vista was checked and clicked on to the next screen

On the next screen I chose to to customize the application architecture.

Saved the file, exited installshield and then came back in. I then went back to Application Files and Selected QuickTime Custom Session XML from the drop down, right clicked and selected Show Pre-defined folders and chose [LocalAppData]. From there I added a sub-folder "Apple Computer" and added a sub-folder to that "QuickTime"

At this point I loaded QuickTime on another workstation. I then went in under player preferences and de-selected Show Content Guide at Startup under the General Tab and hit apply then okay. Next went into Quicktime Preferences and went to the update tab to ensure check for updates automatically was deselected. Under the advanced tab made sure that Install QuickTime icon in system tray was deselected. Started quicktime told it not to reassociate files and to never ask again. I then copied the three files off that system:

The plist (not sure if I even need it) does this only store serial?
the qtp
the session.xml

Next I added the QTPlayerSession.xml to the [LocalAppDataFolder]\Apple Computer\QuickTime under the Session.xml feature that was created and set it to read only.

Then I went into the Installation Designer and created a registry key under HKEY_Current_User\Software\Apple Computer, Inc. named the key QTPlayerSessionRepairKey.

At this point I think I have pretty much addressed everything minus QuickTime's notorious QTP.

Adminstudio currently does not have a folder that is equivalent to where Quicktime stores the QTP for Vista Users.
Macrovision suggested a C++ script using winapi's to get the folder. I am not well versed in C++ and would hope to find a simpler solution. I would appreciate any help on this. I have created just the feature (none of the workflow to go with it) and I have the qtp we wish to use. Users not being able to change preferences after the fact is not a major deal as we don't encourage that anyway. I was hoping there was a way to add the file and use a regkey in similar manner as I did with the Session.xml file. Again any assistance would be welcome.

Hi Ric,
i wasn't exact on the post #, but it's in that thread.
What are you going to do, to copy those files to each profile?
The "DuplicateFile Table" has proved to be a suitable solution to do it.
IMHO, you will need to read up that thread anyway to go further.

If you read my post I have already setup for the QuickTimeSessionPlayer.xml using a repair function in the registry. I have it going into LocalAppDataFolder. I believe this is correct. In Vista the QuickTimeSessionPlayer.xml and the QTP do not go into the same folder. However AdminStudio does not have all the Vista Folders in AdminStudio 8.6. So all I really need to know is:

What is the folder I need to create in Vista for .QTP?
Can I do what I am attempting without having to write a VB or C++ script (have qtp copied to every profile)?
Can I use the registry table and a registry entry that acts as a repair option to accomplish this?

Hi Ric,
please, please read my posts carefully!
In post #26, i gave you the exact path to the QTP file.

Another thing: Have you tested the repair in other profiles?
A feature placed below the feature the shortcut is targeting, will not always be repaired.
Please read this post from John McFadyen carefully:
http://itninja.com/question/distribution-message21
This is the guide for things like this.
Regards, Nick

Nick this is exactly what I tried to add then I went into Files and Folders to show the Directory and I get an error when I click on Show Predefined Folder and select AppData. I was wondering did you create that CurrentUserFolder also.

Hi Ric,
tailoring a package someone else has built, needs in deep analysis, if you want produce usable results.
The 'CurrentUserFolder' is set by the CA 'Set_CurrentUserFolder'.
Seems, that IS doesn't recognize this folder change by the CA...
But it works, believe me... :-)
Maybe, it's time to change to table mode...
Another thing: Be aware, that this file is not roamed in a environment with roaming profiles!
See: http://www.appdeploy.com/messageboards/fb.asp?m=28685 for an explanation.
Regards, Nick

Yes I am familiar that it does, and I have packaged many apps, as you know and can see by the number of threads on appdeploy. Quicktime is quite unique. Also when I created those directories, it was in direct editor in the directory table.

What I am saying is I am getting an error once I create the folders in the directory table. Backtracking and testing today it would seem there is an issue with the

Nick I could go ahead and make entries in the Component, File, and Registry tables but there would still be the problem of how to bring the file in because you have to import it somehow. It seems that the QT6OrEarlierUninstall and the QT7InstallShieldUninstall components are causing the problem at least that's what Macrovision said. They are stating that there is a problem with the keypath value.They are set at QuickTimeUpdater.exe & InstallShield_ respectively.

As far as I know to add the .qtp you would need the following table entries:

a directory entry
a file entry
a component entry
a registry entry

and of course you would have to import the .qtp file itself into the directory.

I am almost at a point where I am going to ditch the idea of using a custom .qtp

Hi Ric,
i don't know what you exactly are trying to prove here.
In this thread: http://itninja.com/question/how-do-you-roll-out-new-machines?7774
i have posted a hole receipt to do this stuff, using ORCA.
Ok. you have to dig it out of the different posts, but it works.
Other forum members where able to do it successfully.
With this method, a new QT version is done in about a half hour, using the MST from the previous version.
IMHO, tools like Wise or Installshield are not ideal for such tasks.
You are fiddling around with problems, that stem from Installshield, instead of making some progress.
I have similar experiences with Wise, doing things like that.
Regards, Nick