Migrating windows 2003 standard edition to windows 2008 enterprise edition

Question

Hi
We are using ECC 5.0 and our PRD system is running on windows 2003 standard edition,and recently we have got some physical memory problem.as windows 2003 standard edition supports only 4 GB of RAM. and we want to extend our RAM for that we are planning to upgrade os to windows 2008 enterprise edition,is that possible.and after upgrading OS what are the activities that need to be performed for SAP to run succesfully,kindly suggest.
Regards
Pranav

Answer 1

Hi Markus
I read note SAP Note 690432 - Windows 2003 Support in it regarding upgradation of os  windows 2003 standard edition to windows 2003 enterprise edition.
Upgrade of Your Operating System
If you upgrade an existing SAP system to Windows Server 2003 perform the
following actions:
o Install the latest R3DLLINS
You find the latest dynamic link libraries R3DLLINS for Windows
Server 2003 on the EXT-Kernel CD in the NTPATCH directory.
o Replace the R/3 kernel with the EXT-Kernel.
If you do not replace it you will get error "SICK" after the first
logon attempt after the start.
In this case, download the disp+work package(s) from the SAP
Service Marketplace at service.sap.com/patches and unpack the
patch(es) to directory usr\sap\exe:
dw*_<patch-level>
Use at least patch level 186.
o Use the latest saposcol version.
This version supports the changed performance counter of Windows
Server 2003 to determine values for ST06 and RZ20.
You can find the latest version in file saposcol_<Patch Level>.CAR.
in the SAP Service Marketplace.
o SAP DB only: See SAP Note 315237.o Compatibility of the Hardware with Windows Server 2003
You can perform the upgrade to Windows Server 2003 only if the
hardware has been explicitly released for this purpose. To check,
do one of the following:
- If the Windows Server 2003 CD is available, check compatibility
with WINNT32.EXE in the \I386 directory. The exact statement
is: <DRIVE:>\I386\WINNT32 /CHECKUPGRADEONLY. The result is
stored as text file WINNT32.LOC in the present Windows
directory (e.g. C:\WINNT).
- The hardware has successfully passed SAP hardware certification
(http://www.addon.de).
- The hardware is contained in the Microsoft Hardware
Compatibility List (http://www.microsoft.com/hcl).
- The hardware has been released for Windows Server 2003 by the
manufacturer. This information is published on the
corresponding website.
o Kerberos Single Sign-On
When the SAP system is installed on Windows Server 2003 you can
setup the Kerberos Single Sign-On. If you use the kerberos protocol
the information exchanged between the SAP frontend and the
application server for authentication is encrypted.
The procedure for setting up Single Sign-On is described in all
recent installation guides which you can download from the SAP
Service Marketplace at: service.sap.com/instguides.
o SAP domain under Windows Server 2003
Follow the instructions of the Windows documentation for the
migration of a Windows NT 4 domain to Windows 2003. For the SAP
environment some additional points need to be observed.
For Windows NT 4 there are two models for the SAP system domain:
- Single domain
All users and the SAP system build one single domain. This
domain can be migrated to Windows Server 2003 and exist there
as single domain.
- Additional domain
There is one domain for the users and a second domain for the
SAP system(s). For a migration to Windows Server 2003 the SAP
system domain has to be created as child domain under the user
domain. A "Top-down" procedure is to be used. The higher domain
(the user domain) must be migrated prior to the SAP child
domain. If the user and SAP domain is part of a larger domain
structure the complete domain structure for Windows Server 2003
needs to be planned in a preparing phase. Usually, the
structure created under Windows NT 4 has to be re-arranged and
consolidated.
The name space of the root domain and all sub-ordinated domains
has to be defined and the distribution of the DNS services
needs to be determined.
Note the following:
The SAP domain has to be created as child domain.
The SAP domain must not be converted into an organizational
unit (OU). OUs are not supported by R3SETUP and R3up.
in it nowhere it is mentioned about system copy so plz suggest.