Undelete 2.0 Upgrade

Rating:
Summary: Truly useless for NT networks with Macintosh volumes
Review: We bought this product in November of 2000 hoping that it would be useful in our mixed Win9x/MacOS network, common in the publishing industry. After using it for a week, our Macintosh users were complaining that their files were "disappearing" from the network. We described the problem to Executive Software as follows:

We're having an unusual problem on our NT 4.0 Server running Services for Macintosh and Undelete 2.0. An example of the problem is described as follows:

One of our Macintosh users has a subdirectory on the NT Server. Within this sudirectory, he has files that are periodically replaced by newer files of the same name. When attempting to overwrite the file, he is asked to confirm the file replacement. Answering affirmatively, the file is appropriately replaced. HOWEVER, within a minute, the updated file disappears.

Executive Software replied to the problem by acknowledging that there were known issues with Macintosh files and Undelete. Their solution was to exclude Macintosh volumes from Undelete operations. They also indicated that they hoped to have the problem resolved in a future build of the software although there was no ETA on such a build.

In our network, which is 40% Macintosh, Undelete is more of a problem than a resolution. It is quite a chore to maintain customized exclusions in Undelete on an ongoing basis, particularly when new Mac users join the company and you need to provide them with home directories, etc...

Rating:
Summary: Truly useless for NT networks with Macintosh volumes
Review: We bought this product in November of 2000 hoping that it would be useful in our mixed Win9x/MacOS network, common in the publishing industry. After using it for a week, our Macintosh users were complaining that their files were "disappearing" from the network. We described the problem to Executive Software as follows:

We're having an unusual problem on our NT 4.0 Server running Services for Macintosh and Undelete 2.0. An example of the problem is described as follows:

One of our Macintosh users has a subdirectory on the NT Server. Within this sudirectory, he has files that are periodically replaced by newer files of the same name. When attempting to overwrite the file, he is asked to confirm the file replacement. Answering affirmatively, the file is appropriately replaced. HOWEVER, within a minute, the updated file disappears.

Executive Software replied to the problem by acknowledging that there were known issues with Macintosh files and Undelete. Their solution was to exclude Macintosh volumes from Undelete operations. They also indicated that they hoped to have the problem resolved in a future build of the software although there was no ETA on such a build.

In our network, which is 40% Macintosh, Undelete is more of a problem than a resolution. It is quite a chore to maintain customized exclusions in Undelete on an ongoing basis, particularly when new Mac users join the company and you need to provide them with home directories, etc...