SuperGumby
Sun Oct 28 14:23:37 PDT 2007
Yes, I think it's worth a go (re-install Exch). You probably need to remove
'newserver' and manually remove references to 'server' and the Exchange org
from AD. It may however be unnecessary.
This may be handy
How to remove the last Exchange Server 5.5 computer from an Exchange 2000
administrative group
http://support.microsoft.com/kb/284148/en-us
as may this and the articles linked from it
XADM: How to Remove the First Exchange Server in a Site
http://support.microsoft.com/kb/152959/
"Sprocket" <Sprocket@discussions.microsoft.com> wrote in message
news:ABCEB537-AE61-4026-A8C4-EAB72B6671EA@microsoft.com...
>I absolutely agree...even with all the neat cool features of SBS2003 which
> would benefit the customer, they are unwilling to spend the money and in
> fact
> may not have the money to spend. I will approach them with the idea of
> wiping and reinstalling Exchange. That would solve this issue.
>
> --
> Sprocket in Texas
>
>
> "Larry Struckmeyer" wrote:
>
>> Hi Sprocket:
>>
>> IMHO, you and your client will be much further along to spend the few
>> hundred it costs to upgrade to SBS 2003.
>>
>> SBS 2000 is out of its support window, and most have forgotten more about
>> SBS 2000 than they remember.
>>
>> There are several flags on this installation. I don't like it, and I
>> would
>> probably not want to support it.
>>
>> You could also backup the exchange to pst files, backup the data to known
>> good restore points, and flatten and reinstall SBS 2000 to have a clean
>> installation.
>>
>> If they went to 2000 in 2003, the cycle is about right for them to go to
>> 2003 in 2007. :-)
>>
>>
>> Larry
>>
>>
>> "Sprocket" <Sprocket@discussions.microsoft.com> wrote in message
>> news:34E8B09F-AFBC-4D1E-A567-22CDD2C2DBA1@microsoft.com...
>> > I've recently taken over this account which apparently has had several
>> > "experts" over the last 10 years. The customer at one time had sbs 4.5
>> > with
>> > a server name of server and an internal domain name of company, not
>> > company.local, just company. For purposes of discussion, let's say
>> > their
>> > public domain was company.com. They upgraded to SBS2000 in 2003.
>> >
>> > Now in Exchange, there are two servers listed, one called server and
>> > we'll
>> > call the other newserver. I cannot access server, when I click on it,
>> > I
>> > get
>> > a time out. I can click on and configure newserver. However, I
>> > discovered
>> > that server was setup as the master and I have changed that with
>> > newserver
>> > as
>> > the master and server as a member. I have been unable to delete the
>> > old
>> > server.
>> >
>> > When I send mail, I get the normal SMTP connector. However I'm also
>> > getting
>> > a strange remote mail listing under queues. The queue name is
>> > server.domain
>> > (which is the old server name) and when I click on that, I get the sent
>> > from:
>> > newserver-IS@company.com. There are several of these messages queued
>> > up
>> > and
>> > if I delete them, more appear. I don't know who they are going to and
>> > I
>> > can't read the message.
>> >
>> > My questions are:
>> > Is there any way to read the messages in queue so I can figure out what
>> > they
>> > are?
>> > What is the origin of messages with the from being newserver-IS? What
>> > does
>> > the IS mean.
>> > How can I delete the non-functioning listing of the old server in
>> > Exchange
>> > 2000.
>> >
>> > y'all have been great. Thanks for your help.
>> > --
>> > Sprocket in Texas
>>
>>
>>