RE: Friday funnies

[Paul Steele]

You're right, sorry everyone. Having a bad day. I guess I'm more of a
cat person!

-Original Message-
From: Dan Cooper [mailto:d...@180amsterdam.com] 
Sent: March-19-10 11:08 AM
To: MS-Exchange Admin Issues
Subject: RE: Friday funnies

thats a little harsh, this is one of the best lists I have seen for
exchange issues. and every now and then some quality humour.  Though I
must say, this particular friday funny is not of the highest quality
ever...apologies Steve, but it did raise a chuckle.

If you need help working out filters there is probably something in this
list, unless you have left already!




____
From: Paul Steele [paul.ste...@acadiau.ca]
Sent: Friday, March 19, 2010 2:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Friday funnies

I don't need more junk mail. This list is definitely not for me...

From: Ellis, John P. [mailto:johnel...@wirral.gov.uk]
Sent: March-19-10 10:03 AM
To: MS-Exchange Admin Issues
Subject: RE: Friday funnies

its Exchanging air.
A little bit off topic humour keeps us all amused. Unless you're
offended by dogs giving mouth to mouth,

John


From: Clayton Doige [mailto:clayton.do...@gmail.com]
Sent: 19 March 2010 12:39
To: MS-Exchange Admin Issues
Subject: Re: Friday funnies
The dog is also trained as an Exchange Admin On 19 March 2010 11:08,
Paul Steele mailto:paul.ste...@acadiau.ca>>
wrote:
I thought this list was for Microsoft Exchange discussion?

From: Steve Szabo [mailto:steve...@gmail.com<mailto:steve...@gmail.com>]
Sent: March-19-10 5:00 AM
To: MS-Exchange Admin Issues
Subject: OT: Friday funnies

New South Wales Ambulance Service introduces Trained Dogs to cut
costs

Breathe damn you...BREATHE !

[cid:6068BBB3D1DD464298569C46195B5BC2@owner7ec88e618]




\\Steve//









--
Regards,

Clayton
clay...@alsipius.com<mailto:clay...@alsipius.com>
http://alsipius.com

**

This email and any files transmitted with it are confidential and

intended solely for the use of the individual or entity to whom they

are addressed. If you have received this email in error please notify

the system manager.

This footnote also confirms that this email message has been swept by

MIMEsweeper for the presence of computer viruses.

www.clearswift.com<http://www.clearswift.com>

**


DISCLAIMER 3/19/2010

This communication is intended only for use by MS-Exchange Admin Issues.
It may contain confidential or privileged information. If you receive
this communication unintentionally, please inform us immediately. Thank
you. 180 has registered companies in the United States and in the
Netherlands. 180 Los Angeles LLC . (180) 1424 Second Street, Suite 200
and 300, Santa Monica, California 90401, is registered with the trade
register in the US in Delaware under file number 4260284 and the
corporation's FEIN is 20-5982098. 180 Amsterdam BV (180) Herengracht
506, 1017 CB, Amsterdam is registered with the trade register in the
Netherlands under number 34253037 and VAT number NL8161.54.673.B.01. The
content of this communications is not legally binding unless confirmed
by letter or telefax. Please note that 180 is neither liable for the
proper transmission nor for the complete transmission of the information
contained in this communication or for any delay in its receipt. Also
please note that the confidentiality of email communication is not
warranted. All services and other work provided by 180 are subject to
our general conditions (supplier terms and conditions). The conditions
are available for inspection at Herengracht 506, Amsterdam and at the
Chamber of Commerce in Amsterdam. If you wish to receive a hard copy of
these conditions, please send an e-mail with your address to
i...@180amsterdam.com <mailto:i...@180amsterdam.com> 

In the event you send to 180 any unsolicited ideas and/or materials
(whether consisting of texts, images, sounds, software, information or
otherwise) ("Materials") by e-mail or otherwise, 180 shall be entitled
to use, copy and/or commercially exploit such Materials to the fullest
extent, free of charge and 180 will not be bound by any confidentiality
obligation in respect thereof.

Backup Options for Exchange 2010

[Paul Steele]

We plan to upgrade our Exchange 2003 server this spring to Exchange
2010. We're still in the preliminary phases but one issue I've
encountered is that EMC has indicated they will not have a client module
for Networker (our backup software) until Q4 this year. I was wondering
if anyone else has deployed (or plan to) Exchange 2010 in a Networker
environment, and what alternatives there might be if we need to find an
interim solution until the Networker module is available. We've looked
at Microsoft's backup software but I'm not sure it would be suitable. 

 

Any suggestions would be appreciated.

 

RE: One email with multiple recipients, stuck in queue

[Paul Steele]

We've seen this sort of problem occur when one of the addresses in the
distribution list is invalid. Rather than just causing a single bounce
for the one message a bunch of messages end up in retry state in the
queue. We have to go in and clear the queue manually, and tell the user
which address is wrong. It may be some sort of local configuration
problem, and I'm hoping the problem will go away when we upgrade to
2010...

 

From: Robert Peterson [mailto:robert.peter...@prin.edu] 
Sent: April-15-10 1:48 PM
To: MS-Exchange Admin Issues
Subject: One email with multiple recipients, stuck in queue

 

Setup... Exchange 2003, front and backend servers, Outlook 2007 client.

 

I have a user who sent an email yesterday to one of his own Distribution
lists within Outlook 2007, about 22 members. In the evening he received
"Delivery Status Notification (Delay)" notices for each group of
recipients within the same domain, about 15 different domains, including
Hotmail, Gmail, along with others. 

 

Looking at the queue, each individual email for each domain is in retry
status, but won't deliver.   I have tried to force the connection with
no results. I sent a new email to one of the same domains and it went
through fine.  So I'm thinking there must be something about this
particular email. 

 

Anything particular I should look at, or should I just delete the
messages and ask him to send again?

 

Thanks,

Robert

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

I thought I would add a bit more info to Tammy's first question. Our two test 
servers are called EXCH2003 and EXCH2010. After the 2010 installation, two 
connectors were created and appear when using Exchange System Manager. In the 
First Routing Group (associated with EXCH2003), the new routing connector was 
called EXCH2003-EXCH2010. In the Exchange Routing Group (created by the 2010 
install), another connector was created called EXCH2010-EXCH2003. These 
connectors cannot be modified with Exchange System Manager (complains that 
version 8 is required). 

 

Our understanding is that the first connector controls mail going from EXCH2003 
to EXCH2010, while the second one controls mail from EXCH2010 to EXCH2003. They 
appear to configured properly, but obviously something isn't quite right. Email 
works from mailboxes on EXCH2003 to mailboxes on EXCH2003, from EXCH2010 to 
EXCH2010, and EXCH2010 to EXCH2003. However, EXCH2003 to EXCH2010 does not 
work, so our guess is that the EXCH2003-EXCH2010 connector is the one that is 
not working properly. If anyone has any suggestions on what to look for we 
would really appreciate it. We don't want to proceed with the production 
upgrade until we get all the details working in our test environment.

 

Thanks!

 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 2:56 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

The cover article in May's WindowsITPro covers Exchange 2003 to Exchange 2010 
migrations and covers everything that you have to set up for it to work 
properly. It'll be out next week.

 

(I should know, I wrote it.)

 

As a guess, without further information, I would guess that you do not have a 
bi-directional routing group connector or if you have one, it isn't properly 
configured (get-routinggroupconnector | fl ß from the Exchange Management 
Shell).

 

Insofar as your second issue - if you want to change the retry interval, that's 
fine. But I would consider this more of a postfix issue.

 

