Prinergy Mac Client File-Sharing Protocols

Prinergy Workflow System Version 4 and 5

Mac Client File-Sharing Protocols English

Excerpt from Prinergy System Administration Guide, 731-00463C Rev I, October 2008

Contents

1 Qualified tertiary servers and Mac client computer file-sharing protocols 1

2 List of Mac client computer file-sharing protocols and related software 5

3 Limitations of Mac client computer file-sharing protocols 7

4 Understanding file resources 9 File resources...... 9 Storing file resources...... 10 Archiving and Mac client computer file-sharing protocols...... 10

5 Setting up Mac client computer file-sharing protocols 11 Starting SFM to support AFP...... 11 Configuring AFP with ExtremeZ-IP...... 12 Identifying non-SFM servers in the OTHERHOSTS file...... 16 Updating the SFMHOSTS file...... 17 Enabling Preps under SMB...... 18

6 Changing Mac client computer file-sharing protocols 21 Limitations of protocol conversions using Prinergy Administrator...... 21 Converting to SMB with AppleDouble...... 22 Converting to AFP...... 26 Manually converting protocols...... 29 Converting files with Fork Translator...... 31 Troubleshooting...... 32 iv Prinergy Qualified tertiary servers and Mac client computer file-sharing protocols

Tertiary servers are qualified for use with Prinergy® only using specific network file-sharing protocols to and from Mac® client computers. Each operating system or platform has a defined service level. Note: Service levels are described below the table.

Tertiary server Mac client computer protocol Service level and comments

® Windows Server 2000 and Either of the following protocols: ● Service level 1, if the server is ® Windows Server 2003 purchased from Kodak® ● AFP with SFM

™ ● Service level 3, if the server is ● AFP with ExtremeZ-IP not purchased from Kodak We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS® X 10.5. Do not use SMB with ADS until it is qualified.

Windows 2003 Server Cluster AFP with ExtremeZ-IP Service level 3 We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified.

Windows Server 2008 Not currently qualified Not currently qualified We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified.

Isilon SMB with AppleDouble Service level 1 We are working to qualify this operating system for SMB with ADS, if all Mac client computers run Mac OS X 10.5. Do not use SMB with ADS until it is qualified.

Mac OS X Server 10.4 SMB with AppleDouble Service level 2 until Mac OS X Server 10.5 is qualified. Service level 3 after Mac OS X Server 10.5 is qualified. 2 Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols

Tertiary server Mac client computer protocol Service level and comments

Mac OS X Server 10.5 Qualified for AFP for Prinergy 4.1.2.2 and Service level 2, when this solution higher is qualified Not yet qualified for any other protocol

Brisque® Server, which uses Samba AFP via Helios Service level 1 and Helios Archiving is not supported.

UNIX® with Samba and an AFP AFP via the AFP server Service level 3 server, such as Helios or Xinet® Archiving is not supported.

UNIX with Samba and no AFP server SMB with AppleDouble Service level 3

Service level descriptions Service The solution is documented, tested with every major and minor level 1 upgrade, and fully supported, which means problems are investigated. Service The solution is documented and tested with every major upgrade level 2 but not directly supported. A problem will be investigated only if it meets the following conditions:

● The problem is caused by Prinergy.

● The problem can be replicated on a job volume on the customer's Prinergy primary server. The customer must keep the job volume on the primary server for this purpose.

Service The solution is documented but not tested with every major level 3 upgrade and not supported. Support is limited to documentation. A problem will be investigated only if it meets the following conditions:

● The problem is caused by Prinergy.

● The problem can be replicated on a job volume on the customer's Prinergy primary server. The customer must keep the job volume on the primary server for this purpose. After a Prinergy upgrade, you must confirm that the solution still works to your satisfaction. Consider buying a software testing solution to test upgrades before implementing them on a production system. For information about testing solutions, contact your sales representative. 3

Limitations across all solutions Note: Kodak does not support, and assumes no responsibility for, problems or performance issues that may occur as a result of using third-party products. Problems related to third-party products are not covered by Kodak service contracts.

● All servers in your Prinergy system must use the same Mac client computer protocol. Otherwise, Mac users may unknowingly mount the a volume using the wrong protocol, which might cause data loss.

● The Job Replication option cannot be used with any third-party tertiary server. If you want to replicate jobs, you must buy a server from your Prinergy supplier or find an alternate solution.

● A storage area network connected to a tertiary server is qualified and supported, according to the operating system of the tertiary server that it is connected to.

Solutions that are permitted but not qualified

● UNIX tertiary server supported by running an NFS client, such as SFU, on all Prinergy primary and secondary servers: This solution is not qualified—it is not documented, tested, or supported. Use it at your own risk.NFS has many known problems and many potential problems, because Microsoft® does not test the solution on all variants of UNIX. If you use this solution, use it only for input volumes, not for job volumes.

● Network-attached storage other than Isilon: This solution is not qualified—it is not documented, tested, or supported.Use it at your own risk. If you use this solution, use it only for input volumes, not for job volumes.

● Storage area network directly connected to the Prinergy primary server: This solution is not qualified—it is not documented, tested, or supported.

● All other configurations not identified above or in the above table. 4 Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols List of Mac client computer file-sharing protocols and related software

Mac client computers can connect to a Prinergy primary server using several protocols over several types of software.

