Migrating filePro to Windows Server2003 ?

[Robert Haussmann]

> On Tue, Nov 01, 2005 at 10:53:45AM -0500, Dan Snyder wrote:
> >    We  have  an SCO server v5.0.6 that is having serious 
> hardware issues.
> >    We  have  about  35  users  accessing filePro on this 
> system.  We were
> >    hoping the server would last until we migrated to a new 
> ERP system but
> >    the  server doesn't look like it's going to make it.  
> Since we already
> >    have several  Windows servers and support resources are 
> easier to come
> >    by,  we  are  considering  migrating filePro to a 
> Windows 2003 server.
> >    I'd  like  to  get  some  feedback  from anyone that has 
> migrated from
> >    filePro on SCO to filePro on Windows.
> 
[...]

> >    How  do  client  workstations  access the windows 
> server?  Is it still
> >    telnet or is it file sharing (we are using SCO 
> termvision right now)?
> 
> Each workstation will access the key, data and index files on imported
> filesystems -- it is *not* client server; you need to 
> appraise how much
> traffic that's going to cause on your LAN and make sure you have
> sufficient bandwidth.
> 
> On the Unix side, the client is *on the same backplane* as the data;
> that won't be true on a Windows network.
> 

Just a clarification--Jay is referring to the default installation 
on a standard windows network.  That being said, there are ways to
make the Windows implementation work in much the same was as the 
*nix one.  Using Terminal services, for example, the client would
be on the same backplane as the data.  One could also use a 
telnet implementation and utilize the character-based filePro system
directly on the server.  We using both types of solutions in different
locations with very positive results.

Bob Haussmann
Tabor Children's Servcies.