Re: Switching domain logins on Win XP computer from a SBS 4.5 server to a SBS 2003 one
- From: harry.mandel@xxxxxxxxxxxx
- Date: 18 Jul 2006 07:10:35 -0700
Thanks. sbsmigration.com looks interesting, maybe we'll just "start
over" with them. The reason I am doing all this back and forth is that
initially we were going to just re-point all the workstations to the
new domain, but as I said two of them had the issues I mentioned
earlier and others logged into the new domain extremely slowly (a
totally separate issue) so we're trying to avoid where people have
problems enormous enough on the first day of the new server that we
have to go back to the old one until we work them out, that's why the
back and forth testing.
Thanks again for your reply. Any other advice you can give will be
much appreciated.
Cris Hanna (SBS-MVP) wrote:
You should not be going back and forth
You also could have saved yourself probably considerable effort by looking at sbsmigration.com
When you reboot the xp pro after disjoining the old domain, you should logon to "This computer".
Then start internet explorer on the workstation and type
http://servername/connectcomputer to join it to the new domain.
Once a production machine is joined to the new domain, it should not go back
--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
<harry.mandel@xxxxxxxxxxxx> wrote in message news:1153160649.110715.70740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We are on the verge of migrating from Small Business Server 4.5 to
Small Business Server 2003. The new server and accounts are all setup.
Both servers (the old 4.5 and the new 2003) exist on the network with
unique domain names for now so I can test without disrupting others.
To test if individual workstations get changed without problems, we
want to be able to have the ability to log into either domain at
signup. With the few Windows 98 SE computers we have left, this is
easy, you can change the domain name and type in whatever you want at
login and I can easily test them.
But with the Windows XP Pro computers, it is much more complicated it
seems. At logon, you have the option of logging into ''ComputerName
(this computer)'' where 'ComputerName' would be replaced with the name
for the computer or to a single domain.
When I do the XP process of adding the computer to a new domain, after
the reboot, I only have the option of ''this computer'' or the new
domain, not the old domain anymore. So when my test is done, to have it
re-link back to the old domain, I have to go through the whole process
all over again.
Besides being a chore to go back and forth like this, it has proven a
bit dangerous. On one computer I tried it on a couple of times, there
eventually was an error generated when trying to connect to the new
domain for a 2nd test. After that, the computer refused to log into
anything (even into just itself, insisted on a password for
Administrator even though one wasn't required for it before) and we
eventually had to get the data off this computer's C: drive (we were
able to) and then do a reformat/reinstall of Win XP since we couldn't
log in. On another computer after doing this a couple of times, it
wouldn't boot anymore because it said that HAL.DLL became corrupted. I
was able to fix this with Recovery Console, but it was rather onerous.
So I have two questions:
1) Is there any way to make the XP computers so I can choose at logon
one or the other domain?
2) Why would problems like the HAL.DLL issue occur? Is it bad to keep
joining back and forth between 2 domains (we wouldn't do this once the
new server is "live" but I don't want to just change all the
workstations one night and if there are immediate unforeseen problems
the next morning people can't work for awhile because it is long and
problematic to "go back")?
Any help would be much appreciated, thanks.
------=_NextPart_000_0029_01C6A9A5.9F565110
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Google-AttachSize: 4621
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>You should not be going back and forth</FONT></DIV>
<DIV><FONT face=Arial size=2>You also could have saved yourself probably
considerable effort by looking at sbsmigration.com</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>When you reboot the xp pro after disjoining the old
domain, you should logon to "This computer".</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Then start internet explorer on the workstation and
type</FONT></DIV>
<DIV><FONT face=Arial size=2><A
href="http://servername/connectcomputer";>http://servername/connectcomputer</A>
to join it to the new domain.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Once a production machine is joined to the new
domain, it should not go back</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna
[SBS-MVP]<BR>--------------------------------------<BR>Please do not respond
directly to me, but only post in the newsgroup so all can take advantage</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><<A
href="mailto:harry.mandel@xxxxxxxxxxxx";>harry.mandel@xxxxxxxxxxxx</A>>
wrote in message <A
href="news:1153160649.110715.70740@xxxxxxxxxxxxxxxxxxxxxxxxxxxx";>news:1153160649.110715.70740@xxxxxxxxxxxxxxxxxxxxxxxxxxxx</A>...</DIV>We
are on the verge of migrating from Small Business Server 4.5 to<BR>Small
Business Server 2003. The new server and accounts are all setup.<BR>Both
servers (the old 4.5 and the new 2003) exist on the network with<BR>unique
domain names for now so I can test without disrupting others.<BR><BR>To test
if individual workstations get changed without problems, we<BR>want to be able
to have the ability to log into either domain at<BR>signup. With the few
Windows 98 SE computers we have left, this is<BR>easy, you can change the
domain name and type in whatever you want at<BR>login and I can easily test
them.<BR><BR>But with the Windows XP Pro computers, it is much more
complicated it<BR>seems. At logon, you have the option of logging into
''ComputerName<BR>(this computer)'' where 'ComputerName' would be replaced
with the name<BR>for the computer or to a single domain.<BR><BR>When I do the
XP process of adding the computer to a new domain, after<BR>the reboot, I only
have the option of ''this computer'' or the new<BR>domain, not the old domain
anymore. So when my test is done, to have it<BR>re-link back to the old
domain, I have to go through the whole process<BR>all over
again.<BR><BR>Besides being a chore to go back and forth like this, it has
proven a<BR>bit dangerous. On one computer I tried it on a couple of times,
there<BR>eventually was an error generated when trying to connect to the
new<BR>domain for a 2nd test. After that, the computer refused to log
into<BR>anything (even into just itself, insisted on a password
for<BR>Administrator even though one wasn't required for it before) and
we<BR>eventually had to get the data off this computer's C: drive (we
were<BR>able to) and then do a reformat/reinstall of Win XP since we
couldn't<BR>log in. On another computer after doing this a couple of times,
it<BR>wouldn't boot anymore because it said that HAL.DLL became corrupted.
I<BR>was able to fix this with Recovery Console, but it was rather
onerous.<BR><BR>So I have two questions:<BR><BR>1) Is there any way to make
the XP computers so I can choose at logon<BR>one or the other
domain?<BR><BR>2) Why would problems like the HAL.DLL issue occur? Is it bad
to keep<BR>joining back and forth between 2 domains (we wouldn't do this once
the<BR>new server is "live" but I don't want to just change all
the<BR>workstations one night and if there are immediate unforeseen
problems<BR>the next morning people can't work for awhile because it is long
and<BR>problematic to "go back")?<BR><BR>Any help would be much appreciated,
thanks.<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0029_01C6A9A5.9F565110--
.
- Prev by Date: RE: This server has a trust relationship
- Next by Date: How 2 Suppress Security Events from SYSTEM user?
- Previous by thread: RE: NT Backup failing consistantly
- Next by thread: How 2 Suppress Security Events from SYSTEM user?
- Index(es):
Relevant Pages
|
