I'm in the process of planning the W2K to W2K3 upgrade on my Development Box. Anyone out there already gone thru or is now going thru this process? Did you apply W2K3 as an Upgrade on top of W2K or did you build a new box from scratch? What issues did you encounter for either method? What things should I look out for?

I know I'll need to upgrade Tomcat to at least 4.1x, I'll probably jump to 5.0. What about any issues with IIS6?

My current system:

W2K
ENV 8.0.3.6+, IOS, CCBase, ProcessFlowPro, etc at this level - Running in LOOPBACK mode, everything running on one box.
Portal, Design Studio 3.1.6.2
Manager Self Service 8.0.3.8 (I know, it's old, but it's working for us)
Tomcat 4.0.6
IIS5
Net Express 4.0
Java SDK 1.4.2_09
Tax Factory 7.0e
Oracle 9.2.0.6
MKS 8.5
FlexForms print adapter 6.0

Earlier this year we migrated to new servers, going from W2K to W2K3. I think this tends to be the recommended way if new server(s) are an option. It allows full testing to be completed on your actual production server(s) prior to going live. An in place upgrade is much more stressful. :banghead:

A couple of notes to be aware of. This is definitely not a complete list, but covers some items that immediately come to mind.

1. Nothing to do with the OS upgrade, but if you go to new servers make sure that you remember to copy the registry entries for to keep your NT User ID's the same. This will allow you to copy the GEN database across keeping security and audit trails intact.

2. If you are not familiar with IIS 6.0 be aware that there are some differences from 5.0. IIS 6.0 is more secure and requires that you allow varios web service extensions to get Lawson/Tomcat working. We also changed IIS to run in IIS 5.0 isolation mode, but I'm pretty sure that is not necessary.

3. Disable Data Execution Protection. There was some discussion on Topica recently about this and the last posts recommend turning DEP completely off. This can be done by modifying boot.ini. You might also have to consider hardware DEP and the impact that might have although I am not really familiar in this area.

As I stated these are just the first thoughts that come to mind. If anything else does I will post them.

In our W2K to W2K3 upgrade, we ran into a new issue.

Windows 2000 Registry Editor does not have any security.

Windows 2003 Registry Editor implements security on all registry settings.

This means that users must have rights to the Registry branch that contains their NT ID entries. Those are contained in:
HKEY_LOCAL_MACHINE\SOFTWARE\Lawson Software\LAWSON INSIGHT Environment\Global\Security\UserMap\

If you use Portal, there is no issue. However this affects LID.

A quirk: While users could not log in when they didn't have rights to their UserMap entry, running laua fixed the problem. When laua is loaded, there must be internal buffering that apparently short-cuts the Registry lookup.

Watch out for this! :merc: