Software Deployment

my document doesnt cover deploying files into the user profile for "local settings" as these are excluded from roaming profiles this can cause other issues. In this case using a script to handle the deployment would be better.

the problem with roaming profiles and "local settings" is that the key used to trigger the deployment is in the HKCU hive. As such this will roam with the user where the file will not. This in turn means you need a trigger to deploy the file for the roaming profile users.

If you can exclude the specific key from roaming then you have a workaround. If you cannot then the only method to handle this deployment correctly would be script unless anyone else has solved the problem using another method.

Hey JoeDown,

I would make sure that your application is launched via an advertised shortcut and then place the component that your file is in into the same feature that the shortcut is in.

Make sure that the file that you want is set as the keypath to the component.

If you don't want to go down the line of advertised shortcuts then using Active setup is probably the next best thing. See http://itninja.com/blog/view/appdeploy:-articles:-activesetup

Hope that helps,

Cheers, Mike

Hi Joe,
Use this guide: http://itninja.com/question/distribution-message21
to use self healing or Active Setup.
Use the DuplicateFile table to copy the file to the profiles.
Regards, Nick

Here is what I'm trying to do and I've been partially successful. For some reason adding these to files to the msi is not documented in the Package KB for Apple Quicktime. To specify the configuration settings you want for Quicktime two modified files have to be deployed to the following locations:

C:\Documents and Settings\%UserProfile%\Application Data\Apple Computer\QuickTime\QTPlayerSession.xml

C:\Documents and Settings\%UserProfile%\Local Settings\Application Data\Apple Computer\QuickTime\QuickTime.qtp

QuickTime.qtp gets created towards the end of installation of the program if it does not already exist. The QTPlayerSession.xml gets created the first time the application launches if it does not already exist.


I don't understand how to tell the MSI where those two files go. In the component table I have them going to QuickTimeCommonAppDataFolder. Looking in the Directory table it's not obvious what the directory value for the Component table should be. The folders where I want to put the quicktime.qtp file get created by the installation so I should be able to use that value right?

If I'm successful with this it will be invaluable for other applications.

I am so confused. I have read through many entries in the messageboards and the other places on this website.

I am trying to create a package to deploy Quicktime 7.2.024 via group policy. Why is it so hard? I found the .msi and edited it for English only. Then I used Orca to make a few changes as listed in some of the posts. I deployed it to a computer that had 7.1 installed. It seemed fine and I ran a little video successfully.

This is on a computer in a public library and I was logged in as the patron and ran the movie from a link on a webpage. Then I logged in as tech and ran quicktime from the Start menu and it began the installation again. When I checked the preferences after the installation completed, the modifications I made in the .mst file were not there.

I have seen references to copying over the .qtp file but I don't know how to do that with GP.

Thanks
Jane

Hi Jane,
have a look at this thread:
http://itninja.com/question/how-do-you-roll-out-new-machines?7774
Their, i have posted a complete tutorial for this particular problem.
This works also with GPO installs.
Regards, Nick

Thanks. I read that before and was pretty confused but I will try again.

I am looking at that thread. When you say 'create a new top level feature', what are using to do this? I have been fiddling with Orca but am not seeing anything like that.

Thanks.

Hi Jane,
load 'Quicktime.msi' into ORCA.
Select 'Feature' in the left pane.
Click with the right mouse button into the right pane and select Add Row.
Now fill in the necessary fields and you have your new feature.

But there is an easier way to do it. As i stated in this other thread, copy the hole post with the receipt into Notepad,
search for ' ' (4 spaces) and replace them with a tab (because this board is replacing all tabs with those four spaces).
Then you should be able to paste the lines into the according tables in ORCA with Ctrl-Shift-V.

Hope this brings you further on the track.
Regards, Nick

I am working away at this. I got to the part that says to embed the CAB file with this command: cscript WiStream.... etc. I don't really get that. I have the .msi file and all the other ones including the config.cab file in c:\temp\qt72. I found that I do have the .vbs file so at a command prompt I went to that directory and typed

cscript WiStream.vbs c:\temp\QT72\Quicktime.msi config.cab Binary.config.cab and got the error:

Msi API Error 80004005: SetStream,Field,FilePath
1: 1101 2: config.cab 3: 2

What do I do now?

Thanks so much for your help. I did get that 'top level' part that I asked about earlier.

Jane

Hi Jane,
you need to add the path to the "config.cab".
cscript WiStream.vbs c:\temp\QT72\Quicktime.msi c:\temp\QT72\config.cab Binary.config.cab
Regards, Nick

Thanks. I wondered about that but thought I would get an error that said 'file not found' or path not found so thought it was something else.

Thanks.

I'm using Admin Studio to try this with the QuickTime.msi. When I try to validate the msi (even prior to starting through your directions) I get errors such as Registry key 'QuickTimeUpdater.exe' and 'InstallShield_' not found in Registry table and a whole slew of The targe file 'QuickT~1.QTX|QuickTime...qtx installed by two different components on an SFN system. I'm just trying to figure out what I'm doing wrong, but until I obviously figure out these errors I won't be able to test the directions. Any assistance is appreciated!

therren,

You mean you validate a native MSI before you even work on it? Don't worry about the validation errors mate. Native MSI's don't really bother to be correct most of the time. Just make the changes you need and try to deploy it on a test system.