Archived from groups: microsoft.public.win2000.dns (More info?)

Got Windows 2000 Active Directory domain with AD Integrated DNS.

Built from scratch XP clients register fine; Ghost cloned XP clients
are not registering.

The clones were not sysprepped or Ghost Walked. We tried using NewSID
utility from www.sysinternals.com. After changing SID on clients, the
clients are still not registering in DNS.

Any suggestions on workaround for our existing Ghost cloned machines
to work without having to rebuild the machines from scratch?

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi

Wild guess. Try running sysprep on them now and rebooting straight away.
This will possibly fix any SID problems. Also think about removing and
re-installing the NIC's, checking the ip configuration and repairing the
TCP/IP stack. Failing these suggestions, I think you're in for a rebuild.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: markreno@online.microsoft.com

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

"Robut2" <rmoreno_google@pobox.com> wrote in message
news:4652234f.0410070014.39078071@posting.google.com...
> Got Windows 2000 Active Directory domain with AD Integrated DNS.
>
> Built from scratch XP clients register fine; Ghost cloned XP clients
> are not registering.
>
> The clones were not sysprepped or Ghost Walked. We tried using NewSID
> utility from www.sysinternals.com. After changing SID on clients, the
> clients are still not registering in DNS.
>
> Any suggestions on workaround for our existing Ghost cloned machines
> to work without having to rebuild the machines from scratch?

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:eXu9PhLrEHA.2964@TK2MSFTNGP14.phx.gbl,
Mark Renoden [MSFT] <markreno@online.microsoft.com> made a post then I
commented below
> Hi
>
> Wild guess. Try running sysprep on them now and rebooting straight
> away. This will possibly fix any SID problems. Also think about
> removing and re-installing the NIC's, checking the ip configuration
> and repairing the TCP/IP stack. Failing these suggestions, I think
> you're in for a rebuild.
> Kind regards
>


To add, are the machines being added to the domain upon reboot automatically
thru your sysprep.inf file?
Is the Primary DNS Suffix of the XP clients set to the zone name in DNS?
(The suffix dictates what zone to register into).
Are the clients set to use ONLY the internal DNS server, assuming Option 006
in DHCP is only set to the internal DNS server(s)? (Between the suffix and
what DNS server is being used, are two of the factors dictating
regsitration.

Otherwise, if the SID is being mangled by the 3rd party utility, then I can
see that the machines may not be joining the domain and hence the Primary
DNS Suffix is not being set by default, assuming you are only using your
internal DNS server(s).

btw- Sysprep is a wonderful tool. I don't know what I would do without it.
It creates a new SID upon rolling out the images. I have the computername
set to blank in the .inf file and upon reboot after multicasting them out,
it just prompts me for the computername and a password. Cool stuff!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================