Computer Migration, w2003-w2003, ADMT v3

Sponsored Links

I get the following error when :
"ERR2:7666 Unable to access server service on the machine 'AAA.DOMAIN.COM'.
Make sure netlogon and workstation services are running and you can
authenticate yourself to the machine. hr=0x80070005. Access is denied."

--
Francisco Vaz

Hello Francisco,

Based on my knowledge, the problem is that the SPN for the computer account
in getting incorrectly changed in the target domain from
HOST/computername.targetdomain.com to HOST/computername.sourcedomain.com.
The computer account in the target domain already exists because it was
migrated previously.

To work around this problem make sure to exclude the dNSHostName attribute
on the "Object Property Exclusion" Computer Migration Wizard page.

If the SPN is already mangled then you will have to manually fix the SPN in
the target domain or join the computers to the target domain manually.

Hope this helps.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hello Ada,

I think that the problem is with the ADMT agent instalation.
The migration is between to Florests, do I need a trust between the two
domains ?
--
Francisco Vaz


"Ada Pan [MSFT]" wrote:

> Hello Francisco,
>
> Based on my knowledge, the problem is that the SPN for the computer account
> in getting incorrectly changed in the target domain from
> HOST/computername.targetdomain.com to HOST/computername.sourcedomain.com.
> The computer account in the target domain already exists because it was
> migrated previously.
>
> To work around this problem make sure to exclude the dNSHostName attribute
> on the "Object Property Exclusion" Computer Migration Wizard page.
>
> If the SPN is already mangled then you will have to manually fix the SPN in
> the target domain or join the computers to the target domain manually.
>
> Hope this helps.
>
> Regards,
>
> Ada Pan
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>

Yes, you may need to first setup the trust relationship between the
dowmains.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[felipecpv]

Hi all,

In my case, the machine account was already created in the target domain because I was already testing.

I just deleted the object in the target domain and tried again. That worked.

Good luck.