Protocols for connecting Mac client computers in Prinergy SMB Server Message Block protocol, which is built into the Windows operating system SMB is also known as CIFS and Microsoft Windows network. On UNIX servers, SMB can be implemented with the Samba software. SMB handles file resources in the following ways:

● With AppleDouble, using the AppleDouble file format for foreign files AppleDouble stores file resources in separate files with a ._ prefix. For example, a file named input.pdf has a corresponding AppleDouble file that is named ._input.pdf.

● With ADS, storing file resources in alternate data streams (ADS)

AFP Apple® Filing Protocol, which is built into the Mac OS On Windows servers, AFP can be implemented via SFM or ExtremeZ-IP. On UNIX servers, AFP can be implemented with Helios, Xinet, and other software. AFP stores file resources in resource forks.

NFS Network File System, which is built into the UNIX operating system On Windows servers, NFS can be implemented with SFU.

Software to assist Mac client computer connections SFM Microsoft Services for Macintosh®, which is built into the Windows Server 2000 and Windows Server 2003 operating systems to provide AFP connections for Mac client computers ExtremeZ-IP File server software that you can install on a Windows server to provide AFP connections for Mac client computers. Samba Open-source file server software that you can install on a UNIX tertiary server to provide SMB connections for the Windows Prinergy primary and secondary servers Helios Software that provides AFP connections on a UNIX server 6 Chapter 2—List of Mac client computer file-sharing protocols and related software

Xinet Software that provides AFP connections on a UNIX server SFU Services for UNIX, which you can install on a Windows server to provide NFS connections Limitations of Mac client computer file-sharing protocols

Many Mac client computer protocols have significant limitations in a Prinergy system.

SMB with ADS SMB with alternate data streams is available when all Mac client computers run Mac OS X 10.5.

SMB with AppleDouble format SMB with AppleDouble format has the following limitations:

● Files copy more slowly when you copy a large number of small files. The per-file overhead is doubled because there are two files. ™ ● When InSite users upload or download files, resources are lost because InSite is not AppleDouble enabled. This issue applies to both Windows and Mac client computers. This issue is not significant because InSite primarily uses PDF files.

● If some Mac client computers use Mac OS X 10.4.7 or earlier, the operating system may leave files open, locking them from other users. To avoid this issue, upgrade all Mac client computers to Mac OS X 10.4.8 or later.

● Fonts used in Font Converter do not have file resources, because Font Converter works only with font files that have resource forks stored in alternate data streams. You must use the Fork Translator software to manually convert the font files' resources from AppleDouble to ADS.

● Files restored by Microsoft Backup from Prinergy archiver tapes do not have file resources, because Microsoft Backup does not create the AppleDouble files required by SMB. If you want resources for files restored by Microsoft Backup, you must use the Fork Translator software to manually convert the files' resources from ADS to AppleDouble.

AFP The main limitation of all AFP servers is that archiving is not supported on tertiary servers using UNIX or on tertiary servers using Mac OS X 10.4 or earlier. Although the files are archived, the resource forks are lost. AFP with ExtremeZ-IP does not have any significant limitations. AFP with SFM has the following limitations:

● Does not support long file names (31 characters or longer)

● Is associated with problems on Mac client computers, such as corrupted desktops

● Has a limited life span. In the Windows 2003 operating system, Microsoft does not support SFM. As of Windows 2008, SFM will not exist. 8 Chapter 3—Limitations of Mac client computer file-sharing protocols

● Is not scalable

● Results in slower Prinergy performance under heavy loads

● Has indexing problems

● Limits the volume size to a maximum of 2 GB

NFS NFS is not qualified for use with Prinergy, so its limitations are not relevant. Understanding file 4 resources

Files have resources, such as icons that appears next to the file name in a file browser. File resources The Mac OS and the Windows operating system store file resources in different ways.

What file resources are File resources are descriptive information about files, such as:

● File type

● Icons that appear in a file browser

● Preview images

● Originating software

What happens when you don't have file resources The Mac OS and the Windows operating system store file resource information in different ways, so files stored in one operating system lack resources when opened in the other operating system. If a file lacks resources:

● If you double-click the file in the Prinergy Workshop software or in a file browser, the file does not open in its originating software.

● The file name extension is missing in the Workshop software and in a file browser.

● The Kind column is blank in the Workshop software and in a file browser.

● The file icon is missing in a file browser.

● The Get Info dialog box in the Workshop software does not display a preview image, and the Open With and Kind fields are blank. Resources do not affect how Prinergy processes files. Prinergy processes files the same way, regardless of whether they have resources. The exception is Font Converter as mentioned in Limitations of Mac client computer file-sharing protocols on page 7. 10 Chapter 4—Understanding file resources

Storing file resources File resources can be stored in forks, AppleDouble files, or alternate data streams.

Resource forks Resource forks store file resources in the file itself. The Hierarchical File System (HFS) of the Mac OS uses resource forks.

AppleDouble UNIX file systems can store Mac OS-compliant resources with the AppleDouble file format, which places resources in a separate file with the same file name as the data file but prefixed with "._". For example, a file named input.pdf has a corresponding AppleDouble file named ._input.pdf.

Alternate data streams (ADS) Alternate data streams allow files to be associated with more than one data stream. One use of ADS is to store resources. The New Technology File System (NTFS) of the Windows operating system and Isilon support alternate data streams. SFM and ExtremeZ-IP store resources in an alternate data stream named AFP_Resource.

