Prinergy Mac Client File-Sharing Protocols

PrinergyWorkflow System

Version 4 and 5

Mac Client File-Sharing ProtocolsEnglish

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

Contents

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

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

7Limitations of Mac client computer file-sharing protocols3

9Understanding file resources4

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

11Setting up Mac client computer file-sharing protocols5

Starting SFM to support AFP.....................................................................................................................................................11Configuring AFP with ExtremeZ-IP..........................................................................................................................................12Identifying non-SFM servers in the OTHERHOSTS file......................................................................................................16Updating the SFMHOSTS file....................................................................................................................................................17Enabling Preps under SMB........................................................................................................................................................18

21Changing Mac client computer file-sharing protocols6

Limitations of protocol conversions using Prinergy Administrator.................................................................................21Converting to SMB with AppleDouble...................................................................................................................................22Converting to AFP.......................................................................................................................................................................26Manually converting protocols................................................................................................................................................29Converting files with Fork Translator......................................................................................................................................31Troubleshooting...........................................................................................................................................................................32

Prinergyiv

Qualified tertiary servers and Mac client computerfile-sharing protocols

Tertiary servers are qualified for use with Prinergy® only using specificnetwork file-sharing protocols to and from Mac® client computers. Eachoperating system or platform has a defined service level.

Note: Service levels are described below the table.

Service level and commentsMac client computer protocolTertiary server

● Service level 1, if the server ispurchased from Kodak®

● Service level 3, if the server isnot purchased from Kodak

Either of the following protocols:

● AFP with SFM

● AFP with ExtremeZ-IP™

We are working to qualify this operatingsystem for SMB with ADS, if all Mac clientcomputers run Mac OS® X 10.5. Do notuse SMB with ADS until it is qualified.

Windows® Server 2000 andWindows Server® 2003

Service level 3AFP with ExtremeZ-IP

We are working to qualify this operatingsystem for SMB with ADS, if all Mac clientcomputers run Mac OS X 10.5. Do not useSMB with ADS until it is qualified.

Windows 2003 Server Cluster

Not currently qualifiedNot currently qualified


Windows Server 2008

Service level 1SMB with AppleDouble


Isilon

Service level 2 until Mac OS XServer 10.5 is qualified.

Service level 3 after Mac OS XServer 10.5 is qualified.

SMB with AppleDoubleMac OS X Server 10.4

Service level and commentsMac client computer protocolTertiary server

Service level 2, when this solutionis qualified

Qualified for AFP for Prinergy 4.1.2.2 andhigher

Not yet qualified for any other protocol

Mac OS X Server 10.5

Service level 1

Archiving is not supported.

AFP via HeliosBrisque® Server, which uses Sambaand Helios

Service level 3

Archiving is not supported.

AFP via the AFP serverUNIX® with Samba and an AFPserver, such as Helios or Xinet®

Service level 3SMB with AppleDoubleUNIX with Samba and no AFP server

Service level descriptions

The solution is documented, tested with every major and minorupgrade, and fully supported, which means problems areinvestigated.

Servicelevel 1

The solution is documented and tested with every major upgradebut not directly supported.

A problem will be investigated only if it meets the followingconditions:

Servicelevel 2

● The problem is caused by Prinergy.

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

The solution is documented but not tested with every majorupgrade and not supported. Support is limited to documentation.

A problem will be investigated only if it meets the followingconditions:

Servicelevel 3

● The problem is caused by Prinergy.

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

After a Prinergy upgrade, you must confirm that the solution stillworks to your satisfaction. Consider buying a software testingsolution to test upgrades before implementing them on aproduction system. For information about testing solutions, contactyour sales representative.

Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols2

Limitations across all solutionsNote: Kodak does not support, and assumes no responsibility for, problems orperformance issues that may occur as a result of using third-party products.Problems related to third-party products are not covered by Kodak servicecontracts.

● All servers in your Prinergy system must use the same Mac client computerprotocol. Otherwise, Mac users may unknowingly mount the a volume usingthe 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 supplieror find an alternate solution.

● A storage area network connected to a tertiary server is qualified andsupported, according to the operating system of the tertiary server that it isconnected 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 isnot documented, tested, or supported. Use it at your own risk.NFS has manyknown problems and many potential problems, because Microsoft® does nottest the solution on all variants of UNIX. If you use this solution, use it onlyfor input volumes, not for job volumes.

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

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

● All other configurations not identified above or in the above table.

