Re: PLEASE HELP ME GET OUT OF EXCHANGE 2007 HELL - CAN't UNINSTALL

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

Did you create a send connector (can be done from the gui).

Leif

"boe" <boe_d@xxxxxxxxxxxxxxxxxx> wrote in message
news:eWgEe2aiHHA.4624@xxxxxxxxxxxxxxxxxxxxxxx
OK, I may have exagerated a tad - I have set up about 50 exchange servers
but the amount of reading I've had to do over the past 8 years of setting
up servers is minimal compared to what I've had to do for just setting up
on exchange 2007 server. The only thing I have to reference on occassion
is the commands for eseutil and isinteg since I don't do them often and
they are not gui - everything that is gui seems pretty straight forward
and very easy to find and use. I understand some people can remember IP
addresses and phone numbers and command lines easily - I can't even
remember my last work phone number, street address - some people are just
more visually capable and poor with remembering words, numbers etc - I
would definitely be poor at all of those.

I've got the server receiving e-mails - can't seem to figure out why
outgoing aren't working at this point - even incoming required command
shell to enable on this thing - not terribly friendly out of the box if
you ask me. I don't even know what command shell to look for since I
don't get an error on why outgoing messages are going nowhere.

"Bharat Suneja [MVP]" <bharat@xxxxxxxxxx> wrote in message
news:e5XtoAWiHHA.4976@xxxxxxxxxxxxxxxxxxxxxxx
Please don't mistake my frustation with
exchange 2007 with frustration towards those who are good enough to try
to help.

I did not - but I do find the capability of having installed over 50
Exchange 2003 servers, including clusters, without reading anything -
interesting!

I do suggest if you haven't already - set up an exchange test server and
uninstall it - see if it is easy or not without reading my post.

Have been doing that since early 2006. :)

it does little easily (unless you happen to be able to remember 100's
of lines of powershell)

Agreed, if all you've done is GUI in the past, it's going to be a little
challenging at first. Nevertheless, it's important to realize if you want
to administer going forward, there will be plenty of things that'll
require familiarity with the shell. If you spend some effort in learning
the basics, you'll find it's not that difficult, and actually makes a lot
of things quite easier, imo.

Of course, the shell's not perfect - it's a v1.0 product, and given that
fact it's a pretty good v1.0. :)
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
------------------------------


"boe" <boe_d@xxxxxxxxxxxxxxxxxx> wrote in message
news:OZP3ZgViHHA.4680@xxxxxxxxxxxxxxxxxxxxxxx
I appreciate your attempts to help. Please don't mistake my frustation
with exchange 2007 with frustration towards those who are good enough to
try to help.

