[dan@macdatatech.com: RE: Migrating filePro to Windows Server2003 ?]

[Jay R. Ashworth]

I believe, from his tone, that Dan meant to send this to the list, so
I'm forwarding it. (You sent it to me, off list, Dan, and I only just
noticed.)

Cheers,
-- jra


----- Forwarded message from Dan Snyder <dan at macdatatech.com> -----

From: "Dan Snyder" <dan at macdatatech.com>
To: "'Jay R. Ashworth'" <jra at baylink.com>
Subject: RE: Migrating filePro to Windows Server2003 ?
Date: Tue, 8 Nov 2005 11:52:23 -0500
X-Mailer: Microsoft Office Outlook 11


Thanks for the replies. 

I sent the original message about migrating to Windows on a morning when our
SCO server went down.  It was the third time in 18 months.  The first two
times were fixed by replacing hard drives, so it didn't seem like a big
problem (hard drives tend to go bad after running for 5 years non-stop).
This time it appeared to be the hard drives again, but some of the same
drives that were replaced before.  Therefore, I was hoping to install new
hard drives to patch it and then plan a migration to a new server running
Windows so all my servers are on the same platform for easier management.
Originally, we were planning on migrating to a new ERP system by now, so we
weren't concerned about replacing/upgrading the aging SCO/filePro server.
Anyway, it turned out that the old SCO server had other hardware issues.

Since we were completely down, getting us back online was our only concern.
Luckily, I had a spare server for our ERP project.  Thinking that a SCO to
Windows filePro migration would take me more time than a SCO to SCO or SCO
to LINUX, I tried to install our old SCO version on the new server but it
wasn't recognizing hardware and I couldn't easily find drivers.  Next, I
tried to contact SCO to purchase an upgrade that would hopefully recognize
the newer hardware.  While waiting on someone from SCO to call back I
downloaded and installed RedHat LINUX.  Everything went smoothly, so I
purchased the LINUX version of filePro and got us up and running on the new
server, before anyone from SCO even called back!!

I would have liked to switch to Windows to have only one server platform to
manage, but not having the luxury of time, the LINUX install was quick and
easy and is working quite well.

Thanks again for the advice.

Dan Snyder
IT Manager
Mercury Electronics
717-854-9557 ext.224


 

-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Jay R.
Ashworth
Sent: Friday, November 04, 2005 8:33 PM
To: filepro-list at seaslug.org
Subject: Re: Migrating filePro to Windows Server2003 ?

On Fri, Nov 04, 2005 at 12:21:12PM -0500, Robert Haussmann wrote:
> > 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.

True, both of those are possible, and I can't much diss WTS anymore, since I
have a Linux box doing the same dance with VNC terminals, now can I?  :-)

Cheers,
-- jra
-- 
Jay R. Ashworth
jra at baylink.com
Designer                          Baylink                             RFC
2100
Ashworth & Associates        The Things I Think                        '87
e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647
1274

	"NPR has a lot in common with Nascar... we both turn to the left."
		- Peter Sagal, on Wait Wait, Don't Tell Me!
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list



----- End forwarded message -----

-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

	"Space is called 'space' because there's so much *space* there."
		- John Walker, of Fourmilab, on Trek's End