Hi Mario
I'm the author of compname and you're right, it will break domain
membership. Unfortunately, it's not possible to make compname run before
the automated domain join in the mini-setup wizard, either.
One option would be to leave the machine in a workgroup, run compname,
script a reboot and then use netdom from the Support Tools folder on your
Windows 2000 CD to script a domain join. If you use the cmdlines.txt
functionality, you have a built-in reboot anyway after running the command,
so you don't have to do any extra rebooting, except for the reboot required
after joining the domain with netdom.
It's not the prettiest method, but it's what I do for unattended setups.
Hope this helps
Oli
"Mario Lipinski" <(E-Mail Removed)> wrote in message
news

(E-Mail Removed)...
> Hello,
>
> i am deploying Windows 2000 machines using Sysprep for image preparation
> and Symantec Ghost Corp for the cloning process via network.
> This works fine. There is only one problem: since i am using sysprep the
> hostname gets reset in the "mini-setup". i now could configure sysprep to
> prompt for the hostname. but i want it full-automated - so no
> userinteraction.
> is there any way to change the hostname - maybe based on ghost variables,
> dns reverse lookup, mac-address - hostname table - automatically using
> sysprep.
> the machines join a domain automatically so it would be best if if got
> changed before sysprep joins the domain.
>
> i found a tool "compname" on the internet which sets the hostname for
> example by reverse dns. but there i expect problems with the domain
> membership.
>
> Any suggestions are welcome,
>
> Thx in advance,
>
> Mario Lipinski