Prinergy 3.1/Windows 2000 to Prinergy 4/Windows 2003

by admin on October 4, 2007

The follow describes how we upgraded to Prinergy 4.0 AND Windows 2003 with a minimum of hassle. Of course, if you are really serious about doing this yourself, you should e-mail me for the PDF instructions.

TABLE OF CONTENTS
REVISION HISTORY i
TABLE OF CONTENTS ii
1. Purpose of this Document 1
1.1 Introduction 1
1.2 Background Information/Sponsor and Stakeholders 1
1.3 Scope of Work to be Provided 2
1.5 Scope of Work to be Excluded 2
2. Backup/Preparation of the Server for Ghosting 3
2.1 Settings Backup 3
2.2 Data Backup 3
2.3 Norton Anti-Virus License Key 3
2.3 Packaging of the Server 4
3. Rebuilding the Server 5
3.1 Hostname, License Key, Static IP check 5
3.2 Restoring the System Settings 5
3.3 Reconnecting the Output and Proofing Devices 5
3.5 Configuration Windows in the Prinergy Administrator Window 6
3.5 Re-registering Jobs in the Oracle Database 8
3.6 Install the Anti-Virus Software 9
4.0 CONCLUSION 10
5.0 APPENDIX A: MIGRATING OF ENTERPRISE SYSTEMS 11

1. Purpose of this Document
1.1 Introduction
Printcraft Solutions, a printing company based in Burnaby BC, has a significant investment in digital pre-press workflow including a number of pieces of hardware and software. The most significant piece of pre-press equipment is the Prinergy server, which consist of Kodak workflow software installed on a Dell 2900H with RAID storage.

This project is meant to detail the upgrading of this server from Prinergy 3.1/Windows 2000 to Prinergy 4.0/Windows 2003. This shall be accomplished NOT by the official migration strategy of Creo/Kodak but by the ghosting of the hard drives and the erasing of the Oracle database. Note that:
1. Ghosting of the drives shall be done by Creo personnel.
2. This procedure does not void the warranty or service contract with Creo/Kodak.
However, Printcraft has agreed to undertake this migration knowing that:
1. The Oracle database will not be recovered.
2. Custom settings for this shop will be rebuilt by the Printcraft system administrator (details to follow).

1.2 Background Information/Sponsor and Stakeholders
Printcraft Solutions is a small to medium size offset printing business based in Burnaby BC. It has 12-15 staff, three presses (including a six color Komori press) and relatively new Lotem Quantum CTP device.
David Schindel, as owner of Printcraft Solutions, is the sponsor of this document and any projects that are authorized because of the contents of this document.
Jackie, as Prinergy/ÇTP operator, handles the day-to-day operation of the digital workflow. Therefore, she needs to be briefed on any project involving the Prinergy workflow system.

1.3 Scope of Work to be Provided
The system administrator at Printcraft will:
Backup all custom settings of the Prinergy server, including printer settings, Preps templates and process plan settings.
Backup all job data by means of the job export function.
Make note of the license key, and print out same, record hostname of server, remove dongle, and transport server to Creo production facilities.
After the server has been re-ghosted, the sys admin will arrange for pickup, connect the Prinergy server to the network, reinstall custom settings and ensure that plates and proofs can be generated. Then, jobs will be re-imported into the new Oracle database by means of a smart hot folder.

1.5 Scope of Work to be Excluded
As stated previously, there will no attempt to recover or rebuild the Oracle database. However, there will be a procedure implemented that will re-register the jobs in the Prinergy and therefore the end result will be the same (as if we did rebuild the database).

2. Backup/Preparation of the Server for Ghosting

2.1 Settings Backup
In the D:\Prinergy\CreoAraxi subdirectory, you should back up the following folders:
1. AraxiPreps
2. Data (includes the Processplans, MarkSets, and ICC-Profile folders)
All the printer drivers for the print devices for Windows 2000 should be backed up as well. The following are the settings for the print devices set up on the Prinergy server.
1. Bizhub IP address: 113 letter
2. RICO IP address: 117 dlbsided letter
3. rico_tab IP address: 117 dlbsided tab
4. Ricoh 1075 same PCL driver
5. Xante IP address: 113 Letter tabloid extra
You should look in the D:\Prinergy\AdobeExtreme\bin\Harmony and backup all files with the hmy extension (those are your Harmony curves).
Finally, ensure that the names of all the custom windows accounts have been recorded, like the names of the operators (the ghosted box will come with the Administrator and Araxi account installed.)

