Moving SMS site server from one domain to another domain

[zau]

Hi,
we are moving SMS site server from one domain (nt) to another domain (ad) in our lab.
My moving plan is based on Microsoft's Moving SMS Servers between domains whitepaper.
However, I am stuck in the begining:
(Create a new SMS Service account
Create a new SMS Service account in the destination domain. Make it a member of the Domain Admins group in the destination domain or make it a local administrator on the computers that SMS will manage, including site server, and site systems. Give the SMS Service account the Log on as a service right on the SMS site server.)

We create smsservice account to the destination domain with domain user rights. In the source domain destinationdomain/smsservice -account has domain admin rights + local admin rights and local log on as service rihts on the site server.

When I try to reset smssservice -account In the SMS Administrator console, (navigate to Systems Management Server \ Site Database \ Site Hierarchy \ <site code>. and so on..) I still get the following error message form SMS_hierarchy_manager:
SMS Hierarchy Manager cannot reinstall the SMS Site Component Manager under the new service account and password. The operating system reported error 1060: The specified service does not exist as an installed service.

Possible cause: The service account and password are not valid.
Solution: Specify a valid service account and password using the SMS Administrator console.

Possible cause: The account does not have Administrator permissions and &quot;Log on as a service&quot; rights.
Solution: Grant the appropriate permissions and rights using the Windows NT User Manager.

I am not familiar with AD user right practice.
So I really need some good advices..

Thanks in advance!

 

[ziczac]

Hello Zau,

what you are describing is the same problem I have right now. Since your post is several months old, I hope that you have found a solution that you can share with me!?

Thanks in advance!
Chris

 

[staro30]

I have the same problem. Since your post is nearly a year old, I hope that you have found a solution that you can share with me?

 

[tbrennans]

you don't want to make a new name you want to put the old name and password on the new domain. (i think I'm reading this right)

The only other thing I can suggest is that you use the same name on your test network as you have on you production, that way you can stick a domain controller on your test domain to synch them up from time to time so they &quot;look the same&quot;

http://www.microsoft.com/technet/tr...hnol/sms/sms2/deploy/upgrdmigrate/dommvmt.asp

that has some info...you might have it already