Here’s a quick command that will set the amount of days your lagged database is lagged for Set-MailboxDatabaseCopy –Identity “DatabaseNameServerName” –ReplayLagTime “7.0:0:0” The Above command will set a lag retention of 7 days, but change the days to what you need (Please note the Maximum is 14 Days)
You receive the error below when attempting to login to Outlook Web Access (OWA). In an environment with multiple Client Access (CAS) servers where CAS proxying is being used: Solution: On the target CAS server, Ensure that Windows Integrated Authorisation is the only the authorisation method enabled on the OWA and ECP virtual directories.
Just a quick post to let you know how you can get the lag times that are set on the databases if you have any configured in your DAG: Get-MailboxDatabase –Identity dbname -Status | Format-List replaylagtimes This should output something similar to this: Hope this helps Paul
Just a very quick blog to let you know how you can force an Object Discovery instead of waiting the desired amount of time specified in the Discovery rule which can sometimes take up to 24 hours. You can just restart the “System Center Management” service and the discovery will kick in straight away
Pure-IP seem to be going from strength to strength. Not only did they get on MS’ Interoperability site a few weeks back but it looks as though NET (Network Equipment Technologies) are happy to sing their praises as well. http://www.marketwatch.com/story/network-equipment-technologies-announces-support-for-pure-ips-business-sip-trunking-service-2011-09-06 Good luck NeilC
Microsoft have released an update to some of the Lync server documentation. For full details have a look at the following URL: http://blogs.technet.com/b/nexthop/archive/2011/09/20/lync-server-2010-documentation-update-september-2011.aspx Good luck NeilC
We had an issue recently when we migrated some exchange 2003 mailboxes onto an Exchange 2010 (Please note Exchange 2010 was SP1) Environment. Basically after the migration all migrated users using Outlook in online mode could only see a blank Global Address List. After looking into the issue we found that the resolution was to …
We came across an issues recently where one of our Exchange servers in a DAG started having the below errors appear in it’s Event Log. Event ID 5301 Detected catalog corruption for database Database1 Event ID 123 At ’9/20/2011 3:17:57 PM’ the Microsoft Exchange Information Store Database ‘Database1’ copy on this server experienced a corrupted …
We were having a few SCOM alerts each day to inform us that the anti spam updates that usually come through Windows Update were failing to install on a customers Exchange 2007 server that was running on Windows Server 2008 SP1. Looking in the c:WindowsWindowsUpdate.log file I could see that there was an error with …
In the Exchange 2010 Management Console, mailbox databases do not display any information in regards to the number of mailboxes stored within them. Below is a command which can be run in the Exchange Management Shell to retrieve this information: (Get-MailboxDatabase) | ForEach-Object {Write-Host $_.Name (Get-Mailbox -Database $_.Name).Count}