• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 575
  • Last Modified:

Macintosh Files Residing on Windows Server

Hello...
I have a 2 related questions. My 1st QUESTION is: I'd like to know at what point a 'Macintosh Resource Fork' can be lost with it's corresponding data fork when it resides on a Windows File Server? What do I need to avoid as a sysadmin on the Windows File Server that could mess up Macintosh Files that sit on it?

Basically the Windows 2000 Server has NTFS running on it along with 'Services for Macintosh' although the folder where the macintosh files sit is NOT shared out/published as a Macintosh Volume for security reasons. Macintosh Files get uploaded into this folder via a 3rd party client application.

Second, due to space constraints, I need to copy the Macintosh Folder from the Windows 2000 Server to a new Windows 2003 Server. Here's my 2nd QUESTION: Can I just do a regulary Windows Copy from Server 1 to Server 2 and maintain all the Resource Forks? Or must I do the Server to Server copy via a Macintosh?

The files are critical and they are about 300 GB of macintosh data that I don't want to mess up. Any help and direction on this would be appreciated.

Thx
Ken
0
kencrest
Asked:
kencrest
  • 2
2 Solutions
 
slyongCommented:
Hi Ken,

Just from my understanding.  The Resource Fork is only maintained when you copy with Service for Macintosh protocol.  If you copy the file directly from directory to another directory, it will be lost.

The best way to perform the migration is to mount both UAM volumes on a Mac and transfer the file across using a Mac.

0
 
ParadiseITSCommented:
Ken -- even if you don't give anyone access to it, the files MUST reside on a Services for Macintosh Share... otherwise Windows will not see the RF as slyong said.  So, create the share, and only give access to admin or whomever you feel comfortable with .
0
 
kencrestAuthor Commented:
Hi Slyong/PardiseITS,
I'm testing this out and will let you know tomorrow my results...thx for the feedback.

Ken
0
 
kencrestAuthor Commented:
Hi Slyong/ParadiseITS,
I did a test in copying Macintosh Quark Files from a Windows 2000 Server to a new Windows 2003 Server thru a Windows Share (not a Macintosh Share)..basically Server to Server copy. It was alot of data. After the copy was done to the new Windows 2003 Server I created a 'new share' as a Macintosh Share (SFM) on the folder for Mac's to be able to access it.

All the Macs were able to open the Quark documents just fine with no loss of the resource forks after doing the Windows Server to Server copy!

The only way I can explain the reason for this is that I found a tech note on the Microsoft Site stating that NTFS stores both the data fork and resource fork as one file in what is called a NTFS Stream. Being that Windows doesn't need to access the resource fork of Mac files it just ignores it. And during a file copy, it copies the entire NTFS Stream (which has the resource fork included in it).

Here's the tech note:
How To Use a File Created by an Apple Macintosh in Windows 2000, Windows NT, or Windows XP -
Article ID : 147438
..."When a file created by a Macintosh is stored on a Windows server, it is stored in a single file that contains a stream for each fork. When Windows- based applications gain access to a file created by a Macintosh client, File Server for Macintosh presents only the data fork because the data fork is the equivalent of the representation of files on Windows platforms. Windows-based applications may not access the resource fork."

Let me know if I'm on the right track here as I know this is a different line of thought than what we were all originally thinking. I hope my findings help...

Regards,
Ken
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now