Things I wished I knew about library server setup before I started:
1) Some tagging/library maintenance activities can only easily be done from the server:
a) Adding/Changing cover art
b) Changing library views or theater view schemes
c) Renaming files/Changing the location of files on a disc from inside MC
d) Importing new items into the library
e) Ripping CDs
And I'm sure there are a few others. There are workarounds for some of these: you can use remote desktop software like Teamviewer to do 1,2,3, and 4. You can use a separate special purpose "maintenance" local library on a client to do 1, 3, and 5, and then move the files to folders on the server (see 2.b below for how that might work). But generally, if neither box will be headless and all other things are equal, make the server the box that's easier for you to get face-time in front of, it will make your life easier
2) Everything works much better if you share the directories/drives on the server over the network and either map them the same way on the client or use UNC paths in the library. For example, if all of your audio is in a directory on your server called "X:\Audio," share the server's X: drive over the network and then map the resulting share to the X: drive on your client so the client sees everything as X:\Audio as well (or just use UNC paths). That does two useful things:
a) The client can access the files directly through the share which means that playback is less dependent on the server computer to serve and transcode files. File access just works much better this way.
b) If you have autoimport setup to watch the shared directories on the server, then you can prepare, tag, and rip files in a separate library on the client box and then just dump them into the shared directory. The server will then automatically pick them up and read all the tags, etc.
3) Turn off auto-import on the client box, it can lead to mischief the way the system currently works.