3

Chapter 1—Qualified tertiary servers and Mac client computer file-sharing protocols4

List of Mac client computer file-sharing protocols and relatedsoftware

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

Protocols for connecting Mac client computers in Prinergy

Server Message Block protocol, which is built into the Windowsoperating system

SMB

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 foreignfiles

AppleDouble stores file resources in separate files with a ._ prefix.For example, a file named input.pdf has a correspondingAppleDouble file that is named ._input.pdf.

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

Apple® Filing Protocol, which is built into the Mac OSAFP

On Windows servers, AFP can be implemented via SFM or ExtremeZ-IP.On UNIX servers, AFP can be implemented with Helios, Xinet, and othersoftware.

AFP stores file resources in resource forks.

Network File System, which is built into the UNIX operating systemNFS

On Windows servers, NFS can be implemented with SFU.

Software to assist Mac client computer connections

Microsoft Services for Macintosh®, which is built into theWindows Server 2000 and Windows Server 2003 operatingsystems to provide AFP connections for Mac client computers

SFM

File server software that you can install on a Windows serverto provide AFP connections for Mac client computers.

ExtremeZ-IP

Open-source file server software that you can install on a UNIXtertiary server to provide SMB connections for the WindowsPrinergy primary and secondary servers

Samba

Software that provides AFP connections on a UNIX serverHelios

Software that provides AFP connections on a UNIX serverXinet

Services for UNIX, which you can install on a Windows serverto provide NFS connections

SFU

Chapter 2—List of Mac client computer file-sharing protocols and related software6

Limitations of Mac client computer file-sharing protocols

Many Mac client computer protocols have significant limitations in aPrinergy system.

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

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

● Files copy more slowly when you copy a large number of small files. Theper-file overhead is doubled because there are two files.

● When InSite™ users upload or download files, resources are lost becauseInSite is not AppleDouble enabled. This issue applies to both Windows andMac client computers. This issue is not significant because InSite primarilyuses PDF files.

● If some Mac client computers use Mac OS X 10.4.7 or earlier, the operatingsystem may leave files open, locking them from other users. To avoid thisissue, 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 FontConverter works only with font files that have resource forks stored in alternatedata streams. You must use the Fork Translator software to manually convertthe font files' resources from AppleDouble to ADS.

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

AFPThe main limitation of all AFP servers is that archiving is not supported on tertiaryservers using UNIX or on tertiary servers using Mac OS X 10.4 or earlier. Althoughthe 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 corrupteddesktops

● Has a limited life span. In the Windows 2003 operating system, Microsoftdoes not support SFM. As of Windows 2008, SFM will not exist.

● Is not scalable

● Results in slower Prinergy performance under heavy loads

● Has indexing problems

● Limits the volume size to a maximum of 2 GB

NFSNFS is not qualified for use with Prinergy, so its limitations are not relevant.

Chapter 3—Limitations of Mac client computer file-sharing protocols8

Understanding fileresources4

Files have resources, such as icons that appears next to the file name ina file browser.

File resourcesThe Mac OS and the Windows operating system store file resources indifferent ways.

What file resources areFile 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 resourcesThe Mac OS and the Windows operating system store file resource informationin different ways, so files stored in one operating system lack resources whenopened in the other operating system.

If a file lacks resources:

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

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

● 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 previewimage, and the Open With and Kind fields are blank.

Resources do not affect how Prinergy processes files. Prinergy processes filesthe same way, regardless of whether they have resources. The exception is FontConverter as mentioned in Limitations of Mac client computer file-sharing protocolson page 7.

Storing file resourcesFile resources can be stored in forks, AppleDouble files, or alternate datastreams.

Resource forksResource forks store file resources in the file itself.

The Hierarchical File System (HFS) of the Mac OS uses resource forks.

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

Alternate data streams (ADS)Alternate data streams allow files to be associated with more than one datastream. One use of ADS is to store resources.

The New Technology File System (NTFS) of the Windows operating system andIsilon support alternate data streams.

SFM and ExtremeZ-IP store resources in an alternate data stream namedAFP_Resource.

OtherOther platforms, such as EtherShare and Xinet, store resources in separate fileswith special file name extensions.

Archiving and Mac client computer file-sharing protocolsPrinergy archives, retrieves, and restores appropriately when you changeprotocols.

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 withAppleDouble, when Prinergy retrieves the files, it converts the resourceinformation from resource forks into AppleDouble files. If files containresource information in both AppleDouble files and resource forks, thePrinergy system uses the resource information required by the currentprotocol and ignores the other resource information.