Other Other platforms, such as EtherShare and Xinet, store resources in separate files with special file name extensions.

Archiving and Mac client computer file-sharing protocols Prinergy archives, retrieves, and restores appropriately when you change protocols. When you retrieve files that were archived under a different protocol, Prinergy converts the resource information to the appropriate format. For example, if you archive jobs under AFP and then convert to SMB with AppleDouble, when Prinergy retrieves the files, it converts the resource information from resource forks into AppleDouble files. If files contain resource information in both AppleDouble files and resource forks, the Prinergy system uses the resource information required by the current protocol and ignores the other resource information. Setting up Mac client computer file-sharing 5 protocols Starting SFM to support AFP Start Microsoft Services For Macintosh (SFM), if necessary.

● This task applies only if you are using using SFM to enable Mac client computers to connect via AFP to Windows servers.

● Perform this task on each Windows server in the Prinergy system.

1. Right-click My Computer and select Manage. 2. In the Computer Management window, expand Services and Applications and click Services. 3. In the right pane, right-click File Server for Macintosh and select Properties. 4. In the Startup type list, select Automatic and click Apply. 5. Click Start and then click OK. 6. In the right pane, right-click Print Server for Macintosh and select Properties. 7. In the Startup type list, select Automatic and click Apply. 8. Click Start and click OK. 12 Chapter 5—Setting up Mac client computer file-sharing protocols

Configuring AFP with ExtremeZ-IP Install and configure ExtremeZ-IP on a Prinergy primary, secondary, or tertiary server to enable AFP connections from Mac client computers without Services for Macintosh (SFM). Requirements:

● This task applies only if you are using ExtremeZ-IP to enable Mac client computers to connect via AFP to Windows servers.

● If you are using Prinergy 4.0.2.6, 4.1.2.2, or 5.0.2.0, perform this task on primary, secondary, or tertiary servers. If you are using earlier versions, perform this task only on tertiary servers because ExtremeZ-IP is not supported on primary or secondary servers on earlier versions.

● Ensure that the server uses a version of Windows that is compatible with the version of ExtremeZ-IP. For example, ExtremeZ-IP 5.0 is compatible with Windows 2003 R2 SP2 operating systems but not Windows NT® Workstation platform, which is used by the Renaissance scanner.

● Ensure that the server is already part of the Prinergy system.

● Ensure that the Prinergy job volume on the server is not at the root of a volume. ExtremeZ-IP does not allow shares to be created below another share. If you create a share at the root of the volume, you cannot create any other shares on that volume.

● Ensure the volume share name does not exceed 27 characters.

1. If you are installing ExtremeZ-IP on a primary or secondary server, skip this step because you want ExtremeZ-IP to convert all your existing Mac shares. Perform this step only under the following conditions:

● you are installing ExtremeZ-IP on a tertiary server

● you are using SFM to support AFP Stop and disable the SFM services on all Windows operating system servers in the Prinergy system: a. Right-click My Computer and select Manage. b. In the Computer Management window, expand Services and Applications and click Services. c. In the right pane, right-click File Server for Macintosh and select Properties. d. Click Stop. Configuring AFP with ExtremeZ-IP 13

e. In the Startup type list, select Disabled and click OK. f. In the right pane, right-click Print Server for Macintosh and select Properties. g. Click Stop. h. In the Startup type list, select Disabled and click OK. When SFM stops, all AFP shares are deleted, so there is no need to manually remove AFP mappings. If you do not disable the service, a message about migrating SFM shares appears when you start ExtremeZ-IP for the first time. You can either click Yes to migrate all shares, or click No and create the shares manually for SMB and Mac shares. 2. Install the ExtremeZ-IP File Server software on the Prinergy server using the ExtremeZ-IP Quick Start Guide that is available at http://www.grouplogic.com. 3. If you just installed ExtremeZ-IP, you can start the ExtremeZ-IP Administrator immediately. Otherwise click Start > Programs > ExtremeZ-IP > ExtremeZ-IP Administrator. If a warning appears that non-standard port 549 is in use, you can ignore this warning for now as you will change it later.

4. When you see the message The server contains Services for Macintosh (SFM) shares. Would you like to migrate these shares to ExtremeZ-IP volumes nad disable SFM?, perform either of the following actions:

● If you are installing on a primary or secondary server, click Yes to migrate all shares.

● If you are installing on a tertiary server, click No because you will create the shares manually for SMB and Mac shares.

5. If you see the message The server contains Windows (SMB) shares. Would you like to replicate these shares as ExtremeZ-IP volumes?, click No. 14 Chapter 5—Setting up Mac client computer file-sharing protocols

6. On the ExtremeZ-IP Administrator Summary screen, click Settings to configure ExtremeZ-IP settings. a. Click the File Server Settings tab.

● Confirm that AFP Port is 548

● Confirm that the Enable home Directory Support check box is cleared

b. Click the Security tab, and confirm that the following check boxes are cleared.

● Allow Workstations to Save Password

● Show Only Accessible Volumes

● Reset Permission on Moves (Global)

● Notify Mac Clients of Password Expirator

● Enable IPv6

