In Place upgrade to Windows 2000

Hi List,

We're planning on upgrading our operating system for the deployment server and the enterprise server from NT to 2000. Has anyone had problems with an "In Place" upgrade?

Any other suggestions or problems encountered during this upgrade process would be greatly appreciated.

Thanks,
Kevin Gray

I wouldn't recommend performing an upgrade from NT4.0 to Win2000 - it might be ok for a workstation - but I certainly would not recommend it for a server.

Backup all of your oneworld data and objects - reformat the machine, partition the machine how you want and ensure a clean OS is installed (every service pack etc etc) - then reinstall OneWorld as per instructions and finally restore your data.

Email me for more info if you wish.

Jon Steel
erpSOURCING LLC
http://www.erpsourcing.com

Hi Kevin,

I agree with Jon, DON'T upgrade your server. You will have problems.

Deployment Server Upgrade Process :

(I think I posted this sometime before - but I couldn't find it !!!)

a. Backup. Fully. Everything !
b. Copy the B7333 directory from the Deployment Server to another server
somewhere on your network. If you have to temporarily compress it to fit, then
thats fine. you might want to clean up the b7333 directory first - delete old
packages etc etc
c. Format the Deployment Server
d. Install Windows 2000. Do NOT install Terminal Services or Web Services.
Try to perform as small an install as you need for a reliable box. Install
WITH THE SAME DEPLOYMENT SERVER NAME AS BEFORE - and preferably the same IP
settings, though not totally required. IF YOU USE a DIFFERENT name - you will
encounter issues in the planner.
e. Run through the Windows Update - (Start Windows Update or in internet
explorer connect through to http://windowsupdate.microsoft.com) - install all
patches - you will need to reboot and perform this several times and it will
take several hours
f. Install Microsoft Visual C++ - again, patch to the latest service pack
g. Install MS office if you wish - but again, patch to the latest SP
h. Find your OneWorld Installation CD's - you will do a new install of
Oneworld and you will need to call JDE for an authorization code. Try to do
this between 9am-5pm MST to ensure you're not waiting around forever for JDE
response line (though its not too bad getting this code these days) - you are
doing this to create all of the JDE registry values
i. When OneWorld is installed on the deployment server - erase the B7333
directory and all files underneath
j. Copy the backed-up B7333 path from the other machine back to this
machine. Share the B7333 directory as "B7333" to everyone who needs to see it.
k. Go through Database Connection Settings (ODBC or TNSNames) settings - make
sure everything connects ok.
l. Build a new package to ensure that everything is all ok.

Total time to complete - less than 1 day usually. Make sure the developers
understand they cannot check in/check out objects - it should not affect your
production environment except for missing Media Objects and inability to build
packages while this is going on.

Jon Steel
OneWorld Technical Specialist
erpSOURCING LLC
24/7 Response Line - (904) 382 5701

Based on my experience, Window 2000 is more stable and more user-friendly than NT. It is the right choice. If I were about to upgrade the deployment server and enterprise server to Window 2000, instead of “upgrading” the OS, I would install and configure a full version of Window 2000 (OneWorld Installation as well) from ground-up. If you have any spare servers, you can re-format the hard-drive or add a bigger size of hard disk and add more memory if needed.

I would also install 2000 on one terminal server so they all can be fully tested for quality assurance. If everything works, what I have done will serve as a blueprint for the rest of the server installations. A little extra work will ensure me do the job right.

Kevin,

Timely post this is. We are in the process of moving our Deployment Server from NT4.0 to Win2K right now. We started the process last Friday, and spent today recovering the OneWorld directory from backup (we have a very slow tape drive). I just have a few comments.

From the Windows experts here, they highly recommended a new install of Win2K vs. an upgrade -- cleaner all around.

You might also want to check out document # OTI-99-0057 on the Knowledge Garden, if you haven't already. This is JDE's document about changing out a deployment server, and is pretty good.

One other item to keep in mind that you should also ensure that any update packages that have been deployed have been accepted. Otherwise clients may have trouble accepting if your deployment server is down.

Regarding media objects, we couldn't live without these, so we moved the media object directory to another server, and changed the media object queue setup in OW to point to this new directory. From menu GH9016, run application P98MOQUE to do this reassignment of the media object queue destination.

Good luck!