Domain Migration

I am trying to migrate users accounts from a 2000 Server to 2003 server I am changing domain names and the new domain a is a child domain off a parent domain. I have created a trust on both domain servers and the parent domain and I have created administrative users on each domain I am using the ADMIT migration tool and can get all the way through it then get an access denied when it trys to create the accounts. The knowledge bases on this say I need a Domain Admin user on each domains for the other domain. Being in a child domain it does not let me create this I have created users and added the admistrative group for each user this should give the rights to create the users on the new domain, but still am getting the access denied.

Does anyone know what I am missing on this? Any help would be greatly appreciated.

thanks,

Shawn

I would suggest posting this question on a Windows forum, given that you are doing Windows operations, not SQL Server operations.

Thanks
Laurentiu

|||

Is your login is a part of domain and local admin on both of those domains?

As suggested above its better to search through the Windows related forums, if this is not a SQL related issue.

Domain change has affected SQL need help

Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well
,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:

> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>

Domain change has affected SQL need help

Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
Joe
Joe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000.
> Joe
|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:

> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
>
>

Domain change has affected SQL need help

Hey,
One of my clients has migrated from an old NT domain to an AD domain with
Win2K servers. When the migration was performed, SQL 7.0 came across as well,
but now displays some strange characteristics. NT authentication no longer
works, only SQL authentication.
The MS Search service does not start but I have an article to fix this.
Do I need to do anything else to SQL besides the MS Search service to get
SQL seeing the new domain correctly?
I was never involved in the move of SQL, and now this damn server runs a
mission-critical CRM package on SQL that can in no way be interupted or go
down during the day, and rebuilding is out of the question :(
Any help would be appreciated.
SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
JoeJoe
SQL Server is a member of domain or stand alone?
Try to delete an old NT/Logins and create a new ones.
"Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> Hey,
> One of my clients has migrated from an old NT domain to an AD domain with
> Win2K servers. When the migration was performed, SQL 7.0 came across as
> well,
> but now displays some strange characteristics. NT authentication no longer
> works, only SQL authentication.
> The MS Search service does not start but I have an article to fix this.
> Do I need to do anything else to SQL besides the MS Search service to get
> SQL seeing the new domain correctly?
> I was never involved in the move of SQL, and now this damn server runs a
> mission-critical CRM package on SQL that can in no way be interupted or go
> down during the day, and rebuilding is out of the question :(
> Any help would be appreciated.
> SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> Joe|||Hi Uri,
The server is a member server of an AD domain.
The domain has 2 AD controllers, and 6 member servers.
Joe
"Uri Dimant" wrote:
> Joe
> SQL Server is a member of domain or stand alone?
> Try to delete an old NT/Logins and create a new ones.
>
> "Joe from NZ" <Joe from NZ@.discussions.microsoft.com> wrote in message
> news:C79F6DCD-6C16-40B2-9189-1773ECAD335B@.microsoft.com...
> > Hey,
> >
> > One of my clients has migrated from an old NT domain to an AD domain with
> > Win2K servers. When the migration was performed, SQL 7.0 came across as
> > well,
> > but now displays some strange characteristics. NT authentication no longer
> > works, only SQL authentication.
> > The MS Search service does not start but I have an article to fix this.
> >
> > Do I need to do anything else to SQL besides the MS Search service to get
> > SQL seeing the new domain correctly?
> >
> > I was never involved in the move of SQL, and now this damn server runs a
> > mission-critical CRM package on SQL that can in no way be interupted or go
> > down during the day, and rebuilding is out of the question :(
> >
> > Any help would be appreciated.
> > SQL7 running latest SP. Unfortunately cannot move to SQL 2000. :(
> >
> > Joe
>
>