Wednesday, July 30, 2008
OCS / Communicator - Cannot Synchronize Address Book
Although there are lots of reasons for this error appearing, including problems with the Web Server itself, or a corrupt file, one solution that keeps cropping up in a LAN environment is that the OCS Address Book server is not in the "Bypass proxy for" part of internet explorer. In this case, the Communicator client tries to connect to the address book server via a proxy server, which may need authentication, and therefore fails
Although there are lots of reasons for this error appearing, including problems with the Web Server itself, or a corrupt file, one solution that keeps cropping up in a LAN environment is that the OCS Address Book server is not in the "Bypass proxy for" part of internet explorer. In this case, the Communicator client tries to connect to the address book server via a proxy server, which may need authentication, and therefore fails
Thursday, July 24, 2008
Strange problem sending an email as attachment in a task Outlook 2007 / Exchange 2007 / Forefront for Exchange SP1
Strange problem.... if Forefront is configured to block TNEF files in the wild card file filtering, and somebody sends a task to somebody else, and in the task there is an attachment, and in the attachment there is a full stop (.) in the subject, it gets rejected. Work that one out.
Strange problem.... if Forefront is configured to block TNEF files in the wild card file filtering, and somebody sends a task to somebody else, and in the task there is an attachment, and in the attachment there is a full stop (.) in the subject, it gets rejected. Work that one out.
Labels: TNEF Forefront Exchange Outlook subject full stop point .
Wednesday, July 23, 2008
Cannot delegate calendar to shared mailbox or mail non-universal group -Exchange 2007
Strange problem with Outlook 2007 users running against an Exchange 2007 server. Outlook 2000 users were not affected by the problem.
If a user tries to delegate their calendar (or grant other types of permissions) to either a shared mailbox or a global mail-enabled security group, they cannot. When they try to select the object, it is marked with a red cross. This is because shared mailboxes are normally associated with a disabled user, or because exchange 2007 does not support non-universal groups. Fix? Change the mailboxes back to normal user mailboxes with the set-mailbox -recipienttype:regular (or even a get-mailbox -recipienttypedetails:shared set-mailbox -recipienttype:regular). As for the groups. I manually changed them to universal groups, and they're all working now
Strange problem with Outlook 2007 users running against an Exchange 2007 server. Outlook 2000 users were not affected by the problem.
If a user tries to delegate their calendar (or grant other types of permissions) to either a shared mailbox or a global mail-enabled security group, they cannot. When they try to select the object, it is marked with a red cross. This is because shared mailboxes are normally associated with a disabled user, or because exchange 2007 does not support non-universal groups. Fix? Change the mailboxes back to normal user mailboxes with the set-mailbox -recipienttype:regular (or even a get-mailbox -recipienttypedetails:shared set-mailbox -recipienttype:regular). As for the groups. I manually changed them to universal groups, and they're all working now
Labels: calendar delegate permissions shared mailbox outlook 2007 exchange
Tuesday, July 01, 2008
0x80050014 - Server-sided Active Sync
Yes, I've followed article http://support.microsoft.com/kb/817379 and no, I still can't sync over the wire. I'm running a front-end/back-end scenario. (With multiple back-end servers and some are working fine)
Solution: On the back-end server make sure that the /exchange directory has BASIC and Integrated Windows Authentication checked. For some reason the IWA was missing on one server :-(
p.s. download the virtual images of Windows Mobile, this helps in troubleshooting and means you don't have to hard-reset your own device when testing... go here
Yes, I've followed article http://support.microsoft.com/kb/817379 and no, I still can't sync over the wire. I'm running a front-end/back-end scenario. (With multiple back-end servers and some are working fine)
Solution: On the back-end server make sure that the /exchange directory has BASIC and Integrated Windows Authentication checked. For some reason the IWA was missing on one server :-(
p.s. download the virtual images of Windows Mobile, this helps in troubleshooting and means you don't have to hard-reset your own device when testing... go here
Labels: 0x80050014 80050014 817379 active sync