Chapter 4—Understanding file resources10

Setting up Mac clientcomputer file-sharingprotocols5

Starting SFM to support AFPStart Microsoft Services For Macintosh (SFM), if necessary.

● This task applies only if you are using using SFM to enable Mac clientcomputers 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 andApplications and click Services.

3. In the right pane, right-click File Server for Macintosh and selectProperties.

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 selectProperties.

7. In the Startup type list, select Automatic and click Apply.

8. Click Start and click OK.

Configuring AFP with ExtremeZ-IPInstall and configure ExtremeZ-IP on a Prinergy primary, secondary, ortertiary server to enable AFP connections from Mac client computerswithout Services for Macintosh (SFM).

Requirements:

● This task applies only if you are using ExtremeZ-IP to enable Macclient 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 taskon primary, secondary, or tertiary servers.

If you are using earlier versions, perform this task only on tertiaryservers because ExtremeZ-IP is not supported on primary or secondaryservers on earlier versions.

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

● 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 ofa volume. ExtremeZ-IP does not allow shares to be created belowanother share. If you create a share at the root of the volume, youcannot 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 yourexisting 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 systemservers in the Prinergy system:

a. Right-click My Computer and select Manage.

b. In the Computer Management window, expand Services andApplications and click Services.

c. In the right pane, right-click File Server for Macintosh and selectProperties.

d. Click Stop.

Chapter 5—Setting up Mac client computer file-sharing protocols12

e. In the Startup type list, select Disabled and click OK.

f. In the right pane, right-click Print Server for Macintosh and selectProperties.

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 needto manually remove AFP mappings.

If you do not disable the service, a message about migrating SFMshares appears when you start ExtremeZ-IP for the first time. You caneither click Yes to migrate all shares, or click No and create the sharesmanually for SMB and Mac shares.

2. Install the ExtremeZ-IP File Server software on the Prinergy serverusing the ExtremeZ-IP Quick Start Guide that is available athttp://www.grouplogic.com.

3. If you just installed ExtremeZ-IP, you can start the ExtremeZ-IPAdministrator immediately. Otherwise click Start > Programs >ExtremeZ-IP > ExtremeZ-IP Administrator.

If a warning appears that non-standard port 549 is in use, you canignore this warning for now as you will change it later.

4. When you see the message The server contains Services forMacintosh (SFM) shares. Would you like to migrate these

shares to ExtremeZ-IP volumes nad disable SFM?, perform eitherof the following actions:

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

● If you are installing on a tertiary server, click No because you willcreate 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.

13Configuring AFP with ExtremeZ-IP

http://www.grouplogic.com

6. On the ExtremeZ-IP Administrator Summary screen, click Settings toconfigure 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 iscleared

b. Click the Security tab, and confirm that the following check boxesare 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 checkbox is cleared.

d. Click the Filename Policy tab, and confirm that all of the checkboxes are cleared.

e. Click the Service Discovery tab, and confirm that the Zidget/HTTPcheck box is cleared.

Important: The Server Name must not have IP at the end of theserver 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 migratedshares, 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 mustuse the same folder path as the ExtremeZ-IP share.

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

● If you have existing jobs and are adopting ExtremeZ-IP, do notchange share names.


If you did not migrate shares on atertiary server

If you migrated shares on a primary orsecondary server

On the ExtremeZ-IP AdministratorSummary screen, click Volumes.

On the ExtremeZ-IP AdministratorSummary screen, click Volumes.

In the Volumes dialog box, clickCreate.

In the Volumes dialog box, select the Jobson J drive volume, for example, Jobs onMyServerName J, and click Modify.

Locate and select your Jobs drive,usually drive J.

In the Volume Properties dialog box, clickthe ellipses beside Path and select yourJobs drive, usually drive J.

Click Make New Folder and type theshared folder name, for example,AraxiVolume. Click OK.

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

In the Volume Properties dialog box,type the Volume Name of thePrinergy share, for example, Jobson MyServerName J. Click OK.

When asked if you want to restart thevolume, click Yes and click Restart.

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 inWindows using the folder path you created in the previous step.


b. In the Computer Management window, navigate to System Tools> Shared Folders > Shares.

c. Write down the existing Share Name, for example AraxiVolume_MyServerName_J.

