Hot answers tagged

7

I haven't done any O365 migrations, but here's what I'd say about it. The 72 hour "warning" is a bit of misinformation. It will take the amount of time related to the TTL of the MX record, whether that's 1 hour or 72 hours. It's based on the TTL, not some antiquated misinformation about DNS record changes. If the TTL for your MX record is 1 hour thenm it ...


5

The MX record will only affect mail delivery for your SMTP domain; client configuration is up to you and totally independent from it. When the MX change will be fully propagated, all mailservers sending messages to your domain will send them to Exchange Online, instead of your current mail server. That's it. Also, the 72 hours delay is related to DNS ...


4

By default, when you configure your domain @domain.com in your email system, they typically assume they are completely authoritative for the entire namespace. In other words, they are the ultimate authority on whether to accept and deliver mail addressed to <anyone>@domain.com. In this scenario, you have two independent email systems, with different ...


4

Deleting the mailboxes isn't going to reduce the size of the mailbox database file. You need to perform an offline defrag of the mailbox database to shrink the file. You might be better off moving all mailboxes to a new mailbox database and removing/deleting the original mailbox database, if you have enough disk space to do so.


3

Find out what the source of your time server is from an elevated powershell ....shell w32tm /query /computer:localhost /source make sure you timezone is correct - your NTP server might jump ahead 5 hours because your local settings might be the wrong zone from Powershell [System.TimeZone]::CurrentTimeZone at least knowing those two variables might ...


3

I tried changing the authentication type from Basic to NTLM but that did not make it work. I tried using Exchange Remote instead of Outlook Anywhere and that worked, but you cannot use Exchange Remote for a Cutover Migration. If you are going to do a Cutover Migration you must use Outlook Anywhere. After some research I decided to go with the get rid of ...


3

You can't restore the mailbox by restoring the user account. If you don't have a backup of the mailbox then see this link: https://technet.microsoft.com/en-us/library/jj863438(v=exchg.150).aspx You can restore the deleted user account with the ADResore utility from Sysinternals: https://technet.microsoft.com/en-us/sysinternals/bb963906.aspx


2

Bring in some virtual shared storage and build a Hyper-V cluster. DCs have own replication built-in, and while you can fake HA with Hyper-V Replica for ordinary VMs it's not supported with Exchange and has issues with SharePoint. https://blogs.technet.microsoft.com/rmilne/2013/07/29/exchange-and-hyper-v-replica-support/


1

I haven't actually done this. But there are no other answers yet, so... According to classes/documentation, things are never really delted from the AD schema, they are only marked inactive. I am unsure what affect this will have on user accounts that were created when the attributes in question were deleted (aka marked inactive). I kind of doubt the ...


1

Exchange isn't really designed to do that and it can get messy very quickly. What you are talking about though is sharing the SMTP address space. Take a look at this question for more details. Running company emails at two different suppliers The version of Exchange is completely immaterial - the same issues apply whether it is two Exchange servers, ...


1

The Exchange 2010 Management Tools are only supported on Windows 7 or Vista. You may get lucky and have it work on Windows 10 but there is no support for this setup. You can install the Exchange 2010 management tools on the following Windows operating systems: Windows 7 Windows Vista with Service Pack 2 (SP2) Windows Server 2008 SP2 Windows Server ...


1

List out mailboxes and remove Get-Mailbox -Database <database> You can do something fast like Get-Mailbox -Database DB02 >> C:\MailboxesToDelete.txt and then $users=Get-Content C:\MailboxesToDelete.txt foreach ($user in $users) { Try{ #Print to screen user mailbox to delete Write-Host "User: $($User)" #Mark Mailbox for ...


1

Offline defrags? Is it 2005? Create a new database and move the mailboxes. Zero risk, zero downtime - unlike an offline defrag. If you really don't have the space, then another option would be to stand up a temporary Exchange server, move those mailboxes you want to delete to that temporary server and delete them from there. That should give the white ...


1

Exchange 2007 SP3 Rollup 19 fixed the issue!


1

You get this error because you cannot delete a public folder database that contains data. To get in detailed about how do we remove public folder replicas from the database refer to this article that have documented steps and the links to get this job done. www.petenetlive.com/KB/Article/0000227 You may also get help from this step-by-step guide to migrate ...


1

I know this is an old question, but I just had to look up the same thing. You can verify that an AD account has become a room mailbox by checking the following attributes: msExchResourceMetaData -> ResouceType:Room msExchResourceDisplay -> Room msExchResourceSearchProperties -> Room If you're trying to access the actual capabilities of the room (or ...


1

Users are still able to delete messages, and this is the most likely cause of the missing messages. Retention Policies are used to "expire" items based on certain criteria, but they will not prevent objects from being deleted by a user. In Office 365 if you need to prevent users from deleting messages you need place a hold on the mailboxes. You can ...


1

I don't think there is a specific way to warn about repeating bookings outside work hours but you can restrict meetings to only during work hours, see set-calendarProcessing.


1

I have Microsoft and Blackberry working on the very same issue for last 30 days and MS is the one being slow to action/reply - however, in my case, the environment is full cloud, no migration, no multi-domain SSL. Today, I logged in to check if I got any reply from MS - none. Then I decided to RELOAD USER within BES Cloud console - agent status has changed ...



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