camm.id.au

Can’t really explain this recipientfilter issue, it just looks weird maybe.

Doesnt work

-RecipientFilter {((IsShared -eq $false))}

Works

-RecipientFilter {((-not(IsShared -eq $true)))}

You are an Exchange administrator, and a user reports that when they attempt to attach a file using Outlook Web Access, they receive the message:

The following files weren’t attached because they exceed the maximum size limit for attachments (5 MB)

You check all the message limits that you can think of, send connectors, receive connectors, web.config file for OWA, and transport config, but you still can’t see the source of the attachment limit.

When you run the get-transportconfig command on your Exchange server, you notice that the “MaxSendSize” and “MaxReceiveSize” is set to unlimited. Like any english speaking person, you assume that the term “unlimited” means, without limits. Well, that’s where you’ve gone wrong….

Turns out that Microsoft speaks a different language. The term “unlimited” when running the get-transportconfig command on Exchange 2010 SP1 or possibly earlier versions, actually means that there is no limit set. When OWA reads this, it doesn’t quite know how to handle that, so it uses the default attachment limit.

If you’re having the above problem. Try setting the limit. If you want this to be unlimited, just set it to a really high number, for instance 1024MB

 set-transportconfig -maxreceivesize:1024MB -maxsendsize:1024MB 

You will need to wait for your the cached message limits to expire, or manually restart the Exchange Information Store service on your servers for this setting to take effect.

After setting up my lab environment for my MCTS Exchange 2010 examination preperation, I decided to play a little bit and get a Lync server trial set up in my lab, and integrate it with the Client Access server I had just deployed.

For those who are not familiar with Microsoft Lync, it’s a SIP Communicator product from Microsoft, consisting of a SIP back-end with a instant messaging client front-end (kind of like MSN Messenger, but not..). Lync can integrate with all sorts of things like; cisco phone systems, and of course: Exchange.

Here are some example images of the client running under Windows 7:

Lync Client on Windows

Lync Chat Window

So, anyway.. Integrating it in to Exchange wasn’t too difficult. I won’t go in to the procedure here, but one thing I will mention for those who attempt to install this – make sure that you pay attention to your client access servers certificate CN, this must match the trust name you set up in Lync!

So, upon logging in to the OWA interface. There are some new items.

1. An instant messenger status box on the top right hand (appears as a green square when you are online)
2. A contact list underneath your mail folders showing your online contacts

Lync Integrated OWA Home

You can control your status from that drop down menu in the top right.

OWA Lync Control Status

When someone sends you an IM, it appears as a popup similar to the new interface popup for emails in exchange 2010 OWA.

Received Message

Clicking on the new message brings up a list of your current chats.

List of Active Chats

You can then click on one of your active chats and it will load up a chat window, where you can ofcourse, return a message or two.

Lync OWA Message Window

The other pretty cool thing about the Lync OWA integration is when you receive an email from someone, their IM status appears in the email window (indicated by the green square again for online status).

Received Email

Instead of replying to their email, you can initiate an IM chat.

Received Email - Online Contact Chat

As you can see, it integrates pretty seamlessly..

This is not actually specific to BackupExec according to http://support.microsoft.com/kb/2476973

However, when performing a back up of an Exchange System, you may receive:

Event 2168, MSExchangeRepl
“Log file ‘L:\XXX\XXXXXXXXXXX.log’ for database copy ‘XXX\XXXXXX’ couldn’t be read. Error: File ‘L:\XXX\XXXXXXXXXXX.log’ could not be opened. The process cannot access the file because it is being used by another process”

This is fixed in “Update Rollup 3 for Exchange Server 2010 Service Pack 1″, but its definitely possible (according to our environment) that this can cause hit and miss backups/backups to fail.