Hi,

We have Exchange 2008 and it has been running without problem for weeks. In
the last few days it has been prompting all local users for their domain
logon credentials every 5 minutes or so?

We do have a public ssl cert for OWA, do you think this might cause this
problem?

Please advise?

OS: Windows 2003 STD, Exchange STD SP2.

I got an Exchange server with problems, and a friend of mine told me all I
need is to redo the server and move the mailboxes back. He did all those
steps and he deleted the Exchange server account too, so he could not use the
/disasterrecovery option. What steps do you recommend to get this server back
online?

I have tried so far create an account with the same name and join the server
into the domain, no go. I was able to see the mailboxes in System Manager but
I could not connect from any client or OWA.

What I want right now, if remove all referrences to the old server and put a
new one with the same name just a different box.

Thanks in advance,

I just installed a certificate on an Exchange 2003 frontend server and I
would like to get the http url too redirect to the https url. I tried a few
different steps but still unsuccessful. Any help would be appreciated.

Thanks

Hello,

I've never had need to do this before but a company we design web banners
for would like to have an e-mail sent to our e-mail servr, through our
e-mail server but using a widget on their web server where they host the web
site and the page the site is on.

I would like to restrict it as much as possible. I know the IP address of
their web server. We have both the sending e-mail address and receiving
e-mail address on our exchange 2007 server. They want to be able to send
through our web server as well.

Can someone help me out on what I can do to make this possible and what I
can do to make sure it is as secure as possible so I don't risk relaying
spam to other people through this web app?

Sorry for the double post - I originally posted this under exchange admin
but think it might be better under setup.

I have an Exchange 5.5 server with a small user base (approx 30). I've been
digging into the "Migrating from Exchange Server 5.5 to Exchange Server
2003" technet document. It seems to me that I might be able to simplify
this greatly by:

1. installing the Exchange Server 2003 in native mode, setting up
distribution lists, public folders, etc.
2. exporting the 5.5 mailboxes to .pst files (Looking at the current
resource usage, everybody is using less than 2G so I'm assume the 2G .pst
limit won't be exceeded.)
3. moving the users over to the Active Directory domain
4. setting up Outlook to use 2003
5. importing the .pst files into Exchange 2003

Comments / Suggestions?

Thanks.

After I install the first CAS server into an existing Exchange 2003
environment, will users who are access OWA have to type the URL for the CAS
server to access their mailbox if it's still sitting on an Exchange 2003 BE
server, or are they able to continue to use the existing Exchange 2003 FE
server to get to it. (I know that the CAS server has the /exchange URL for
mailboxes on the Exchange 2003 BE server, and the /owa url for mailboxes that
have been moved to the Exchange 2007 Mailbox server. What I want to know for
sure is whether or not users can continue logging on to OWA via the Exchange
2003 FE OWA server.

I received 4 "crt" files from Networksolutions after submitted CSR:
1. AddTrustExternalCARoot.crt
2. NetworkSolutions_CA.crt
3. Company.com.crt
4. UTNAddTrustServer_CA.crt
How to import them using Import-ExchangeCertificate? One at a time?
Please advice!
Thanks,
Roger

Here's the current architecture.

We have 2 Exchange 2007 Client Access Servers running on Windows 2008
64-bit.

We have 2 Exchange 2003 legacy front-end systems running on Windows
2003.

We have multiple Exchange 2003 back-end mailbox servers.

All servers reside on the same subnet and are local to each other.

Here's the issue:

Upon logging into OWA locally on the Client Access Servers, page
rendering is extremely slow and can take minutes to render the full
OWA interface completely. Transitioning between messages takes longer
than usual, etc. Using the same mailbox and logging into the Exchange
2003 legacy OWA site we don't experience any slowness, etc.

The interesting thing is this only occurs against ONE of our Exchange
2003 back-end servers. When we log into OWA with a mailbox on our
other Exchange 2003 mailbox back-ends, the interface is snappy and
renders quickly.

Hi!
We have an old environment with Exchange 2003 back-end and front-end
servers. We have now installed Exchange 2007 mailbox role using CCR on two
servers and CAS/HUB on two servers with network load balancer. When accessing
OWA the automatic redirect from directory Exchange to OWA fails. I can access
mailboxes on 2003 with the https://cas-server/exchange without any problems
and mailboxes on 2007 with https://cas-server/owa without any problem. But
the redirection from exchange to owa doesn’t work for mailboxes on 2007 so I
can't publish just one name through ISA Server. How can I get this
redirection to work? The IIS server is started on the 2007 CCR servers.

Regards,
Ulf

I have been trying to join Exchange Server 2003 into an existing Exchange
5.5. i have one all the necessary prerequisites, but when I got to Select a
server in an Exchange 5.5 Organisation page and typed in the name of the
Exchange 5.5 which I named Server01, the installation wizard says "setup has
detected the dispaly name of the organisation or one of the Exchange Ites in
your Organisation is greater than 64 characters or contains at least one of
the following invalid characters: ~`¬!"£$%%^&*()_=+/?|\,.<> (including a
leading or trainling space. To correct this problem, you must use the
Exchange 5.x Administration tool to change the display name of either the
organisation and/or the affected sites and then re-run the setup."
But I think is not applicable in my situation. The organisation...