d. Right-click the existing share, for example AraxiVolume_MyServerName_J, and select Stop Sharing.

e. Click Action > New Share and click Next.

f. Click Browse and navigate to the AraxiVolume folder you set upin the previous step. Click OK and click Next.

g. In the Share a Folder Wizard > Name, Description, and Settingswindow, type the same Share Name you just deleted, for exampleAraxiVolume_MyServerName_J. Click Next.

h. In the Share a Folder Wizard > Permissions window, select Usecustom share and folder permissions and click Customize.

i. In the Customize Permissions window, select all the check boxesunder the Allow column. Click OK, click Finish, and click Close.

15Configuring AFP with ExtremeZ-IP

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

Identifying non-SFM servers in the OTHERHOSTS fileEdit the otherhosts file to prevent Prinergy from making calls tonon-SFM servers.

Requirements:

The OTHERHOSTS file is located in the %AraxiHome%\CreoAraxi\etc folder.

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

● This task applies whenever you configure Mac client computerprotocols.

● Prinergy performance suffers unless you ensure that all non-SFMservers are listed in the OTHERHOSTS file. Otherwise, Prinergy makesRPC calls to the SFM service on the server. These calls occurfrequently—for example, every time a page is refined. Although thecalls 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 replacethe asterisk (*) with the name of your Mac zone, or leave the asterisk(*) if you don't want to specify any Mac zone. Replace all instancesof MyServerName with the name of your server.

5. Locate the [shares] section, and add NtHost="MyServerName", addMac volume share name=Windows share name, for example "Jobson 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"


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

Example

In this example:

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

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

● The second volume name after the Mac Zone ("PrinergyLab:TertiaryServer"="TertiaryServer") is the UNIX servername 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 typeafp://TertiaryServer to connect to your server. Thenselect Jobs on TertiaryServer.

Updating the SFMHOSTS fileUpdate 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 clientcomputers to connect via AFP to Windows servers.

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

1. Open the %AraxiHome%\CreoAraxi\etc\SFMHOSTS file in atext editor.

2. In the [/etc/sfmhosts] section of the file, add an entry in the followingformat: "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.

17Updating the SFMHOSTS file

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

Enabling Preps under SMBIn some network configurations, you must enable integrated Preps onMac client computers when you use SMB with AppleDouble.

Use this procedure only if you use SMB with AppleDouble as your Macclient computer protocol and if you use integrated Preps on Mac clientcomputers that are not in the same domain as the primary server. This


prevents the error message Could not locate the PrepsPrinergy.cfgtemplate file.

Perform one of the following tasks on each client computer:

Do thisWith thisversion

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

Add the primary server to the NetInfo™ Manager of the Mac client computer:

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 administratoraccount. 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 typingip_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 NetInfoManager.

Mac OS X10.3 or 10.4

Add the primary server to the hosts file of the Mac client computer:

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.

Mac OS X10.5 or later

19Enabling Preps under SMB


Changing Mac clientcomputer file-sharingprotocols6

You can change your Mac client computer protocol to AFP or to SMB withAppleDouble, and you can convert resources in existing files on job shares.

Limitations of protocol conversions using PrinergyAdministrator

Prinergy Administrator's ability to convert from AFP to SMB or to AFPfrom SMB with AppleDouble has several limitations.

Files on non-Windows servers require manual conversionPrinergy Administrator can convert only volumes that run on the Windowsoperating system. Prinergy Administrator cannot convert UNIX volumes, Xserve®

volumes, or volumes with any operating system other than Windows. If you haveUNIX and Xserve volumes, you must manually convert them.

Some files are not converted on Windows volumesPrinergy 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 Translatorsoftware.

Conversion is not possible when using VERITASPrinergy Administrator blocks protocol conversions if the VERITAS StorageReplicator™ (VSR) software is installed on the Prinergy system. To determinewhether 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 whenthe service is stopped. If you copy files from a computer running the Max OS Xto a primary or secondary server that is running the VERITAS service, the networkis 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 athttp://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 convertprotocols. After removing VERITAS, you can convert protocols.

http://support.Microsoft.com/kb/288301

If you use VERITAS and you do not need to copy files to a primary or secondaryserver (because you store files only on tertiary servers), you can manually convertprotocols.

The DoubleTake software offers several advantages over VERITAS. Forinformation, see the Prinergy Emergency Platemaking Plus (EPM+) WithDouble-Take® User Guide.

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

