Nicholas
Tue Sep 23 03:59:28 CDT 2003
Steve, I would like to just clarify the dns issue - sorry if this is
becoming monotonous for you!
Do you suggest I create a secondary DNS server on the temporary server using
the procedures described in this MS article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;313563&Product=win20
00
Theoretically, that would copy all the dns zones and settings required by
active directory to the new server from the old controller which we want to
re-install.
We would then re-install take down the old DC/DNS Server, re-install Windows
Server 2003 on it and point its dns to the temporary server.
Then run DCPROMO so it can copy the AD across. Then take over the GC and
FSMO roles and then move the dns back.
Would that work?
Thanks again!
"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:eU4kfjJgDHA.128@tk2msftngp13.phx.gbl...
> Nicholas wrote:
>
> > Steve, thanks for your reply.
> >
> > You are correct in saying that the SBS installation was not completed
> > correctly in the first place. The Windows 2000 installation was done
> > by booting from SBS Disk 1 and it doesnt look like the rest of the SBS
> > components were ever installed!
> >
> > They have tried installing BackOffice tools such as the Management
> > Console etc, however immediately when setup is run from Disk 1, they
> > receive an error message stating that Small Business Server cannot
> > upgrade the current installation - or something to that effect.
>
> There's a KB article that covers this scenario, but I don't have the
> number to hand. Searching on the error given will return the relevant
> KB.
>
> >
> > The reason they have chosen the route of rather buying the individual
> > products is two fold:
> >
> > 1. They want to immediately go to the 2003 suite of products, instead
> > of first buying the migration pack and then also having to buy all the
> > individual 2003 products too!
>
> The Migration Pack would get you all the 2000 products, since it's
> SBS2000 that would be being unbundled. But there would be no
> expectation to then buy all the 2000 products as well - that's the
> whole idea of the MP.
>
> However you dice it, there's no direct path from the 2000 generation
> products to the 2003 series, other than SA or retail VUPs (where they
> still exist). That's MS policy, whether we like it or not (we can of
> course grouse at MS and try to persuade them to change their policy -
> if enough do, we may succeed).
>
> >
> > 2. They also only use Exchange and Windows 2000 Server, not SQL or
> > ISA.
>
> The Migration Pack changes the licensing to just Windows Server and
> Exchange anyway, SQL licensing is left out and ISA doesn't use CALs
> anyway. They left out SQL because the proportion of SBS users making
> use of SQL was reckoned to be a pretty low percentage.
>
> >
> > How would you suggest we tackle the DNS issue?
> >
> > Would you suggest we first setup DNS on the temporary server before
> > doing a DCPROMO? Will this automatically create all the necessary
> > zones and configurations for the domain on the new temporary server
> > when we run the DCPROMO? I remember those zones etc got automatically
> > created on the DNS server when AD was initially set up.
>
> No. You would need to manually add DNS Server to a second machine, and
> either move the zone file by hand, or use DNS replication (either by
> zone or AD).
>
> >
> > Or is there a way to migrate a DNS server to another server?
>
> Of course. DNS is designed to handle multiple servers. See above.
>
> >
> > After the new DNS server is running we will point all dns records to
> > the temporary server so it stays up to date during all this
> > re-installing etc.
>
> The temporary server is going to be the only server for a while, so yes
> all DNS records will need to point to it, but the DCPromo process and
> AD FSMO role transfers should take care of that.
>
> >
> > The Exchange issue is not really a problem as all their users mail is
> > stored in local pst's on the workstations, not on the server. So my
> > question for this is, if we simply re-install Windows Server 2003
> > with Exchange 2003 - will it immediately re-create mailboxes for all
> > the domain users, or does this need to be done manually for each and
> > every user?
>
> If Exchange is not currently configured in the AD domain, then no,
> mailboxes will not automatically be created. You'll need to mail-enable
> every user by hand. And if Exchange is already installed, you're going
> to have to remove it unless you use the Exchange migration strategy I
> already outlined.
>
> >
> > I must say, I find it strange that Microsoft does NOT have an upgrade
> > path for SBS 2000 to Windows Server 2003. Especially if customers
> > have purchased both products legally.
>
> Microsoft's exit strategy for SBS2000 is either an upgrade to SBS2003
> when it arrives, or the Migration Pack. There's no direct upgrade path
> from NT4 to WS2003 either, although there's nothing to stop you from
> adding a WS2003 server to an NT4 domain in exactly the same way that
> you can with SBS2000.
>
> >
> > IMHO MS should certainly provide the Migration pack for free when
> > customers buy the 2003 products so that an upgrade can simply be done
> > after the migration pack is installed. I don't see why this should be
> > a problem as this tool would make it far easier for customer to do an
> > upgrade instead of re-installing from scratch!
>
> If you want to use the Migration Pack route, buy the MP, don't buy
> individual product! Duh. Technically, there's nothing particularly
> complex about a migration using the standard products. The whole point
> of the MP is that it's a direct, in-place, on the SBS, breakout. It
> modifies the SBS itself to unlock all the SBS constraints.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.