RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- From: "Rory" <Rory@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 05:05:04 -0700
Amanda, you are a diamond!!!
This has definately solved the problem I was having, thank you...
Is this documented anywhere? As it is not in the ADMT help files...
Thanks again...
Rory
"Amanda Wang [MSFT]" wrote:
> Hello,
>
> Thanks for your post.
>
> I understand that you run the workstation migration via batch scripts, and
> it fails with the following error: WRN1:0198 The name 'hostname' could not
> be resolved. If I have misunderstood, please feel free to let me know.
>
> I suggest you check if the name has already exists. If so, the cause of the
> issue is that the command-line finding the computer in the target domain
> when it already existed at the time of migration.
>
> You can perform the following suggestion to resolve the issue:
>
> Appending a dollar sign ($) to the computer name allowed the name to be
> resolved and the process worked fine after that modification. Computer
> names in active directory are much like user names, except computer
> accounts have a dollar sign in their name (much like a hidden share). So
> when looking up the account "hostname", it was failing because there is no
> account which matches that name. There is, however, an account that is
> named hostname$.
>
> Hope that helps.
>
> Any update, let's get in touch!
>
> Thanks & Regards
>
> Amanda Wang[MSFT]
>
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.
- Follow-Ups:
- RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- From: Amanda Wang [MSFT]
- RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- References:
- ADMT - WRN1:0198 The name 'hostname' could not be resolved
- From: Rory
- RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- From: Amanda Wang [MSFT]
- ADMT - WRN1:0198 The name 'hostname' could not be resolved
- Prev by Date: RE: kb325379 - InetOrgPersonPrevent.ldf not working
- Next by Date: My post was deleted
- Previous by thread: RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- Next by thread: RE: ADMT - WRN1:0198 The name 'hostname' could not be resolved
- Index(es):
Relevant Pages
|