As an ex-Novell man myself, I'd suggest you follow the basic good practices
of Novell engineers, that is, allocate shares with a logon script or policy
instead of allowing ad-hoc Explorer mappings.  Use drive-mappings rather than
UNC shares, most users understand them better.  

One departure I'd suggest is to use share-permissions to control access,
rather than filesystem-rights. If you're used to Netware, you're in for an
unpleasant surprise when you see that NTFS filesystem rights are nowhere near
as logical as those of Netware volumes. Some people persist in struggling
with them. My answer is not to use them at all.

Printers - I prefer to link them with printserver-boxes (or buy
network-ready models) Needs an additional network port per printer, true, but
if these use TCP/IP (LPR) printing, then that avoids the need for
peer-sharing of printers from workstations, which is always a regular source
of trouble. All you need on the workstations is the LPR client (Part of
Windows Setup) and of course the print driver. The server plays no part in
printing this way, freeing its processor for more pressing duties.

-------------------------------

An alternative approach to XP network logon -  http://mylogon.net