Prev: Writing Exchange 2003 DR documentation
Next: default user in "manage full access permission"
From: IT on 26 Apr 2010 06:59
This is caused by Outlook 2003 not encrypting traffic bewtween Exchange server and client and Exchange 2007 only accepting encrypted traffic by default. Running the cmdlet Set-RpcClientAccess ?Server <Server Name> ?EncryptionRequired $False on your CAS server will resolve the issue. Ken, you have changed it to True not False which is probably why it isn't working.

This worked great for me.

Cheers

Andy




Matt Scott wrote:

urs03sbeltheyofne workss topened2003.$TrueHi Ken.
22-Apr-10

ur
s
03
s
be
l
they
of
ne work
ss to
pened
2003.
$True

Hi Ken. I am having this exact same problem after a 2003 to 2010
migration. Have you had any luck resolving it?

Thanks,
Matt

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Crypto Obfuscator for .NET - Product Review
http://www.eggheadcafe.com/tutorials/aspnet/bf15c41b-6510-403e-9af8-f5fd987fafb1/crypto-obfuscator-for-ne.aspx
 | 
Pages: 1
Prev: Writing Exchange 2003 DR documentation
Next: default user in "manage full access permission"