|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
--____JVODRLRJPTLRGJNYQUON____
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; modification-date="Tue, 9 Jul 2007 02:55:59
+1200"
Hi There!
We are planning a migration for a server which is running SBS 2003 (Non =
Service Packed Non R2) to a 2003 R2 Fully Patched Environment
We are relunctant to patch the old server as its pretty unstable and we =
are worried the entire thing is going to fall over, though if its required =
to complete
then we will take the plunge and do it.=20
I am wondering if there are any step by step guides for doing this =
migration to new hardware around that we can use to do this migration.=20
The last attempts we have tried didn't work well, the first when we tried =
to join the new server to the old domain, which went ok, but when we tried =
to install Exchange
on the new server it threw up installation errors we were unable to =
resolve (and unfortunately the engineer in question didn't take note of =
the error message).
We then tried to use an interim server, however we were unable to join the =
new server to the interim server domain due to unresolvable DNS type =
errors.=20
I suspect we are not executing one or more steps correctly, but to me it =
seemed information on these exact types of migrations were relatively thin =
on the ground.=20
Any information would be much appreciated.
--____JVODRLRJPTLRGJNYQUON____
Content-Type: multipart/related; boundary="____OLUAPOKFLIQWXGRSNSNL____"
--____OLUAPOKFLIQWXGRSNSNL____
Content-Type: text/html; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; modification-date="Tue, 9 Jul 2007 02:55:59
+1200"
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-15=
">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Arial">
<DIV>Hi There!</DIV>
<DIV> </DIV>
<DIV>We are planning a migration for a server which is running SBS 2003 =
(Non Service Packed Non R2) to a 2003 R2 Fully Patched Environment</DIV>
<DIV> </DIV>
<DIV>We are relunctant to patch the old server as its pretty unstable and =
we are worried the entire thing is going to fall over, though if its =
required to complete</DIV>
<DIV>then we will take the plunge and do it. </DIV>
<DIV> </DIV>
<DIV>I am wondering if there are any step by step guides for doing this =
migration to new hardware around that we can use to do this migration. =
</DIV>
<DIV> </DIV>
<DIV>The last attempts we have tried didn't work well, the first when we =
tried to join the new server to the old domain, which went ok, but when we =
tried to install Exchange</DIV>
<DIV>on the new server it threw up installation errors we were unable to =
resolve (and unfortunately the engineer in question didn't take note of =
the error message).</DIV>
<DIV> </DIV>
<DIV>We then tried to use an interim server, however we were unable to =
join the new server to the interim server domain due to unresolvable DNS =
type errors. </DIV>
<DIV> </DIV>
<DIV>I suspect we are not executing one or more steps correctly, but to me =
it seemed information on these exact types of migrations were relatively =
thin on the ground. </DIV>
<DIV> </DIV>
<DIV>Any information would be much appreciated.</DIV></BODY></HTML>
--____OLUAPOKFLIQWXGRSNSNL____--
--____JVODRLRJPTLRGJNYQUON____--
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0195_01C7C0E3.856CAEB0
Content-Type: text/plain;
charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
Well, its not free, but the widely accepted standard for migrating to =
new hardware is found at sbsmigration.com
It involves the use of an intermediate server, which allows you to have =
the new final target server have the same name and preserve the domain
Now granted with lots of research and time, you can go out and find all =
this yourself...but Jeff has done a great job of bring all this togehter =
and adding some tools to automate some of the required AD cleanup, etc.
worth the money in the amount of time you will save on the migration.=20
--=20
Cris Hanna [SBS-MVP]
------------------------------
Please do not contact me directly, only respond in the Newsgroups
MVPs do not work for Microsoft
------------------------------
Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2
"Andre Southgate" <Andre[ at ]sapphiresolutions.co.nz.NOSPAM!> wrote in =
message news:4690FAFF.DCE4.00AE.0[ at ]sapphiresolutions.co.nz.NOSPAM!...
Hi There!
We are planning a migration for a server which is running SBS 2003 =
(Non Service Packed Non R2) to a 2003 R2 Fully Patched Environment
We are relunctant to patch the old server as its pretty unstable and =
we are worried the entire thing is going to fall over, though if its =
required to complete
then we will take the plunge and do it.=20
I am wondering if there are any step by step guides for doing this =
migration to new hardware around that we can use to do this migration.=20
The last attempts we have tried didn't work well, the first when we =
tried to join the new server to the old domain, which went ok, but when =
we tried to install Exchange
on the new server it threw up installation errors we were unable to =
resolve (and unfortunately the engineer in question didn't take note of =
the error message).
We then tried to use an interim server, however we were unable to join =
the new server to the interim server domain due to unresolvable DNS type =
errors.=20
I suspect we are not executing one or more steps correctly, but to me =
it seemed information on these exact types of migrations were relatively =
thin on the ground.=20
Any information would be much appreciated.
------=_NextPart_000_0195_01C7C0E3.856CAEB0
Content-Type: text/html;
charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-15">
<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Arial" bgColor=3D#ffffff>
<DIV>Well, its not free, but the widely accepted standard for migrating =
to new=20
hardware is found at sbsmigration.com</DIV>
<DIV>It involves the use of an intermediate server, which allows you to =
have the=20
new final target server have the same name and preserve the domain</DIV>
<DIV> </DIV>
<DIV>Now granted with lots of research and time, you can go out and find =
all=20
this yourself...but Jeff has done a great job of bring all this =
togehter=20
and adding some tools to automate some of the required AD cleanup,=20
etc.</DIV>
<DIV> </DIV>
<DIV>worth the money in the amount of time you will save on the=20
migration. </DIV>
<DIV><BR>-- <BR>Cris Hanna =
[SBS-MVP]<BR>------------------------------<BR>Please=20
do not contact me directly, only respond in the Newsgroups<BR>MVPs do =
not work=20
for Microsoft<BR>------------------------------<BR>Send via Windows Mail =
on=20
Vista Ultimate connected to SBS 2003 R2</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Andre Southgate" <<A=20
=
href=3D"mailto:Andre[ at ]sapphiresolutions.co.nz.NOSPAM">Andre[ at ]sapphiresoluti=
ons.co.nz.NOSPAM</A>!>=20
wrote in message <A=20
=
href=3D"news:4690FAFF.DCE4.00AE.0[ at ]sapphiresolutions.co.nz.NOSPAM">news:46=
90FAFF.DCE4.00AE.0[ at ]sapphiresolutions.co.nz.NOSPAM</A>!...</DIV>
<DIV>Hi There!</DIV>
<DIV> </DIV>
<DIV>We are planning a migration for a server which is running SBS =
2003 (Non=20
Service Packed Non R2) to a 2003 R2 Fully Patched Environment</DIV>
<DIV> </DIV>
<DIV>We are relunctant to patch the old server as its pretty unstable =
and we=20
are worried the entire thing is going to fall over, though if its =
required to=20
complete</DIV>
<DIV>then we will take the plunge and do it. </DIV>
<DIV> </DIV>
<DIV>I am wondering if there are any step by step guides for doing =
this=20
migration to new hardware around that we can use to do this migration. =
</DIV>
<DIV> </DIV>
<DIV>The last attempts we have tried didn't work well, the first when =
we tried=20
to join the new server to the old domain, which went ok, but when we =
tried to=20
install Exchange</DIV>
<DIV>on the new server it threw up installation errors we were unable =
to=20
resolve (and unfortunately the engineer in question didn't take note =
of the=20
error message).</DIV>
<DIV> </DIV>
<DIV>We then tried to use an interim server, however we were unable to =
join=20
the new server to the interim server domain due to unresolvable DNS =
type=20
errors. </DIV>
<DIV> </DIV>
<DIV>I suspect we are not executing one or more steps correctly, but =
to me it=20
seemed information on these exact types of migrations were relatively =
thin on=20
the ground. </DIV>
<DIV> </DIV>
<DIV>Any information would be much =
appreciated.</DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0195_01C7C0E3.856CAEB0--
|
|
In article <4691022D.DCE4.00AE.0[ at ]sapphiresolutions.co.nz.NOSPAM!>,
Andre[ at ]sapphiresolutions.co.nz.NOSPAM! says...
[Quoted Text] > Thanks for the information. I have had a look at this site,
> but I can't really figure out what this kit actually is.
The kit is a information and a set of scripts that make certain tasks a
LOT easier. I was able to migrate an SBS 2003 Prem server to a new
server in what appeared to be several minutes to the users, it took me
about 4 hours not including the restore/copy of user data, but I had
done the restore of profiles from a backup tape so I did the production
restore on the night shift and the users were (night shift) back online
in 5 minutes once I swapped servers (then I restored the backups over
top their day-old data).
I think that the hardest part was manually recreating the printers using
the scripted information - and the only hard part was making the IP
again :)
--
Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free[ at ]rrohio.com (remove 999 for proper email address)
|
|
|