migrating domain and sql domain user logins

Hello!
Today, I've successfully migrated a domain controler named DC2 to the new
domain. I've also changed its computer name, after joining him into the
new domain. And later i've promoted this server back to DC.
Now here is my Q: This server is also running SQL 2000 and OLAP services.
The migration of the server was success, I've rebuild the master tables
(on default and second instance) fine with exactly
defined stored procedures. But a lot of applications were using domain
logons to connect to SQL. For examle: on one of the instances there were
users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
Now the problem is that domain name has changed but domain user info
stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
domain, so they already exist in the new domain.
To make thing short:
How to tell SQL server to change the
OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
Please help!!!!You want to start with this:
http://support.microsoft.com/kb/246133/
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||Hi
Check out the links on http://support.microsoft.com/kb/246133/
John
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.18.50.16.974701@.email.si...
> Hello!
> Today, I've successfully migrated a domain controler named DC2 to the new
> domain. I've also changed its computer name, after joining him into the
> new domain. And later i've promoted this server back to DC.
> Now here is my Q: This server is also running SQL 2000 and OLAP services.
> The migration of the server was success, I've rebuild the master tables
> (on default and second instance) fine with exactly
> defined stored procedures. But a lot of applications were using domain
> logons to connect to SQL. For examle: on one of the instances there were
> users like OLD_DOMAIN_NAME\user1, OLD_DOMAIN_NAME\user2 etc...
> Now the problem is that domain name has changed but domain user info
> stayed. HOW do i tell SQL server to change the domain name OLD_DOMAIN_NAME
> to NEW_DOMAIN_NAME (the users were migrated successfuly into the new
> domain, so they already exist in the new domain.
> --
> To make thing short:
> How to tell SQL server to change the
> OLD_DOMAIN_NAME\users* --> NEW_DOMAIN_NAME\users* logins?
> Please help!!!!
>|||On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:

> You want to start with this:
> http://support.microsoft.com/kb/246133/
I wrote the whole thing a bit confusing, so here is the article that
describes my dilema:
http://support.microsoft.com/kb/240872/
I'm reading this article and I'm wondering... Do i really need to go thrue
this procedure, or is it enough just to delete old sql domain user
login and than recreate it, for example:
I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
and than i will create a new user:
NEW_DOMAIN_NAME\user1.
Is this ok, or will I be experiences some problems when trying to connect
(because of SID's etc..)?
This is a production server, so I really need to get clear with his facts
here.
Thank you!|||Yes, follow the instruction in this kb. sp_sidmap should help resolve your
issue.
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.21.39.620670@.email.si...
> On Sat, 16 Apr 2005 12:23:47 -0700, oj wrote:
>
> I wrote the whole thing a bit confusing, so here is the article that
> describes my dilema:
> http://support.microsoft.com/kb/240872/
> I'm reading this article and I'm wondering... Do i really need to go thrue
> this procedure, or is it enough just to delete old sql domain user
> login and than recreate it, for example:
> I'll delete OLD_DOMAIN_NAME\user1 (in SQL logins)
> and than i will create a new user:
> NEW_DOMAIN_NAME\user1.
> Is this ok, or will I be experiences some problems when trying to connect
> (because of SID's etc..)?
> This is a production server, so I really need to get clear with his facts
> here.
> Thank you!|||On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:

> Yes, follow the instruction in this kb. sp_sidmap should help resolve your
> issue.
Ok, so I've study the material, I understand everything except this:
1.) "Log on to the server that is running SQL Server as a system
administrator, and then run the Sp_sidmap.sql file in the user database."
So, where exactly is the user database? I really don't know what's meant
by that.
2.) I need to execute this script and the other things on the second
instance too, right?
Thank you.|||The script can be download from:
http://download.microsoft.com/downl...id
s.exe
The user database is your database (i.e. not master, msdb, tempdb, model).
Yes, you will have to do it for each (unfortunately).
-oj
"Francelj Smuk" <Francelj.Smuk@.email.si> wrote in message
news:pan.2005.04.16.20.45.00.969560@.email.si...
> On Sat, 16 Apr 2005 13:25:01 -0700, oj wrote:
>
> Ok, so I've study the material, I understand everything except this:
> 1.) "Log on to the server that is running SQL Server as a system
> administrator, and then run the Sp_sidmap.sql file in the user database."
> So, where exactly is the user database? I really don't know what's meant
> by that.
> 2.) I need to execute this script and the other things on the second
> instance too, right?
> Thank you.