FMPServer only on W2k Server How Lame! Options?

[complete-db]

Hello,

I am in the process of configuring a new network for a client. I had planned to buy an IBM server with Windows Small Business Server 2003 Standard Edition. However after checking with FMI they don't support SBS 2003 (how lame). I really hate having to dish out $1000 for an outdated Filemaker Pro 5.5 Server and then having to dish out another $1000 for W2k Server(SBS 2003 is only $600). I only have 5 users sharing about 15 files. Would I be better off going with a WinXP Pro box with Filemaker Client? Also would hosting Qbooks Pro Files on the same box really hurt my performance?

Thanks,

PSC

[Vaughan]

Not supporting FMS on a particular platform is a long way from saying that it doesn't work. They are only really saying that they haven't tested it thoroughly so they don't know.

I run a lab of machines running Windows 2000 under VirtualPC (ie, Macintosh hardware emulating PC with software) and believe me, *nobody* supports anything when I tell them its in VirtualPC. Why? They haven't tested it so they don't know what will happen. I'm on my own. But guess what, just about everything works except for programs with wacky copy protection schemes that try to access hardware directly.

So try it and see what happens.

Go to the FMI web site and read the FMS Best Practices white paper.

[Anatoli]

Instal FMS on W2000 *client*

[complete-db]

Do you mean Windows 2000 Professional?

Thanks for your help.

PSC

[Anatoli]

Yes, W2k Professional, not server, just workstation. Just set Background tasks as priority.

[gwmbox]

Anatoli

I have read the white paper and is says that workstation should not be used, but from your post the Workstation W2000 Pro should be fine, apart from the background settings is there anything else I need to be careful of if I set it up on Win 2000 workstation? and have you encountered any issues running it on the workstation version?

Thanks

Greg

[Anatoli]

Never any issues. The only thing to avoid is 2 NIC cards, which FM doesn't like much. See also my thread about FM Server performance.

In fact, because FM is *not* using anything at all from Windows Server, why use it?

FM server is running in own TCP/IP transport.