2.2 Data Backup
All jobs should be exported from the Workshop by using the ExportAll process plan to a fixed directory.

2.3 Norton Anti-Virus License Key
Before sending the server off to be ghosted, log on to Norton’s web site and ensure that a copy of the license key is e-mailed to you (this means you have to find the certificate with the serial number. If you can’t find the certificate, make sure you contact support and convince them to send you a license file.)

2.3 Packaging of the Server
The license key documentation was printed out and taped to the side of the server, along with hostname and static ip address. The license key digital file was stored on the J: drive and the location also written on the note (so that an operator can import the license and not have to manually type it in.)
Lastly, the name of the customer and site # along with phone number was written on the side of the server case as well.

3. Rebuilding the Server

3.1 Hostname, License Key, Static IP check
1. Hostname: Right-click on your computer and select System p\Properties, then Network Identification then Properties. Type in the name of your computer
2. License Key: In Prinergy Administrator, select License and then select Enter File and then navigate to your license key file.
3. Static IP check: Control Panel then Network & Dial-up connection then right-click on your LAN connection then navigate to the TCP/IP protocol and then click on properties. Type in your static IP address along with the default gateway.

3.2 Restoring the System Settings
In the D:\Prinergy\CreoAraxi subdirectory, you should recover from backup the following folders:
1. AraxiPreps
2. Data (includes the Processplans, MarkSets, and ICC-Profile folders)
3. Any custom made Harmony curves
Recreate your Windows NT print devices and user account.

3.3 Reconnecting the Output and Proofing Devices
If you are running Xpo from the Prinergy server, you will need to reinstall it. Ensure that you have Prinergy CD for doing so. REALLY IMPORTANT NOTE: In upgrading from Windows 2000 to Windows 2003, you need to install the special Windows 2003 patch for Xpo if you are running version 3.00.79 (connects to Lotem Quantum). You can get this patch from the response center, although it’s too big to e-mail, so get it ahead of installation.
After starting up Prinergy and Xpo, click on all the “Final Output” process plans to ensure that the settings are synchronized, especially with regard to plate sizes and Harmony curves.
Next, click on all the imposed process plans to ensure there have been synched properly.
3.5 Configuration Windows in the Prinergy Administrator Window

I needed to add my Kodak proofer to Prinergy (screensnap in PDF file):

Then I had to re-register my input volumes (screensnap)

Finally, I added back my custom folders that are created in each Prinergy job:

3.5 Re-registering Jobs in the Oracle Database
I did this by means of a smart hot folder (screensna)

And finally…

To trigger the re-importation process, I dumped the zip archives into the hot folder.

3.6 Install the Anti-Virus Software
After re-installing Norton (you do have the CD, don’t you), access your e-mail for the license key.

4.0 CONCLUSION
The server was dropped off at Creo integration at about 11:30 am and was picked up at 2:00 pm on Friday afternoon. Very little integration was done that Friday as the CTP was powered off and everybody went home early.
On Monday morning, there was about a 2.5 hour delay in getting the Lotem to make plates as I was unaware we needed the Windows 2003 patch to run Xpo (the device connectivity software to run the Lotem).
Outside of the usual goofy start-up errors that also accompany a new Prinergy installation (and go away after a number of restarts), there were very little re-integration problems.
The most pleasant surprise was the ease of re-registering the jobs in the Oracle database. About 300 jobs were re-registered in less than 90 minutes of processing time. The biggest chore was the manual creation of groups and moving the re-imported jobs back into the proper groups.
Based on this one experience, I would suspect that for all but the largest shops, it would warrant serious consideration to take the path of re-registering the jobs by means of a smart hot folder, rather than attempting to update the database, especially if you are moving to Windows 2003.
But that’s just my opinion.

