Hi Torgeir,
We're rolling out Windows 2000 right now, and that's the technique that we
use to rename the PCs. After your comment, I decided to check out why this
is working for us...
It looks like one of the consultants who helped us design our build process
nabbed the NETDOM.EXE from a beta build of Windows Server 2003.
I've just confirmed that the release version of Windows Server 2003's
NETDOM.EXE (5.2.3790) does work on Windows 2000.
Sorry for the bit of misinformation. It was news to me, too! :)
--
Mike Kolitz MCSE 2000
MS-MVP - Windows Setup and Deployment
Remember to check Windows Update often,
and apply the patches marked as Critical!
http://windowsupdate.microsoft.com
"Torgeir Bakken (MVP)" <Torgeir.Bakken-s...@hydro.com> wrote in message
news:3FD7959C.FC79ABE0@hydro.com...
> Mike Kolitz wrote:
> > To keep domain memberships, you'll need a tool called NetDom.
> > Once you've got it, the syntax is something similar to:
> > netdom renamecomputer %computername% /newname:<new name> /userd:<userID>
> > /passwordd:<password> /force /verbose /reboot:<time limit>
> Hi
> That is for the netdom.exe that comes with "Support Tools" for Windows XP,
and
> it will not work on a Windows 2000 computer as the OP wanted. It will err
with
> the message "The procedure entry point NetAddAlternateComputerName could
not be
> located in the dynamic link library NETAPI32.dll." if you try it on a
Win2k
> computer.
> The netdom.exe that comes with "Support Tools" for Windows 2000 does not
> support the parameter renamecomputer.
> --
> torgeir
> Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of the 1328 page
> Scripting Guide: http://www.microsoft.com/technet/scriptcenter
|