c. Click the Search tab, and confirm that the Use lazy indexing check box is cleared. d. Click the Filename Policy tab, and confirm that all of the check boxes are cleared. e. Click the Service Discovery tab, and confirm that the Zidget/HTTP check box is cleared.

Important: The Server Name must not have IP at the end of the server name. Otherwise the server will appear twice in the Finder.

f. Click OK. 7. If you are installing on a primary or secondary server, and you migrated shares, follow the left column to modify the path of the volume. If you are installing on a tertiary server, and you did not migrate shares, follow the right column to create an ExtremeZ-IP share for Prinergy. When creating shares, ensure you follow these conventions:

● The Windows Share Name must start with AraxiVolume_ and must use the same folder path as the ExtremeZ-IP share.

● The AFP and ExtremeZ-IP Volume Name cannot exceed 27 characters.

● If you have existing jobs and are adopting ExtremeZ-IP, do not change share names. Configuring AFP with ExtremeZ-IP 15

If you migrated shares on a primary or If you did not migrate shares on a secondary server tertiary server

On the ExtremeZ-IP Administrator On the ExtremeZ-IP Administrator Summary screen, click Volumes. Summary screen, click Volumes.

In the Volumes dialog box, select the Jobs In the Volumes dialog box, click on J drive volume, for example, Jobs on Create. MyServerName J, and click Modify.

In the Volume Properties dialog box, click Locate and select your Jobs drive, the ellipses beside Path and select your usually drive J. Jobs drive, usually drive J.

Click Make New Folder and type the Click Make New Folder and type the shared folder name, for example, shared folder name, for example, AraxiVolume. Click OK twice. AraxiVolume. Click OK.

When asked if you want to restart the In the Volume Properties dialog box, volume, click Yes and click Restart. type the Volume Name of the Prinergy share, for example, Jobs on MyServerName J. Click OK.

Note: In the Volumes window, do not click Migrate SFM Shares. Close ExtremeZ-IP. 8. After you have set up the ExtremeZ-IP share, re-create the share in Windows using the folder path you created in the previous step. a. Right-click My Computer and select Manage. b. In the Computer Management window, navigate to System Tools > Shared Folders > Shares. c. Write down the existing Share Name, for example AraxiVol ume_MyServerName_J. d. Right-click the existing share, for example AraxiVolume_My ServerName_J, and select Stop Sharing. e. Click Action > New Share and click Next. f. Click Browse and navigate to the AraxiVolume folder you set up in the previous step. Click OK and click Next. g. In the Share a Folder Wizard > Name, Description, and Settings window, type the same Share Name you just deleted, for example AraxiVolume_MyServerName_J. Click Next. h. In the Share a Folder Wizard > Permissions window, select Use custom share and folder permissions and click Customize. i. In the Customize Permissions window, select all the check boxes under the Allow column. Click OK, click Finish, and click Close. 16 Chapter 5—Setting up Mac client computer file-sharing protocols

Next: Stop and restart Prinergy for these changes to take effect.

Identifying non-SFM servers in the OTHERHOSTS file Edit the otherhosts file to prevent Prinergy from making calls to non-SFM servers. Requirements: The OTHERHOSTS file is located in the %Araxi Home%\CreoAraxi\etc folder.

● Perform this task to identify all non-SFM servers (that is, servers not using Microsoft Services for Macintosh) in your system with any Mac client computer protocols—not only with AFP.

● This task applies whenever you configure Mac client computer protocols.

● Prinergy performance suffers unless you ensure that all non-SFM servers are listed in the OTHERHOSTS file. Otherwise, Prinergy makes RPC calls to the SFM service on the server. These calls occur frequently—for example, every time a page is refined. Although the calls eventually time out, they affect Prinergy performance.

1. Locate %AraxiHome%\etc\otherhosts. 2. Open the otherhosts file in a text editor. 3. Locate the [/etc/otherhosts] section, and add "*:MyServerName"="MyServerName" as the third line. [/etc/otherhosts] "SOMEZONE:blatserver1"="NTBLATSERVER1" "SOMEZONE:blatserver2"="NTBLATSERVER2" "*:MyServerName"="MyServerName"

4. In the "*:MyServerName"="MyServerName" line, you can either replace the asterisk (*) with the name of your Mac zone, or leave the asterisk (*) if you don't want to specify any Mac zone. Replace all instances of MyServerName with the name of your server. 5. Locate the [shares] section, and add NtHost="MyServerName", add Mac volume share name=Windows share name, for example "Jobs on MyServerName J"="AraxiVolume_MyServerName_J", and add "AraxiPreps"="AraxiPreps" as the last lines. [shares] NtHost="NTBLATSERVER1" "MacVolumeA"="NTShareA" "MacVolumeB"="NTShareB" NtHost="NTBLATSERVER2" "MacVolumeX"="NTShareX" NtHost="MyServerName" "Jobs on MyServerName J"="AraxiVolume_MyServerName_J" "AraxiPreps"="AraxiPreps" Updating the SFMHOSTS file 17

6. Replace all instances of MyServerName with the name of your server.

Example In this example:

● The tertiary server is called "TertiaryServer" and it is configured in the Mac Zone "Prinergy Lab".

● The first volume name after the Mac Zone ("Prinergy Lab:TertiaryServer"="TertiaryServer") is the UNIX server name that appears on Mac computers.

● The second volume name after the Mac Zone ("Prinergy Lab:TertiaryServer"="TertiaryServer") is the UNIX server name that appears on Windows 2000-based computers.

