Look at it the other way round: your BES activation was being slowed down by
something else killing Exchange. I’ve never known an Enterprise Activation to
do that sort of thing to an Exchange Server – but I guess that’s not to see it
hasn’t happened! Next time, cancel the Activation and see if E
All -
Environment: Single exchange2k3 SP2 server. AD 2003 R2. BES server: 4.1.6
I was troubleshooting an issue this morning where most outlook users were
receiving the infamous "Outlook is trying to retrieve data". I opened
perfmon and almost fell out of my chair: I noticed the RPC Averaged Laten
If you mean, ESM, Administrative Groups, '2003 Servers', Folders, Public
Folders, Properties, 'Public Stores Associated to the folder tree:' - then the
new server is already listed there.
Also, under connectors under both the 2003 server group and the new Exchange
Administrative group there is
I was referring specifically to adding the exchange 2010 server to the
replication list of the public folders, using esm on 2003 instead of powershell
or emc on 2010.
-Original Message-
From: Brad Metzler [mailto:bmetz...@cu-portland.edu]
Sent: Tuesday, February 02, 2010 11:23 AM
To: MS
Michael,
What specifically do you mean by "add" the server? If I open the ESM on the
Exchange 2003 server, I do in-fact see the new administrative group and the new
2007 server under that group.
Brad
-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Tuesd
The 2010 server is listed on all Replication pages of the OAB folders on the
Exchange 2003 server. There are 4 different OABs listed: Two version 2, one
with 688 KB and one with 0 KB, one version 3a and one version 4. On the version
3a and version 2 with 688 KB size clicking on properties retu
Have y’all tried adding the server using ESM on the Exchange 2003 server?
From: chipsh...@comcast.net [mailto:chipsh...@comcast.net]
Sent: Tuesday, February 02, 2010 8:50 AM
To: MS-Exchange Admin Issues
Subject: Re: Evil OAB message 0x8004010F
I don't have a solution for you. I just stopped by
We are on Ex2003, so not sure of autodiscover.
The advantage of keeping the cerificate to ourselves and not publishing
it means we can stop non work supplied devices being used to sync
emails.
Some more investigation needed.
john
-Original Message-
From: Michael B. Smith [mailto:mich...@
I don't have a solution for you. I just stopped by to commiserate. I am going
through the exact same thing with a 2003>2010 migration. Error messages are
just about identical along with the attempted steps to resolve. It's as much
fun as sticking pencils in my eye. PSS is in my very near futur
With autodiscover on Exchange 2007+, the user just needs to know their email
address and password. I think that was in WM 6.1. I know it's in WM 6.5.
I can't help you with "pre-installing a certificate", but you can certainly
make the certificate available on a website and have them hit the webs
Is it possible to preconfigure ActiveSync Email on a Windows
Mobile(WM6.x) device so when a user starts up active sync all they need
to enter is their password.
Currently we have to arrange with the user to get the device, then
install a certificate, get the users password or change it, and set it
11 matches
Mail list logo
