EWS Beta and SP1 rollup 4

J

janastasiou

Version: 2008
Operating System: Mac OS X 10.5 (Leopard)
Processor: Intel
Email Client: Exchange

For roll up 4, is it an issue if the patches from roll up 4 are installed individually or does roll up 4 need to be installed.

My company installed the patches as they come in individually and do not wait for the roll ups.
 
C

Corentin Cras-Méneur

For roll up 4, is it an issue if the patches from roll up 4 are
installed individually or does roll up 4 need to be installed.


From what I read, you even need Rollup 5...
My company installed the patches as they come in individually and do not
wait for the roll ups.


What really matters is that all the issues that were fixed up to rollup
5 have been fixed on the server. If there is a way to get the fixes
without installing the rollup, that's what really matters.

Corentin
 
J

janastasiou

Well after a discussion with my company's IT team it appears they patch the servers on a weekly basis with the latest updates from Microsoft.

I've tried connecting but it will not synch down my inbox and if for example i try to check the properties of my exchange account such as my storage capacity and stats it will complain saying it can't connect to the exchange server.
 
C

Corentin Cras-Méneur

Well after a discussion with my company's IT team it appears they patch
the servers on a weekly basis with the latest updates from Microsoft.


Good.
There is a way to sort of check too. If you connect through OWA, you can
see an Option link on the top right corner.
In the Option page, on the pane on the left, there is an About link
displaying tons of info about your configuration.

Mine indicates Outlook Web Access version: 8.1.336.0, which is Exchange
2007 (8), SR1 (.1), rollup 5 (build 336.0)
I've tried connecting but it will not synch down my inbox and if for
example i try to check the properties of my exchange account such as my
storage capacity and stats it will complain saying it can't connect to
the exchange server.

Well there could be tons of possibilities why it can't connect at this
point.
Did you try connecting to the front-end server instead of the backend
one for instance (or vice versa)??

Corentin
 
J

janastasiou

Mine has OWA version at 8.1.340.0, i have no problems accessing this through my browser.

Client access server version is at 8.1.240.0.

with entourage 2008 12.1.5 i can connect to version 8.1.240.0 but not to 8.1.340.0.

The path i use to connnect successfully is melexhange01.xxx.local and it connects fine.

using <https://melxchange01.xxx.local/owa> doesn't connect via entourage.
 
T

thompson.trey

Mine has OWA version at 8.1.340.0, i have no problems accessing this through my browser.

Client access server version is at 8.1.240.0.

with entourage 2008 12.1.5 i can connect to version 8.1.240.0 but not to 8.1.340.0.

The path i use to connnect successfully is melexhange01.xxx.local and it connects fine.

using <https://melxchange01.xxx.local/owa> doesn't connect via entourage.

Try using this path instead:

https://melxchange01.xxx.local/exchange/<youremailaddress>
 
C

Corentin Cras-Méneur

Mine has OWA version at 8.1.340.0, i have no problems accessing this
through my browser.

Client access server version is at 8.1.240.0.

with entourage 2008 12.1.5 i can connect to version 8.1.240.0 but not to
8.1.340.0.

Entourage 12.1.5 and EWS have different needs. 12.1.5 needs WebDAV
access (basically, OWA without crazy scripts or cookie-based
authentucation). EWS uses Web Services.
I am in the same situation. I can't connect to the back-end through EWS,
and I can't conenct to the front-end through 12.1.5.

Corentin
 
Top