● The Mac share name is "Jobs on TertiaryServer".

● The Samba share name is "AraxiVolume_TertiaryServer". [/etc/otherhosts] "Prinergy Lab:TertiaryServer"="TertiaryServer" [shares] NtHost="TertiaryServer" "Jobs on TertiaryServer"="AraxiVolume_TertiaryServer" "AraxiPreps"="AraxiPreps" In Finder, click Go > Connect to Server and type afp://TertiaryServer to connect to your server. Then select Jobs on TertiaryServer.

Updating the SFMHOSTS file Update the SFMHOSTS file if you use SFM (Services for MacIntosh).

● Perform this task only on tertiary servers.

● This task applies only if you are using using SFM to enable Mac client computers to connect via AFP to Windows servers.

● Perform this task when you add a server, remove a server, or change the name or IP address of a server.

1. Open the %AraxiHome%\CreoAraxi\etc\SFMHOSTS file in a text editor. 2. In the [/etc/sfmhosts] section of the file, add an entry in the following format: "zone:sfmservername"="ntservername" If there are no zones on your system, type "*" for the zone. 3. Save and close the file. Do not accidentally add a file name extension, such as .txt. 18 Chapter 5—Setting up Mac client computer file-sharing protocols

Next: Stop and restart Prinergy for these changes to take effect.

Enabling Preps under SMB In some network configurations, you must enable integrated Preps on Mac client computers when you use SMB with AppleDouble. Use this procedure only if you use SMB with AppleDouble as your Mac client computer protocol and if you use integrated Preps on Mac client computers that are not in the same domain as the primary server. This Enabling Preps under SMB 19

prevents the error message Could not locate the PrepsPrinergy.cfg template file.

Perform one of the following tasks on each client computer: With this Do this version

Any version Add the Mac client computer to the same domain as the Prinergy primary server.

Mac OS X Add the primary server to the NetInfo™ Manager of the Mac client computer: 10.3 or 10.4 1. Log on to the Mac client computer with an administrator account. 2. In Finder, click Go > Utilities. 3. Double-click NetInfo Manager. 4. Click machines. 5. From the Security menu, choose Authenticate, and type the password of the administrator account. If Deauthenticate is available, skip this step because you are already authenticated. 6. From the Directory menu, choose New Subdirectory. 7. In the lower pane, double-click new_directory, and type the name of the Prinergy primary server. 8. From the Directory menu, choose New Property, and then replace new_property by typing ip_address. 9. Double-click new_value, and replace it by typing the IP address of the Prinergy primary server. 10. From the Domain menu, choose Save Changes, click Update this copy, and then quit NetInfo Manager.

Mac OS X Add the primary server to the hosts file of the Mac client computer: 10.5 or later 1. Log on to the Mac client computer with an administrator account. 2. In Finder, click Go > Utilities. 3. Double-click Terminal. 4. In the Terminal dialog box, type sudo nano /etc/hosts 5. If you are prompted for a password, type your password. 6. Add the IP address of the Prinergy primary server in the following format: ip hostname

7. Press Ctrl+X, press Y to save your changes, and press Enter to save the file in the /etc folder. 20 Chapter 5—Setting up Mac client computer file-sharing protocols Changing Mac client computer file-sharing 6 protocols

You can change your Mac client computer protocol to AFP or to SMB with AppleDouble, and you can convert resources in existing files on job shares. Limitations of protocol conversions using Prinergy Administrator Prinergy Administrator's ability to convert from AFP to SMB or to AFP from SMB with AppleDouble has several limitations.

Files on non-Windows servers require manual conversion Prinergy Administrator can convert only volumes that run on the Windows operating system. Prinergy Administrator cannot convert UNIX volumes, Xserve® volumes, or volumes with any operating system other than Windows. If you have UNIX and Xserve volumes, you must manually convert them.

Some files are not converted on Windows volumes Prinergy Administrator does not convert the following files on Windows volumes:

● Files that are open during the conversion

● Files with names that contain certain special characters, such as * | \ / ? < >

® ● Files that are located on system volumes, in the Recycle Bin, or in Oracle data directories If files are not converted, you can manually convert them using the Fork Translator software.

Conversion is not possible when using VERITAS Prinergy Administrator blocks protocol conversions if the VERITAS Storage Replicator™ (VSR) software is installed on the Prinergy system. To determine whether VERITAS is installed, check the Start menu on the primary server. VERITAS, which is often part of a Hot Standby (EPM+) configuration of Prinergy, uses a Windows operating system service that interferes with SMB, even when the service is stopped. If you copy files from a computer running the Max OS X to a primary or secondary server that is running the VERITAS service, the network is interrupted and Prinergy stops responding. For information about the problem, see the Microsoft Knowledge Base item "Server Randomly Drops All Connections, System Log Records Multiple Instances of Event ID 2000," which is located at http://support.Microsoft.com/kb/288301. If you use VERITAS and you need to copy files to a primary or secondary server, you must replace VERITAS with the DoubleTake software before you can convert protocols. After removing VERITAS, you can convert protocols. 22 Chapter 6—Changing Mac client computer file-sharing protocols

