Final Cut Studio 3

[#1]

I know that some people were having problems with this, and I don't know
if it was ever resolved.

I was able to successfully deploy Final Cut Studio 3 with a Volume license
with the method below. I don't know if it will work with a single user
license.

1) When creating your package, install just the Applications without the
content. DO NOT RUN ANY OF THE APPLICATIONS. You have to serialize
during install. After install, remove the FCP System ID, and the ProApps
System ID. Make Package. Build as DMG.

2) On the same computer, make a separate package for the content. DO NOT
RUN ANY OF THE APPLICATIONS.

3) Set the priorities so the content install after the Apps.

Tim Marris
Building Technology Specialist
Liverpool Central Schools

Please consider the environment before printing this email.

[#2]

Hi Tim,

I realize this is a couple weeks old now, but I'm looking at making a new
Final Cut package currently and I'm not sure I'm 100% clear on your
instructions here...

Do you run the entire installer twice? I'm not sure how to separate out
applications and content. Could you explain?

Thanks,
Bob

[CasperSally]

Anyone have suggestions on packaging Final Cut Studio 3?

I found old thread below, and I have same question as Bob. If separating the installer from the media is the best way to do things (together they seem to be over 50 gigs), what's the best way to do this?

Thanks!

-----------------
Hi Tim,

I realize this is a couple weeks old now, but I'm looking at making a new
Final Cut package currently and I'm not sure I'm 100% clear on your
instructions here...

Do you run the entire installer twice? I'm not sure how to separate out
applications and content. Could you explain?

Thanks,
Bob

[Cem]

Yes, run the installer twice and capture each with Composer snapshot. But make sure only select contents on second run and don't worry if main app installer greyed out (checked), as snapshot will only capture new additions to the system.
I hope this helps.
Cem

Sent from my iPad

[#5]

Hiya,

I packaged the entire suite.

FCStudio requires a license number BEFORE you can install anything (this file is removable if you wish to create a non-licenced full install)

I have three files made from Composer as
FCPS3-Core (FUT & FET) as dmg <j---- Everything minus the Loops & DVDSPcontent & Serial Number
FCPS3-Loops.pkg <j---- just the loops
FCPS3-DVDSPcontent.pkg <j---- just the loops

We don't have a site license so I strip out the Serial Number from Composer before the Core dmg is finalized.
My installs are few, so I visit the machine post install to serialize it by hand.
All my managed clients point to an internal Apple SUS and updating the install is fast.
Works like a charm.

hope that helps!

-p@

[#6]

Ours appears to be working fine. I also built ours using a new/modified
snapshot, and make sure to Fill User Templates/Fill Existing Users.
Final Cut is launching on our machines and the splash screen indicates
that it's a Volume License.

Bob

[taugust04]

Has anyone been able to get a volume license of Final Cut Studio 3 packaged up using Composer, and then deployed to machines without it requesting a serial number? I've built it using a new/modified snapshot, and all the applications work perfectly except for Final Cut Pro asking for the serial number the first time it is opened. Any suggestions are appreciated. It's a pain to register each machine by hand in a lab setting.

Thanks!

-- Ted August
Salve Regina University

[#8]

Yes, as a matter of fact I've been pushing Final Cut Studio 3 for months
with a VLK, and with no issues. I did a full install running New & Modified,
serialized it, and then built a .pkg file. Works fine ­ as a matter of fact,
I also found that you can change the key just by updating the
ProAppsSystemID file under /Library/Application Support/ProApps/.

This file has changed from previous versions of FCP from a plain text file
to a binary, but what I did was re-name the file & re-launch Final Cut. This
causes it to launch the serialization dialog again, so I re-serialized it
with the next VLK and it created a new ProAppsSystemID file. Repeat as
necessary - I created 3 separate VLK versions this way, and was able to push
them over an existing FCP installation without any issues.

I noticed that this doesn't work with individual licenses ­ I think it keys
against the computer's MAC address (had to re-serialize a single-user
license after installing a new logic board). The VLK version, however, has
never given me problems with this.
-- Christopher Kemp
CNN-BEST Central Engineering

[Cem]

I would test it all after installing FCP by starting it up and make sure
all good, then Build Package...
Cem