Falcon91

No Problem ..... Just schedule these two bat files to stop & start the FMServer NT Service ..... Drop them on the root of your FMServer Drive... and Have NT Scheduler Service run them at designated times... By the way, it's a good idea that when installing FileMkaer Server to ask for a custom install and install the directory FMServer on the Root of your Data Drive, not in the "Programs Folder !! =============================== @ECHO OFF d:FMSERVERFMSERVER START EXIT =============================== @ECHO OFF d:FMSERVERFMSERVER STOP EXIT =============================== Be sure and save these as .BAT FILES That should do it .... have been doing it for years and never a problem...

Justin, I have been deploying FMP 5 On NT Servers since day 1 .... You Server Spec is more then enough to handle your user connections except I would install 2 36 Gig IBM 10,000 SCSI Drives and Mirror them and bump the memory to 1 GIG ....If you need additional data drives for document storage, just add them on.. Windows 2000 Server is the way I would recomend for you to go ...It is far more stable then NT 4 and you can also remotley administrate the server with the "Administrator Mode Terminal Server" ..... This should be a dedicated Filemkaker server .... No other applications/services ie; (Print Server Services, Email or Fax Services etc; ... should be installedon this machine ! ... You can use another Windows workstation and FM Pro Unlimited to publish your web layouts for your employee access!

I would sugggest using Thin Clinet Technology such As MS Terminal Server .... We have been deploying it over various connection types and it works great .... This does require a multi server envoirnment ... Your FM File Server and Terminal Servers with a limit of 15 users per Terminal server ... Not exactly cheap, but by far, better then any other way..... Feed each Terminal Server with a dedicated 1.5 DSL and you should have no problems.... Of course if you want to step up to T3, that will reduce the load balancing issues and the need for multiple DSL Lines

Move he FMSERVER Directory .... First, Make A Copy Of Your Fm Pro Data Files Directory To The Larger Partitiion.... Then Uninstall Filemaker Server .....Restart Your NT Server .... Reinistall FIlemaker Server Using Custom Install Options Put Filemaker Server On The Root Of The Larger Partition.... Set Up The Preferences And Copy Your Original Data File Directory Back Into The New FMServer Directory ....Make Sure You HAve The Filemaker Service Auto Start Restart The NT Server ... It's That Simple....

Make sure that Internet Explorer 4.0 is installed on your NT server .... This is necessary for the Filemaker Server Panel to operate

We have been deploying remotely via NT Terminal Server for quite some time and have had great success .... If the NT TS Box has dual NIC's, you could secure this with "Black Ice".

Always run Filemaker Server As an NT Service ... That is the only way that works!

To run Filemaker 5 on NT Terminal Server you need to build up another NT Server with TSE just to handle the terminal connections.. Your existing server will continue to run Filemaker Server to publish the files... I would highly recommend that if you are considering this, you defintely use NT 2000 Server on the Terminal Server box. Memory requirements are rather large for FMP ... I would allocate 100 Meg Ram for each terminal connection accesing FMP..and 256 Meg to run the operating System... I would also suggest this Terminal Box be of high quality with an Intel MB and using the newer IBMS SCSI 10,000 RMP drives and dual PIII 500 processors or greater!! Depending on the number of connections you want to deploy, additional "TS" boxes and a plan for load balancing may be required.. Also, be sure and install your Site License copy of FMP by using the "Add Programs" option in the control panel... This applies to any other applications your connected user may need as well..

If your looking for reliability,an NT box set up properly with either SVC Pak 4 or 5, is bullet proof. The operative word here is "Properly". You will notice we didn't specify SVC Pak 6! Be sure and dedicate the box to just serving the FMP Database. "No Mail Server, Web Server Or Print Server services." Allocate about 20 Meg Ram in the Filemaker Server Setup Options... Use a 100 MPS Switch instead of a Hub ... The box itself should be a good quality SCSI 10,000 RPM system, with about 256K of Ram, dual processor board, "Intel" and a current PIII 500 - ? processor. We have been deploying on NT for several years and neither our clients or ourselves have lost even an hour of downtime... We dedicate all our database servers, regardless of which tool ie; SQL, Filemaker Server or Oracle we deploy. With the cost of hardware today you just can't go wrong. If you peruse the various forums for filemaker, you will notice most have far more server problem type postings on the Mac side.... With over 80% of the business world deploying on PC's you have to ask yourself why? ... Using the NT platform, be careful about applying Filemaker's patches ... For some reason, "can't seem to be explained by the fine folks at Filemaker" these so called patches cause nothing but problems... It has been our experience with Filemaker that their first offering is usually the best.. Test carefully before deploying these patches! This applies to the client workstations as well! .. The only other creavat to be aware of is your NT Event manager is going to be saturated with a lot of useless Filemaker entries... Our way of dealing with this annoying problem "Although not exactly elegant" is to set the Event manager file size up to about 100 meg and replace itself every seven days... One last thing, be sure and schedule a restart of any NT 4.0 servers at least one per week ... Not necessary with NT Server 2000 and SVC Pak 1.... Hope this helps. ... By the way, if you are going to have any need for WAN Types of connections, consider building up an second or third NT 2000 Server and deploying these conections via 2000 terminal server!!

I don't believe the speed at the Server Level is what's causing your problems .... Most likely it's the performance of the local machine that your attempting to run your summary reports on .... Or the solution need some serious design attention!

Back Exec 8.0 Software By Ver1tas is the best on the market for NT Server... Be sure and get the Server Edition as well as the "Open File" Agent ! Nothing else comes close.

Dos anyone know of a way to surpress recording all the opening of all files by all users from displaying in the NT Event Manager? This does nothing but clog up the event manager with a lot of garbage!!

Has this always been a problem, or did it occur after applying Filemakers 4.2 or 4.3 patch? We have run FMP 4 on our NT Workstations with no problems except when we apply the 4.2 or 4.3 patches.... Try reinstalling FMP without the patch. .. We have found that in general, Filemaker releases these patches with either little or no beta or their using inexperinced beta testers.... either way, tread carefully!

Have you check the NT Event Manager for any system errors? Be sure and check the application section of the manager.. Are you running any other enterprise applications on the sane NT Server such as a mail server or web server application? If you are not getting any application errors in the NT event manager, I would reinstall Filemaker Server as well as the FM Server patches and then reapply you NT Service Pak.... You may also want to perform a recovery of your FM Data files as well. Our experience that either Svc Pak 4 or 5 is quite stable... not so for Svc Pak 6..

According to the folks at Filemaker, the file size limitation is 2 Gig ... OF course they have been know to fool with us in the past !!