If you use VERITAS and you do not need to copy files to a primary or secondary server (because you store files only on tertiary servers), you can manually convert protocols. The DoubleTake software offers several advantages over VERITAS. For information, see the Prinergy Emergency Platemaking Plus (EPM+) With Double-Take® User Guide.

New volumes are not affected If you add a new volume to the Prinergy system after you convert protocols, any files on that volume will not contain resource information. If you want resources for files on the new volume, you must manually convert the file resources using the Fork Translator software.

Converting to SMB with AppleDouble Use Prinergy Administrator to change the Mac-sharing protocol of Prinergy and files on job volumes to SMB with AppleDouble. Requirements:

● The protocol that you want to adopt must be qualified for the servers in your Prinergy system.

● All Prinergy server and client computers must be successfully updated to Prinergy 3.1.0.7 or later.

● VERITAS Storage Replicator (VSR) software must not be installed in the Prinergy system.

● Plan for down time ranging from one to several hours, depending on the size of your volumes. For example, after you shut down the required software, converting a volume that contains 10,000 files takes two to three minutes. Use this procedure if your system includes one or more Windows job volumes. If your system has only UNIX, XServe, or Isilon servers, you must manually convert the system, which does not require you to stop the Prinergy system.

1. Close all files. Open files will not be converted and, therefore, will not have resources. Converting to SMB with AppleDouble 23

2. Stop all archiving, purging, and retrieving activities:

● If you use the Prinergy Rules-Based Automation (RBA) software and an enabled rule set uses the Archive/Retrieve JTP or Purge JTP, stop Prinergy to prevent the rule sets from executing.

● If you do not stop Prinergy, stop the Archive/Retrieve JTP and Purge JTP. They are located on either the Prinergy primary server or a secondary server.

3. If you use SFM to support AFP, stop and disable the SFM services on all Windows operating system servers in the Prinergy system: a. Right-click My Computer and select Manage. b. In the Computer Management window, expand Services and Applications and click Services. c. In the right pane, right-click File Server for Macintosh and select Properties. d. Click Stop. e. In the Startup type list, select Disabled and click OK. f. In the right pane, right-click Print Server for Macintosh and select Properties. g. Click Stop. h. In the Startup type list, select Disabled and click OK. When SFM stops, all AFP shares are deleted, so there is no need to manually remove AFP mappings. 4. If you use ExtremeZ-IP to support AFP, uninstall it. Click Start > Programs > ExtremeZ-IP > Uninstall ExtremeZ-IP File Server and follow the prompts to uninstall ExtremeZ-IP. 5. In Prinergy Administrator, from the Tools menu, select File Sharing. If File Sharing is not available, verify that you met the requirements at the start of this procedure. The File Sharing dialog box appears, listing the names of every server and input volume in the Prinergy system, including the volumes on all servers listed on the Servers and Input Volumes tabs. 6. In the File Sharing dialog box, select all Windows volumes that contain job data:

● If a volume uses Windows and contains jobs, select it. All Windows job volumes must be converted at the same time.

● If a volume uses Windows but does not contain jobs, you do not have to select it. Select it only if it contains files that you want to convert. For example, you do not need to convert a volume that is used only for temporary storage or a volume that contains hot 24 Chapter 6—Changing Mac client computer file-sharing protocols

folders or smart hot folders that accept input files and move them to other locations.

● If a volume uses UNIX or Xserve, do not select it, because Prinergy cannot convert them. If you select UNIX or Xserve volumes, you create unnecessary and useless hidden files on the target volume.

7. Click Convert to SMB and click OK when prompted to confirm. 8. Wait until the conversion is complete. As Prinergy counts the files on the volumes, the File Sharing dialog box displays Converting. While Prinergy converts files, the dialog box indicates how many files it has converted, such as 500 out of estimated 10,000. The time that the conversion takes depends on the number of files on the volumes. When the conversion is complete, the following changes occur:

● Files on the selected volumes are converted to SMB.

● The File Sharing dialog box indicates how many files were converted, such as Processed 10,000 out of 10,000. Files that do not contain file resources are not processed, so the number of files processed may not match the total number of files, even if there are no errors.

● Prinergy is converted to SMB.

e. Copy the files back to the UNIX volume, but place them in a different folder. If the files contain resource information, AppleDouble files are created during the copying process. f. Delete the original files. 11. If you have a job volume on a server running Mac OS X Server 10.4, use third-party software called Fork Server Helper to convert the Xserve volume. The demonstration version of Fork Server Helper is free to use. a. Contact your service representative or visit the Marcel Bresink Software-Systeme (MBS) Web site at http://www.bresink.de/osx/ForkServerHelper.html to get Fork Server Helper and information about it. b. Use Fork Server Helper to convert the files on the Xserve volume. 12. If you have a job volume on an Isilon server, disable ADS on each Isilon share: a. From a Windows client computer, connect to the Isilon share. b. In the root folder, create a file named t.txt. c. Open a command-prompt window, and change drives to the Isilon share's root folder. d. Run the following command: ren t.txt .com.apple.smb.streams.off

If you do not disable ADS, any client computers with Mac OS X 10.5 may connect to the server via alternate data streams, not AppleDouble. 13. Verify that all non-SFM servers are identified in OTHERHOSTS files. See Identifying non-SFM servers in the OTHERHOSTS file on page 16. 14. Perform either of the following tasks to complete the conversion:

● If you stopped Prinergy, restart it.