I do suggest if you haven't already - set up an exchange test server and
uninstall it - see if it is easy or not without reading my post. I
think a lot of people have done a great deal with exchange 2007 that I
have not even scratched the surface of however it seems that many who
tout it's praises have not yet tried to do what a lot of people are
having difficulty with. While exchage 2007 has the ability to do a great
deal, it does little easily (unless you happen to be able to remember
100's of lines of powershell) or intuitively, not too many people are
going to instinctively type powershell commands whereas with a gui
interface - everything can be discovered without having to speak in
tongues.

"Bharat Suneja [MVP]" <bharat@xxxxxxxxxx> wrote in message
news:u$7rxrSiHHA.4076@xxxxxxxxxxxxxxxxxxxxxxx
I've set up and maintained over 50 exchange servers all the way up to
exchange 2003 SP2 clustered still without having to really read
anything -

You have my respect for such capabilities. And so do your hiring
managers, if these were full time gigs.

...neither of us could even figure out the datbase id until a few
tries.

Understandable, but it's not because of any complexity built-in into
the shell, imho.

Just about every solution I've seen involves using ADSIEDIT...

Haven't really had to fire up ADSIEdit for any changes, except to
determine certain values change.

...since no one seems to be able to figure out the powershell.

...that certainly isn't the case, imo. There are plenty of
powershell/Exchange shell resources available out there, including in
the product documentation, online on microsoft.com, these newsgroups,
and plenty of blogs and web sites out there. The shell also has plenty
of help built-in, if you've cared to use the get-help command you'd
know. However, all of that would require reading, something you've said
you don't want to indulge in.

Understand your frustration overall, but some of the above is plain
incorrect, imo.

BTW, did you look at any of the following:
How to Completely Remove Exchange 2007 from a Server
http://technet.microsoft.com/en-us/library/bb123893.aspx

How to Remove an Exchange 2007 Organization
http://technet.microsoft.com/en-us/library/aa998313.aspx

Finally, if it's a test environment, you can simply format the box and
reinstall the OS (if that's an option).
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
------------------------------


"boe" <boe_d@xxxxxxxxxxx> wrote in message
news:%23GdKggSiHHA.4288@xxxxxxxxxxxxxxxxxxxxxxx
The first time I had the issue, I made the mistake of installing in a
production environment with an exchange 2003 server. I did a system
state restore to get out of that nasty bit of unpleasantness.

I have an MS MVP on the phone and he even has remote access to the
exchange server and can't figure out this mess. We set up a brand
new Domain Controller in a brand new domain. Set up the new exchange
server and it choked on the roll up update, so we are wanted to
unistall exchange since this is not a production environment.

It is getting stuck on uninstall saying the public folders has
replicas - I haven't even created any public folders - there are no
other exchange servers - where the heck is it replicating. My MS
buddy couldn't make heads nor tails of the powershell any more than I
could. They really need real examples since we can't seem to get the
variables correct - neither of us could even figure out the datbase id
until a few tries.

You can admonish me all you like about having to read the 5000 pages
of powershell commands thoroughly before attempting an exchange 2007
install - don't worry - I've given up on exchange 2007 - I'm going
back to exchange 2003. Installed my first exchange 5.5 server
without reading a single thing - I've set up and maintained over 50
exchange servers all the way up to exchange 2003 SP2 clustered still
without having to really read anything - can't uninstall exchange 2007
without begging for help. Just about every solution I've seen
involves using ADSIEDIT since no one seems to be able to figure out
the powershell.

I'm reading this - http://support.microsoft.com/kb/927464/en-us and
the solution seems to be setting up another exchange server so I can
pass off the replica to another server - Click Start, point to
Programs, point to Exchange Server 2007, and then click Exchange
Management Shell.
2. At the MSH prompt, change to the following folder:
Drive_Letter:\Program Files\Microsoft Exchange Server\Scripts
3. Run the following command:
MoveAllReplicas.ps1 Server Source_Server_Name -NewServer
Target_Server_Name
Note The source server must be an Exchange 2007 mailbox server
that contains a public folder store. The target server must be an
Exchange server that contains a public folder store.


Isn't there a way to remove it without having another exchange server?
Where are the replicas configured - and why does it do it without ever
asking you about it?

Sorry for being so frustrated but this is a nightmare. I'm sure
programmers love the new powershell but this is not intuitive at all -
all previous versions were intuitive. There is always learning but
since this isn't intuitive like the last 3 versions, it is most
unsettling.









.

Relevant Pages

  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.connectivity)
  • Exchange 2003 SP1 periodicaly losses connection to active directory for about 30 minutes
    ... We have active directory in two servers but the mail server fails to ... the promotion of the server to active directory the exchange was up. ... After a Domain Controller is promoted to a Global Catalog, ...
    (microsoft.public.exchange.misc)
  • Re: LDAP Bind Unsuccessful
    ... We have a similar problem with Exchange 2003 and two DC servers 2003. ... After a Domain Controller is promoted to a Global Catalog, ... server that is designated to be a Global Catalog Server but did ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Exchange Service Pack 1 Install fails
    ... I have a Small Business Server 2003 set up. ... Exchange SP1 resolves. ... before installing this Microsoft Exchange Server Service Pack. ...
    (microsoft.public.exchange.setup)