Question:
Hello All
I have a Query...
We need to change the Domain name of our SAP installations.
Now I want to know what can be the negative effect of it and at what all place do I have to change the domain name entry?
Does it effect working of SAP?
It would be of Great help if some one provide me with steps of it.
Please help.
_________________
Rahul
SAP Basis
Answer:
search OSS notes.
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
I'm having real trouble finding any information on what needs changing on a SAP system after a domain is changed. I've tried looking for Snotes but OSS throws up unrelated posts and having gone through them no luck. I'm using the search string "doman change" and have used "windows domain change" also.
Do any of you have any documents or specific snotes on this subject?
Answer:
What OS and DB are you using?
What type of systems - R/3, Portals, etc?
What kind of domain are you moving to/from?
Answer:
Thanks for your quick response.
Our SAP systems are running Windows 2000 and databases are SQL 2000 SP3.
All are R/3 systems with the single exception of an XI system.
We are moving from an old NT domain to active directory 2003.
Cheers
Answer:
Hi SAPTastic,
Seems you have a lot to learn!
Domain changes are often very complex, if you are migrating to an Active Directory from NT which I believe is the case then unfortunately this means a total reinstall of the SAP systems. The reason being that the instance when installed makes a tag to the domain name which cannot be changed.
You will have to detach your database, trash the existing SAP installations, then migrate the server to the new domain and finally reinstall SAP and re-attch the database. Further complication may be if you are in the Public Sector and have installed that particular add-on then there are a number of references in the database to the domain name thus these will all have to be checked and changed.
We recently when through this process and it took 3 months to migrate 6 servers with a lot of late nights and headaches along the way.
Yours,
Ern.
Answer:
SAP outlines some of the steps in note 620954 but it is Oracle specific. We did the same migration last year and here are the basic steps followed. There may be some specifics to XI that I'm unaware of.
1. Follow the Install guide procedures for creating accounts <sid>adm and SAPService<SID>, creating and assigning the accounts to local and domain user groups, and making the accounts local administrators. This is all available in the Planning and Preperation installation guide.
2. Grant local security policies this can be found in the Installation and Post Installation Guide. There are 3or 4 security policies that need to be updated depending on Win 2000 or 2003. Three that I remember are:
Act as part of the operating system
Repeat for Increase quotas
Replace a process-level token
3. Shutdown the SAP Services.
4. Make note of any system and user environment variables that exist under the old <sid>adm account
5. In the SQL Enterprise manager manually add the accounts/groups that reside on the new domain. Verify their permissions/database(s) are the same as their old domain counterpart.
6. Shut down the MS SQL Services.
7. Change the logon as user for any services running with domain accounts from the old domain to the new domain.
8. Join the new domain - you will require a reboot.
9. Logon as the new <sid>adm account. Setup the profile/desktop/start menu/etc to suit your needs.
10. Edit the following registry setting:
HKEY_LOCAL_MACHINE\Software\SAP\<SID>\AdmUser to <Domain>\
<SID>adm.
11. Execute \usr\sap\<SID>\sys\exe\run\ntreg2env - this will update specific system and user environment variables. I think it may prompt you with a few questions.
12. Verify all required system and user environment variables are created and are correct.
13. Start MS SQL/SAP... I ran sap_droproc just to be on the safe side.
14. Change over any automatically scheduled Windows/SQL scripts to run under the new domain account..
Answer:
Also forgot to mention -
Verify the new SAPService<SID> account has the same network permissions as the old account. This is necessary if you have any overnight routines that save data in external databases or file shares.
I'm assuming this would also apply to content management systems.
Answer:
Hi,
For a SQL Server installation the steps are very easy and you do not have to trash the system.
1. Open Enterprise Manager and add the logins <New domain>\SAPService<SID> and <New domain>\<sid>adm and give them a login to the database or use SAP note 551915 attachment to create the new logons
2. In the new domain create the user ID SAPService<SID> and <sid>adm
3. Stop SAP make a backup of the database.
4. Attach the server to the domain
5. change the serviced SAP<SID> to run under the new domain user ID <New domain>\SAPService<SID>
6. Change the service saposcol to run under the new domain user ID <New domain>\SAPService<SID>
7. Change the SQL Services to run under the new domain user ID <New domain>\<sid>addm
8. Start the services and user the SAP Manamenent consol to Start SAP, and all should work ok.
PS I have successfully moved SQL Server SAP systems from an NT4 Domain to a W2K3 domain
Regards
Answer:
Hi,
You might have to change some instance parameters like icm/host_name_full
You also need to check the host file for any entried refering to the old domain.
Regards
Answer:
Thank you very much for your responses.
kitkat - Your message has been most helpful and I will use this as a starting point. I tried looking at the SAP note you supplied 620954 however this doesn't appear to have been released!!! Could you have got this number wrong?
ernie_els - Do you think looking at the other communty responses that re-installing SAP instances could have been avoided?
caddickd - Thank you for your input I'll add this to the information given by kitkat.
I'll be able to test a move from the old domain to the new domain as we have a DR box and this will allow me to go through the process ironing out any problems that arise.
If anybody knows the actual SAP note to domain changing or any other SAP official or unofficial documentation on this subject, it would be appreciated if you could point it out.
James
Answer:
The note number is correct but it is only released internally.
You should be able to request the note from SAP or I can send you the version of it that SAP provided me about a year ago.
If you want me to send it to you please PM me your email addresss.
Answer:
kitkat, you should copy and paste this OSS note here instead of sending to an individual. This wil lhelp many, not just one.
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
This is the version of the note from around 2005/06 and it may be outdated or have incomplete information:
You want to change the domain where the SAP System is running or convertthe operating system users SAPService<SID> and <SID>adm from local usersto domain users.
Other terms
Change Windows Domain, SAPService<SID>, <SID>adm
Solution
If you want to change the domain containing the SAP System or you want
to convert the user SAPService<SID> and <SID>adm from a local to domain
user, follow the steps described under I.
IMPORTANT:
The procedure described under point I should also be applied if the OS
users were deleted or the domain was created again even if the name of
the users has not changed !! Since the operating system assigns a new
SID to every user internally, the name may look identical 'from the
outside' while the internal number, however, is actually different.
If your system runs on a Microsoft Cluster Service (MSCS), refer also toPoint II.
Point I:
1. Create the users <SID>adm and SAPService<SID> in the domain.
2. Create a Domain Global Group SAP_<SID>_GlobalAdmin in the
domain.
3. Assign the user created under point 1 to the group created under
point 2.
You must create the following steps 4 - 11 on the application server.
4. Enter the two users created in step 1 in the group of the local
administrators.
5. Enter the group created in step 2 in the local groups SAP_<(><<)>(>
<<(><<)>)>SID>_LocalAdmin and SAP_LocalAdmin.
6. Log onto the SAP server with the domain user <SID>adm created
in step 1.
7. Open a 'Command Prompt' and call the program 'ntreg2env'. The programis located in the following directory:
\usr\sap\<SID>\sys\exe\run
This step 'transfers' the required SAP to the user.
8. Close the desktop session (log off) and log on again as the domain
user <SID>adm to activate the environment you have just copied.
9. Open the Registry Editor (regedit) and change the value for
HKEY_LOCAL_MACHINE\Software\SAP\<SID>\AdmUser to <Domain>\
<SID>adm.
10. Change the Windows Service definitions for the services SAP<(><<)>(><<(><<)>)>SID>_ and SAPOsCol. In the 'Log On' tab under 'This account' ,change the user to the domain user created in step 1. Enter the correct
password.
11. Copy SAP-specific desktop shortcuts from the 'old' user <(><<)>(>
<<(><<)>)>SID>adm to the desktop of the domain user.
Database-specific changes: Oracle
a) Enter the user created in step 1 into the local user groups ORA_<(>
<<)>(>
<<(><<)>)>DBSID>_DBA and ORA_<DBSID>_OPER.
b) Follow the steps described in note 50088 and create the new OPS$
user.
Now stop the database and the SAP system (reboot the server) and restartthe SAP system.
If problems occur during startup, reset the changes described in step 9
and 10 (databases: Oracle: b) to the 'old' user.
Point II:
If you are using a Microsoft Service cluster (MSCS), you must also
change all DCOM authorizations and reset them. To do this, call the
program ' dcomcnfg', select the relevant entries there and enter the newuser.
These are some extra ponts to take into consideration.
Based on the assumption that the SAP Server hostname is unchanged
Firstly, ensure that the domain account SAPService<SID> is changed
via
Control Panel->Services. Also,ensure the any Global Groups for SQLServerhave been recreated and the SAPService<SID> and <SID>adm
have been added
to the new groups in the correct domain (refer to your Installation
Manual).
After you have done so, please check your license using "saplicense
-test" and see if it is valid for the new domain name. Chances are you
will have to apply for a new license key as well.
You also will need to change the NT service entries for SAP<SID>_
<(><<)>NN>,
SAPOSCOL. The startup account for these services should match the new
accounts you are using (usually <DOMAIN>\SAPService<SID>).
Also,the command-line for these services uses UNC names, which must alsobe changed, by using the registry editor regedt32.
The key is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\
under which you will find SAP<SID>_<(><<)>NN> and SAPOSCOL keys.
Under each key is the value "ImagePath", which contains thecommand-line
used to start the service. Change every occurence of the computer name
in this value.
Further details regarding NT/2000 can be found at
http://service.sap.com/platforms -> Microsoft
Answer:
thanks a lot kitmat for providing this useful information.
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759