● If you stopped the Archive/Retrieve JTP and Purge JTP, start them.

If you use integrated Preps on Mac client computers that are not in the same domain as the primary server, see Enabling Preps under SMB on page 18. If you add a new volume to the Prinergy system after you convert protocols, files on that volume will not contain resource information. If you want resources for files on the new volume, manually convert the files' resources to AFP format. See Converting files with Fork Translator on page 31. 26 Chapter 6—Changing Mac client computer file-sharing protocols

Converting to AFP Use Prinergy Administrator to change the Mac-sharing protocol of Prinergy and files on job volumes from SMB to AFP with AppleDouble. Requirements:

● The protocol that you want to adopt must be qualified for the servers in your Prinergy system.

● All Prinergy server and client computers must be successfully updated to Prinergy 3.1.0.7 or later.

● VERITAS Storage Replicator (VSR) software must not be installed in the Prinergy system.

1. Close all files. Open files will not be converted and, therefore, will not have resources. 2. Stop all archiving, purging, and retrieving activities:

● If you use the Prinergy Rules-Based Automation (RBA) software and an enabled rule set uses the Archive/Retrieve JTP or Purge JTP, stop Prinergy to prevent the rule sets from executing.

● If you do not stop Prinergy, stop the Archive/Retrieve JTP and Purge JTP. They are located on either the Prinergy primary server or a secondary server.

3. (Optional) If your system requires SFM, configure SFM on all Windows servers in the Prinergy system. See Starting SFM to support AFP on page 11. 4. (Optional) If you have a server that requires ExtremeZ-IP, install and configure ExtremeZ-IP on all Windows servers in the Prinergy system. See Configuring AFP with ExtremeZ-IP on page 12. Converting to AFP 27

5. In Prinergy Administrator, from the Tools menu, select File Sharing. If File Sharing is not available, verify that you met the requirements at the start of this procedure. The File Sharing dialog box appears, listing the names of every server and input volume in the Prinergy system, including the volumes on all servers listed on the Servers and Input Volumes tabs. 6. In the File Sharing dialog box, select all Windows volumes that contain job data:

● If a volume uses Windows and contains jobs, select it. All Windows job volumes must be converted at the same time.

● If a volume uses Windows but does not contain jobs, you do not have to select it. Select it only if it contains files that you want to convert. For example, you do not need to convert a volume that is used only for temporary storage or a volume that contains hot folders or smart hot folders that accept input files and move them to other locations.

7. Click Convert to AFP and click OK when prompted to confirm. 8. Wait until the conversion is complete. As Prinergy counts the files on the volumes, the File Sharing dialog box displays Converting. While Prinergy converts files, the dialog box indicates how many files it has converted, such as 500 out of estimated 10,000. The time that the conversion takes depends on the number of files on the volumes. When the conversion is complete, the following changes occur:

● Files on the selected volumes are converted to SMB.

● Prinergy is converted to SMB. 28 Chapter 6—Changing Mac client computer file-sharing protocols

9. If errors occur, a message appears, telling you to view the log file: a. Click OK to close the error message. b. In the %AraxiHome%\CreoAraxi\System folder, open the forktranslator.log file in Notepad. c. If the log identifies job files that were not converted, locate the original job file from a backup or other source, and copy the file to the volume. Resources are created automatically when you copy the file. 10. If you have a job volume on a UNIX server with an AFP server, such as the Xinet software or the HELIOS software, use a Mac OS X computer to convert the files on the UNIX volume to AFP: a. Use a Mac computer running Mac OS X to connect to the UNIX volume via SMB. b. Copy the files from the UNIX volume to another location, such as the Mac computer. c. Enable the AFP server on the UNIX volume. d. Use a Mac computer running Mac OS X to connect to the UNIX volume via AFP. e. Copy the files back to the UNIX volume, but place them in a different folder If the files contain resource information, resource forks are created during the copying process. f. Delete the original files. 11. If you have a job volume on a server running Mac OS X Server 10.4, use third-party software called Fork Server Helper to convert the Xserve volume. The demonstration version of Fork Server Helper is free to use. a. Contact your service representative or visit the Marcel Bresink Software-Systeme (MBS) Web site at http://www.bresink.de/osx/ForkServerHelper.html to get Fork Server Helper and information about it. b. Use Fork Server Helper to convert the files on the Xserve volume. 12. Verify that all non-SFM servers are identified in OTHERHOSTS files. See Identifying non-SFM servers in the OTHERHOSTS file on page 16. 13. Perform either of the following tasks to complete the conversion:

● If you stopped Prinergy, restart it.

● If you stopped the Archive/Retrieve JTP and Purge JTP, start them. Manually converting protocols 29

If you add a new volume to the Prinergy system after you convert protocols, files on that volume will not contain resource information. If you want resources for files on the new volume, manually convert the files' resources to AFP format.

Manually converting protocols Manually change the Mac-sharing protocol of Prinergy and files on job volumes to AFP or to SMB with AppleDouble. Requirements:

● The protocol that you want to adopt must be qualified for the servers in your Prinergy system.

● All Prinergy server and client computers must be successfully updated to Prinergy 3.1.0.7 or later. Only use this procedure if one of the following conditions apply:

● Your system includes the VERITAS Storage Replicator (VSR) software or the VERITAS Replication Exec software, you are not able to replace VERITAS with the Double-Take software, and you do not need to copy files to the secondary server (because you store jobs only on tertiary servers).