Converting to SMB with AppleDoubleUse Prinergy Administrator to change the Mac-sharing protocol ofPrinergy and files on job volumes to SMB with AppleDouble.

Requirements:

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

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

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

● Plan for down time ranging from one to several hours, depending onthe size of your volumes. For example, after you shut down the requiredsoftware, converting a volume that contains 10,000 files takes two tothree minutes.

Use this procedure if your system includes one or more Windows jobvolumes. If your system has only UNIX, XServe, or Isilon servers, youmust manually convert the system, which does not require you to stopthe Prinergy system.

1. Close all files.

Open files will not be converted and, therefore, will not have resources.

Chapter 6—Changing Mac client computer file-sharing protocols22

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

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

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

3. If you use SFM to support AFP, stop and disable the SFM services onall Windows operating system servers in the Prinergy system:


b. In the Computer Management window, expand Services andApplications and click Services.

c. In the right pane, right-click File Server for Macintosh and selectProperties.

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 selectProperties.

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 needto 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 andfollow 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 requirementsat the start of this procedure.

The File Sharing dialog box appears, listing the names of every serverand input volume in the Prinergy system, including the volumes on allservers listed on the Servers and Input Volumes tabs.

6. In the File Sharing dialog box, select all Windows volumes that containjob data:

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

● If a volume uses Windows but does not contain jobs, you do nothave to select it. Select it only if it contains files that you want toconvert. For example, you do not need to convert a volume that isused only for temporary storage or a volume that contains hot

23Converting to SMB with AppleDouble

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

● If a volume uses UNIX or Xserve, do not select it, because Prinergycannot convert them. If you select UNIX or Xserve volumes, youcreate 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 dialogbox displays Converting. While Prinergy converts files, the dialog boxindicates how many files it has converted, such as 500 out ofestimated 10,000. The time that the conversion takes depends onthe 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 wereconverted, such as Processed 10,000 out of 10,000. Files that donot contain file resources are not processed, so the number of filesprocessed may not match the total number of files, even if thereare no errors.

● Prinergy is converted to SMB.

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 theforktranslator.log file in Notepad.

c. If the log identifies job files that were not converted, locate theoriginal job file from a backup or other source, and copy the file tothe volume.Resources are created automatically when you copy the file.

10. 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 Xcomputer to convert the files on the UNIX volume to SMB:

a. Use a Mac computer running Mac OS X to connect to the UNIXvolume via AFP.

b. Copy the files from the UNIX volume to another location, such asthe Mac computer.

c. Disable the AFP server on the UNIX volume.

d. Use a Mac computer running Mac OS X to connect to the UNIXvolume via SMB.


e. Copy the files back to the UNIX volume, but place them in adifferent folder.If the files contain resource information, AppleDouble files arecreated 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 theXserve volume.

The demonstration version of Fork Server Helper is free to use.

a. Contact your service representative or visit the Marcel BresinkSoftware-Systeme (MBS) Web site athttp://www.bresink.de/osx/ForkServerHelper.html to get Fork ServerHelper 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 Isilonshare:

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 Isilonshare'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.5may 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 samedomain 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, fileson that volume will not contain resource information. If you want resources forfiles on the new volume, manually convert the files' resources to AFP format.See Converting files with Fork Translator on page 31.

25Converting to SMB with AppleDouble

http://www.bresink.de/osx/ForkServerHelper.html

Converting to AFPUse Prinergy Administrator to change the Mac-sharing protocol ofPrinergy and files on job volumes from SMB to AFP with AppleDouble.

Requirements:



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

● Plan for down time ranging from one to several hours, depending onthe size of your volumes. For example, after you shut down the requiredsoftware, converting a volume that contains 10,000 files takes two tothree minutes.

Use this procedure if your system includes one or more Windows jobvolumes. If your system has only UNIX, XServe, or Isilon servers, youmust manually convert the system, which does not require you to stopthe Prinergy system.

1. Close all files.


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

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

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

3. (Optional) If your system requires SFM, configure SFM on all Windowsservers 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 andconfigure ExtremeZ-IP on all Windows servers in the Prinergy system.

See Configuring AFP with ExtremeZ-IP on page 12.


5. In Prinergy Administrator, from the Tools menu, select File Sharing.

If File Sharing is not available, verify that you met the requirementsat the start of this procedure.

The File Sharing dialog box appears, listing the names of every serverand input volume in the Prinergy system, including the volumes on allservers listed on the Servers and Input Volumes tabs.

