Re: Migration Question -Anyone Please

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: SuperGumby [SBS MVP] (not_at_your.nellie)
Date: 06/27/04


Date: Sun, 27 Jun 2004 10:01:35 +1000

http://www.imho.dyndns.org/addns.htm

"Ian McCulloch" <-remove-khattarsupport@syd.eastlink.ca> wrote in message
news:OlYRwi9WEHA.1352@TK2MSFTNGP10.phx.gbl...
> Thanks there Gumby - I realize I should have opened up the formun to
> everyone - my mistake - any other takers?
>
> Why the insistence on the unique FQDN as opposed the Internet one?
> "SuperGumby [SBS MVP]" <not@your.nellie> wrote in message
> news:eeodWO8WEHA.3664@TK2MSFTNGP12.phx.gbl...
> > by limiting your respondents to MVP's you're severely depleting your
> > 'library' of information. Many of the non-mvp regulars would be able to
> > answer your questions and Microsoft employees are excluded from our
little
> > club.
> >
> > I'd probably dive in headfirst and throw CD1 of the SBS set into ServerA
> and
> > inplace upgrade the 2K domain to SBS2K3.
> >
> > BTW. You mention you have a spare box that is not in production. GOOD!!!
> > Grab the SBS media, put a second NIC in the spare box and a spare switch
> so
> > the NICs are live but not connected to your existing domain and do a
test
> > install onto this box. Come back and ask questions, of which you should
> have
> > many. FLATTEN it and DO IT AGAIN. You may then be ready to try a trial
run
> > of your 'migration' by running up W2K as a DC on the box, make it as
> similar
> > to your existing box as possible, and then upgrading it.
> >
> > It's a fairly common belief around here that you don't know how to
install
> > SBS until you've done it three times.
> > DON'T name your AD DNS the same as your public FQDN (and on this point,
if
> > your current AD is incorrectly named, ie. if it is named as your FQDN,
> this
> > would be a great opportunity to fix it).
> > Interfere with the SBS install as little as possible, the wizard will
> guide
> > you.
> > The most important part of the install is right at the end. You MUST
> > complete the To-Do list.
> >
> > Mick
> > Sydney, NSW
> > Australia
> >
> > "Ian McCulloch" <-remove-khattarsupport@syd.eastlink.ca> wrote in
message
> > news:OvgJDa5WEHA.2176@TK2MSFTNGP11.phx.gbl...
> > > Hello guys
> > >
> > > In response to my last post in which I have discovered SBS 2003 must
> exist
> > > in its own domain, I really need some advice on migrating an existing
2k
> > > domain to an SBS domain. I do have white papers in hand and will be
> > reading
> > > them. I would like to supplement my reading material with some hard
> core
> > > experience out there.
> > >
> > > So here goes:
> > >
> > > 15 users, 2 servers
> > >
> > > Server A
> > > P3 1.2GHz, 1 GB RAM
> > > Win2k SP4 DC, F/P, Backup,
> > > C (2.6 GB free)/D (20 GB free) (runs a small 250 MB database that is
> > easily
> > > transportable)
> > >
> > > Server B
> > > P4 2.4 GHZ Xeon, 1 GB RAM, 70 GB HDD (RAID 5)
> > > Win2K SP4 Citrix Metaframe XPs FR3
> > > Runs all users in Citrix
> > >
> > > Server C (not in Production)
> > > P4, 2.3 GHx, 512 MB RAM
> > > C (15GB), D(18GB)
> > > Windows 2003 Server currently member server on Win2k domain
> > >
> > > My thinking so far is this -
> > >
> > > port the database, files, home folders on server A to server C
> > > Upgrade the 2k domain controller to SBS 2003 using the appropriate
white
> > > paper
> > >
> > > A few questions:
> > > What considerations are there for the TS licensing server currently
> > running
> > > on Server A
> > > What about IIS 5.0 on server A? Should this be uninstalled first as
it
> > may
> > > complicate the migration (I run a small web interface for some help
desk
> > > software)
> > > Any paging file considerations?
> > > any serious AD considerations?
> > > What would you guys/gals do?
> > >
> > > Your suggestions are so much appreciated!
> > >
> > > Ian
> > > Sydney, NS
> > > Canada
> > >
> > >
> > >
> >
> >
>
>



Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 messed up after sp3 install
    ... I feel this tool is a must for any SBS install. ... You might also want to check the binding order since you have 2 NICs: ... Check Internet access and Exchange mailboxes ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server with SBS 2K3
    ... I am not sure how you configure your SBS fax, does the issue occur on every ... Do normal users try to install a network printer? ... Have you installed the Windows 2003 printer driver on ... |> "Prevent users from adding printers" group policy in the default domain ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... slip stream SBS you would have had it ages ago. ... How did they buy this Server? ... My main reason for slipstreaming the install is because I cannot get the ...
    (microsoft.public.windows.server.sbs)
  • Re: Does SP1 install XP SP2 on all workstations?
    ... This newsgroup only focuses on SBS technical issues. ... >Subject: Re: Does SP1 install XP SP2 on all workstations? ... >> be assigned to client computers when you apply SBS 2003 SP1. ...
    (microsoft.public.windows.server.sbs)