IMO, instead of returning a 450 error, postfix should be returning a 5xx error.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Tammy George [mailto:tammy.geo...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 1:36 PM
To: MS-Exchange Admin Issues
Subject: Two questions - Exchange 2003 & 2010

 

We are preparing to upgrade to Exchange 2010 from Exchange 2003.  We presently 
have a test environment setup.  Our 2003 test server is unable to send to our 
2010 server.  We can send from 2010 to 2003 and from 2010 to Internet addresses 
(i.e. non acadiau.ca addresses) but we're unable to send from Exchange 2003 to 
Exchange 2010 and from Exchange 2010 to other non-Exchange addresses within our 
domain (i.e. acadiau.ca addresses on other servers).  Exchange 2010 appears to 
be trying to deliver them locally.   Any pointers?   Everything appears to be 
configured properly but obviously we've missed something.

 

Also - our Exchange 2003 server occasionally gets tied up trying to deliver 
messages to domains that are registered but their DNS servers aren't answering 
to accept email (1800thriller.com just this afternoon for example).  Our 
Exchange 2003 server is configured to send through a Postfix server before 
going on to the Internet.  Our Postfix server is sending the message back to 
Exchange with a 450 error.  Exchange retries 1 minute later.  And as is 
configured, this continues for 2 days until Exchange gives up (or if we delete 
before then).  This isn't usually a problem unless 3 or 4 outgoing emails get 
in this state at the same time then all outgoing email comes to a halt.  I 
previously read about this issue and the fix I found mentions to not make the 
change unless Microsoft Support Services advises (the only URL I can find this 
aft is 
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24771370.html.
  it references Exchange 2007 but it's the same sort of thing for 2003)
We've been addressing this issue as it arises and we're hoping it'll disappear 
once we migrate to 2010.  I was hoping someone on this list might know the 
answer to that for sure.  

 

Huge thanks in advance & my apologies if these questions have already been 
asked & answered.

 

 

 

-- 

Tammy George

Sr. Systems Operator

Technology Services

Acadia University

tel: (902) 585-1158

fax: (902) 585-1066

 

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

We did run the command but everything looked ok, at least to us. The 
Get-receiveconnector has so much information it's not entirely easy to 
decipher, this being our first Exchange 2010 server. 

 

I think I have narrowed down the problem though. When I tried a manual mail 
session using "telnet exch2010 25" from exch2003, when I give the "mail 
from:usern...@acadiau.ca", I get the error "530 5.7.1 Client was not 
authenticated". That gave me the clue I needed to at least find a workaround. 
During the 2010 install, a Receive connector was created in the Server 
Configuration Hub Transport section for handling mail coming from EXCH2003. I 
disabled that connector so that mail coming from exch2003 would arrive using 
the SMTP connector I had created for mail coming from the Internet. Since that 
one had no authentication requirments that solved the connectivity problem for 
mail coming from exch2003.

 

That brings up another question. Should there be a separate Receive Connector 
for Exch2003 to Exch2010 mail (one which enforces authentication) and another 
one for normal (Internet) mail?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 8:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That's why I suggested you execute this command, and examine all the 
information output from it:

 

get-routinggroupconnector | fl

 

This is a PowerShell command, you'll execute it from the Exchange Management 
Shell on the 2010 server.

 

You might want to do the same thing with "get-receiveconnector | fl" and 
"get-sendconnector | fl".

 

While there are another potential knobs and switches involved, with the output 
from those 3 commands we will likely be able to identify any culprit or provide 
an additional lead to continue the investigation.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 7:00 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I thought I would add a bit more info to Tammy's first question. Our two test 
servers are called EXCH2003 and EXCH2010. After the 2010 installation, two 
connectors were created and appear when using Exchange System Manager. In the 
First Routing Group (associated with EXCH2003), the new routing connector was 
called EXCH2003-EXCH2010. In the Exchange Routing Group (created by the 2010 
install), another connector was created called EXCH2010-EXCH2003. These 
connectors cannot be modified with Exchange System Manager (complains that 
version 8 is required). 

 

Our understanding is that the first connector controls mail going from EXCH2003 
to EXCH2010, while the second one controls mail from EXCH2010 to EXCH2003. They 
appear to configured properly, but obviously something isn't quite right. Email 
works from mailboxes on EXCH2003 to mailboxes on EXCH2003, from EXCH2010 to 
EXCH2010, and EXCH2010 to EXCH2003. However, EXCH2003 to EXCH2010 does not 
work, so our guess is that the EXCH2003-EXCH2010 connector is the one that is 
not working properly. If anyone has any suggestions on what to look for we 
would really appreciate it. We don't want to proceed with the production 
upgrade until we get all the details working in our test environment.

 

Thanks!

 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 2:56 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

The cover article in May's WindowsITPro covers Exchange 2003 to Exchange 2010 
migrations and covers everything that you have to set up for it to work 
properly. It'll be out next week.

 

(I should know, I wrote it.)

 

As a guess, without further information, I would guess that you do not have a 
bi-directional routing group connector or if you have one, it isn't properly 
configured (get-routinggroupconnector | fl ß from the Exchange Management 
Shell).

 

Insofar as your second issue - if you want to change the retry interval, that's 
fine. But I would consider this more of a postfix issue.

 

IMO, instead of returning a 450 error, postfix should be returning a 5xx error.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Tammy George [mailto:tammy.geo...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 1:36 PM
To: MS-Exchange Admin Issues
Subject: Two questions - Exchange 2003 & 2010

 

We are preparing to upgrade to Exchange 2010 from Exchange 2003.  We presently 
have a test environment setup.  Our 2003 test server is unable to send to our 
2010 server.  We can send from 2010 to 2003 and from 2010 to Internet addresses 
(i.e. non acadiau.ca addresses) but we're unable to send from Exchange 2003 to 
Exchange 2010 and from

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

I spoke too soon. The change allowed a manual telnet session to work, but mail 
initiated from Outlook still gets hung up.  Does Exchange use standard 
SMTP/port 25 protocol for inter-Exchange email transfers, or does it use 
something different?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: April-21-10 9:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

We did run the command but everything looked ok, at least to us. The 
Get-receiveconnector has so much information it's not entirely easy to 
decipher, this being our first Exchange 2010 server. 

 

I think I have narrowed down the problem though. When I tried a manual mail 
session using "telnet exch2010 25" from exch2003, when I give the "mail 
from:usern...@acadiau.ca", I get the error "530 5.7.1 Client was not 
authenticated". That gave me the clue I needed to at least find a workaround. 
During the 2010 install, a Receive connector was created in the Server 
Configuration Hub Transport section for handling mail coming from EXCH2003. I 
disabled that connector so that mail coming from exch2003 would arrive using 
the SMTP connector I had created for mail coming from the Internet. Since that 
one had no authentication requirments that solved the connectivity problem for 
mail coming from exch2003.

 

That brings up another question. Should there be a separate Receive Connector 
for Exch2003 to Exch2010 mail (one which enforces authentication) and another 
one for normal (Internet) mail?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 8:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That's why I suggested you execute this command, and examine all the 
information output from it:

 

get-routinggroupconnector | fl

 

This is a PowerShell command, you'll execute it from the Exchange Management 
Shell on the 2010 server.

 

You might want to do the same thing with "get-receiveconnector | fl" and 
"get-sendconnector | fl".

 

While there are another potential knobs and switches involved, with the output 
from those 3 commands we will likely be able to identify any culprit or provide 
an additional lead to continue the investigation.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 7:00 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I thought I would add a bit more info to Tammy's first question. Our two test 
servers are called EXCH2003 and EXCH2010. After the 2010 installation, two 
connectors were created and appear when using Exchange System Manager. In the 
First Routing Group (associated with EXCH2003), the new routing connector was 
called EXCH2003-EXCH2010. In the Exchange Routing Group (created by the 2010 
install), another connector was created called EXCH2010-EXCH2003. These 
connectors cannot be modified with Exchange System Manager (complains that 
version 8 is required). 

 

Our understanding is that the first connector controls mail going from EXCH2003 
to EXCH2010, while the second one controls mail from EXCH2010 to EXCH2003. They 
appear to configured properly, but obviously something isn't quite right. Email 
works from mailboxes on EXCH2003 to mailboxes on EXCH2003, from EXCH2010 to 
EXCH2010, and EXCH2010 to EXCH2003. However, EXCH2003 to EXCH2010 does not 
work, so our guess is that the EXCH2003-EXCH2010 connector is the one that is 
not working properly. If anyone has any suggestions on what to look for we 
would really appreciate it. We don't want to proceed with the production 
upgrade until we get all the details working in our test environment.

 

Thanks!

 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 2:56 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

The cover article in May's WindowsITPro covers Exchange 2003 to Exchange 2010 
migrations and covers everything that you have to set up for it to work 
properly. It'll be out next week.

 

(I should know, I wrote it.)

 

As a guess, without further information, I would guess that you do not have a 
bi-directional routing group connector or if you have one, it isn't properly 
configured (get-routinggroupconnector | fl ß from the Exchange Management 
Shell).

 

Insofar as your second issue - if you want to change the retry interval, that's 
fine. But I would consider this more of a postfix issue.

 

IMO, instead of returning a 450 error, postfix should be returning a 5xx error.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Tammy George [mailto:tammy.geo...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 1:36 PM
To: MS-Excha

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

Unfortunately there seems to be some other issue. We simply can't get mail 
flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication 
issue since the Public Folders aren't replicating either. The various settings 
in the default receive connector look correct. I've verified that port 25 on 
EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on 
the various post-installations steps that should be performed and we've 
completed all of them. We may redo our test installation and see if we have 
better results. I guess this is why we set up test environments before tackling 
the real thing...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 10:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Well, you've identified the problem.

 

You shouldn't have disabled the default receive connector. If you take a look 
at it, you'll see on the "Permission Groups" tab, that "Legacy Exchange 
Servers" is one of the options.

 

Exchange servers speak to each other using a number of extensions to the SMTP 
protocol. Those extensions are only allowed when you enable the permissions. 
The default receive connector allows those permissions from Exchange servers 
(2007/2010) and legacy Exchange servers (2003).

 

However, the Internet receive connector should only enable "anonymous".

 

Generally speaking, most people just enable the "anonymous" permissions on the 
default receive connector so they can get by with a single connector.

 

And to answer your other question - Outlook and Exchange preferentially 
communicate using MAPI, not SMTP.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 8:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I spoke too soon. The change allowed a manual telnet session to work, but mail 
initiated from Outlook still gets hung up.  Does Exchange use standard 
SMTP/port 25 protocol for inter-Exchange email transfers, or does it use 
something different?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: April-21-10 9:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

We did run the command but everything looked ok, at least to us. The 
Get-receiveconnector has so much information it's not entirely easy to 
decipher, this being our first Exchange 2010 server. 

 

I think I have narrowed down the problem though. When I tried a manual mail 
session using "telnet exch2010 25" from exch2003, when I give the "mail 
from:usern...@acadiau.ca", I get the error "530 5.7.1 Client was not 
authenticated". That gave me the clue I needed to at least find a workaround. 
During the 2010 install, a Receive connector was created in the Server 
Configuration Hub Transport section for handling mail coming from EXCH2003. I 
disabled that connector so that mail coming from exch2003 would arrive using 
the SMTP connector I had created for mail coming from the Internet. Since that 
one had no authentication requirments that solved the connectivity problem for 
mail coming from exch2003.

 

That brings up another question. Should there be a separate Receive Connector 
for Exch2003 to Exch2010 mail (one which enforces authentication) and another 
one for normal (Internet) mail?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 8:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That's why I suggested you execute this command, and examine all the 
information output from it:

 

get-routinggroupconnector | fl

 

This is a PowerShell command, you'll execute it from the Exchange Management 
Shell on the 2010 server.

 

You might want to do the same thing with "get-receiveconnector | fl" and 
"get-sendconnector | fl".

 

While there are another potential knobs and switches involved, with the output 
from those 3 commands we will likely be able to identify any culprit or provide 
an additional lead to continue the investigation.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 7:00 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I thought I would add a bit more info to Tammy's first question. Our two test 
servers are called EXCH2003 and EXCH2010. After the 2010 installation, two 
connectors were created and appear when using Exchange System Manager. In the 
First Routing Group (associated with EXCH2003), the new routing connector was 
called EXCH2003-EXCH2010. In the E

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

That revealed that puzzle. Mail destined to Exch2010 was being routed up to our 
Unix smart host. I thought that Exchange would first check to see if the 
recipient email address was present in Active Directory and route to the 
appropriate Exchange server before sending the mail to the smart host. I 
obviously have more reading to do. It's difficult when our single Exchange 2003 
server was installed 7 years ago and you sort of forget how everything all 
works!

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 2:32 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

You can enable protocol logging on the Exchange 2003 server and 
receive-connector logging on the Exchange 2010 server (connection logging is on 
by default).

 

You can see from those logs why communication is failing.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 1:30 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Unfortunately there seems to be some other issue. We simply can't get mail 
flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication 
issue since the Public Folders aren't replicating either. The various settings 
in the default receive connector look correct. I've verified that port 25 on 
EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on 
the various post-installations steps that should be performed and we've 
completed all of them. We may redo our test installation and see if we have 
better results. I guess this is why we set up test environments before tackling 
the real thing...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 10:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Well, you've identified the problem.

 

You shouldn't have disabled the default receive connector. If you take a look 
at it, you'll see on the "Permission Groups" tab, that "Legacy Exchange 
Servers" is one of the options.

 

Exchange servers speak to each other using a number of extensions to the SMTP 
protocol. Those extensions are only allowed when you enable the permissions. 
The default receive connector allows those permissions from Exchange servers 
(2007/2010) and legacy Exchange servers (2003).

 

However, the Internet receive connector should only enable "anonymous".

 

Generally speaking, most people just enable the "anonymous" permissions on the 
default receive connector so they can get by with a single connector.

 

And to answer your other question - Outlook and Exchange preferentially 
communicate using MAPI, not SMTP.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 8:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I spoke too soon. The change allowed a manual telnet session to work, but mail 
initiated from Outlook still gets hung up.  Does Exchange use standard 
SMTP/port 25 protocol for inter-Exchange email transfers, or does it use 
something different?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: April-21-10 9:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

We did run the command but everything looked ok, at least to us. The 
Get-receiveconnector has so much information it's not entirely easy to 
decipher, this being our first Exchange 2010 server. 

 

I think I have narrowed down the problem though. When I tried a manual mail 
session using "telnet exch2010 25" from exch2003, when I give the "mail 
from:usern...@acadiau.ca", I get the error "530 5.7.1 Client was not 
authenticated". That gave me the clue I needed to at least find a workaround. 
During the 2010 install, a Receive connector was created in the Server 
Configuration Hub Transport section for handling mail coming from EXCH2003. I 
disabled that connector so that mail coming from exch2003 would arrive using 
the SMTP connector I had created for mail coming from the Internet. Since that 
one had no authentication requirments that solved the connectivity problem for 
mail coming from exch2003.

 

That brings up another question. Should there be a separate Receive Connector 
for Exch2003 to Exch2010 mail (one which enforces authentication) and another 
one for normal (Internet) mail?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 8:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That's why I suggested you execute this command, and examine all the 
information output 

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

Thanks for all your help. I must admit that I find the configuration of the 
various connectors a bit confusing. I know that it's really not that 
complicated, but trying to find documentation that explains how to set up 
something for our simple environment is not always easy. Most examples assume a 
more complex setup. I haven't come across anything that describes an 
environment with staff on an Exchange server, students on a Unix mail server, 
all with a company MX server on Unix. We want st...@acadiau.ca to go to 
Exchange 2010 server and stud...@acadiau.ca to go our Unix mail server. We have 
this working with our existing Exchange 2003 environment, but I haven't quite 
figured out all the Exchange 2010 settings to accomplish the same thing. I 
think I'm getting close though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 3:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Depends on where you have smarthost configured.

 

If it's on a smtp connector, that would be the proper behavior (but even that 
can be overridden if you've specified a masquerade host).

 

If it's on the default smtp virtual server, that overrides everything.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 2:51 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That revealed that puzzle. Mail destined to Exch2010 was being routed up to our 
Unix smart host. I thought that Exchange would first check to see if the 
recipient email address was present in Active Directory and route to the 
appropriate Exchange server before sending the mail to the smart host. I 
obviously have more reading to do. It's difficult when our single Exchange 2003 
server was installed 7 years ago and you sort of forget how everything all 
works!

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 2:32 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

You can enable protocol logging on the Exchange 2003 server and 
receive-connector logging on the Exchange 2010 server (connection logging is on 
by default).

 

You can see from those logs why communication is failing.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 1:30 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Unfortunately there seems to be some other issue. We simply can't get mail 
flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication 
issue since the Public Folders aren't replicating either. The various settings 
in the default receive connector look correct. I've verified that port 25 on 
EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on 
the various post-installations steps that should be performed and we've 
completed all of them. We may redo our test installation and see if we have 
better results. I guess this is why we set up test environments before tackling 
the real thing...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 10:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Well, you've identified the problem.

 

You shouldn't have disabled the default receive connector. If you take a look 
at it, you'll see on the "Permission Groups" tab, that "Legacy Exchange 
Servers" is one of the options.

 

Exchange servers speak to each other using a number of extensions to the SMTP 
protocol. Those extensions are only allowed when you enable the permissions. 
The default receive connector allows those permissions from Exchange servers 
(2007/2010) and legacy Exchange servers (2003).

 

However, the Internet receive connector should only enable "anonymous".

 

Generally speaking, most people just enable the "anonymous" permissions on the 
default receive connector so they can get by with a single connector.

 

And to answer your other question - Outlook and Exchange preferentially 
communicate using MAPI, not SMTP.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, April 21, 2010 8:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

I spoke too soon. The change allowed a manual telnet session to work, but mail 
initiated from Outlook still gets hung up.  Does Exchange use standard 
SMTP/port 25 protocol for inter-Exchange email transfers, or does it use 
something different?

 

From: Paul Steele [mailto:paul.st

RE: Two questions - Exchange 2003 & 2010

[Paul Steele]

Got it working. Just had to change the accepted domain "acadiau.ca" from 
authoritative  to Internal Relay. Everything is starting to make sense!

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 7:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Depends on how you have it set up today.

 

SOMEONE has to be authoritative resource for the domain's email addresses. 
Every version of Exchange since Exchange 5.5, including 2010, supports sharing 
SMTP address spaces. You can configure it the same in 2010 as you did in 2003. 
The only difference is instead of a custom recipient policy, you have a custom 
accepted domain, and (optionally) a custom send connector. Same concept, 
different names.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 6:22 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Thanks for all your help. I must admit that I find the configuration of the 
various connectors a bit confusing. I know that it's really not that 
complicated, but trying to find documentation that explains how to set up 
something for our simple environment is not always easy. Most examples assume a 
more complex setup. I haven't come across anything that describes an 
environment with staff on an Exchange server, students on a Unix mail server, 
all with a company MX server on Unix. We want st...@acadiau.ca to go to 
Exchange 2010 server and stud...@acadiau.ca to go our Unix mail server. We have 
this working with our existing Exchange 2003 environment, but I haven't quite 
figured out all the Exchange 2010 settings to accomplish the same thing. I 
think I'm getting close though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 3:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Depends on where you have smarthost configured.

 

If it's on a smtp connector, that would be the proper behavior (but even that 
can be overridden if you've specified a masquerade host).

 

If it's on the default smtp virtual server, that overrides everything.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 2:51 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

That revealed that puzzle. Mail destined to Exch2010 was being routed up to our 
Unix smart host. I thought that Exchange would first check to see if the 
recipient email address was present in Active Directory and route to the 
appropriate Exchange server before sending the mail to the smart host. I 
obviously have more reading to do. It's difficult when our single Exchange 2003 
server was installed 7 years ago and you sort of forget how everything all 
works!

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-22-10 2:32 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

You can enable protocol logging on the Exchange 2003 server and 
receive-connector logging on the Exchange 2010 server (connection logging is on 
by default).

 

You can see from those logs why communication is failing.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, April 22, 2010 1:30 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Unfortunately there seems to be some other issue. We simply can't get mail 
flowing from EXCH2003 to EXCH2010. It's obviously some sort of communication 
issue since the Public Folders aren't replicating either. The various settings 
in the default receive connector look correct. I've verified that port 25 on 
EXCH2010 is open to EXCH2003, but still no go. I've read some good documents on 
the various post-installations steps that should be performed and we've 
completed all of them. We may redo our test installation and see if we have 
better results. I guess this is why we set up test environments before tackling 
the real thing...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: April-21-10 10:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Two questions - Exchange 2003 & 2010

 

Well, you've identified the problem.

 

You shouldn't have disabled the default receive connector. If you take a look 
at it, you'll see on the "Permission Groups" tab, that "Legacy Exchange 
Servers" is one of the options.

 

Exchange servers speak to each other using a number of extensions to the SMTP 
protocol. Those extensions are only allowed when you 

Exchange 2003 to 2010 issues

[Paul Steele]

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchange
2010. We've done various test installs in our  lab and thought we had
everything figured out. Unfortunately we're having mail delivery
problems after completing the install. The actual installation went
without problems. We have a shared address space, with some users on our
Exchange server and some on a Unix host. The biggest issue we're having
is sending to users who are not on our Exchange server. We've set the
Accepted Domains for "acadiau.ca" to Internal Relay, but when we try to
send to usern...@acadiau.ca that does not exist in the Exchange name
space, the message bounces (it never makes it to our Unix smart host).
We've compared things with our test servers and everything looks
correct. At this point we've very confused what we're doing wrong. If
anyone has a suggestion what to look for we really appreciate it.

 

RE: Exchange 2003 to 2010 issues

[Paul Steele]

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Did you create a send-connector to forward the scoped domain to the Unix
host?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 11:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 to 2010 issues

 

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchange
2010. We've done various test installs in our  lab and thought we had
everything figured out. Unfortunately we're having mail delivery
problems after completing the install. The actual installation went
without problems. We have a shared address space, with some users on our
Exchange server and some on a Unix host. The biggest issue we're having
is sending to users who are not on our Exchange server. We've set the
Accepted Domains for "acadiau.ca" to Internal Relay, but when we try to
send to usern...@acadiau.ca that does not exist in the Exchange name
space, the message bounces (it never makes it to our Unix smart host).
We've compared things with our test servers and everything looks
correct. At this point we've very confused what we're doing wrong. If
anyone has a suggestion what to look for we really appreciate it.

 

RE: Exchange 2003 to 2010 issues

[Paul Steele]

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since the 2010 install is a problem
with Public folders. When I try to look at the folder in System Manager
on Exch2003, I get the error 

 

"The HTTP service used by Public Folders is not available, possible
causes are that Public stores are not mounted and the Information Store
service is not running."

 

I'm getting lots of google hits for this error but none specifically
relating to an Exchange 2010 upgrade. The folders show up fine in
Outlook, but not in OWA or System Manager. This issue did not come up in
our test lab.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 1:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That would tend to indicate that the mail is being routed through the
Exchange 2003 server and you don't have  a properly scoped
send-connector on the 2010 side.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Did you create a send-connector to forward the scoped domain to the Unix
host?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 11:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 to 2010 issues

 

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchange
2010. We've done various test installs in our  lab and thought we had
everything figured out. Unfortunately we're having mail delivery
problems after completing the install. The actual installation went
without problems. We have a shared address space, with some users on our
Exchange server and some on a Unix host. The biggest issue we're having
is sending to users who are not on our Exchange server. We've set the
Accepted Domains for "acadiau.ca" to Internal Relay, but when we try to
send to usern...@acadiau.ca that does not exist in the Exchange name
space, the message bounces (it never makes it to our Unix smart host).
We've compared things with our test servers and everything looks
correct. At this point we've very confused what we're doing wrong. If
anyone has a suggestion what to look for we really appreciate it.

 

RE: Exchange 2003 to 2010 issues

[Paul Steele]

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and I haven't installed a UC cert on 2010 yet. I'm reading
everything I can find on the topic before tackling the certificate
install. After the way things went today I doubt that things will go
problem free...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 2:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

How have you configured namespace sharing, i.e., namespaces vs. SSL
certificates on the two servers?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since the 2010 install is a problem
with Public folders. When I try to look at the folder in System Manager
on Exch2003, I get the error 

 

"The HTTP service used by Public Folders is not available, possible
causes are that Public stores are not mounted and the Information Store
service is not running."

 

I'm getting lots of google hits for this error but none specifically
relating to an Exchange 2010 upgrade. The folders show up fine in
Outlook, but not in OWA or System Manager. This issue did not come up in
our test lab.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 1:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That would tend to indicate that the mail is being routed through the
Exchange 2003 server and you don't have  a properly scoped
send-connector on the 2010 side.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Did you create a send-connector to forward the scoped domain to the Unix
host?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 11:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 to 2010 issues

 

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchange
2010. We've done various test installs in our  lab and thought we had
everything figured out. Unfortunately we're having mail delivery
problems after completing the install. The actual installation went
without problems. We have a shared address space, with some users on our
Exchange server and some on a Unix host. The biggest issue we're having
is sending to users who are not on our Exchange server. We've set the
Accepted Domains for "acadiau.ca" to Internal Relay, but when we try to
send to usern...@acadiau.ca that does not exist in the Exchange name
space, the message bounces (it never makes it to our Unix smart host).
We've compared things with our test servers and everything looks
correct. At this point we've very confused what we're doing wrong. If
anyone has a suggestion what to look for we really appreciate it.

 

RE: I'm getting conflicting information...

[Paul Steele]

You can definitely have all components on a single server. I just did
the same upgrade today after several weeks of testing in the lab.

 

From: Reimer, Mark [mailto:mark.rei...@prairie.edu] 
Sent: May-03-10 5:59 PM
To: MS-Exchange Admin Issues
Subject: I'm getting conflicting information...

 

We are moving from Exchange 2003 to Exchange 2010. We have one physical
server running Exchange 2003, and I was planning on one physical,
dedicated (i.e. nothing virtual) server for Exchange 2010.

 

I've heard a report that I can put all "parts" of Exchange 2010 on a
physical box except Transport Server. It wants/needs to be on a separate
box.

 

Can somebody give me guidance?

 

We have only about 350 hundred users, and many of these use OWA, and
only occasionally. We have about 100 that use Outlook, and most don't do
a lot of emailing. All this to say, there isn't a whole lot of email
traffic that the server would have to actively, concurrently handle.

 

Thanks in advance.

 

Mark Reimer,  A+, MCSA

Windows Servers & Networking

Prairie Bible Institute

Box 4000

Three Hills, AB  T0M-2N0

Canada

Tel: 403-443-5511, Ext. 3476

Fax: 403-443-5540

Email: mark.rei...@prairie.edu

www.prairie.edu

 

 

RE: Exchange 2003 to 2010 issues

[Paul Steele]

I've just discovered that I made a mistake during the installation
process. In the install wizard when it asks for the Internet facing name
for the server I put in smtp.acadiau.ca instead of exchange.acadiau.ca.
I'm not exactly sure what issues this mistake will cause, but it
definitely messes up the certificate installation process. I've looked
though the various dialogs to find out where I can change that setting
but it doesn't appear anywhere obvious. Is there a quick solution to
this mistake?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-03-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and I haven't installed a UC cert on 2010 yet. I'm reading
everything I can find on the topic before tackling the certificate
install. After the way things went today I doubt that things will go
problem free...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 2:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

How have you configured namespace sharing, i.e., namespaces vs. SSL
certificates on the two servers?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since the 2010 install is a problem
with Public folders. When I try to look at the folder in System Manager
on Exch2003, I get the error 

 

"The HTTP service used by Public Folders is not available, possible
causes are that Public stores are not mounted and the Information Store
service is not running."

 

I'm getting lots of google hits for this error but none specifically
relating to an Exchange 2010 upgrade. The folders show up fine in
Outlook, but not in OWA or System Manager. This issue did not come up in
our test lab.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 1:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That would tend to indicate that the mail is being routed through the
Exchange 2003 server and you don't have  a properly scoped
send-connector on the 2010 side.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Did you create a send-connector to forward the scoped domain to the Unix
host?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 11:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 to 2010 issues

 

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchange
2010. We've done various test installs in our  lab and thought we had
everything figured out. Unfortunately we're having mail delivery
problems after completing the install. The actual installation went
without problems. We have a shared address space, with some users on our
Exchange server and some on a Unix host. The biggest issue we're having
is sending to users who are not on our Exchange server. We've set the
Accepted Domains for "acadiau.ca" to Internal Relay, but when we try to
send to usern...@acadiau.ca that does not exist in the Exchange name
space, the message bounces (it never makes it to our Unix smart host).
We've compared things with our test servers and everything looks
correct. At this point we've very confused what we're doing wrong. If
anyone has a suggestion what to look for we really appreciate it.

 

RE: Exchange 2003 to 2010 issues

[Paul Steele]

I'm glad other people make mistakes too! :)

 

From: John Bowles [mailto:john.bow...@wlkmmas.org] 
Sent: May-04-10 3:32 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

This sounds awfully familiar ;-)

 

 

John Bowles 

 



From: Michael B. Smith [mich...@smithcons.com]
Sent: Tuesday, May 04, 2010 1:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

You will have to edit the ExternalURLs on all the Exchange virtual
directories.

 

Personally, I find this easier to do via EMS; but most of them can be
edited on the Server Configuration -> Client Access tabs.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 04, 2010 1:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

I've just discovered that I made a mistake during the installation
process. In the install wizard when it asks for the Internet facing name
for the server I put in smtp.acadiau.ca instead of exchange.acadiau.ca.
I'm not exactly sure what issues this mistake will cause, but it
definitely messes up the certificate installation process. I've looked
though the various dialogs to find out where I can change that setting
but it doesn't appear anywhere obvious. Is there a quick solution to
this mistake?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-03-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and I haven't installed a UC cert on 2010 yet. I'm reading
everything I can find on the topic before tackling the certificate
install. After the way things went today I doubt that things will go
problem free...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 2:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

How have you configured namespace sharing, i.e., namespaces vs. SSL
certificates on the two servers?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since the 2010 install is a problem
with Public folders. When I try to look at the folder in System Manager
on Exch2003, I get the error 

 

"The HTTP service used by Public Folders is not available, possible
causes are that Public stores are not mounted and the Information Store
service is not running."

 

I'm getting lots of google hits for this error but none specifically
relating to an Exchange 2010 upgrade. The folders show up fine in
Outlook, but not in OWA or System Manager. This issue did not come up in
our test lab.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 1:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That would tend to indicate that the mail is being routed through the
Exchange 2003 server and you don't have  a properly scoped
send-connector on the 2010 side.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 12:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Did you create a send-connector to forward the scoped domain to the Unix
host?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 11:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 to 2010 issues

 

We did as much testing as we could in our test lab, so we moved ahead
and installed our production Exchange 2010 server. The installation went
fine without any errors, but we're have delivery problems.

 

We've been preparing for a transition from Exchange 2003 to Exchan

RE: Exchange 2003 to 2010 issues

[Paul Steele]

Ok, I read your Windows IT Pro article, which was very good.
Unfortunately it didn't help and I'm officially *very* frustrated now.
After fiddling with send/receive connectors for last couple of days, I
still haven't gotten mail to flow within our new Exchange 2003/2010
organization properly. My ultimate goal is to have mail arrive on
Exchange 2010 and if necessary route mail to Exchange 2003 for mailboxes
that are still on the 2003 server. At this point no mail boxes have been
moved, although I've created a couple of test 2010 accounts. I can send
mail from 2003 users to 2010 mailboxes, and I can send mail externally
directly to 2003 mailboxes or 2010 mailboxes.  Unfortunately I cannot
get mail working from 2010 mailboxes to 2003 mailboxes, or externally
through the 2010 server to 2003 mailboxes. This issue is also causing
Public Folder Replication problems. 

 

After the 2010 install, two routing group connectors were created
(Exch2003-Exch2010 in the First Administrative Group side, and
Exch2010-Exch2003 in the newly created Exchange Admin Group). I haven't
modified those in any way. I also had an existing SMTP Connector with a
Unix smart host specified. The SMTP address space is * and applies to
the entire organization. This SMTP connector also appears on the 2010
server as a Send Connector. Finally, there is an SMTP Virtual Server
under the SMTP protocol section of the First Admin Group, with no smart
host specified.

 

After the installation, I created scoped Send Connector for SMTP/*,
specifying our Unix smart host and the 2010 server as the source server.
Under Accepted Domains, I added acadiau.ca as an Internal Relay. There
is also another SMTP Virtual Host in the Exchange Admin Group.

 

I actually had this all working in my ESXi test environment but due to
some disk issues I lost my VMs. I thought I remembered how I had
configured things but obviously I don't have a very good memory. I've
gotten totally confused about what send connectors, SMTP virtual hosts,
smart hosts, accepted domains, etc, etc, that I need. I think I've tried
every obvious configuration. I know it should be simple, but it seems to
have beaten me.

 

What am I missing?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-03-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and I haven't installed a UC cert on 2010 yet. I'm reading
everything I can find on the topic before tackling the certificate
install. After the way things went today I doubt that things will go
problem free...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 2:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

How have you configured namespace sharing, i.e., namespaces vs. SSL
certificates on the two servers?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since the 2010 install is a problem
with Public folders. When I try to look at the folder in System Manager
on Exch2003, I get the error 

 

"The HTTP service used by Public Folders is not available, possible
causes are that Public stores are not mounted and the Information Store
service is not running."

 

I'm getting lots of google hits for this error but none specifically
relating to an Exchange 2010 upgrade. The folders show up fine in
Outlook, but not in OWA or System Manager. This issue did not come up in
our test lab.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 1:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That would tend to indicate that the mail is being routed through the
Exchange 2003 server and you don't have  a properly scoped
send-connector on the 2010 side.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Yes, I had already done that. I'm a bit confused now though. I
stopped/started the SMTP virtual host (on the EXCH2003 side), and that
seemed to solve the problem. Things seem to be working so I guess
whatever was broken/stuck is ok. At least it's working...

RE: Exchange 2003 to 2010 issues

[Paul Steele]

Great idea. I did document some of the steps, but I tend to rely on memory. I 
came across two very good web articles on the upgrade process so it wasn't 
really necessary, but I should have paid more attention to the connector setup 
in my test environment...

-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: May-05-10 2:00 AM
To: MS-Exchange Admin Issues
Subject: Re: Exchange 2003 to 2010 issues

On Tue, May 4, 2010 at 14:27, Paul Steele  wrote:

> I actually had this all working in my ESXi test environment but due to 
> some disk issues I lost my VMs. I thought I remembered how I had 
> configured things but obviously I don’t have a very good memory. I’ve 
> gotten totally confused about what send connectors, SMTP virtual 
> hosts, smart hosts, accepted domains, etc, etc, that I need. I think 
> I’ve tried every obvious configuration. I know it should be simple, but it 
> seems to have beaten me.
>
>
>
> What am I missing?

Documentation of your original process?

Kurt

RE: Exchange 2003 to 2010 issues

[Paul Steele]

Thanks for the info. I'll have to take some time to digest your points.
One thing that jumps out though is your comment that there should only
be one Routing Group Connector. On the Exchange 2003 server, there are
actually two RGCs, one called EXCH2003-EXCH2010 in the First Admin
Group, and another called EXCH2010-EX2003 in the newly created Exchange
Admin Group. These have not been modified, in fact ESM doesn't let you,
complaining about version issues. Are these the RGs that you're
referring to? I assumed they are both needed since they were created as
part of the install process.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-05-10 11:25 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

I would need to see email headers, and/or smtp logs, to determine how
email is actually currently flowing.

 

It sounds to me as if either the RGC is incorrectly configured or you
have the send-connector on the 2010 side misconfigured.

 

Actual attempted email flow (message headers or smtp logs) from the 2003
-> 2010 and vice versa would identify the guilty party.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 04, 2010 5:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Ok, I read your Windows IT Pro article, which was very good.
Unfortunately it didn't help and I'm officially *very* frustrated now.
After fiddling with send/receive connectors for last couple of days, I
still haven't gotten mail to flow within our new Exchange 2003/2010
organization properly. My ultimate goal is to have mail arrive on
Exchange 2010 and if necessary route mail to Exchange 2003 for mailboxes
that are still on the 2003 server. At this point no mail boxes have been
moved, although I've created a couple of test 2010 accounts. I can send
mail from 2003 users to 2010 mailboxes, and I can send mail externally
directly to 2003 mailboxes or 2010 mailboxes.  Unfortunately I cannot
get mail working from 2010 mailboxes to 2003 mailboxes, or externally
through the 2010 server to 2003 mailboxes. This issue is also causing
Public Folder Replication problems. 

 

After the 2010 install, two routing group connectors were created
(Exch2003-Exch2010 in the First Administrative Group side, and
Exch2010-Exch2003 in the newly created Exchange Admin Group). I haven't
modified those in any way. I also had an existing SMTP Connector with a
Unix smart host specified. The SMTP address space is * and applies to
the entire organization. This SMTP connector also appears on the 2010
server as a Send Connector. Finally, there is an SMTP Virtual Server
under the SMTP protocol section of the First Admin Group, with no smart
host specified.

 

After the installation, I created scoped Send Connector for SMTP/*,
specifying our Unix smart host and the 2010 server as the source server.
Under Accepted Domains, I added acadiau.ca as an Internal Relay. There
is also another SMTP Virtual Host in the Exchange Admin Group.

 

I actually had this all working in my ESXi test environment but due to
some disk issues I lost my VMs. I thought I remembered how I had
configured things but obviously I don't have a very good memory. I've
gotten totally confused about what send connectors, SMTP virtual hosts,
smart hosts, accepted domains, etc, etc, that I need. I think I've tried
every obvious configuration. I know it should be simple, but it seems to
have beaten me.

 

What am I missing?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-03-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and I haven't installed a UC cert on 2010 yet. I'm reading
everything I can find on the topic before tackling the certificate
install. After the way things went today I doubt that things will go
problem free...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-03-10 2:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

How have you configured namespace sharing, i.e., namespaces vs. SSL
certificates on the two servers?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, May 03, 2010 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That might be it. I had sort of wanted to keep Exchange 2010 out of the
picture after this first phase since all the mail boxes are still on
Exchange 2003. I want to get backups, certificates, and other misc stuff
working on Exchange 2010 before moving mailboxes. 

 

One weird problem that has surfaced since

RE: Exchange 2003 to 2010 issues

[Paul Steele]

I *think* everything is working properly now. The only change I had to
make in the end was turn on Integrated Windows Authentication on the
Default SMTP Virtual Server.  Only anonymous was selected. Once I turned
that on mail started flowing from the Exchange 2010 server to Exchange
2003. I figured it was going to be something simple in the end...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-05-10 12:34 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

That's actually two sides of a single bidirectional RGC. It was created
by the installation process and IF you provided accurate info during the
installation process (i.e., you identified the proper legacy bridgehead
and the proper new bridgehead) it should be fine.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 05, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Thanks for the info. I'll have to take some time to digest your points.
One thing that jumps out though is your comment that there should only
be one Routing Group Connector. On the Exchange 2003 server, there are
actually two RGCs, one called EXCH2003-EXCH2010 in the First Admin
Group, and another called EXCH2010-EX2003 in the newly created Exchange
Admin Group. These have not been modified, in fact ESM doesn't let you,
complaining about version issues. Are these the RGs that you're
referring to? I assumed they are both needed since they were created as
part of the install process.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-05-10 11:25 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

I would need to see email headers, and/or smtp logs, to determine how
email is actually currently flowing.

 

It sounds to me as if either the RGC is incorrectly configured or you
have the send-connector on the 2010 side misconfigured.

 

Actual attempted email flow (message headers or smtp logs) from the 2003
-> 2010 and vice versa would identify the guilty party.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 04, 2010 5:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Ok, I read your Windows IT Pro article, which was very good.
Unfortunately it didn't help and I'm officially *very* frustrated now.
After fiddling with send/receive connectors for last couple of days, I
still haven't gotten mail to flow within our new Exchange 2003/2010
organization properly. My ultimate goal is to have mail arrive on
Exchange 2010 and if necessary route mail to Exchange 2003 for mailboxes
that are still on the 2003 server. At this point no mail boxes have been
moved, although I've created a couple of test 2010 accounts. I can send
mail from 2003 users to 2010 mailboxes, and I can send mail externally
directly to 2003 mailboxes or 2010 mailboxes.  Unfortunately I cannot
get mail working from 2010 mailboxes to 2003 mailboxes, or externally
through the 2010 server to 2003 mailboxes. This issue is also causing
Public Folder Replication problems. 

 

After the 2010 install, two routing group connectors were created
(Exch2003-Exch2010 in the First Administrative Group side, and
Exch2010-Exch2003 in the newly created Exchange Admin Group). I haven't
modified those in any way. I also had an existing SMTP Connector with a
Unix smart host specified. The SMTP address space is * and applies to
the entire organization. This SMTP connector also appears on the 2010
server as a Send Connector. Finally, there is an SMTP Virtual Server
under the SMTP protocol section of the First Admin Group, with no smart
host specified.

 

After the installation, I created scoped Send Connector for SMTP/*,
specifying our Unix smart host and the 2010 server as the source server.
Under Accepted Domains, I added acadiau.ca as an Internal Relay. There
is also another SMTP Virtual Host in the Exchange Admin Group.

 

I actually had this all working in my ESXi test environment but due to
some disk issues I lost my VMs. I thought I remembered how I had
configured things but obviously I don't have a very good memory. I've
gotten totally confused about what send connectors, SMTP virtual hosts,
smart hosts, accepted domains, etc, etc, that I need. I think I've tried
every obvious configuration. I know it should be simple, but it seems to
have beaten me.

 

What am I missing?

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-03-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 to 2010 issues

 

Mail delivery seems to be working properly now, so I think I've got the
various connectors configured properly. The 2003 server does not have a
certificate and

Exchange 2010 OWA bottom viewing pane

[Paul Steele]

*Why* did Microsoft remove the bottom viewing pane in Exchange 2010 OWA?
I never liked the right side pane in Outlook and fortunately Outlook
2010 still supports the bottom pane. It makes no sense that they would
support it in Outlook 2010 but not in Exchange 2010 OWA. I'm going to
have some upset users when we switch...

 

RE: Exchange 2010 OWA bottom viewing pane

[Paul Steele]

The article doesn't mention a release date. I had heard it's going to be
later in the fall. What's the current rumour?

 

From: Vandael Tim [mailto:tim.vand...@khlim.be] 
Sent: May-06-10 11:21 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 OWA bottom viewing pane

 

No you don't, just wait for SP1 J

See http://msexchangeteam.com/archive/2010/04/07/454533.aspx

 

 

 

Met vriendelijke groeten,

 

KHLim

Katholieke Hogeschool Limburg
Associatie KULeuven

http://www.khlim.be <http://www.khlim.be/> 

 

Tim Vandael

ICT Systeembeheerder

 

Campus Diepenbeek, Agoralaan gebouw B, bus 1, 3590 Diepenbeek

T +32 11 23 08 94 - F +32 11 23 07 89 - G +32 478 40 52 36

tim.vand...@khlim.be <mailto:tim.vand...@khlim.be> 

 

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: donderdag 6 mei 2010 16:14
To: MS-Exchange Admin Issues
Subject: Exchange 2010 OWA bottom viewing pane

 

*Why* did Microsoft remove the bottom viewing pane in Exchange 2010 OWA?
I never liked the right side pane in Outlook and fortunately Outlook
2010 still supports the bottom pane. It makes no sense that they would
support it in Outlook 2010 but not in Exchange 2010 OWA. I'm going to
have some upset users when we switch...

 

<>

Can Powershell do this?

[Paul Steele]

As we proceed with our Exchange 2010 migration, I discovered that some
mailboxes appear corrupted to powershell users, resulting in this error:

[PS] C:\>get-mailbox -identity rmurphy
WARNING: The object ad.acadiau.ca/academic/rmurphy has been corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression "rmurphy" isn't valid. Valid values are:
Strings that includes '@',
 where '@' cannot be the last character

After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it (e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in ADUC
under the Account tab, but with over 100 users in this state I'd like to
find a programmatic way of doing it. I could whip together a C# or VB
script to fix the problem, but I was wondering if this sort of thing
could be done in PowerShell. I'm still learning PS but from what I've
seen I think the answer is yes. Anyone PowerShell experts out there?

RE: Can Powershell do this?

[Paul Steele]

Looks similar to C# or VBscript. I'll have to track down the Quest
cmdlet stuff and give it a try...

 

From: KenM [mailto:kenmli...@gmail.com] 
Sent: May-06-10 9:37 PM
To: MS-Exchange Admin Issues
Subject: Re: Can Powershell do this?

 

I found some things wrong in my last post this is a little better.

 

$users - get-qaduser

Foreach ($user in $users){

$sam = $user.samaccountname

set-qaduser $sam -UserPrincipalName $...@domain.local

}

 

 

 



 

On Thu, May 6, 2010 at 7:26 PM, KenM  wrote:

You can do sometihng like this with the quest cmdlts

 

I dont know your environment so this may not work for you and may need a
little tweaking if you have over 1000 users in your domain. Can make it
more efficient with a LDAP filter looking for users without a UPN.

 

 

$user = get-qaduser

Foreach($user in $users) {set-qaduser $user.samaccountname
-Userprincipalname '$user.samaccountn...@domain.local'}

 

 



 

On Thu, May 6, 2010 at 7:06 PM, Paul Steele 
wrote:

As we proceed with our Exchange 2010 migration, I discovered
that some
mailboxes appear corrupted to powershell users, resulting in
this error:

[PS] C:\>get-mailbox -identity rmurphy
WARNING: The object ad.acadiau.ca/academic/rmurphy has been
corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression "rmurphy" isn't valid. Valid values
are:
Strings that includes '@',
 where '@' cannot be the last character

After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it
(e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily
in ADUC
under the Account tab, but with over 100 users in this state I'd
like to
find a programmatic way of doing it. I could whip together a C#
or VB
script to fix the problem, but I was wondering if this sort of
thing
could be done in PowerShell. I'm still learning PS but from what
I've
seen I think the answer is yes. Anyone PowerShell experts out
there?





 

 

RE: Can Powershell do this?

[Paul Steele]

It probably took me longer to figure out the PowerShell version than if
I had written it in C#, but it was more interesting!

 

$mailbox = get-mailbox | where {$_.userprincipalname -notlike "*...@*"}

foreach ($mailbox in $mailboxes) {set-mailbox $mailbox.name
-userprincipalname (($mailbox.name)+("@ad.acadiau.ca"))}

 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-06-10 10:56 PM
To: MS-Exchange Admin Issues
Subject: RE: Can Powershell do this?

 

C# is on the glide path from PowerShell.

 

You don't need the Quest cmdlets, you just need get-mailbox and
set-mailbox; which are built-in cmdlets for Exchange.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 06, 2010 9:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Can Powershell do this?

 

Looks similar to C# or VBscript. I'll have to track down the Quest
cmdlet stuff and give it a try...

 

From: KenM [mailto:kenmli...@gmail.com] 
Sent: May-06-10 9:37 PM
To: MS-Exchange Admin Issues
Subject: Re: Can Powershell do this?

 

I found some things wrong in my last post this is a little better.

 

$users - get-qaduser

Foreach ($user in $users){

$sam = $user.samaccountname

set-qaduser $sam -UserPrincipalName $...@domain.local

}

 

 

 



 

On Thu, May 6, 2010 at 7:26 PM, KenM  wrote:

You can do sometihng like this with the quest cmdlts

 

I dont know your environment so this may not work for you and may need a
little tweaking if you have over 1000 users in your domain. Can make it
more efficient with a LDAP filter looking for users without a UPN.

 

 

$user = get-qaduser

Foreach($user in $users) {set-qaduser $user.samaccountname
-Userprincipalname '$user.samaccountn...@domain.local'}

 

 



 

On Thu, May 6, 2010 at 7:06 PM, Paul Steele 
wrote:

As we proceed with our Exchange 2010 migration, I discovered
that some
mailboxes appear corrupted to powershell users, resulting in
this error:

[PS] C:\>get-mailbox -identity rmurphy
WARNING: The object ad.acadiau.ca/academic/rmurphy has been
corrupted,
and it's in an
inconsistent state. The following validation errors happened:
WARNING: Property expression "rmurphy" isn't valid. Valid values
are:
Strings that includes '@',
 where '@' cannot be the last character

After some digging I discovered that the AD account attribute
UserPrincipleName does not have a domain associated with it
(e.g.
'rmurphy' instead of 'rmur...@domain'). This can be fixed easily
in ADUC
under the Account tab, but with over 100 users in this state I'd
like to
find a programmatic way of doing it. I could whip together a C#
or VB
script to fix the problem, but I was wondering if this sort of
thing
could be done in PowerShell. I'm still learning PS but from what
I've
seen I think the answer is yes. Anyone PowerShell experts out
there?



 

 

RE: Can Powershell do this?

[Paul Steele]

Watch out for my typo! Here's the correct commands:

$mailboxes = get-mailbox | where {$_.userprincipalname -notlike "*...@*"}
foreach ($mailbox in $mailboxes) {set-mailbox $mailbox.name  -userprincipalname 
(($mailbox.name)+("@ad.acadiau.ca"))}

-Original Message-
From: Steven Peck [mailto:sep...@gmail.com] 
Sent: May-07-10 3:21 PM
To: MS-Exchange Admin Issues
Subject: Re: Can Powershell do this?

This was awesome.  We are just ramping up a migration from e2k3 to
e2k7 and just extended the schema.  While playing with the get0mailbox cmdlets 
I saw several of those errors.  Now I know the issue and fix.

Thanks.

On Fri, May 7, 2010 at 7:03 AM, Michael B. Smith  wrote:
> And the skill you acquired can be used in future Exchange 
> PowerShell'ing :-P
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> Consultant and Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: Paul Steele [mailto:paul.ste...@acadiau.ca]
> Sent: Friday, May 07, 2010 10:00 AM
>
> To: MS-Exchange Admin Issues
> Subject: RE: Can Powershell do this?
>
>
>
> It probably took me longer to figure out the PowerShell version than 
> if I had written it in C#, but it was more interesting!
>
>
>
> $mailbox = get-mailbox | where {$_.userprincipalname -notlike "*...@*"}
>
> foreach ($mailbox in $mailboxes) {set-mailbox $mailbox.name 
> -userprincipalname (($mailbox.name)+("@ad.acadiau.ca"))}
>
>
>
>
>
> From: Michael B. Smith [mailto:mich...@smithcons.com]
> Sent: May-06-10 10:56 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Can Powershell do this?
>
>
>
> C# is on the glide path from PowerShell.
>
>
>
> You don't need the Quest cmdlets, you just need get-mailbox and 
> set-mailbox; which are built-in cmdlets for Exchange.
>
>
>
> Regards,
>
>
>
> Michael B. Smith
>
> Consultant and Exchange MVP
>
> http://TheEssentialExchange.com
>
>
>
> From: Paul Steele [mailto:paul.ste...@acadiau.ca]
> Sent: Thursday, May 06, 2010 9:53 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Can Powershell do this?
>
>
>
> Looks similar to C# or VBscript. I'll have to track down the Quest 
> cmdlet stuff and give it a try...
>
>
>
> From: KenM [mailto:kenmli...@gmail.com]
> Sent: May-06-10 9:37 PM
> To: MS-Exchange Admin Issues
> Subject: Re: Can Powershell do this?
>
>
>
> I found some things wrong in my last post this is a little better.
>
>
>
> $users - get-qaduser
>
> Foreach ($user in $users){
>
> $sam = $user.samaccountname
>
> set-qaduser $sam -UserPrincipalName $...@domain.local
>
> }
>
>
>
>
>
>
>
>
>
> On Thu, May 6, 2010 at 7:26 PM, KenM  wrote:
>
> You can do sometihng like this with the quest cmdlts
>
>
>
> I dont know your environment so this may not work for you and may need 
> a little tweaking if you have over 1000 users in your domain. Can make 
> it more efficient with a LDAP filter looking for users without a UPN.
>
>
>
>
>
> $user = get-qaduser
>
> Foreach($user in $users) {set-qaduser $user.samaccountname 
> -Userprincipalname '$user.samaccountn...@domain.local'}
>
>
>
>
>
>
>
> On Thu, May 6, 2010 at 7:06 PM, Paul Steele  wrote:
>
> As we proceed with our Exchange 2010 migration, I discovered that some 
> mailboxes appear corrupted to powershell users, resulting in this error:
>
> [PS] C:\>get-mailbox -identity rmurphy
> WARNING: The object ad.acadiau.ca/academic/rmurphy has been corrupted, 
> and it's in an inconsistent state. The following validation errors 
> happened:
> WARNING: Property expression "rmurphy" isn't valid. Valid values are:
> Strings that includes '@',
>  where '@' cannot be the last character
>
> After some digging I discovered that the AD account attribute 
> UserPrincipleName does not have a domain associated with it (e.g.
> 'rmurphy' instead of 'rmur...@domain'). This can be fixed easily in 
> ADUC under the Account tab, but with over 100 users in this state I'd 
> like to find a programmatic way of doing it. I could whip together a 
> C# or VB script to fix the problem, but I was wondering if this sort 
> of thing could be done in PowerShell. I'm still learning PS but from 
> what I've seen I think the answer is yes. Anyone PowerShell experts out there?
>
>
>
>

Any using MS Backup for Exchange 2010?

[Paul Steele]

Since EMC isn't releasing a Networker module for Exchange 2010 until Q4,
we're investigating options that will get us by in the interim. MS
Backup seems like the obvious choice, but I have serious concerns with
it. Our intent was to back up each night to a local disk using MS
backup, and then use Networker to back up the MS Backup data files to
tape. Unfortunately there doesn't seem to be anyway to manage the MS
Backup files. I'd like to remove save sets from the backup to keep the
backup drive from getting too full. I had also hoped to be able to
restore a previous backup set just in case we needed to go back to an
older save set, but MS Backup doesn't seem to like any external
manipulation of its data files. Even worse, I made a copy of the MS
Backup data files, blew away the backup drive and recreated it, then put
the MS Backup data files back in place. Unfortunately MS Backup can no
longer access any of the save sets after this process. It knows the
files are there, but it says the backup destination is offline. I think
the reason is because the volume GUID has changed, but if that's the
case it makes MS Backup very inflexible.

 

Is there anyone using MS Backup who might have some suggestions on how
to use it?

 

Thanks!

 

RE: Any using MS Backup for Exchange 2010?

[Paul Steele]

A block differential style backup is fine. I'm more concerned about DR
scenarios where I might have to recover my entire server, including the
backup drive. I don't really expect that to happen, but if it does then
I have to make sure my backups are reliable. WSB doesn't seem to deal
with that situation very well (where the backup drive has to be
recreated), at least in my testing. If you could point me to one of your
scripts that might be a better option. I just need to find something
that will be suitable for the next 3 months, assuming EMC keeps to their
schedule.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 11:25 AM
To: MS-Exchange Admin Issues
Subject: RE: Any using MS Backup for Exchange 2010?

 

Windows Server Backup (WSB) should be used for:

 

[1] one-shot backups, or

[2] regular backups where you dedicate one or more volumes to the
backup.

 

Like DPM, WSB will do a block differential backup, not an old-style
file-based backup. This makes all backups after the first backup very
fast, and it allows for many generations of backups to be stored in a
relatively small space.

 

If you want an old-style file-based backup every night, you can write a
script to do it, use one of my scripts that already does this, or use
some other tool. WSB isn't a good fit.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:53 AM
To: MS-Exchange Admin Issues
Subject: Any using MS Backup for Exchange 2010?

 

Since EMC isn't releasing a Networker module for Exchange 2010 until Q4,
we're investigating options that will get us by in the interim. MS
Backup seems like the obvious choice, but I have serious concerns with
it. Our intent was to back up each night to a local disk using MS
backup, and then use Networker to back up the MS Backup data files to
tape. Unfortunately there doesn't seem to be anyway to manage the MS
Backup files. I'd like to remove save sets from the backup to keep the
backup drive from getting too full. I had also hoped to be able to
restore a previous backup set just in case we needed to go back to an
older save set, but MS Backup doesn't seem to like any external
manipulation of its data files. Even worse, I made a copy of the MS
Backup data files, blew away the backup drive and recreated it, then put
the MS Backup data files back in place. Unfortunately MS Backup can no
longer access any of the save sets after this process. It knows the
files are there, but it says the backup destination is offline. I think
the reason is because the volume GUID has changed, but if that's the
case it makes MS Backup very inflexible.

 

Is there anyone using MS Backup who might have some suggestions on how
to use it?

 

Thanks!

 

Outlook won't connect to Exch2010

[Paul Steele]

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

It was already set. I tried turning it off but it didn’t help, but I wasn’t 
really expecting it to since POP3 and IMAP connections are failing as well. 
Even Entourage on a Mac won’t connect…

 

From: chipsh...@comcast.net [mailto:chipsh...@comcast.net] 
Sent: May-12-10 7:52 AM
To: MS-Exchange Admin Issues
Subject: Re: Outlook won't connect to Exch2010

 

If not already set, try turning on encryption in Outlook.
- Original Message -
From: "Paul Steele" 
To: "MS-Exchange Admin Issues" 
Sent: Tuesday, May 11, 2010 7:21:23 PM GMT -05:00 US/Canada Eastern
Subject: Outlook won't connect to Exch2010

We’ve encountered yet one more problem on our new Exchange 2010 server. When 
the server install was first completed, one of the first things I did was 
create a test account and connected to it using Outlook. It worked as expected. 
OWA also worked fine, as did access to the account from an iPod Touch. When 
Outlook tries to verify the user account, it says it can’t connect to the 
Exchange server. One thing I’ve done since the install was completed was 
install a UC certificate and it works as expected with OWA. Being paranoid I 
removed the UC cert and assigned services back to the default Exchange cert, 
but that didn’t help. At this point I’m not even sure if it’s a certificate 
problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and both of 
those protocols failed as well. The error message indicates that the server is 
rejecting the username/password but since I know I’m using the right 
credentials there’s obviously something else happening. What would allow OWA to 
work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of those
situations where I need to check some box some place. It's just not
obvious what needs to be done.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 9:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you attempting to connect directly (i.e., MAPI) or while using
AutoDiscover/OutlookAnywhere?

 

What does testexchangeconnectivity.com say?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:20 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of those
situations where I need to check some box some place. It's just not
obvious what needs to be done.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 9:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you attempting to connect directly (i.e., MAPI) or while using
AutoDiscover/OutlookAnywhere?

 

What does testexchangeconnectivity.com say?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:20 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of those
situations where I need to check some box some place. It's just not
obvious what needs to be done.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 9:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you attempting to connect directly (i.e., MAPI) or while using
AutoDiscover/OutlookAnywhere?

 

What does testexchangeconnectivity.com say?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:20 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Windows Mail using both POP3 and IMAP protocols, and
both of those protocols failed as well. The error message indicates that
the server is rejecting the username/password but since I know I'm using
the right credentials there's obviously something else happening. What
would allow OWA to work but break everything else?

 

RE: Outlook won't connect to Exch2010

[Paul Steele]

When installing the UC cert, should the original Microsoft cert be
deleted? I still think this issue is somehow related to a certificate
problem...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of those
situations where I need to check some box some place. It's just not
obvious what needs to be done.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 9:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you attempting to connect directly (i.e., MAPI) or while using
AutoDiscover/OutlookAnywhere?

 

What does testexchangeconnectivity.com say?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 8:20 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I've tried Outlook 2007 and 2010 under XP, Vista, and Windows 7

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-11-10 8:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

What version of Outlook?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, May 11, 2010 7:21 PM
To: MS-Exchange Admin Issues
Subject: Outlook won't connect to Exch2010

 

We've encountered yet one more problem on our new Exchange 2010 server.
When the server install was first completed, one of the first things I
did was create a test account and connected to it using Outlook. It
worked as expected. OWA also worked fine, as did access to the account
from an iPod Touch. When Outlook tries to verify the user account, it
says it can't connect to the Exchange server. One thing I've done since
the install was completed was install a UC certificate and it works as
expected with OWA. Being paranoid I removed the UC cert and assigned
services back to the default Exchange cert, but that didn't help. At
this point I'm not even sure if it's a certificate problem. 

 

I tried setting up Win

RE: Outlook won't connect to Exch2010

[Paul Steele]

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed. What event service
controls logging for authentication requests? I didn't see anything
obvious in the list of possible event categories. Maybe it will have a
better explanation of why the server is rejecting the logins.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Doesn't matter whether you delete it or not. "Most" people run with the
default cert for SMTP and a SAN cert for everything else. If you run a
Get-ExchangeCertificate, you need a "W", and a "S" on valid
certificates. The others ("I", "P") are secondary to the first two.

 

I'm kinda at a loss. You might try those same tests from a workstation
that has the management tools installed, instead of from the Exchange
Server itself.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 9:29 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

When installing the UC cert, should the original Microsoft cert be
deleted? I still think this issue is somehow related to a certificate
problem...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=CA"

 

It would imply that it expected to find acadiau.ca or www.acadiau.ca in
the cert, but I'm not sure why it's using those entries. My UC cert has
three entries and they appear to work properly for the other tests, and
in OWA. We never had a cert on Exchange 2003, but the UC cert I got from
Digicert seem to install properly. I don't reference www.acadiau.ca
anywhere as far as I know.

 

The problem I'm encountering is that Outlook (any version) won't connect
to the server. As I started troubleshooting, I've also discovered that
POP3 and MAPI connections fail as well. The only way I can connect to
the server is using OWA or through my iPod Touch. I'm pretty sure this
whole problem occurred when I installed the UC cert, although I'm not
100% sure. I had been using OWA for my testing so I didn't notice when
Outlook broke. I suspect it's going to be another one of t

RE: Outlook won't connect to Exch2010

[Paul Steele]

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed. What event service
controls logging for authentication requests? I didn't see anything
obvious in the list of possible event categories. Maybe it will have a
better explanation of why the server is rejecting the logins.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Doesn't matter whether you delete it or not. "Most" people run with the
default cert for SMTP and a SAN cert for everything else. If you run a
Get-ExchangeCertificate, you need a "W", and a "S" on valid
certificates. The others ("I", "P") are secondary to the first two.

 

I'm kinda at a loss. You might try those same tests from a workstation
that has the management tools installed, instead of from the Exchange
Server itself.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 9:29 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

When installing the UC cert, should the original Microsoft cert be
deleted? I still think this issue is somehow related to a certificate
problem...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried these two commands, to verify RPC and HTTP connectivity:

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

Test-OutlookConnectivity -Protocol:Http
-GetDefaultsFromAutoDiscover:$true

 

Both completed without errors. I tried an Outlook session configured
using Outlook Anywhere and Outlook just keeps prompting for username and
password. For some reason Outlook doesn't like the credentials even
though they are valid. I'm very puzzled...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-12-10 12:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

In Exchange Management Shell, on the Exchange Server, run the
Test-OutlookConnectivity cmdlet. Read the help first, so you know what
to expect.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 12, 2010 11:01 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I ran the tests at textexchangeconnectivity.com and they all pass except
for the first one, Exchange ActiveSync. If I tell it to ignore the
certificate validity check, then it also work. The detailed error is:

 

"Host name acadiau.ca does not match any name found on the server
certificate e=r...@acadiau.ca, CN=www.acadiau.ca, OU=Technology
Services, O=Acadia University, L=Wolfville, S=Nova Scotia, C=C

RE: Outlook won't connect to Exch2010

[Paul Steele]

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/work
offline/cancel error. Is it actually possible to disable that protocol
on the server end? The problem has to be a configuration mistake on the
Exchange server. 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 7:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

If testexchangeconnectivity and test-outlookconnectivity  work then you
ARE making it all the way to the exchange server.

 

Then only other thing I can think of is using rpc-ping. That's not for
the weak.. :-P

 

Check out the articles about it on support.microsoft.com.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 4:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed. What event service
controls logging for authentication requests? I didn't see anything
obvious in the list of possible event categories. Maybe it will have a
better explanation of why the server is rejecting the logins.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Doesn't matter whether you delete it or not. "Most" people run with the
default cert for SMTP and a SAN cert for everything else. If you run a
Get-ExchangeCertificate, you need a "W", and a "S" on valid
certificates. The others ("I", "P") are secondary to the first two.

 

I'm kinda at a loss. You might try those same tests from a workstation
that has the management tools installed, instead of from the Exchange
Server itself.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 9:29 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

When installing the UC cert, should the original Microsoft cert be
deleted? I still think this issue is somehow related to a certificate
problem...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:52 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I also tried 

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and it worked as well...

 

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: May-12-10 2:14 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

RE: Outlook won't connect to Exch2010

[Paul Steele]

Are you saying that if Outlook Anywhere is enabled then regular non-HTTP
connections aren't going to work?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Oh. Duh. You can just "Disable-OutlookAnywhere".

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Friday, May 14, 2010 11:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess you could rename the RPC virtual directory on the server. I'm
not sure that's a supported thing to do though.

 

The supported way to do that would be "Set-CASMailbox
-MAPIBlockOutlookRpcHttp $true"

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 10:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/work
offline/cancel error. Is it actually possible to disable that protocol
on the server end? The problem has to be a configuration mistake on the
Exchange server. 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 7:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

If testexchangeconnectivity and test-outlookconnectivity  work then you
ARE making it all the way to the exchange server.

 

Then only other thing I can think of is using rpc-ping. That's not for
the weak.. :-P

 

Check out the articles about it on support.microsoft.com.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 4:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed. What event service
controls logging for authentication requests? I didn't see anything
obvious in the list of possible event categories. Maybe it will have a
better explanation of why the server is rejecting the logins.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 10:34 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Doesn't matter whether you delete it or not. "Most" people run with the
default cert for SMTP and a SAN cert for everything else. If you run a
Get-ExchangeCertificate, you need a "W", and a "S" on valid
certificates. The others

RE: Outlook won't connect to Exch2010

[Paul Steele]

I guess I don't understand why you suggest to disable Outlook Anywhere.
That is working as expected, but we need non-HTTP connections to work as
well.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Where did I say that? If I said that, I was wrong. :-P

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:30 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you saying that if Outlook Anywhere is enabled then regular non-HTTP
connections aren't going to work?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Oh. Duh. You can just "Disable-OutlookAnywhere".

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Friday, May 14, 2010 11:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess you could rename the RPC virtual directory on the server. I'm
not sure that's a supported thing to do though.

 

The supported way to do that would be "Set-CASMailbox
-MAPIBlockOutlookRpcHttp $true"

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 10:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/work
offline/cancel error. Is it actually possible to disable that protocol
on the server end? The problem has to be a configuration mistake on the
Exchange server. 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 7:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

If testexchangeconnectivity and test-outlookconnectivity  work then you
ARE making it all the way to the exchange server.

 

Then only other thing I can think of is using rpc-ping. That's not for
the weak.. :-P

 

Check out the articles about it on support.microsoft.com.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 4:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I tried the management tools from a notebook and the
test-exchangeconnectivity checks are successful. The
Get-ExchangeCertificate on the server shows IP.WS on the SAN Cert, so I
guess that's correct as well. 

 

When I try setting up Windows Mail in POP3 mode, I get the error:

 

Account: 'exchange2.acadiau.ca', Server: 'exchange2.acadiau.ca',
Protocol: POP3, Server Response: '-ERR Command is not valid in this
state.', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error
Number: 0x800CCC91

 

With an IMAP connection, I get the error "The server has rejected your
login. Please verify that the username and password are correct."

 

I tried setting the event logging for POP3 and IMAP to highest, but I'm
not getting any authentication errors listed.

RE: Outlook won't connect to Exch2010

[Paul Steele]

I guess my statement wasn't clear. I meant is it possible to disable
non-HTTP protocol support. If it can be enabled/disabled perhaps that is
what my issue is. I don't see anything obvious though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:46 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

"Outlook Anywhere" is the new name for "RPC over HTTP".

 

You asked: "Is it actually possible to disable that protocol on the
server end?"

 

I told you how.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess I don't understand why you suggest to disable Outlook Anywhere.
That is working as expected, but we need non-HTTP connections to work as
well.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Where did I say that? If I said that, I was wrong. :-P

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:30 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you saying that if Outlook Anywhere is enabled then regular non-HTTP
connections aren't going to work?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Oh. Duh. You can just "Disable-OutlookAnywhere".

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Friday, May 14, 2010 11:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess you could rename the RPC virtual directory on the server. I'm
not sure that's a supported thing to do though.

 

The supported way to do that would be "Set-CASMailbox
-MAPIBlockOutlookRpcHttp $true"

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 10:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/work
offline/cancel error. Is it actually possible to disable that protocol
on the server end? The problem has to be a configuration mistake on the
Exchange server. 

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 7:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

If testexchangeconnectivity and test-outlookconnectivity  work then you
ARE making it all the way to the exchange server.

 

Then only other thing I can think of is using rpc-ping. That's not for
the weak.. :-P

 

Check out the articles about it on support.microsoft.com.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 4:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

That was a stupid mistake on my part. The POP3/IMAP errors were red
herrings and have nothing to do with the Outlook connectivity issues.
It's definitely baffling though. What event logging categories might be
helpful in determining what's going on? I took a look at them and
nothing really jumped out. I want to see if the attempt to connect is
actually making it all the way to the Exchange server.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-13-10 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you enabling ssl/tls on those connections? Or did you turn it off at
the server?

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 13, 2010 10:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect 

RE: Outlook won't connect to Exch2010

[Paul Steele]

Yeah, the implication is that MAPI is working fine so it has to be
something else. I've tried a few rpcping commands with partial success:

 

RpcPing -t ncacn_http -s exchange.acadiau.ca -o
RpcProxy=exchange.acadiau.ca -P "testuser,acadia,*" -I
"testuser,acadia,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none

 

This command worked.

 

These both give Exception 5 errors:

 

RpcPing -t ncacn_http -s exchange.acadiau.ca -o
RpcProxy=exchange.acadiau.ca -P " testuser,acadia,*" -I "
testuser,acadia,*" -H 1 -F 3 -a connect -u 10 -v 3 -e 6001 

RpcPing -t ncacn_http -s exchange.acadiau.ca -o
RpcProxy=exchange.acadiau.ca -P " testuser,acadia,*" -I "
testuser,acadia,*" -H 1 -F 3 -a connect -u 10 -v 3 -e 6001 -B
msstd:exchange.acadiau.ca

 

The explanation for an exception 5 error is invalid credentials, the
account is disabled, or "Mutual Authorization Failed". I know the
credentials are correct and the account is enabled. Not sure what the
third case means. Maybe a clue here somewhere.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

It isn't possible, as far as I know. You said:

 

Test-OutlookConnectivity -Protocol:TCP
-GetDefaultsFromAutoDiscover:$true

 

and

 

Test-OutlookConnectivity -RpcProxyTestType:Internal -RpcTestType:Server

 

worked though. That leads me to believe that MAPI is working just fine.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:50 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess my statement wasn't clear. I meant is it possible to disable
non-HTTP protocol support. If it can be enabled/disabled perhaps that is
what my issue is. I don't see anything obvious though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:46 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

"Outlook Anywhere" is the new name for "RPC over HTTP".

 

You asked: "Is it actually possible to disable that protocol on the
server end?"

 

I told you how.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:43 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess I don't understand why you suggest to disable Outlook Anywhere.
That is working as expected, but we need non-HTTP connections to work as
well.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Where did I say that? If I said that, I was wrong. :-P

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 11:30 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Are you saying that if Outlook Anywhere is enabled then regular non-HTTP
connections aren't going to work?

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-14-10 12:27 PM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Oh. Duh. You can just "Disable-OutlookAnywhere".

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Friday, May 14, 2010 11:24 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

I guess you could rename the RPC virtual directory on the server. I'm
not sure that's a supported thing to do though.

 

The supported way to do that would be "Set-CASMailbox
-MAPIBlockOutlookRpcHttp $true"

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, May 14, 2010 10:44 AM
To: MS-Exchange Admin Issues
Subject: RE: Outlook won't connect to Exch2010

 

Yikes. I see what you mean. It will take me a while to figure out the
proper command to use.

 

I've actually made some progress this morning. As it turns out, it
appears that RPC over HTTP does work properly. Authentication can
sometimes take a lot longer that I would expect, but otherwise it
functions as expected. Unfortunately I still can't get regular non-HTTP
connections to work. If I switch from a configuration using RPC over
HTTP and turn that setting off, loading Outlook immediately says it
can't connect to the server and gives you that standard Retry/wo

Office 2010 for the Mac

[Paul Steele]

Has anyone tried the Office 2010 for the Mac beta version? We just found
out that Office 2008 for the Mac will not work with Exchange 2010, so
that puts a bit of a wrench into our migration plans.

RE: Office 2010 for the Mac

[Paul Steele]

This looks like it should suffice for now. Thanks!

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-19-10 11:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Office 2010 for the Mac

 

You can separately download Entourage 2008 EWS that works with Exchange
2010.

 

http://www.microsoft.com/mac/itpros/entourage-ews.mspx

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 19, 2010 10:03 AM
To: MS-Exchange Admin Issues
Subject: Office 2010 for the Mac

 

Has anyone tried the Office 2010 for the Mac beta version? We just found
out that Office 2008 for the Mac will not work with Exchange 2010, so
that puts a bit of a wrench into our migration plans.

RE: Office 2010 for the Mac

[Paul Steele]

Can anyone confirm if the EWS version will work with Exchange 2003? From
what I've been reading it doesn't, which would add yet one more
complication to our migration...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-19-10 11:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Office 2010 for the Mac

 

You can separately download Entourage 2008 EWS that works with Exchange
2010.

 

http://www.microsoft.com/mac/itpros/entourage-ews.mspx

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 19, 2010 10:03 AM
To: MS-Exchange Admin Issues
Subject: Office 2010 for the Mac

 

Has anyone tried the Office 2010 for the Mac beta version? We just found
out that Office 2008 for the Mac will not work with Exchange 2010, so
that puts a bit of a wrench into our migration plans.

RE: Office 2010 for the Mac

[Paul Steele]

That's what I was afraid. Our Helpdesk won't be happy...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-20-10 12:11 PM
To: MS-Exchange Admin Issues
Subject: RE: Office 2010 for the Mac

 

It will not work with Exchange 2003.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Thursday, May 20, 2010 10:59 AM
To: MS-Exchange Admin Issues
Subject: RE: Office 2010 for the Mac

 

Can anyone confirm if the EWS version will work with Exchange 2003? From
what I've been reading it doesn't, which would add yet one more
complication to our migration...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: May-19-10 11:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Office 2010 for the Mac

 

You can separately download Entourage 2008 EWS that works with Exchange
2010.

 

http://www.microsoft.com/mac/itpros/entourage-ews.mspx

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, May 19, 2010 10:03 AM
To: MS-Exchange Admin Issues
Subject: Office 2010 for the Mac

 

Has anyone tried the Office 2010 for the Mac beta version? We just found
out that Office 2008 for the Mac will not work with Exchange 2010, so
that puts a bit of a wrench into our migration plans.

RE: Move Mailbox back to 2003 from 2010

[Paul Steele]

The move wizard should let you move it back to Exchange 2003. We’ve been doing 
that quite a bit for testing purposes until we’re ready for the full migration.

 

From: Harry Singh [mailto:hbo...@gmail.com] 
Sent: June-07-10 12:12 PM
To: MS-Exchange Admin Issues
Subject: Move Mailbox back to 2003 from 2010

 

All -

 

A Exchange 2003 mailbox was moved to Exchange 2010 over the weekend but it 
turns out my Unified Messaging system needs that mailbox to sit on a exchange 
2003 database until i can upgrade it to a versions which supports 2010.

 

Anyone know of a way I can move the mailbox back into 2003 ? is it possible ?

IIS/OWA corruption

[Paul Steele]

Problems have appeared in out Exchange 2010 OWA site. Trying to log in
always produces the error:

 

  "The item can't be opened because it's become corrupted."

 

The URL being referenced at the time is https://exchange.domain.com/owa.
I am definitely not an expert in IIS, but running up IIS Manager and
looking around seems to be fine. I'm considering restore the directory
for  "C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa",
although it looks fine. Google searches hasn't helped in identifying the
problem.

 

Anyone got any suggestions?

 

 

RE: IIS/OWA corruption

[Paul Steele]

No problems found. The only changes I've made to OWA is setting up a
redirect for the base URL, but removing that doesn't help. Not exactly
sure when it stopped working since we're not in production yet. Probably
only a couple of days though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: June-09-10 1:10 PM
To: MS-Exchange Admin Issues
Subject: RE: IIS/OWA corruption

 

I've never heard of this one.

 

I'd run a chkdsk, first thing, before I started restoring anything.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, June 09, 2010 12:07 PM
To: MS-Exchange Admin Issues
Subject: IIS/OWA corruption

 

Problems have appeared in out Exchange 2010 OWA site. Trying to log in
always produces the error:

 

  "The item can't be opened because it's become corrupted."

 

The URL being referenced at the time is https://exchange.domain.com/owa.
I am definitely not an expert in IIS, but running up IIS Manager and
looking around seems to be fine. I'm considering restore the directory
for  "C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa",
although it looks fine. Google searches hasn't helped in identifying the
problem.

 

Anyone got any suggestions?

 

 

RE: IIS/OWA corruption

[Paul Steele]

False alarm. Problem found. It was only happening to one user,
fortunately a test account...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: June-09-10 1:16 PM
To: MS-Exchange Admin Issues
Subject: RE: IIS/OWA corruption

 

No problems found. The only changes I've made to OWA is setting up a
redirect for the base URL, but removing that doesn't help. Not exactly
sure when it stopped working since we're not in production yet. Probably
only a couple of days though.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: June-09-10 1:10 PM
To: MS-Exchange Admin Issues
Subject: RE: IIS/OWA corruption

 

I've never heard of this one.

 

I'd run a chkdsk, first thing, before I started restoring anything.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Wednesday, June 09, 2010 12:07 PM
To: MS-Exchange Admin Issues
Subject: IIS/OWA corruption

 

Problems have appeared in out Exchange 2010 OWA site. Trying to log in
always produces the error:

 

  "The item can't be opened because it's become corrupted."

 

The URL being referenced at the time is https://exchange.domain.com/owa.
I am definitely not an expert in IIS, but running up IIS Manager and
looking around seems to be fine. I'm considering restore the directory
for  "C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa",
although it looks fine. Google searches hasn't helped in identifying the
problem.

 

Anyone got any suggestions?

 

 

Public Folder problems in Exchange 2010 OWA

[Paul Steele]

There always seems to be a new problem with our Exchange 2010 migration.
The latest is some bizarre behaviour with Public Folders in OWA. At
present we have a single Exchange 2003 server and single 2010 server.
We've set up public folder replication between the two servers and
public folders appear to be working properly for Exchange 2010 users
using Outlook. However, in OWA the public folders show up properly but
accessing the content is not so great. If I create new content within
OWA, that appears to work correctly and the new content also appears as
expected in Outlook. However, accessing existing content (such as a
contact list), gives the error "The public folder you're trying to
access couldn't be found. For more information, contact your helpdesk".
In some cases I don't see the content at all.

 

I've been doing some Google searches and have found various references
to this problem (so I know we're not the only place encountering it),
but nothing has been all that helpful in resolving it. I get the
impression that it's a known problem though. What's the scoop with
Public Folders and OWA in Exchange 2010?

 

RE: Public Folder problems in Exchange 2010 OWA

[Paul Steele]

I think I solved the problem. Some of the public folders didn't have
replicas on the new server. I re-ran the addreplicatopf script and
things are working better now. I think...

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: June-11-10 9:23 AM
To: MS-Exchange Admin Issues
Subject: Public Folder problems in Exchange 2010 OWA

 

There always seems to be a new problem with our Exchange 2010 migration.
The latest is some bizarre behaviour with Public Folders in OWA. At
present we have a single Exchange 2003 server and single 2010 server.
We've set up public folder replication between the two servers and
public folders appear to be working properly for Exchange 2010 users
using Outlook. However, in OWA the public folders show up properly but
accessing the content is not so great. If I create new content within
OWA, that appears to work correctly and the new content also appears as
expected in Outlook. However, accessing existing content (such as a
contact list), gives the error "The public folder you're trying to
access couldn't be found. For more information, contact your helpdesk".
In some cases I don't see the content at all.

 

I've been doing some Google searches and have found various references
to this problem (so I know we're not the only place encountering it),
but nothing has been all that helpful in resolving it. I get the
impression that it's a known problem though. What's the scoop with
Public Folders and OWA in Exchange 2010?

 

Monitoring mailbox moves

[Paul Steele]

Is there any way to monitor the percentage complete of a mailbox move in
Exchange 2010 using the EMS? It's available in the properties pane of a
Move Request in the EMC, but I can't find a way to display that
information using get-moverequest.

 

RE: Monitoring mailbox moves

[Paul Steele]

Thanks. For some reason I thought that command only applied to completed
moves...

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: June-14-10 1:53 PM
To: MS-Exchange Admin Issues
Subject: RE: Monitoring mailbox moves

 

Get-moverequeststatistics

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, June 14, 2010 11:51 AM
To: MS-Exchange Admin Issues
Subject: Monitoring mailbox moves

 

Is there any way to monitor the percentage complete of a mailbox move in
Exchange 2010 using the EMS? It's available in the properties pane of a
Move Request in the EMC, but I can't find a way to display that
information using get-moverequest.

 


**
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this
message to  
the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If
you  
have received this communication in error, please notify us immediately
by  
replying to the message and deleting it from your computer. 

**

Problems with Entourage after migration

[Paul Steele]

I'm passing this information on from our Helpdesk. I don't use Macs but
I'm trying to help them with our Exchange 2010 migration.

---

During migration testing from Exchange server 2003 to 2010 we discovered
problems with our Mac Entourage 2008 users. While using Mac Office
12.2.4 and  Entourage WSE version 13.0.4 we were getting a prompt
regarding a certificate not being installed. While this error was
unsolved it would only prompt during the first boot of Entourage and
then never return during our testing. 

As of last week the update to Office 12.2.5 forced us to install the WSE
version 13.0.5 in order to get through the installer. However the
certificate error now occurs every time they open Entourage. The exact
error message is "unable to establist a secure connection to acadiau.ca
because the correct root certificate is not installed". After clicking
ok on the error box Entourage does continue to load and appears to run
correctly.

 

We have a Digicert UC cert installed on our exchange server and the
domain names in the cert appear to match what client have entered in
their Entourage account information. "acadiau.ca" does not appear in the
cert (and shouldn't) and it's not clear why Entourage is complaining
about it. OWA (in Safari) works fine.

 

The upgrade to Entourage WSE is not going to be easy because the WSE
version and Office version must match to get it installed correctly.

Office 12.2.3 needed WSE 13.0.3 to install correctly.
Office 12.2.4 needed WSE 13.0.4 to install correctly.
Office 12.2.5 appears to need WSE 13.0.5 to install correctly.
Microsoft's site today listed 13.0.0 as the current download which
should be older, although we found 13.0.5 on a random website and used
it as 13.0.0 will not install since it's actually older than the
Entourage version most users are running.

Has anyone has similar problems with certificates with Entourage WSE?
Any suggestions would be greatly appreciated.

 

 

RE: Problems with Entourage after migration

[Paul Steele]

I fixed the problem by installing our wildcard certificate on the server
that resolves to acadiau.ca (www.acadiau.ca).  For some reason Entourage
is looking at acadiau.ca and didn't like not finding a cert there...

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: June-14-10 4:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Problems with Entourage after migration

 

I presume that by "WSE" they mean "EWS".

 

It sounds to me as if the MACs don't have the _root certificate_
installed for the certificate. That is, they are attempting to validate
the SSL chain from certificate to root and a piece is missing.

 

Unless you turn it on (off by default), most browsers won't do root
investigation like that.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Monday, June 14, 2010 2:17 PM
To: MS-Exchange Admin Issues
Subject: Problems with Entourage after migration

 

I'm passing this information on from our Helpdesk. I don't use Macs but
I'm trying to help them with our Exchange 2010 migration.

---

During migration testing from Exchange server 2003 to 2010 we discovered
problems with our Mac Entourage 2008 users. While using Mac Office
12.2.4 and  Entourage WSE version 13.0.4 we were getting a prompt
regarding a certificate not being installed. While this error was
unsolved it would only prompt during the first boot of Entourage and
then never return during our testing. 

As of last week the update to Office 12.2.5 forced us to install the WSE
version 13.0.5 in order to get through the installer. However the
certificate error now occurs every time they open Entourage. The exact
error message is "unable to establist a secure connection to acadiau.ca
because the correct root certificate is not installed". After clicking
ok on the error box Entourage does continue to load and appears to run
correctly.

 

We have a Digicert UC cert installed on our exchange server and the
domain names in the cert appear to match what client have entered in
their Entourage account information. "acadiau.ca" does not appear in the
cert (and shouldn't) and it's not clear why Entourage is complaining
about it. OWA (in Safari) works fine.

 

The upgrade to Entourage WSE is not going to be easy because the WSE
version and Office version must match to get it installed correctly.

Office 12.2.3 needed WSE 13.0.3 to install correctly.
Office 12.2.4 needed WSE 13.0.4 to install correctly.
Office 12.2.5 appears to need WSE 13.0.5 to install correctly.
Microsoft's site today listed 13.0.0 as the current download which
should be older, although we found 13.0.5 on a random website and used
it as 13.0.0 will not install since it's actually older than the
Entourage version most users are running.

Has anyone has similar problems with certificates with Entourage WSE?
Any suggestions would be greatly appreciated.

 

 

ActiveSync and Domain Admins

[Paul Steele]

I noticed that my personal account did not work on my iPod with ActiveSync, but 
my test account worked ok. I did some checking and came across an article that 
said that ActiveSync does not work if the user is in the Domain Admins group. 
ExRCA fails as well with the error:

ExRCA is attempting the FolderSync command on the Exchange ActiveSync session.
  The test of the FolderSync command failed.
   Additional Details
  Exchange ActiveSync returned an HTTP 500 response.

Has anyone else encountered this problem?

RE: ActiveSync and Domain Admins

[Paul Steele]

That did the trick. I don't disagree with all the comments concerning security 
concerns. I think I'll investigate alternatives and see if an old dog can learn 
new tricks...

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
Sent: June-17-10 11:11 AM
To: MS-Exchange Admin Issues
Subject: RE: ActiveSync and Domain Admins

I'm in the domain admins group, and I got my Windows Mobile to work after 
migrating to 2010 by going in and enabling inheritance on my user account in 
AD.   The adminSDholder process will disable inheritance again but it appears 
that once you enable it and get AS working, it continues to work after 
inheritance is disabled again.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, June 17, 2010 9:00 AM
To: MS-Exchange Admin Issues
Subject: RE: ActiveSync and Domain Admins

And in Exchange 2010 sp1 it's much more accessible and usable.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Matt Moore [mailto:mattmoore...@hotmail.com]
Sent: Thursday, June 17, 2010 9:54 AM
To: MS-Exchange Admin Issues
Subject: RE: ActiveSync and Domain Admins

RBAC is very, very cool and at the same time kinda like watching paint dry.  
Possibly the biggest leap forward for Exchange to date.  All MS server side 
Apps will follow this model.  Learn it, love it.   Of course all my opinion.
M

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, June 17, 2010 6:23 AM
To: MS-Exchange Admin Issues
Subject: RE: ActiveSync and Domain Admins

It's not a problem, per se. It's by design. ActiveSync won't work with accounts 
in any of the protected groups.

In order to support RBAC, Exchange has to have permissions over much of the AD. 
Protected accounts/groups are explicitly restricted from Exchange having 
control over them. Otherwise, any Exchange admin could make themselves a domain 
admin, enterprise admin, backup operator, server operator, etc.etc.

There is technical documentation on this change, but it isn't very accessible 
from a "normal admin" perspective (that is, ok you made that change - what does 
it mean to me). I bugged that last week.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Thursday, June 17, 2010 9:17 AM
To: MS-Exchange Admin Issues
Subject: ActiveSync and Domain Admins

I noticed that my personal account did not work on my iPod with ActiveSync, but 
my test account worked ok. I did some checking and came across an article that 
said that ActiveSync does not work if the user is in the Domain Admins group. 
ExRCA fails as well with the error:

ExRCA is attempting the FolderSync command on the Exchange ActiveSync session.
  The test of the FolderSync command failed.
   Additional Details
  Exchange ActiveSync returned an HTTP 500 response.

Has anyone else encountered this problem?


**

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**

.Net Programming for Exchange 2010

[Paul Steele]

I like to write simple C#-based GUI utilities for my staff to simplify some of 
the repetitive tasks such as creating accounts. Now that we’ve upgraded to 
Exchange 2010 I have a few utilities that need updating. I’ve been doing some 
Google searches for sample programs and the examples refer to a class library 
Microsoft.Exchange. Unfortunately I haven’t been able to find where this class 
is located in order to add it to my Visual Studio Project. There are a lot of 
built-in Microsoft.* components in the reference library, but not 
Microsoft.Exchange. I’ve looked on the Exchange installation media and also 
checked on MSDN but don’t see anything there. Does anyone know where I can find 
the components needed for .Net programming for Exchange 2010?

Thanks!

Migrating special mailboxes

[Paul Steele]

Should the special mailboxes in Exchange 2003 (SMTP * and SystemMailbox *) be 
migrated. I haven’t found any mention of them in the various migration 
documents I’ve been using so I would assume not.

RE: Migrating special mailboxes

[Paul Steele]

This article seems to apply more about rehoming Exchange 2003 server setup. I’m 
in the process of removing my *only* Exchange 2003 server, making sure that 
everything is properly set up on Exchange 2010. I’ve done the obvious stuff 
like moving all the users and setting up public folder replication to the 
Exchange 2010. Now I need to start to break the link between the two servers 
before decommissioning the 2003 server. I’ve been using a couple of different 
documents for this process. Does anyone have any good articles on this topic?

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: June 28, 2010 1:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

Those system mailboxes are unique to the system they are installed on. You will 
find that they exist on the new server as well. Exchange will recreate them if 
required.

The only folders that need to be migrated are those that are in the 
documentation - http://support.microsoft.com/default.aspx?kbid=822931

Simon.


--
Simon Butler
MVP: Exchange, MCSE
Sembee Ltd.

e: si...@sembee.co.uk<mailto:si...@sembee.co.uk>
w: http://www.sembee.co.uk/
w: http://www.amset.info/
w: http://blog.sembee.co.uk/

Need cheap certificates for Exchange, compatible with Windows Mobile 5.0?
http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for 
certificates from just $23.99.
Need a domain for your certificate? 
http://DomainsForExchange.net/<http://domainsforexchange.net/>

Exchange Resources: http://exbpa.com/



From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 15:44
To: MS-Exchange Admin Issues
Subject: Migrating special mailboxes

Should the special mailboxes in Exchange 2003 (SMTP * and SystemMailbox *) be 
migrated. I haven’t found any mention of them in the various migration 
documents I’ve been using so I would assume not.

RE: Migrating special mailboxes

[Paul Steele]

So far the document seems to adequate for Exchange 2010 as well, although I 
have a ways to go as well.

I have a question though. Is it actually necessary to remove the public folder 
database on the Exchange 2003 server. I’ve confirmed that public folders have 
replicated properly to Exchange 2010 and I’ve removed the 2003 server from the 
replica list on the 2010 server. Is it still necessary to physically delete the 
public folders on the 2003 side as part of the process?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 2:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

They want you to use exdeploy. Which is incomplete (and I bugged with Ross – 
he’s working on improving it).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: Monday, June 28, 2010 1:26 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I was hoping that there was an Exchange 2010 version of this article.
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

But there isn’t.
Probably means I will have to write one… ☺

Simon.

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 18:00
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

This article seems to apply more about rehoming Exchange 2003 server setup. I’m 
in the process of removing my *only* Exchange 2003 server, making sure that 
everything is properly set up on Exchange 2010. I’ve done the obvious stuff 
like moving all the users and setting up public folder replication to the 
Exchange 2010. Now I need to start to break the link between the two servers 
before decommissioning the 2003 server. I’ve been using a couple of different 
documents for this process. Does anyone have any good articles on this topic?

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: June 28, 2010 1:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

Those system mailboxes are unique to the system they are installed on. You will 
find that they exist on the new server as well. Exchange will recreate them if 
required.

The only folders that need to be migrated are those that are in the 
documentation - http://support.microsoft.com/default.aspx?kbid=822931

Simon.


--
Simon Butler
MVP: Exchange, MCSE
Sembee Ltd.

e: si...@sembee.co.uk<mailto:si...@sembee.co.uk>
w: http://www.sembee.co.uk/
w: http://www.amset.info/
w: http://blog.sembee.co.uk/

Need cheap certificates for Exchange, compatible with Windows Mobile 5.0?
http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for 
certificates from just $23.99.
Need a domain for your certificate? 
http://DomainsForExchange.net/<http://domainsforexchange.net/>

Exchange Resources: http://exbpa.com/



From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 15:44
To: MS-Exchange Admin Issues
Subject: Migrating special mailboxes

Should the special mailboxes in Exchange 2003 (SMTP * and SystemMailbox *) be 
migrated. I haven’t found any mention of them in the various migration 
documents I’ve been using so I would assume not.

RE: Migrating special mailboxes

[Paul Steele]

I obviously made a mistake along the way because it won’t let me remove the PF 
database. Says there are still replicas. I tried creating a new PF database but 
I think that just made things worse. Everything is actually fine on the 2010 
side so if I can’t do a uninstall I guess I can live with it. Are there any 
potential problems if the 2003 server is not uninstalled?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 6:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

You do it as a preparatory step to ensure that everything necessary has been 
replicated over and that there are no replicas in the DB except for the current 
server.

If you can’t delete the PF DB, then you won’t be able to uninstall Exchange. 
So…it’s just a step in the process to cleanly remove the server.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Monday, June 28, 2010 2:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

So far the document seems to adequate for Exchange 2010 as well, although I 
have a ways to go as well.

I have a question though. Is it actually necessary to remove the public folder 
database on the Exchange 2003 server. I’ve confirmed that public folders have 
replicated properly to Exchange 2010 and I’ve removed the 2003 server from the 
replica list on the 2010 server. Is it still necessary to physically delete the 
public folders on the 2003 side as part of the process?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 2:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

They want you to use exdeploy. Which is incomplete (and I bugged with Ross – 
he’s working on improving it).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: Monday, June 28, 2010 1:26 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I was hoping that there was an Exchange 2010 version of this article.
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

But there isn’t.
Probably means I will have to write one… ☺

Simon.

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 18:00
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

This article seems to apply more about rehoming Exchange 2003 server setup. I’m 
in the process of removing my *only* Exchange 2003 server, making sure that 
everything is properly set up on Exchange 2010. I’ve done the obvious stuff 
like moving all the users and setting up public folder replication to the 
Exchange 2010. Now I need to start to break the link between the two servers 
before decommissioning the 2003 server. I’ve been using a couple of different 
documents for this process. Does anyone have any good articles on this topic?

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: June 28, 2010 1:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

Those system mailboxes are unique to the system they are installed on. You will 
find that they exist on the new server as well. Exchange will recreate them if 
required.

The only folders that need to be migrated are those that are in the 
documentation - http://support.microsoft.com/default.aspx?kbid=822931

Simon.


--
Simon Butler
MVP: Exchange, MCSE
Sembee Ltd.

e: si...@sembee.co.uk<mailto:si...@sembee.co.uk>
w: http://www.sembee.co.uk/
w: http://www.amset.info/
w: http://blog.sembee.co.uk/

Need cheap certificates for Exchange, compatible with Windows Mobile 5.0?
http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for 
certificates from just $23.99.
Need a domain for your certificate? 
http://DomainsForExchange.net/<http://domainsforexchange.net/>

Exchange Resources: http://exbpa.com/



From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 15:44
To: MS-Exchange Admin Issues
Subject: Migrating special mailboxes

Should the special mailboxes in Exchange 2003 (SMTP * and SystemMailbox *) be 
migrated. I haven’t found any mention of them in the various migration 
documents I’ve been using so I would assume not.

RE: Migrating special mailboxes

[Paul Steele]

I'll look over the blog but unfortunately I think I made a mistake in the 
sequence of steps for removing the PF database. It does not give me the option 
of moving the replicas to another server. I had actually created replicas for 
the PF database by running the addReplicaToPFRecursive.ps1 script and specified 
my 2010 server. After I had migrated all users and had confirmed the PF had 
completed replication, I ran the RemoveReplicaFromPFRecursive.ps1 script and 
removed the 2003 server from the replica list. I've done some of the other 
tasks for decommissioning such as deleting the routing groups, but when I try 
the "Move All Replicas" option it does not list the 2010 server. I know the 
2010 server has a working copy of the PF so I think I'm ok, but something is 
obviously not working exactly like it should...

-Original Message-
From: Rob Sargent [mailto:rbsr...@gmail.com] 
Sent: June-29-10 9:42 AM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

To get rid of the remaining replicas on your Ex2003, some of which could be 
which the standard built-in PFs, use System Manager in Ex2003 and use the Move 
All Replicas option.  Wait for replication to complete .. the Public Folder 
Instances folder will be empty.   Then you can delete the PF database.

This is the blog that helped me the most.
http://msexchangeteam.com/archive/2007/07/09/445967.aspx

Exchange 2010 Restore question

[Paul Steele]

If we restore a database from backup and issue the command

get-mailbox -database restoredb

should it display a list of mailboxes held in the restored database? If not is 
there some way to list the contents of the RestoreDB?

RE: Exchange 2010 Restore question

[Paul Steele]

Thanks. That worked perfectly…

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-29-10 10:05 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 Restore question

Get-mailboxstatistics, not get-mailbox.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, June 29, 2010 3:37 PM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 Restore question

If we restore a database from backup and issue the command

get-mailbox -database restoredb

should it display a list of mailboxes held in the restored database? If not is 
there some way to list the contents of the RestoreDB?

RE: Migrating special mailboxes

[Paul Steele]

I’ve checked all the system folders (EFORMS, Free/Busy, and Offline address 
books) and only see the 2010 server in the replica list. I’ve issued the 
command to move all replicas from the 2003 server to the 2010 server, then 
waited 24 hours. Unfortunately when I try to delete the Public Folder store it 
still says it can’t do it because it contains replicas. Is there any way to 
determine where the 2003 server is seeing replicas? I certainly can’t find any.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-29-10 1:58 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

You need to look at both normal folders and system folders.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, June 29, 2010 8:21 AM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I obviously made a mistake along the way because it won’t let me remove the PF 
database. Says there are still replicas. I tried creating a new PF database but 
I think that just made things worse. Everything is actually fine on the 2010 
side so if I can’t do a uninstall I guess I can live with it. Are there any 
potential problems if the 2003 server is not uninstalled?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 6:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

You do it as a preparatory step to ensure that everything necessary has been 
replicated over and that there are no replicas in the DB except for the current 
server.

If you can’t delete the PF DB, then you won’t be able to uninstall Exchange. 
So…it’s just a step in the process to cleanly remove the server.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Monday, June 28, 2010 2:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

So far the document seems to adequate for Exchange 2010 as well, although I 
have a ways to go as well.

I have a question though. Is it actually necessary to remove the public folder 
database on the Exchange 2003 server. I’ve confirmed that public folders have 
replicated properly to Exchange 2010 and I’ve removed the 2003 server from the 
replica list on the 2010 server. Is it still necessary to physically delete the 
public folders on the 2003 side as part of the process?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 2:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

They want you to use exdeploy. Which is incomplete (and I bugged with Ross – 
he’s working on improving it).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: Monday, June 28, 2010 1:26 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I was hoping that there was an Exchange 2010 version of this article.
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

But there isn’t.
Probably means I will have to write one… ☺

Simon.

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 18:00
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

This article seems to apply more about rehoming Exchange 2003 server setup. I’m 
in the process of removing my *only* Exchange 2003 server, making sure that 
everything is properly set up on Exchange 2010. I’ve done the obvious stuff 
like moving all the users and setting up public folder replication to the 
Exchange 2010. Now I need to start to break the link between the two servers 
before decommissioning the 2003 server. I’ve been using a couple of different 
documents for this process. Does anyone have any good articles on this topic?

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: June 28, 2010 1:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

Those system mailboxes are unique to the system they are installed on. You will 
find that they exist on the new server as well. Exchange will recreate them if 
required.

The only folders that need to be migrated are those that are in the 
documentation - http://support.microsoft.com/default.aspx?kbid=822931

Simon.


--
Simon Butler
MVP: Exchange, MCSE
Sembee Ltd.

e: si...@sembee.co.uk<mailto:si...@sembee.co.uk>
w: http://www.sembee.co.uk/
w: http://www.amset.info/
w: http://blog.sembee.co.uk/

Need cheap certificates for Exchange, compatible with Windows Mobile 5.0?
http://CertificatesForExchange.com/<http://certificatesforexchange.com/> for 
certificates from just $23.99.
Need a domain for your certificate? 
http://DomainsForExchange.net/<http://domainsforexchange.net/>

Exchange Resources: http://exbpa.com/



From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 15:44
To: MS-Exchange Admin Issues
Subject:

RE: Migrating special mailboxes

[Paul Steele]

The process suddenly worked this morning. I guess I just didn’t wait long 
enough for the replication, although I would have though 24 hours would be more 
than enough. In any case the Exchange 2003 public folder is now deleted…

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: July-01-10 4:47 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I don’t have any more 2003 servers in my or my customers environments. 
Generally, it seems to me that there is somewhere in EMS where you can check 
the status of replication and it says “In Sync” or “Local Modified” (that’s 
what the book I wrote on Exchange 2003 says too) ☺. You may want to try 
“resending changes” and see what additional information that PFDAVADMIN can 
provide you.

Thanks.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Thursday, July 01, 2010 6:35 AM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I’ve checked all the system folders (EFORMS, Free/Busy, and Offline address 
books) and only see the 2010 server in the replica list. I’ve issued the 
command to move all replicas from the 2003 server to the 2010 server, then 
waited 24 hours. Unfortunately when I try to delete the Public Folder store it 
still says it can’t do it because it contains replicas. Is there any way to 
determine where the 2003 server is seeing replicas? I certainly can’t find any.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-29-10 1:58 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

You need to look at both normal folders and system folders.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, June 29, 2010 8:21 AM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I obviously made a mistake along the way because it won’t let me remove the PF 
database. Says there are still replicas. I tried creating a new PF database but 
I think that just made things worse. Everything is actually fine on the 2010 
side so if I can’t do a uninstall I guess I can live with it. Are there any 
potential problems if the 2003 server is not uninstalled?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 6:06 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

You do it as a preparatory step to ensure that everything necessary has been 
replicated over and that there are no replicas in the DB except for the current 
server.

If you can’t delete the PF DB, then you won’t be able to uninstall Exchange. 
So…it’s just a step in the process to cleanly remove the server.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Monday, June 28, 2010 2:45 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

So far the document seems to adequate for Exchange 2010 as well, although I 
have a ways to go as well.

I have a question though. Is it actually necessary to remove the public folder 
database on the Exchange 2003 server. I’ve confirmed that public folders have 
replicated properly to Exchange 2010 and I’ve removed the 2003 server from the 
replica list on the 2010 server. Is it still necessary to physically delete the 
public folders on the 2003 side as part of the process?

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: June-28-10 2:29 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

They want you to use exdeploy. Which is incomplete (and I bugged with Ross – 
he’s working on improving it).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: Monday, June 28, 2010 1:26 PM
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

I was hoping that there was an Exchange 2010 version of this article.
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

But there isn’t.
Probably means I will have to write one… ☺

Simon.

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: 28 June 2010 18:00
To: MS-Exchange Admin Issues
Subject: RE: Migrating special mailboxes

This article seems to apply more about rehoming Exchange 2003 server setup. I’m 
in the process of removing my *only* Exchange 2003 server, making sure that 
everything is properly set up on Exchange 2010. I’ve done the obvious stuff 
like moving all the users and setting up public folder replication to the 
Exchange 2010. Now I need to start to break the link between the two servers 
before decommissioning the 2003 server. I’ve been using a couple of different 
documents for this process. Does anyone have any good articles on this topic?

From: Simon Butler [mailto:si...@sembee.co.uk]
Sent: June 28, 2010 1:17 PM
To: MS

Using Exmerge after migrating to 2010

[Paul Steele]

As luck would have it, we have a user who needs his mailbox restored from a few 
days before we moved his account from Exchange 2003 to Exchange 2010. We’ve 
been able to restore the required storage group, but when we run Exmerge to 
extract the user’s mailbox into a PST file, it complains about permission 
problems. This link shows the error we’re getting, but the suggested remedies 
don’t really apply, although I did verify just in case.

http://support.microsoft.com/kb/322312

I think the cause of the problem is because the user no longer has a mailbox on 
the 2003 server. I don’t really want to move his mailbox back to 2003, plus I’m 
not even sure if it will solve the problem. Is there some other way to restore 
a legacy mailbox other than using Exmerge?

RE: Using Exmerge after migrating to 2010

[Paul Steele]

That’s what I was afraid of. This whole issue puts a wrench into 
decommissioning our old Exchange server. We have a rule that old data such as 
user mailboxes must be recoverable from backup for at least 3 years. If we 
completely remove the Exchange 2003 server then that won’t be possible 
(assuming we can find a solution to the Exmerge problem). I think we’re going 
to have to just power off the Exchange server and complete the full 
decommissioning process at some time in the future. I *really* wanted to get 
rid of that old server…

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: July-02-10 3:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I don’t have any good answers for you.

Unfortunately, the interface to the RSG is black magic. I’ve filed a half-dozen 
DCRs over the years trying to get more information about its API, with zero 
success.

You are going to have to move the user back to their original SG and DB on the 
Exchange 2003 server – or use a third party tool (which is going to cost you 
money) such as OnTrack PowerControls.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Friday, July 02, 2010 2:08 PM
To: MS-Exchange Admin Issues
Subject: Using Exmerge after migrating to 2010

As luck would have it, we have a user who needs his mailbox restored from a few 
days before we moved his account from Exchange 2003 to Exchange 2010. We’ve 
been able to restore the required storage group, but when we run Exmerge to 
extract the user’s mailbox into a PST file, it complains about permission 
problems. This link shows the error we’re getting, but the suggested remedies 
don’t really apply, although I did verify just in case.

http://support.microsoft.com/kb/322312

I think the cause of the problem is because the user no longer has a mailbox on 
the 2003 server. I don’t really want to move his mailbox back to 2003, plus I’m 
not even sure if it will solve the problem. Is there some other way to restore 
a legacy mailbox other than using Exmerge?

RE: Using Exmerge after migrating to 2010

[Paul Steele]

That might solve part of the problem, but with our current backup software 
(Networker) we would have to have a working Exchange 2003 server in order to 
recover the Storage Groups…

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: July-02-10 3:37 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

Then look at something like PowerControls. OnTrack isn’t the only vendor with 
this kind of utility (they are probably the most mature solution though). 
Quest, Lucid8, etc.etc. – there are probably 20 vendors that have a utility to 
read mailbox data from a raw database.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Friday, July 02, 2010 2:33 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

That’s what I was afraid of. This whole issue puts a wrench into 
decommissioning our old Exchange server. We have a rule that old data such as 
user mailboxes must be recoverable from backup for at least 3 years. If we 
completely remove the Exchange 2003 server then that won’t be possible 
(assuming we can find a solution to the Exmerge problem). I think we’re going 
to have to just power off the Exchange server and complete the full 
decommissioning process at some time in the future. I *really* wanted to get 
rid of that old server…

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: July-02-10 3:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I don’t have any good answers for you.

Unfortunately, the interface to the RSG is black magic. I’ve filed a half-dozen 
DCRs over the years trying to get more information about its API, with zero 
success.

You are going to have to move the user back to their original SG and DB on the 
Exchange 2003 server – or use a third party tool (which is going to cost you 
money) such as OnTrack PowerControls.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Friday, July 02, 2010 2:08 PM
To: MS-Exchange Admin Issues
Subject: Using Exmerge after migrating to 2010

As luck would have it, we have a user who needs his mailbox restored from a few 
days before we moved his account from Exchange 2003 to Exchange 2010. We’ve 
been able to restore the required storage group, but when we run Exmerge to 
extract the user’s mailbox into a PST file, it complains about permission 
problems. This link shows the error we’re getting, but the suggested remedies 
don’t really apply, although I did verify just in case.

http://support.microsoft.com/kb/322312

I think the cause of the problem is because the user no longer has a mailbox on 
the 2003 server. I don’t really want to move his mailbox back to 2003, plus I’m 
not even sure if it will solve the problem. Is there some other way to restore 
a legacy mailbox other than using Exmerge?

RE: Using Exmerge after migrating to 2010

[Paul Steele]

That's an interesting option. I definitely have some research to do before 
pulling the plug on Exchange 2003!

-Original Message-
From: Rob Sargent [mailto:rbsr...@gmail.com] 
Sent: July-02-10 4:21 PM
To: MS-Exchange Admin Issues
Subject: re: Using Exmerge after migrating to 2010

Quest’s Recovery Manager for Exchange can read the Exchange db right off the 
Networker backup tape without need of an Exchange server.  It can save the mbx 
contents to a pst for importing into the ‘live’ mailbox.  I’ll bet 
PowerControls can do the same.

Quest’s details are here:  
http://www.quest.com/recovery-manager-for-exchange/features-benefits.aspx
I’m not sure about pricing/licensing though.

/Rob

RE: Using Exmerge after migrating to 2010

[Paul Steele]

I guess it's a matter of opinion whether something is too expensive or not. I 
got a quote for our single server, 900 mailbox setup and it was over $6000. 
It's going to be very hard to justify for restoring a single mailbox! We might 
use it once or twice over a few years but it's still too much for something 
that you use so little. I think I'm going to keep looking...

-Original Message-
From: Alice Goodman [mailto:ali...@mckinstry.com] 
Sent: July-02-10 4:54 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I have used Power Controls in a similar fashion as well when we still had data 
on E5.5 tapes and we were a 2003 production shop.  It took me a few days to get 
it to work but I did succeed.   You can get a 30 day eval from them and I did 
not find the cost prohibitive. 

Alice

-Original Message-----
From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, July 02, 2010 12:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

That's an interesting option. I definitely have some research to do before 
pulling the plug on Exchange 2003!

-Original Message-
From: Rob Sargent [mailto:rbsr...@gmail.com] 
Sent: July-02-10 4:21 PM
To: MS-Exchange Admin Issues
Subject: re: Using Exmerge after migrating to 2010

Quest’s Recovery Manager for Exchange can read the Exchange db right off the 
Networker backup tape without need of an Exchange server.  It can save the mbx 
contents to a pst for importing into the ‘live’ mailbox.  I’ll bet 
PowerControls can do the same.

Quest’s details are here:  
http://www.quest.com/recovery-manager-for-exchange/features-benefits.aspx
I’m not sure about pricing/licensing though.

/Rob



This email is the property of McKinstry or one of its affiliates and may 
contain confidential and/or privileged information. If you are not the intended 
recipient or have received this e-mail in error please notify the sender 
immediately and delete this e-mail. 
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

RE: Using Exmerge after migrating to 2010

[Paul Steele]

Quest has a similar product and their pricing is even higher! 

-Original Message-
From: Alice Goodman [mailto:ali...@mckinstry.com] 
Sent: July-06-10 8:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I think we had it since 5.5 days so our pricing was probably better than 
getting a brand new license.. :) 

Alice

-Original Message-
From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Tuesday, July 06, 2010 7:02 AM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I guess it's a matter of opinion whether something is too expensive or not. I 
got a quote for our single server, 900 mailbox setup and it was over $6000. 
It's going to be very hard to justify for restoring a single mailbox! We might 
use it once or twice over a few years but it's still too much for something 
that you use so little. I think I'm going to keep looking...

-Original Message-
From: Alice Goodman [mailto:ali...@mckinstry.com] 
Sent: July-02-10 4:54 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

I have used Power Controls in a similar fashion as well when we still had data 
on E5.5 tapes and we were a 2003 production shop.  It took me a few days to get 
it to work but I did succeed.   You can get a 30 day eval from them and I did 
not find the cost prohibitive. 

Alice

-Original Message-----
From: Paul Steele [mailto:paul.ste...@acadiau.ca] 
Sent: Friday, July 02, 2010 12:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Using Exmerge after migrating to 2010

That's an interesting option. I definitely have some research to do before 
pulling the plug on Exchange 2003!

-Original Message-
From: Rob Sargent [mailto:rbsr...@gmail.com] 
Sent: July-02-10 4:21 PM
To: MS-Exchange Admin Issues
Subject: re: Using Exmerge after migrating to 2010

Quest’s Recovery Manager for Exchange can read the Exchange db right off the 
Networker backup tape without need of an Exchange server.  It can save the mbx 
contents to a pst for importing into the ‘live’ mailbox.  I’ll bet 
PowerControls can do the same.

Quest’s details are here:  
http://www.quest.com/recovery-manager-for-exchange/features-benefits.aspx
I’m not sure about pricing/licensing though.

/Rob



This email is the property of McKinstry or one of its affiliates and may 
contain confidential and/or privileged information. If you are not the intended 
recipient or have received this e-mail in error please notify the sender 
immediately and delete this e-mail. 
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

This email is the property of McKinstry or one of its affiliates and may 
contain confidential and/or privileged information. If you are not the intended 
recipient or have received this e-mail in error please notify the sender 
immediately and delete this e-mail. 
Any unauthorized copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

Uninstalling Exchange 2003

[Paul Steele]

The final step in our Exchange 2010 deployment is uninstalling Exchange 2003. 
I've completed all the other decommissioning steps (deleting routing groups, 
moving Public Folder replicas to the new server, and moving all mailboxes. When 
I try to uninstall Exchange 2003, I get the following error when I select 
"Remove":

Setup encountered an error while checking prerequisites for the component 
"Microsoft Exchange":
0X80072030 (8240): There is no such object on the server.

I found a URL relating to this problem at

http://support.microsoft.com/kb/283089

and have gone through the suggestions on how to resolve it. As far as I can 
tell, there are no mailboxes left on the Exchange 2003 server (I've deleted all 
storage groups in fact). I found some groups that were email enabled which I've 
removed the Exchange attributes from. Unfortunately the problem persists, and 
the log file doesn't give anything useful as far as what condition actually 
caused the error.

Any suggestions on what to look for?

RE: Uninstalling Exchange 2003

[Paul Steele]

It fought a good battle but I eventually got the PF store removed. There are no 
Storage Groups left and as far as I can tell, no users. One thing I did notice 
that has me a bit puzzled is that the 
homeMTA is pointing to the old server (CN=Microsoft 
MTA,CN=EXCHANGE,CN=Servers,CN=First Administrative Group,CN=Administrative 
Groups,CN=Acadia University,CN=Microsoft 
Exchange,CN=Services,CN=Configuration,DC=ad,DC=acadiau,DC=ca) instead of the 
new server (CN=Microsoft MTA,CN=EXCHANGE2,CN=Servers,CN=Exchange Administrative 
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Acadia 
University,CN=Microsoft 
Exchange,CN=Services,CN=Configuration,DC=ad,DC=acadiau,DC=ca). New users get 
the right server, but all the migrated users still have the old value. I was 
wondering if that might be the cause of the uninstall problem. Should I change 
all the homeMTA attributes to the correct value?

RE: Password question

[Paul Steele]

Exchange 2010 OWA definitely provides a mechanism for changing the AD password. 
Not sure about Exchange 2007, and Exchange 2003 OWA does not allow it.

-Original Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov] 
Sent: July-29-10 12:53 PM
To: MS-Exchange Admin Issues
Subject: Password question

Are you able to change your AD password from within OWA?

We have the following situation:

1)  Novell currently handles our authentication, users, e-mail, etc.  We have a 
Windows domain, but it's only for applications.

2)  We are planning a migration from Novell to a new Windows AD domain.

3)  The first stage of this migration is moving from Groupwise to Exchange.  
The plan here is to bring up the AD domain just enough to put users in, and 
install Exchange.  The users would use OWA to access their e-mail.

This brought up a concern for me:  how do users change their AD passwords?  
When the accounts are created initially, we put on a temporary password, and 
let the users change it, but can they do that if the only connection they have 
is OWA?

Using an alias for an Exchange server

[Paul Steele]

Is it possible to set up an alias to use for connecting to an Exchange 2010 
server? For example, if my server's internal name is exch2010.domain.com, I 
would like for users to connect using the alias exchange.domain.com and hide 
the internal server name as much as possible when using Outlook, OWA, and 
ActiveSync. I know that just setting up a DNS alias for the server isn't 
sufficient since there's a certificate involved. Can someone point me to any 
good documentation on this topic?

Thanks!

RE: Using an alias for an Exchange server

[Paul Steele]

Anything online? Believe or not, we can't even afford a new book right now...

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: August-03-10 10:52 AM
To: MS-Exchange Admin Issues
Subject: RE: Using an alias for an Exchange server

"Mastering Exchange Server 2010" by McBee, Elfassy, et. al.

Obligatory Disclaimer: I wrote a couple of chapters for the book. But not the 
ones on this topic (CAS configuration).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, August 03, 2010 9:44 AM
To: MS-Exchange Admin Issues
Subject: Using an alias for an Exchange server

Is it possible to set up an alias to use for connecting to an Exchange 2010 
server? For example, if my server's internal name is exch2010.domain.com, I 
would like for users to connect using the alias exchange.domain.com and hide 
the internal server name as much as possible when using Outlook, OWA, and 
ActiveSync. I know that just setting up a DNS alias for the server isn't 
sufficient since there's a certificate involved. Can someone point me to any 
good documentation on this topic?

Thanks!

RE: Using an alias for an Exchange server

[Paul Steele]

I already have a wildcard certificate so that may be that way I'll go. I sort 
of have things working with my UC cert so I'm happy for now. Hard to play with 
a production server...

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: August-03-10 11:45 AM
To: MS-Exchange Admin Issues
Subject: RE: Using an alias for an Exchange server

As another poster said, the easiest way to do this is with a wildcard 
certificate and then updating the EAS config (using the Set-OutlookProvider 
cmdlet)but if you can't afford a book you probably can't afford a wildcard 
certificate either. :)

On your CAS servers you'll need a SAN that includes the external fully 
qualified domain name (FQDN) you want to use, plus one for autodiscover. Then 
you'll configure each of the virtual directories to use that FQDN. That's 
pretty much the long and the short of it. You'll need to configure the vdir for 
OA, OWA, ECP, EAS, and OAB (and any other TLA you can think of!). :)

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, August 03, 2010 9:58 AM
To: MS-Exchange Admin Issues
Subject: RE: Using an alias for an Exchange server

Anything online? Believe or not, we can't even afford a new book right now...

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: August-03-10 10:52 AM
To: MS-Exchange Admin Issues
Subject: RE: Using an alias for an Exchange server

"Mastering Exchange Server 2010" by McBee, Elfassy, et. al.

Obligatory Disclaimer: I wrote a couple of chapters for the book. But not the 
ones on this topic (CAS configuration).

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, August 03, 2010 9:44 AM
To: MS-Exchange Admin Issues
Subject: Using an alias for an Exchange server

Is it possible to set up an alias to use for connecting to an Exchange 2010 
server? For example, if my server's internal name is exch2010.domain.com, I 
would like for users to connect using the alias exchange.domain.com and hide 
the internal server name as much as possible when using Outlook, OWA, and 
ActiveSync. I know that just setting up a DNS alias for the server isn't 
sufficient since there's a certificate involved. Can someone point me to any 
good documentation on this topic?

Thanks!

RE: Exchange 2010 tools in a Exchange 2003 environment

[Paul Steele]

We just went through the same process. Although it is possible to do an in 
place upgrade of BES and migrate all users at the same time, it complicates 
things. We decided to put in a new BES server in place and migrate users one at 
a time. It made the process easier for everyone. Be warned, you will most 
likely need to involve BES tech support. We were on the line with them many 
times during the switch. A lot of things don't work exactly as documented (also 
known as buggy software). Tech support was able to resolve all the issues 
though.

-Original Message-
From: Martin Blackstone [mailto:mblackst...@gmail.com] 
Sent: August-03-10 1:07 PM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 tools in a Exchange 2003 environment

If you have a valid T-Support contract, you should get the Exchange 2010 
upgrade instructions from them.

-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com]
Sent: Tuesday, August 03, 2010 8:59 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 tools in a Exchange 2003 environment

Brilliant!  Thanks Martin!

-Original Message-
From: Martin Blackstone [mailto:mblackst...@gmail.com]
Sent: Tuesday, August 03, 2010 10:50 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 tools in a Exchange 2003 environment

This is a tough one.
BES does require the Exch 2003 tools, BUT, part of upgrading to Exch
2010
requires you to remove them and run on MAPI/ CDO. This worked fine for my 
Exchange 2003 users. SO, YMMV.
http://www.microsoft.com/downloads/details.aspx?FamilyId=E17E7F31-079A-4
3A9-
BFF2-0A110307611E&displaylang=en


-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com]
Sent: Tuesday, August 03, 2010 8:40 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 tools in a Exchange 2003 environment

We're in the planning stages of going from Exchange 2003 to 2010.  We're also 
wanting to upgrade our BES server to a system running Windows 2008.
BES requires the Exchange Tools to be installed on the server.  Exchange
2003 Tools will not install on Windows 2008.   Will it work to install
the Exchange 2010 Tools on the BES server but still be running Exchange
2003 for now?

Paul

Manual removal of Exchange 2003

[Paul Steele]

Since I was unable to do a properly uninstall of our Exchange 2003 server, I 
followed a Microsoft document on how to do it manually. Everything seems to be 
working ok, although I'm getting a few more errors in the Exchange 2010 log 
than I like to see. Two of the errors involve the SMTP objects that show up 
under the Connections folder in ADSIEDIT. They have names like CN=SMTP 
(EXCHANGE-{FAA12BA2-B5E7-4EC9-9B3A-7EDB53AF3AF3}).  Can these be safely 
deleted. I've also left the old "First Administrative Group" section (although 
I've deleted the reference the Exchange 2003 server). One article I've read is 
that it's safer to not delete the original Administrative Group just in case 
anything still references it. I would rather delete it, but I definitely don't 
want to break anything else.

Any further suggestions about cleaning up after manually removing an Exchange 
2003 server would be appreciated!

RE: [info] Backing up Exchange 2010

[Paul Steele]

We're using a pre-release backup agent for EMC Networker. It does not allow 
backing up/restoring individual mailboxes. We alleviated the problem somewhat 
by breaking our mailbox store into 8 smaller databases. The individual 
databases have already started growing so I may add more to keep sizes at a 
reasonable level. We're not sure what features the full version of the 
Networker agent will have. Restoring individual mailboxes would be a nice 
feature but we have to do it so seldom it's not really a big issue for us.

From: Dan Cooper [mailto:d...@180amsterdam.com]
Sent: August-06-10 4:56 AM
To: MS-Exchange Admin Issues
Subject: [info] Backing up Exchange 2010

Dear All,

Brain picking time...I am currently backup Exchange 2010 using Windows Backup. 
This performs a nice back up of all Stores etc.. We used to use Retrospect to 
backup up our Exchange 2003 which would back up the Databases and 'all' or 
'selected' mailboxes, allowing a very simple restore of a single email back 
into the required mailbox. It does not yet support e2k10.

I was wondering what other Admins out there are using to backup E2k10, and are 
they able to do individual mailbox backup /  single item restores.

Your thoughts, as always are appreciated.

Dan


DISCLAIMER 6-8-2010 9:56:13

This communication is intended only for use by MS-Exchange Admin Issues. It may 
contain confidential or privileged information. If you receive this 
communication unintentionally, please inform us immediately. Thank you. 180  
has registered companies in the United States and in the Netherlands. 180 Los 
Angeles  LLC . (180)  1733 Ocean Avenue, Suite 400, Santa Monica, California 
90401, is registered with the trade register in the US in Delaware under file 
number 4260284 and the corporation's FEIN is 20-5982098. 180 Amsterdam BV (180) 
Herengracht 506, 1017 CB, Amsterdam is registered with the trade register in 
the Netherlands under number 34253037 and VAT number  NL8161.54.673.B.01.  The 
content of this communications is not legally binding unless confirmed by 
letter or telefax. Please note that 180 is neither liable for the proper 
transmission nor for the complete transmission of the information contained in 
this communication or for any delay in its receipt. Also please note that the 
confidentiality of email communication is not warranted. All services and other 
work provided by 180 are subject to our general conditions (supplier terms and 
conditions). The conditions are available for inspection at Herengracht 506, 
Amsterdam and at the Chamber of Commerce in Amsterdam. If you wish to receive a 
hard copy of these conditions, please send an e-mail with your address to 
i...@180amsterdam.com

In the event you send to 180 any unsolicited ideas and/or materials (whether 
consisting of texts, images, sounds, software, information or otherwise) 
("Materials") by e-mail or otherwise, 180 shall be entitled to use, copy and/or 
commercially exploit such Materials to the fullest extent, free of charge and 
180 will not be bound by any confidentiality obligation in respect thereof.

RE: The Future of Exchange Starts Here!

[Paul Steele]

It's very tempting, but I know better than to put a beta service pack on my 
production server.  :-(

-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: August-25-10 1:17 PM
To: MS-Exchange Admin Issues
Subject: The Future of Exchange Starts Here!

I so wanted to share this with y'all a couple of weeks ago...but an NDA is an 
NDA! (And availability dates change all the time anyway...)

The Future of Exchange Starts Here: Exchange Server 2010 SP1 Is Now Available 
http://msexchangeteam.com/archive/2010/08/25/455861.aspx

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

RE: The Future of Exchange Starts Here!

[Paul Steele]

There's a warning on the download page:

"This software is intended for evaluation purposes only. You must accept the 
license terms before you are authorized to use the software. There is no 
product support for this trial software. You are welcome to participate in the 
forums to share your trial experiences with others and to ask for advice."

This implies that Microsoft still considers it beta. I don't really want to 
install a beta SP on a production server, especially if there's going to be an 
official release later this year. What's the deal here???

-Original Message-
From: Greg Olson [mailto:gol...@markettools.com] 
Sent: August-25-10 8:59 PM
To: MS-Exchange Admin Issues
Subject: RE: The Future of Exchange Starts Here!

No it's the full normal release. 
They mentioned they released the beta Sp1 a few months ago and how many have 
been running it in production so that they feel confident in this being a solid 
sp release.
Follow the link and you'll see it says nothing about beta. 
 
-Greg


-Original Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov] 
Sent: Wednesday, August 25, 2010 3:35 PM
To: MS-Exchange Admin Issues
Subject: RE: The Future of Exchange Starts Here!

This isn't a beta SP, is it?  Says the beta was released in June, and half a 
million mailboxes are using it within TAP customers.

>>> Paul Steele  8/25/2010 9:43 AM >>>
It's very tempting, but I know better than to put a beta service pack on my 
production server.  :-(

-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: August-25-10 1:17 PM
To: MS-Exchange Admin Issues
Subject: The Future of Exchange Starts Here!

I so wanted to share this with y'all a couple of weeks ago...but an NDA is an 
NDA! (And availability dates change all the time anyway...)

The Future of Exchange Starts Here: Exchange Server 2010 SP1 Is Now Available 
http://msexchangeteam.com/archive/2010/08/25/455861.aspx 

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com 

RE: Exchange 2010 co-existance in Exchange 2003 environment

[Paul Steele]

If you have a mixed environment (2003 and 2010 servers), the additional tabs 
can still be used to manage your Exchange 2003 servers/users. I don't think 
it's a good idea to do anything with Exchange 2010 users using the ADUC tabs, 
although I know from experience that you can still set things like mailbox 
quota on a 2010 server. When you only have Exchange 2010 servers, the extra 
tabs in ADUC are not really used anymore and you should use the new EMC tool to 
access similar features. I believe it is recommended that you uninstall the 
Exchange management additions to ADUC once you move to 2010...

-Original Message-
From: Maglinger, Paul [mailto:pmaglin...@scvl.com] 
Sent: August-31-10 8:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2010 co-existance in Exchange 2003 environment

So forgive me if I'm missing the obvious here, but when I add my new Exchange 
2010 server into our current Exchange 2003 environment, what happens to the 
Exchange management tabs in ADUC as well as my options in Exchange System 
Manager?  Do I still retain the same abilities using the GUI for the 2003 
server as I always had, but some of the options will be missing when I go to 
the 2010 server?  I'm wanting to go ahead a set up a 2010 server in our 
environment temporarily until we come to a final decision on hardware 
requirements.  I'm just concerned how the changes it makes in AD will affect 
our current ability to manage the servers using the GUI.

-Paul

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Outlook synchronization errors

[Paul Steele]

Ever since we upgraded to Exchange 2010, Outlook users who are using cache mode 
see errors that look like this:

20:45:02 Synchronizer Version 14.0.4734
20:45:02 Synchronizing Mailbox 'Jeffrey Goodine'
20:45:02 Synchronizing Hierarchy
20:45:03 Synchronizing server changes in folder 'Inbox'
20:45:03 Downloading from server 'EXCHANGE2.ad.acadiau.ca'
20:45:0610 item(s) added to offline folder
20:45:061 item(s) deleted in offline folder
20:45:061 view(s)/form(s) updated in offline folder
20:45:06 Synchronizing server changes in folder 'Drafts'
20:45:06 Downloading from server 'EXCHANGE2.ad.acadiau.ca'


I was told that this problem would be fixed in SP1, but after upgrading last 
week users are still reporting the problem. This Technet article seems to 
describe the problem perfectly:

http://blogs.technet.com/b/agobbi/archive/2010/08/04/troubleshooting-error-synchronizing-folder-synchronizing-forms-80004005-501-4b9-560.aspx

Unfortunately the suggestion to remove the PF Replica for the org form doesn't 
work because we only have one server. I tried removing the replica and click 
apply, but the operation fails, presumably because there has to be at least one 
replica.

Does anyone know of another way to solve this problem?


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Time zone problem

[Paul Steele]

We've recently noticed some of our Exchange users have incorrect time zone 
headers in their messages. Their messages look like:

Date: Wed, 29 Sep 2010 13:21:54 +

Instead of

Date: Wed, 29 Sep 2010 10:21:54 -0300

This happens with both Outlook and OWA. The time zone setting on their computer 
is correct, and under the regional settings in OWA are also correct.

Any ideas why some users would be getting this behaviour?


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Time zone problem

[Paul Steele]

After a bit more checking the problem only occurs with Internet bound email, so 
hopefully the patch will fix the problem.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: September-29-10 12:55 PM
To: MS-Exchange Admin Issues
Subject: RE: Time zone problem

Known Transport issue for email leaving an Exchange 2010 environment to the 
Internet.

Most clients (Outlook and OWA included) remap time from the Date header to the 
local timezone prior to display, so it's not commonly seen unless someone is 
looking at email headers. I remember that Yahoo doesn't remap, so it shows up 
there; but Gmail and Hotmail do.

As to why it's "some" and not "all" - I dunno. It should affect all messages 
exiting your environment from Exchange 2010 servers.

(This has nothing to do with the recent timezone patch.)

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Wednesday, September 29, 2010 10:43 AM
To: MS-Exchange Admin Issues
Subject: Time zone problem

We've recently noticed some of our Exchange users have incorrect time zone 
headers in their messages. Their messages look like:

Date: Wed, 29 Sep 2010 13:21:54 +

Instead of

Date: Wed, 29 Sep 2010 10:21:54 -0300

This happens with both Outlook and OWA. The time zone setting on their computer 
is correct, and under the regional settings in OWA are also correct.

Any ideas why some users would be getting this behaviour?


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

OT: Deploying ESXi

[Paul Steele]

We've been using VMware ESXi for test servers for quite a while, but haven't 
put any production virtual servers into place under ESXi. We had a chance to 
deploy Exchange 2010 under ESXi but I wasn't quite ready to take the plunge. A 
new project has come up that requires SharePoint 2007 and SQL Server 2008R2, 
and we're thinking it may be a good time to look at deploying these servers 
under ESXi. This will give us the opportunity to upgrade to SharePoint 2010 
without spending more money on server hardware. We do not have a SAN so we'll 
probably go with two servers with DAS storage, one for the SQL server and 
another for a pair of SharePoint servers.

One thing I was reading about deploying ESXi is that it's a good idea to 
reserve a separate pair of mirrored disks for ESXi and keep all VMs on separate 
disks. This would allow for easier upgrades to ESXi in the future. Are there 
any other tips we should be aware of? Suggestions on using ESXi would be 
greatly appreciated.


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Backup software costs

[Paul Steele]

I don't see MS Backup as an option, although in the case of Networker and 
Windows 2008, its required if you want to do bare metal restores. I'm sure I 
could script something to go with MS Backup, but it definitely wouldn't be as 
good as using Networker. I'm looking for something between free and $500. 
Clients that are buying servers are always very annoyed when I tell them the 
cost of a backup license. They pay $60 for RedHat or $100 for Windows, and 
they're always shocked when they find out they have to spend another $500 for 
the backup software.

Ultimately the purpose of my post was just to confirm that Networker is in line 
with what other people are paying. If that's the case then I guess I'll just 
have to live with it.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: November-29-10 3:38 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup software costs

Likely not.

Be aware of what you are paying for, by the way - you are paying for 
integration.

There is absolutely nothing wrong with the Windows built-in solutions. They 
work well. BUT - to use them in an enterprise environment, you have to script 
quite a bit of integration yourselves. If you know how to do that, and are 
comfortable with doing it, then you can have your solution "for free" - or for 
very low cost.

Purchasing an enterprise-class solution is about risk mitigation. You are 
saying that you trust their programmers more than you trust your capabilities 
to think of everything and get it right. That may - or may not depending on the 
solution - be a reasonable choice.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Jim Holmgren [mailto:jholmg...@xlhealth.com]
Sent: Monday, November 29, 2010 2:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Backup software costs

Our costs for CommVault are pretty much in line with the numbers you are 
posting for Legato.  I don't think you'll find a much less expensive 
enterprise-class backup solution.

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Monday, November 29, 2010 2:26 PM
To: MS-Exchange Admin Issues
Subject: OT: Backup software costs

We've been using Legato (now EMC) Networker for 10+ years. It's not the most 
user friendly application I've seen but it seems to work well. One complaint I 
have though is the cost, and I'm curious what other people are paying (for both 
Networker and other backup software). We currently pay about $500 (Cdn) for one 
standard client license. The price is even higher (over $1000) if we have to 
back up application servers like SQL, SharePoint, or Exchange. We're seriously 
considering moving to another product, but only if the per server cost isn't so 
high. Bakula is another option, but I'm not sure I want to rely on an open 
source product for such a critical need.

If others would like to give me some approximate pricing they're paying for 
backup software, that would be great.

Thanks!


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use 
of the intended recipient(s) and may contain confidential and/or protected 
health information. Under the Federal Law (HIPAA), the intended recipient is 
obligated to keep this information secure and confidential. Any disclosure to 
third parties without authorization from the member of as permitted by law is 
prohibited and punishable under Federal Law. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message.

NOTA DE CONFIDENCIALIDAD: Este mensaje incluyendo cualquier anejo es para uso 
exclusivo del (los) destinatario (s) y puede incluir informaci?n confidencial 
y/o informaci?n de salud protegida. La Ley Federal (HIPAA) establece que el 
destinatario est? obligado a mantener la informaci?n confidencial y sequra. 
HIPAA proh?be y castiga cualquier divulgaci?n a terceras personas sin 
autorizaci?n del afiliado o permitido por ley. Si usted no es el destinatario, 
redirija esta mensaje al remitente, y destruye cualquier copia existente del 
mensaje original.

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Using wildcard certs with Win Server 2008R2

[Paul Steele]

I've done very little with certs in Windows, and have never used the MMC for 
installing certs (or creating) certs. I think I've got the process figured out. 
Won't know for sure until the SharePoint install...

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: January-26-11 11:31 AM
To: MS-Exchange Admin Issues
Subject: RE: Using wildcard certs with Win Server 2008R2

If you install the cert using the MMC, the process hasn't changed since the NT 
4.0 option pack.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Wednesday, January 26, 2011 9:59 AM
To: MS-Exchange Admin Issues
Subject: OT: Using wildcard certs with Win Server 2008R2

We have a Digicert wildcard cert which we've been using primarily with Apache 
installations under Linux. We'd like to try using it on a Windows Server 2008R2 
system as part of a SharePoint 2007 install, but finding documentation on 
installing wildcard certs with Server 2008R2 isn't easy. I found one link that 
applies to Server 2008, but it doesn't match the 2008R2 process exactly. Can 
anyone point to some good documentation on this topic?

Thanks!


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: RBLs

[Paul Steele]

We also use Trend along with SpamHaus...

From: Don Andrews [mailto:don.andr...@safeway.com]
Sent: February-10-11 6:32 PM
To: MS-Exchange Admin Issues
Subject: RE: RBLs

Trend's ERS - used to be MAPS.  Not free if that's important.


From: Bill Songstad [mailto:bsongs...@gmail.com]
Sent: Thursday, February 10, 2011 1:34 PM
To: MS-Exchange Admin Issues
Subject: OT: RBLs

I started using SpamCop and spamhaus a while ago to keep my spam filter from 
bursting into flames, and the results were fantastic, until recently when about 
80 of Gmails servers wound up on SpamCops Block list.  Sure the expire hourly 
if they stop spamming the spamtraps, but I'm missing 5-10 out of 100 emails 
from gmail that I'm aware of.  Not good.

My question:  What block lists are you all using?  Management says Spamcop has 
to go.  Gmail is more important.  But I really liked the sense of quite I got 
from running both blocklists.

Thanks for any feedback,

-Bill

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

OT: Upgrading from 2003R2 to 2008R2

[Paul Steele]

One of our summer tasks is upgrading a couple of servers from 2003R2 to 2008R2, 
using existing hardware. The servers are only used for file sharing so the 
upgrade is pretty simple except for one issue. Both servers have close to 1000 
gigs of shared data on drive D (accessed via shares). In order to avoid a 
lengthy restore process, would it be reasonable to reinstall 2008R2 into the 
existing C partition while leaving the existing D partition intact? I tried the 
process on a test server and the old 2003R2 drive D partition worked fine under 
2008R2. I had to recreate the shares and name spaces, but the NTFS file rights 
within the shares were retained. Seems like a great way to avoid a 10+ hour 
tape restore.

Is there any reason why this approach isn't a good idea?


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Upgrading from 2003R2 to 2008R2

[Paul Steele]

I figured there would be some NTFS differences and I'll have to look into 
those, but at this point the 2003R2 NTFS version should be sufficient for our 
needs. We're more interested in getting the File Server Resource Manager 
upgraded to allow management from Windows 7 systems. Plus we just want to start 
phasing out our older 2003 systems and move everything to 64-bit...

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: March-08-11 7:08 PM
To: MS-Exchange Admin Issues
Subject: RE: Upgrading from 2003R2 to 2008R2

You are aware that 2008 R2 is 64-bit only, right?

That aside, what you suggest is fine. Although, you won't get the benefit of 
aligned volumes and larger default allocation units.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, March 08, 2011 2:56 PM
To: MS-Exchange Admin Issues
Subject: OT: Upgrading from 2003R2 to 2008R2

One of our summer tasks is upgrading a couple of servers from 2003R2 to 2008R2, 
using existing hardware. The servers are only used for file sharing so the 
upgrade is pretty simple except for one issue. Both servers have close to 1000 
gigs of shared data on drive D (accessed via shares). In order to avoid a 
lengthy restore process, would it be reasonable to reinstall 2008R2 into the 
existing C partition while leaving the existing D partition intact? I tried the 
process on a test server and the old 2003R2 drive D partition worked fine under 
2008R2. I had to recreate the shares and name spaces, but the NTFS file rights 
within the shares were retained. Seems like a great way to avoid a 10+ hour 
tape restore.

Is there any reason why this approach isn't a good idea?


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: [OT] Friday Funny

[Paul Steele]

I have yet to get a Facebook account, and after watching the Social Network I 
have even less desire. I still use email...

From: pdw1...@hotmail.com [mailto:pdw1...@hotmail.com]
Sent: March-19-11 10:52 PM
To: MS-Exchange Admin Issues
Subject: RE: [OT] Friday Funny

It does have its uses, though. Through it, I can keep in touch with my nephew 
who lives in Tokyo. Luckily, he was nowhere near where the tsunami hit but he 
did feel some tremors from the after-shocks.

> From: mailvor...@gmail.com
> Date: Fri, 18 Mar 2011 22:24:17 -0400
> Subject: Re: [OT] Friday Funny
> To: 
> exchangelist@lyris.sunbelt-software.com
>
> On Fri, Mar 18, 2011 at 9:42 PM, Micheal Espinola Jr
> mailto:michealespin...@gmail.com>> wrote:
> > This highlights many reasons why I hardly use facebook anymore.
>
> The block/ignore feature is essential.
>
> (Assuming you find *some* of the people you know on Facebook worthwhile.)
>
> -- Ben
>
> ---
> To manage subscriptions click here: 
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to 
> listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe exchangelist
---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: OABvalidate

[Paul Steele]

I'm not familiar with dgoldman's blog. Most of the Google hits I got said that 
only Microsoft support can offer it.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: March-22-11 10:46 AM
To: MS-Exchange Admin Issues
Subject: RE: OABvalidate

Can't it be downloaded from dgoldman's blog?

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, March 22, 2011 9:41 AM
To: MS-Exchange Admin Issues
Subject: OABvalidate

Is there any way to get a copy of oabvalidate.exe without opening a case with 
Microsoft Support? We're getting OABGEN errors and after lots of Google 
searches it looks like OABvalidate.exe along with OABinteg.exe is what's needed 
to fix the problem. Seems like a unneeded expense to open a support call just 
to get a file...


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: OABvalidate

[Paul Steele]

I guess I have come across his blog concerning this issue. This is a relative 
old posting and I'm still not sure if I can ignore the oabgen errors or not. I 
don't think they're causing our users any problems but I don't like getting 
weird errors in the Event log...

http://blogs.msdn.com/b/dgoldman/archive/2009/12/01/please-read-events-9320-and-9359-on-new-installation-of-exchange-2010.aspx

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: March-22-11 10:54 AM
To: MS-Exchange Admin Issues
Subject: RE: OABvalidate

Dgoldman is the guy that wrote it. He has (had? - not sure) primarily 
responsibility for OABs. He has an extensive blog on OAB issues.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, March 22, 2011 9:51 AM
To: MS-Exchange Admin Issues
Subject: RE: OABvalidate

I'm not familiar with dgoldman's blog. Most of the Google hits I got said that 
only Microsoft support can offer it.

From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: March-22-11 10:46 AM
To: MS-Exchange Admin Issues
Subject: RE: OABvalidate

Can't it be downloaded from dgoldman's blog?

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Tuesday, March 22, 2011 9:41 AM
To: MS-Exchange Admin Issues
Subject: OABvalidate

Is there any way to get a copy of oabvalidate.exe without opening a case with 
Microsoft Support? We're getting OABGEN errors and after lots of Google 
searches it looks like OABvalidate.exe along with OABinteg.exe is what's needed 
to fix the problem. Seems like a unneeded expense to open a support call just 
to get a file...


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist