GSNW can help during the migration, though in smaller sites it can be
more trouble than it is worth to setup and administer.
Understand that you can run both client32 and the MS client stacks on the
same system -- passthrough authentication will usually work fine and allow
access to resources on both sides during the transition. I've done migrations
that lasted four months with this configuration.
If you are using, say Backup Exec, you can restore files from the NDS platform
to Windows; it will even restore MS tape format, ArcServe, QIC, etc. (at
last as long as they aren't software-compressed or password
protected). But NW permissions and a whole host of other things won't
translate and this leads to an awful lot of manual work. Over-the-wire with
two server is much better.
If you only have one server and are trying to do the migration in a single step,
it is frankly much more difficult, and I recommend against doing it this way
unless there is just no choice.
If you have a spare workstation around, I'd suggest loading up Windows
Server on that, use it for a temporary platform during migration, or at least
for testing. When you are ready to switch you back it up, turn down Netware
and just restore to the production server.
This MS article is a good reference in that it may point out a few things you
haven't thought of.
http://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspx
Best of success.
Steve Duff, MCSE, MVP
Ergodic Systems, Inc.