● Your system does not include any Windows job volumes, you want to convert file sharing protocols without stopping the Prinergy system, and you are converting between AFP and SMB with AppleDouble.

1. Close all files. Open files will not be converted and, therefore, will not have resources. 2. Change a registry setting that switches between SMB and AFP in Prinergy: Important: If you are not familiar with using Registry Editor, contact your service representative for help with editing the registry key. If you use Registry Editor incorrectly, you can cause serious problems that may require you to reinstall your operating system. Kodak does not guarantee that problems caused by incorrect use of Registry Editor can be resolved. Use Registry Editor at your own risk. a. In the registry of the Prinergy primary server, locate the HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\Set tings\Default\System subkey. b. Change the FileSystemConnectivityForOSXClient value. For SMB, set it to 1. For AFP, set it to 2. 3. If you have a job volume on a Windows server, convert the files on it with the Fork Translator software. See Converting files with Fork Translator on page 31. 30 Chapter 6—Changing Mac client computer file-sharing protocols

4. If you have a job volume on a UNIX server that also has an AFP server, such as the Xinet software or the HELIOS software, use a Mac OS X computer to convert the files on the UNIX volume to SMB: a. Use a Mac computer running Mac OS X to connect to the UNIX volume via AFP. b. Copy the files from the UNIX volume to another location, such as the Mac computer. c. Disable the AFP server on the UNIX volume. d. Use a Mac computer running Mac OS X to connect to the UNIX volume via SMB. e. Copy the files back to the UNIX volume, but place them in a different folder. If the files contain resource information, AppleDouble files are created during the copying process. f. Delete the original files. 5. If you have a job volume on a server running Mac OS X Server 10.4, use third-party software called Fork Server Helper to convert the Xserve volume. The demonstration version of Fork Server Helper is free to use. a. Contact your service representative or visit the Marcel Bresink Software-Systeme (MBS) Web site at http://www.bresink.de/osx/ForkServerHelper.html to get Fork Server Helper and information about it. b. Use Fork Server Helper to convert the files on the Xserve volume. 6. If you have a job volume on an Isilon server, disable ADS on each Isilon share: a. From a Windows client computer, connect to the Isilon share. b. In the root folder, create a file named t.txt. c. Open a command-prompt window, and change drives to the Isilon share's root folder. d. Run the following command: ren t.txt .com.apple.smb.streams.off

If you do not disable ADS, any client computers with Mac OS X 10.5 may connect to the server via alternate data streams, not AppleDouble. 7. Verify that all non-SFM servers are identified in OTHERHOSTS files. See Identifying non-SFM servers in the OTHERHOSTS file on page 16. Converting files with Fork Translator 31

Converting files with Fork Translator Manually run the Fork Translator utility to change resource information for specific files or folders. Requirements: All Prinergy server and client computers must be successfully updated to Prinergy 3.1.0.7 or later. Use Fork Translator to convert file resources in the following situations:

● You use special fonts, which are not converted by Prinergy Administrator.

● Files were not converted by Prinergy Administrator because they were open or had special characters or for other reasons.

● You must manually convert files—for example, because you use the VERITAS software or you have an all-UNIX system.

● You want to restore files that were archived using NT Backup with a different Mac client computer protocol.

1. Close all files that you want to convert. 2. On the Prinergy primary server or another Windows computer, open a command-prompt window. 3. Enter the following command: The complete syntax for the command is: forktranslator {-a|-s|-h} [-i] [-n|-o] [-e] [-p] [-v] pathname... where

-a Create resource fork information from alternate data streams (ADS) to AppleDouble files.

-s Create resource fork information from AppleDouble files to alternate data streams (ADS).

-h Print this usage information.

-i Ignore errors and keeps processing other files.

-n Do not execute. Lists file names only.

-e Exclude the specified folders, separted by semicolons. 32 Chapter 6—Changing Mac client computer file-sharing protocols

-o Overwrite any existing fork information in AppleDouble files or alternate data streams (ADS), if present .

-p Print progress to the screen.

-v Write to standard output (stdout) files. Implied by -n.

pathname... Operate on the specified files and/or folders, separated by spaces. Folders are treated recursively.

4. Close the command-prompt window.

Troubleshooting Refer to this section if you have trouble running ExtremeZ-IP. If you cannot see your shares and you get this message in the Windows system event log: Failed to initialize AppleTalk® support (10049). The ExtremeZ-IP server will not appear in the Chooser, modify your registry.

1. Click Start > Run, type regedit and click OK. 2. Navigate to My Computer > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > AppleTalk > Parameters. 3. Right-click DesiredZone and select Modify. 4. In the Value data box, type * (asterisk) and click OK. 5. Close the Registry Editor window. 6. Right-click My Computer and select Manage. 7. In the Computer Management window, expand Services and Applications and click Services. 8. In the right pane, right-click ExtremeZ-IP File and Print Server for Macintosh and select Restart. 9. Close the Computer Management window. Index

D S

Domain Name System 17 SFMHOSTS file 17 Eastman Kodak Company 343 State Street Rochester, NY 14650 U.S.A. © Kodak, 2008. All Rights Reserved. TM: Kodak To learn more about solutions from Kodak, visit http://graphics.kodak.com. Subject to technical change without notice.