5.0 APPENDIX A: MIGRATING OF ENTERPRISE SYSTEMS
For Prinergy users with an older Prinergy primary that cannot be upgraded to Windows 2003, it might be worthwhile to consider moving the primary to a new server and converting the older server to a secondary server that houses archived jobs.
Such an approach would lessen the migration risks to a considerable extent as the following steps would indicate:
1. Introduce the new server to the shop running Windows 2003 and Prinergy 4.0.
2. Copy all settings from old server to new server, such as process plans, marksets, Prinergy admin configuration settings etc.
3. Migrating/update all secondary servers to connect to the new server, excluding the old Prinergy primary.
4. Set up a process plan on the old server that recovers archived jobs and exports to a folder that is watched by a smart hot folder on the new Prinergy primary.
5. With the use of rule sets (not fully explored by this author), it might even be possible to automate the export/import process even further by automating batches of export jobs to happen outside of regular working shifts.

{ 1 trackback }

» Getting your hands on Prinergy 4.0 www.prepresspilgrim.com: The life of a systems administrator in a printing shop
October 8, 2007 at 1:41 am

{ 9 comments }

koloriten October 6, 2007 at 2:17 pm

we are a printshop in sweden thinking about upgrading from Prinergy 2.2, I know it’s old, to either 3.x or 4. The Adobe pdf print engine is very interesting. My question to you is what are the hardware specs for Prinergy 3 and did you upgrade your hardware for version 4. regards Koloriten

dj October 8, 2007 at 12:29 am

Hi Kooriten:

Our Dell server was pretty new, the 2900 model with 4 gigs of ram and 480 gigs of storage. I don’t remember the CPU speed exacty(it’s Cdn thanksgiving here,so the shop is shut down) but I think it’s a dual 3.2 gigahertz.

If you bought your Dell box and it came as Prinergy 2.2, then I think you have a 2600 which came with maybe 2 gigs, don’t remember the CPU speed. But it should definitely handle an upgrade to 3.1. I don’t know about 4.0.

I would recommend getting Prinergy 4.0 if only for the new PDF engine that can hande transparencies. Printcraft Solutions is a very small shop but even we found transparencies to a real pain in the rear end. I can’t imagine what it’s like for shops that process hundreds, maybe thousands of pages a day.

koloriten October 10, 2007 at 2:40 pm

thank you for your reply

toby twyford December 14, 2007 at 10:07 am

Any issues with workshop on the mac. Changing between different jobs ours will just freeze showing a gray screen?

admin December 14, 2007 at 1:48 pm

Nope, no issues to report at Printcraft-Solutions. It sounds like you have a network OR database issue. Did you upgrade to Windows 2003? And… did you just get upgraded, like within the last two weeks?

Laurent April 7, 2008 at 3:40 am

Hello ! I’e to upgrade my servers to prinergy 4. actualy i’m on windows 2000 and prinergy 3.1.7 . Can you send me the PDF file for upgrading instruction because in europe , Kodak don’t want to give me it. (ok to upgrade to 4.0.2 with 2000 but after that, if i upgrade to 2003, the oracle DB does not work anymore !!!

Mario Paredes June 13, 2008 at 8:23 am

I have a Prinergy 3.1, it was recently upgraed from 3.0.3 and the last step is arrive to 4.0. The process of upgrade was made for kodak technicall support and works fine (apparently). My question is> our database have aprox. 40 Gigabytes and the migration of all data is a very important issue for us. All of our jobs are backup in DLT tapes and this DLT’s are connected directly with Prinergy Connect. But when i want to restore a old job (for example nov 2006), the process is interrupted and show error with the ID number 1080007. But when I try to restore file by file (in the most of cases) works fine. Any suggest?? Thanks in advance. Mario from Lima-Peru

admin June 13, 2008 at 2:25 pm

When you say “backed up” do you mean they have been archived using the Prinergy archiver or just “backed up” using Prinergy back up solution?

Do you have a support contract with Kodak or it is just T & M?

SCOTT August 27, 2008 at 7:19 am

We recently upgraded to an Isilon server, we are running Prinergy 3.1 with Macs. Kodak had to change the way the files are accessed from AppleTalk to smb. Now our Prinergy system takes about 20 to 30 minutes to rip a job. Any help would be appreciated

Comments on this entry are closed.