• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Re: Migration sbs2008 from sbs2003 exchange best practices shows sbs20

  • Thread starter Jeff Middleton [SBS-MVP]
  • Start date
J

Jeff Middleton [SBS-MVP]

#1
Bryan,

I'm not sure if I can really tell you a lot about how to resolve this
without getting into a lot deeper discussion, but I can try to clarify your
situation.

After the conclusion of the SBS 2008 migration sequence you must do an
orderly decommission of your "source" server. That means you uninstall
Exchange in an orderly manner and complete a DCpromo sequence to demote the
"source" server so that it's no longer registered in AD as either an
Exchange Server or Domain Controller. After that there's a bit more minor
cleanup to get rid of the computer object shown in the SBS console or in
DNS.

If you didn't do these things, this explains why you see remnants of the
source server and you need to address that cleanup now.

Removing Exchange from the source server would eliminate the Information
Stores and the Storage Groups.

With all that eliminated you wouldn't have any SPN errors.

As for the original Administrative Group, that's permanent and doesn't go
away.

It sounds to me that you omitted the Exchange cleanup before you removed the
source server, so now you need to remove the Exchange objects and anything
else you overlooked.

I'm hesitent to just offer blind advice on this, it's not the way I would
support a customer of mine, but the documentation path provided by MS for
cleanup is not quite the same as what I provide via SBSmigration.com and so
I'd like to leave it at you need to review the cleanup tasks to be
completed. At this point you would need to use ASDiedit, but you need to be
careful about what you start deleting and I can't know for sure what impact
this may have on your operating server. You might need someone who knows
what to look for to inspect your configuration.


- Jeff Middleton SBS-MVP
YCST@newsgroup


"Bryan Watt" <BryanWatt@newsgroup> wrote in message
news:1CD1B37F-4498-45DA-A2EB-711780F81E82@newsgroup

>I still see a first administrative group and the original source server in
> the best practices analyzer. Everything seems to be working fine even with
> original server shut off. I don't understand why these objects are still
> here. the Exchange administrative group is fine. I have fqdn errors on the
> first administrative group. I'm not sure how to proceed to clean this up.
> Missing fqdn in exchangeMDB service principle name
> missing fqdn in exchangerfr service principle name
> missing netbios name in exchangemdb service principle name
> missing netbios name in exchangerfr service principle name
 

My Computer

B

Bryan Watt

#2
Re: Migration sbs2008 from sbs2003 exchange best practices shows s

It never said to uninstall exchange. It only said to run dcpromo. I followed
the migration every step. When I try to run sbs2003 setup now to remove
exchange it stops at 25-40 and never loads. Is there any other way to remove
exchange from the original server? Can I just run system manager and delete
the first administrative group leaving the exchange administrative group for
exchange 2007?

"Jeff Middleton [SBS-MVP]" wrote:

> Bryan,
>
> I'm not sure if I can really tell you a lot about how to resolve this
> without getting into a lot deeper discussion, but I can try to clarify your
> situation.
>
> After the conclusion of the SBS 2008 migration sequence you must do an
> orderly decommission of your "source" server. That means you uninstall
> Exchange in an orderly manner and complete a DCpromo sequence to demote the
> "source" server so that it's no longer registered in AD as either an
> Exchange Server or Domain Controller. After that there's a bit more minor
> cleanup to get rid of the computer object shown in the SBS console or in
> DNS.
>
> If you didn't do these things, this explains why you see remnants of the
> source server and you need to address that cleanup now.
>
> Removing Exchange from the source server would eliminate the Information
> Stores and the Storage Groups.
>
> With all that eliminated you wouldn't have any SPN errors.
>
> As for the original Administrative Group, that's permanent and doesn't go
> away.
>
> It sounds to me that you omitted the Exchange cleanup before you removed the
> source server, so now you need to remove the Exchange objects and anything
> else you overlooked.
>
> I'm hesitent to just offer blind advice on this, it's not the way I would
> support a customer of mine, but the documentation path provided by MS for
> cleanup is not quite the same as what I provide via SBSmigration.com and so
> I'd like to leave it at you need to review the cleanup tasks to be
> completed. At this point you would need to use ASDiedit, but you need to be
> careful about what you start deleting and I can't know for sure what impact
> this may have on your operating server. You might need someone who knows
> what to look for to inspect your configuration.
>
>
> - Jeff Middleton SBS-MVP
> YCST@newsgroup
>
>
> "Bryan Watt" <BryanWatt@newsgroup> wrote in message
> news:1CD1B37F-4498-45DA-A2EB-711780F81E82@newsgroup

> >I still see a first administrative group and the original source server in
> > the best practices analyzer. Everything seems to be working fine even with
> > original server shut off. I don't understand why these objects are still
> > here. the Exchange administrative group is fine. I have fqdn errors on the
> > first administrative group. I'm not sure how to proceed to clean this up.
> > Missing fqdn in exchangeMDB service principle name
> > missing fqdn in exchangerfr service principle name
> > missing netbios name in exchangemdb service principle name
> > missing netbios name in exchangerfr service principle name
>
>
> .
>
 

My Computer

Users Who Are Viewing This Thread (Users: 1, Guests: 0)