Microsoft Exchange and Active Directory Blog
Exchange Web Services (EWS) are becoming increasingly important. With the EWS, applications are able to access many of the Exchange functions. The EWS interface has been implemented since Exchange 2007. I know many applications that still access Exchange via MAPI, all these applications will no longer be Exchange 2013 compatible, as the protocol will only be ... Read more
Some time ago I already described a problem with the value "MailNickname", which leads to the address lists not being updated. The same problem can occur with e-mail activated public folders. The background is that in Exchange 2003 times the mail nickname (alias) was still allowed to contain special characters such as spaces etc.. With Exchange 2010 ... Read more
Exchange 2010 cannot send mails to Exchange 2003 if it is not authorized to do so. In this case, the queue of the routing group is full with the following error: 451 4.4.0 Primary target IP address responded with: "421 4.4.2 Connection dropped due to SocketError." The problem can be solved by changing the IP address of the Exchange 2010 server on the ... Read more
WARNING: The OWAEnabled property of mailbox 'Mailbox' is not in a consistent state. Reset the OWAEnabled property using the Set-CASMailbox cmdlet. WARNING: Unexpected error. A Watson image is generated: The value 'HTTP§1§1§§§§§§' already exists in the collection... The value 'HTTP§1§1§1§§§§§§' already exists in the collection. + CategoryInfo : NotSpecified: (:) [Set-CASMailbox], InvalidOperationException + ... Read more
Service Pack 3 for Exchange 2010 has been released. The SP3 was probably most eagerly awaited for the migration or coexistence with Exchange 2013. However, we still have to wait for the CU1 for Exchange 2013. The SP3 can be downloaded here: http://www.microsoft.com/de-de/download/details.aspx?id=36768 The CU1 for Exchange 2013 is also expected this quarter. So still ... Read more
I have already described the same error message here: https://www.frankysweb.de/?p=1041 However, there seems to be another problem causing the same error: Source: MSExchange ADAccess ID: 2114 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2588). Error during topology detection. Error: 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Search for information on the LDAP (Lightweight Directory Access Protocol) error code specified in the event description. Use ... Read more
Sometimes users complain that they have not received a certain e-mail. There can be many reasons for this. From time to time, junk mail rules configured by the user are also the reason. Fortunately, in addition to the mailbox rules, the junk mail rules can also be managed from the management shell. To view the rules ... Read more
Today I came across a rather interesting archiving software. The software archives mails from the Exchange Server, is also compatible according to the manufacturer, but cannot handle a journal mailbox. The software has to access the users' mailboxes via POP or IMAP and requires read and write access to the users' mailboxes. The manufacturer of the software ... Read more
The following script can be used to determine all users with Active Sync devices. The data is then written to a CSV file. #Ppath to the CSV file for the export $exportfile = "c:\export.csv" #Name of a mailbox database or "all" to capture all mailbox databases $database = "all" #--------------------- "User;Type;Serial number;Status" | set-content "$exportfile" if ($database -eq "all") ... Read more
"Bring-your-own-device" has long since become the standard in many companies, perhaps even unconsciously. A correctly configured Exchange Server is very sociable and makes it easy for users to connect any number of devices. Even less experienced users can synchronize their private smartphone with the company's Exchange Server via ActiveSync. However, this is not entirely uncritical. Private ... Read more
