Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Email Conversation-Upgrade 3.x to 4.1 Notes

0 views
Skip to first unread message

corey_h...@my-deja.com

unread,
Oct 19, 2000, 3:00:00 AM10/19/00
to
Remember to read this message from the bottom up!

Honestly creating the CD's was the hardest part of the upgrade. I was
at work pretty late that day. I had 2 burners going. The CD's took
about 5 hours to create the CD's and about 2 1/2 to 3 hours to cut
them. Then early the next morning I shipped them out overnight
delivery. Make sure you bundle some kind of remote desktop software
with the CD's. pcAnywhere, MS-Netmeeting, etc.

Remotes:
Just remember you always have a few days of play with the remote users
as long as they don't sync before you have the host done. I had a few
users that ran a little late on the upgrade process. Don't waste your
time on trying to upgrade the remote db's , just cut them a new one
from the v4 host. O' another thing....Once I created the new v4 db's
the sync server kicks out 8,000 to 10,000 tefs. It's best to set up a
remote user or two on your network to sync up the new db's before you
burn the CD's and ship them. If your remotes are on modems it will
take them forever to sync for the first time.

Workgroup Users:
This was my first step. I rolled out the new version of SalesLogix 4.0
to the workgroup users along with a few other hot fixes that brought
the version to 4.0.2.1. You will need to apply the new SP1 to it also.


Host/Admin:
Second Step. Install the new version of SalesLogix Workgroup Admin.
Once opened it will prompt you to upgrade the host DB. Yes to the
prompt and it will continue to upgrade the host db. Install your 4.0
bundles. Remember that the SLXReports will expire when you install
it. If you use SLXReporting you need to contact SLX Tech Support and
they will give you a new license number for them. Now install the hot
fixes and SP1 to the Admin along with the newer SP1 bundles.

Sync Server:
Third Step. Very simple! Install the Sync Server 4.0, hot fixes, SP1,
etc.

Note: You don't need to do this but I did to ensure a proper upgrade
and make it easier for troubleshooting problems with the new version.
Move all old logs files, tefs, everything that SLX creates to separate
folders and name the folders version 3.x. Remember not to cut your
db's for the remotes until you complete this step.

I'm going to post this on DEJA.COM

Your pal,

Corey

-----Original Message-----
From: Steve Vassallo [mailto:SVas...@p21.com]
Sent: Thursday, October 19, 2000 9:50 AM
To: 'Corey Harbaugh'
Subject: RE: Tech Support: Unwritten rules....


How long did it take you to create all those remote db's?


-----Original Message-----
From: Corey Harbaugh [mailto:CHar...@bma.com]
Sent: Thursday, October 19, 2000 10:40 AM
To: 'Steve Vassallo'
Subject: RE: Tech Support: Unwritten rules....


I upgraded on a Friday night and then created new v4 DB's. Overnighted
them
to the remotes. It was kind of expensive but I had no problems once
they
all got the cd.

-----Original Message-----
From: Steve Vassallo [mailto:SVas...@p21.com]
Sent: Thursday, October 19, 2000 9:33 AM
To: 'Corey Harbaugh'
Subject: RE: Tech Support: Unwritten rules....


What database did you send out to the remotes though? What version I
mean?
THe old 3.16 or 4.0?


-----Original Message-----
From: Corey Harbaugh [mailto:CHar...@bma.com]
Sent: Thursday, October 19, 2000 9:43 AM
To: 'Steve Vassallo'
Subject: RE: Tech Support: Unwritten rules....


Yup, we sure did. Actually I'm getting ready to plan and install the
new
Service Pak 1. This will take us to from 4.0.2.1 to 4.1. It's running
great! No more sync problems! What I did for the 30 users we have is
send
them upgrade kit. CD with SLX 4, new DB, and the 4.0.2.1 patch. I have
them
do a final sync on a Friday and them came to the office over the
weekend and
upgraded all the workgroup users, admin server, sync server and also had
them install pcAnywhere remote desktop software. Then told the remotes
to
make sure they upgrade before that following Monday and not to sync
before
they do. It went very well. I had to hire a temp employee for extra
technical phone support for that weekend while they upgraded.

Look me up on MSN Messenger use my email to add me to your contact list:
charba...@hotmail.com

Corey

-----Original Message-----
From: Steve Vassallo [mailto:SVas...@p21.com]
Sent: Wednesday, October 18, 2000 4:16 PM
To: 'Corey Harbaugh'
Subject: RE: Tech Support: Unwritten rules....


Dude so how goes SLX?
You guys upgrade to 4.0 yet? We are looking into but have to
coordinate are
50 remotes to upgrade at the same time.
It's ugly


-----Original Message-----
From: Corey Harbaugh [mailto:CHar...@bma.com]
Sent: Monday, September 25, 2000 12:16 PM


Sent via Deja.com http://www.deja.com/
Before you buy.

K

unread,
Oct 24, 2000, 3:00:00 AM10/24/00
to
This is great! Thanks very much for posting it. I hope that our
conversion can go as smoothly as yours. Unfortunately it takes about
60 hours to cut all our remotes and then we have a remote office to add
to the mix.
Anyway thanks again. I may have questions as we get nearer.
K.

In article <8snd7c$bq7$1...@nnrp1.deja.com>,

corey_h...@my-deja.com

unread,
Oct 24, 2000, 3:00:00 AM10/24/00
to
K,
I would do some research on upgrading the remote DB's. It sounds like
you have allot of remotes. I would contact SLX Tech support and get
step by step instructions for upgrading the remote db's along with the
Interbase Server. If its a standard upgrade process, standard meaning
the upgrade works most of the time, you should look into writing a
vbscript for automating the upgrade. Or even a installer program like
Wise InstallMaster or Install Shield. Hope this helps!

Corey

In article <8t49i9$860$1...@nnrp1.deja.com>,

0 new messages