6. In the File Sharing dialog box, select all Windows volumes that containjob data:

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

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

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

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 dialogbox displays Converting. While Prinergy converts files, the dialog boxindicates how many files it has converted, such as 500 out ofestimated 10,000. The time that the conversion takes depends onthe 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 wereconverted, such as Processed 10,000 out of 10,000. Files that donot contain file resources are not processed, so the number of filesprocessed may not match the total number of files, even if thereare no errors.

● Prinergy is converted to SMB.

27Converting to AFP

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 theforktranslator.log file in Notepad.

c. If the log identifies job files that were not converted, locate theoriginal job file from a backup or other source, and copy the file tothe 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, suchas the Xinet software or the HELIOS software, use a Mac OS Xcomputer to convert the files on the UNIX volume to AFP:

a. Use a Mac computer running Mac OS X to connect to the UNIXvolume via SMB.


c. Enable the AFP server on the UNIX volume.

d. Use a Mac computer running Mac OS X to connect to the UNIXvolume via AFP.

e. Copy the files back to the UNIX volume, but place them in adifferent folderIf the files contain resource information, resource forks are createdduring the copying process.







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.



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

Manually converting protocolsManually change the Mac-sharing protocol of Prinergy and files on jobvolumes to AFP or to SMB with AppleDouble.

Requirements:



Only use this procedure if one of the following conditions apply:

● Your system includes the VERITAS Storage Replicator (VSR) softwareor the VERITAS Replication Exec software, you are not able to replaceVERITAS with the Double-Take software, and you do not need to copyfiles to the secondary server (because you store jobs only on tertiaryservers).

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

1. Close all files.


2. Change a registry setting that switches between SMB and AFP inPrinergy:

Important: If you are not familiar with using Registry Editor, contactyour service representative for help with editing the registry key. Ifyou use Registry Editor incorrectly, you can cause serious problemsthat may require you to reinstall your operating system. Kodak doesnot guarantee that problems caused by incorrect use of Registry Editorcan be resolved. Use Registry Editor at your own risk.

a. In the registry of the Prinergy primary server, locate theHKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\Settings\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 itwith the Fork Translator software.See Converting files with Fork Translator on page 31.

29Manually converting 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 Xcomputer to convert the files on the UNIX volume to SMB:

a. Use a Mac computer running Mac OS X to connect to the UNIXvolume via AFP.


c. Disable the AFP server on the UNIX volume.

d. Use a Mac computer running Mac OS X to connect to the UNIXvolume via SMB.

e. Copy the files back to the UNIX volume, but place them in adifferent folder.If the files contain resource information, AppleDouble files arecreated during the copying process.






6. If you have a job volume on an Isilon server, disable ADS on each Isilonshare:

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 Isilonshare'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.5may connect to the server via alternate data streams, not AppleDouble.




Converting files with Fork TranslatorManually run the Fork Translator utility to change resource informationfor specific files or folders.

Requirements: All Prinergy server and client computers must besuccessfully 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 PrinergyAdministrator.

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

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

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

1. Close all files that you want to convert.

2. On the Prinergy primary server or another Windows computer, opena 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

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

-a

Create resource fork information from AppleDouble files toalternate data streams (ADS).

-s

Print this usage information.-h

Ignore errors and keeps processing other files.-i

Do not execute. Lists file names only.-n

Exclude the specified folders, separted by semicolons.-e

31Converting files with Fork Translator

Overwrite any existing fork information in AppleDouble files oralternate data streams (ADS), if present .

-o

Print progress to the screen.-p

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

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

pathname...

4. Close the command-prompt window.

TroubleshootingRefer to this section if you have trouble running ExtremeZ-IP.

If you cannot see your shares and you get this message in the Windows systemevent log: Failed to initialize AppleTalk® support (10049). TheExtremeZ-IP server will not appear in the Chooser, modify yourregistry.

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 Applicationsand click Services.

8. In the right pane, right-click ExtremeZ-IP File and Print Server for Macintoshand select Restart.

9. Close the Computer Management window.


Index

D

Domain Name System 17

S

SFMHOSTS file 17

Eastman Kodak Company343 State StreetRochester, NY 14650 U.S.A.

© Kodak, 2008. All Rights Reserved.TM: Kodak

To learn more about solutions from Kodak, visithttp://graphics.kodak.com.

Subject to technical change without notice.

Documents

Prinergy Mac Client File-Sharing Protocols