After doing some of this manually for a while I would also like to pass a
few additions to Mark's list. Unfortunately, I haven't had time to write a
script for simplifying this or document the process but here are some
lessons learned.
- Define/change the local admin account name and password so you can get
back in afterwards.
- Use the RunOnce key for initiating post reboot script executions. It's
self-deleting and
hidden from wandering users.
- Don't forget to remove/change the autologin values ("ForceAutoLogon",
"AutoAdminLogon",
and "Default Password") or the PC will always autologon.
Some of these may seem obvious, but it only takes overlooking them to cause
a lot of grief.
Another good reference for NETDOM and scripting this is at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q222525
................................
Kind regards
Glenn Deans
Network Engineer
Siemens Business Services, Inc.
Bellefontaine, OH USA
-----Original Message-----
From: Messenger, Mark [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 9:41 PM
To: 'hugh s'; [EMAIL PROTECTED]
Subject: RE: domain change
IMHO:
1) Join the workgroup (Leave the domain)
2) Rename the computer
3) Join the new domain
Each of these will request a reboot. I know the first two can be combined.
You can (re-)capture the system upon reboot by setting the "ForceAutoLogon",
"AutoAdminLogon", "DefaultUsername", "Default Password", and
"DefaultDomainName" registry values under HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon . All are of type REG_SZ. The first two need
to be set to "1". The middle two should be set to the local administrator's
username and password. the last one should be set to the local computer's
(short) NETBIOS name. Be careful, as this will change with step 2 above.
With this, you can put a script in the
HKLM\software\microsoft\windows\currentversion\run key or the All Users
start menu folder "Startup" and regain control of the computer.
Hope this helps you in your task. :)
-----Original Message-----
From: hugh s [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 6:19 PM
To: [EMAIL PROTECTED]
Subject: domain change
I'm a low hours server helper pilot here so I don't know just
what I'm asking. Is this a huge question?
We have 100 2k boxes on the floor that will change domains and
machine names in mid October. The IS guy wants me to address
each individual machine with mouse in hand. I'm not
really all that enthusiastic about the approach. I want to
script it if I can. As much as I can. Maybe there's even a free
tool. They are not going to spend a dime.
Here's my plan so far. I've got Roth's "Windows NT" in my hand
and, modules aside, consider myself an intermediate Perl programmer.
I really am a server newbee.
This is what I plan. First join a work group. Then rejoin an
msdomain - the new one. After that, rename the computer.
The shares that now fail I'd locate and point to the proper new
share points. I assume here that these shares should be
collected and recorded before all this msdomain change business.
I can't see any reason this couldn't be scripted - but what do I
know. There's a reboot or two in here and I have no clue as to
how to capture the system when it comes back up.
I'm not asking for anyone to write this, but some clues on what to do
would be helpful.
Thanks
If this is way out of line then we could spare the list. Mail me.
Thanks again.
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
