Tag Info

Hot answers tagged

4

Interesting question. I've never dealt with it directly (restoring that far back) to care what happens to the OST files, so I found this article online: http://searchexchange.techtarget.com/answer/What-happens-to-ost-files-after-restoring-an-Exchange-backup To sum up what Brien thinks would happen: The contents on the Exchange server will be ...


3

Pick a name that matches your current naming convention.


2

First off, you can use the great info here: http://penetrateit.wordpress.com/2012/02/11/exchange-2010-balancing-the-number-of-mailboxes-and-average-size-across-all-databases/ to figure out some stats needed to help balance the mailboxes across databases. Or you can use Steve's script here: http://www.stevieg.org/2010/09/balancing-exchange-databases/ ...


2

Thanks for these commands. Here's what I ended up using to find rules that wholesale forward or redirect... foreach ($i in (Get-Mailbox -ResultSize unlimited)) { Get-InboxRule -Mailbox $i.DistinguishedName | where {$_.RedirectTo -or $_.ForwardTo -and -not ($_.description -match "If the message") } | fl MailboxOwnerId,Description >> rules.txt } ...


2

You create a new Database and then Move the mailboxes over. In EMC, right click mailboxes and choose "New Local Move Request", then work the wizard. Or use EMS and use e.g.: Get-Recipient | where {$_.ServerName -eq "<servername>"} | New-MoveRequest -TargetDatabase <targetdbname> after moving all mailboxes, you can start decommissioning the ...


1

According to the results from Microsoft's Remote Connectivity Analyzer, there is a problem with your autodiscover service, which is the service used by Outlook to automatically locate your Exchange server. Autodiscover is a web service running on your Exchange server, and it should be published to the Internet just like OWA and all other Exchange web ...


1

I finally found the answer to my question after logs of googling. Yes, this will affect the archive as well, so we're reevaluating our policy.


1

I found that we'd get this error where a mailbox had been moved to another database (leaving a soft deleted mailbox in the the database) and then the moved mailbox had also been disabled. The guid given couldn't be found using get-mailbox (becasue the mailbox has been disabled) but both the disabled and the soft-deleted mailboxes could be found using ...


1

Step by step guide to export exchange server mailbox to higher version. http://exchangeserverstips.wordpress.com/2013/12/16/steps-to-move-exchange-server-mailbox-to-higher-version/


1

There are also commands such as "New-RemoteMailbox" and "Enable-RemoteMailbox" which can be run from OnPrem powershell (Exchange Shell) to create a 365 mailbox directly on the cloud while also associating it to an AD Account. Check it out.


1

Came across this while searching to do the same - you can use the EWS Access policies, good article here: http://blogs.technet.com/b/matabra/archive/2012/08/23/block-mobile-apps-that-use-exchange-web-services.aspx


1

You could use one of two methods, both require some input/work from the end user and the IT staff. Option 1: Use Outlook Rules and apply a rule that states that when an email is received from HR to not forward it (whether by OOF or some other means). The problem here, is that you have to leave Outlook running on the users computer for the rule to function ...


1

Exchange server enters back pressure mode and refuses external mail when available disk space drops to around 2%. If there is no obvious reason for your server to be running out of space, check that your backups are running properly as otherwise your exchange transaction logs will eventually fill your disk.


1

Report messages that will be deleted using something like this. it will create a report in the target folder. If you remove -LogOnly it will copy the messages to the folder. This REALLY helps with verification: Search-Mailbox -identity user@domain.net -SearchQuery "Sender@domain.com" -TargetMailbox admin@domain.net -TargetFolder searches -Logonly Then ...


1

Found the root of the problem. We updated our firewalls last week and upon update the default security filtering profile from WAN -> LAN changed to include SSL filtering, as such it resigns all SSL traffic and used the default SSL certificate, which was signed by our internal CA. Sometimes it's the simple things...



Only top voted, non community-wiki answers of a minimum length are eligible