Exchange 2010
I created a handy script to fix a Exchange calender the easy way.
I does the following:
– Ask for the username
– Gives full access to user mailbox and disable automapping
– Export Name,LegacyExchangeDN from the user to list.txt
– Run CalCheck
– Remove Full Access Permissions
Put CalCheck.ps1 in de same folder where calcheck.exe exsist.
Download CalCheck
You can find the script the Microsoft Script Libary:
https://gallery.technet.microsoft.com/scriptcenter/CalCheck-Powershell-Script-c419c10e
Exchange Team released Rollup 10 for Exchange Server 2010 Service Pack 3
Fixes:
KB 3069055 Various DAG maintenance scripts do not work in an Exchange Server 2010 environment
KB 3057422 “MapiExceptionNoAccess: Unable to query table rows” error and some mailboxes cannot be moved
KB 3056750 Exchange ActiveSync application pool crashes in an Exchange Server 2010 environment
KB 3054644 “The item no longer exists” error when you access an archive mailbox in Outlook Web App in Exchange Server 2010
KB 3051284 Event ID 4999 is logged and MSExchangeServicesAppPool crashes in an Exchange Server 2010 environment
KB 3049596 Event ID 4999 is logged and remote procedure call Client Access service crashes in an Exchange Server 2010 environment
KB 2964344 MSExchangeRPC service stops working intermittently in Exchange Server 2010
Move Public Folder script from 2007/2010 to Office 365 Script created by Ward Vissers
www.wardvissers.nl
THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER
Please Select the Choice You Want
Prepare for Migration (Legacy Exchange Server
00) Add the Office 365 Domain Name
01) Take a snapshot of the original source folder structure
02) Take a snapshot of public folder statistics such as item count, size, and owner.
03) Take a snapshot of the permissions
04) Locate public folders that have a backslash in the name
05) Rename Public Folder
06) Checks the public folder migration status.
07) Set PublicFolderMigrationComplete to False
Check Office 365
08) Get-PublicFolderMigrationRequest
09) Get-Mailbox -PublicFolder
10) Get-PublicFolder
Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server)
11) Export-PublicFolderStatistics PFSizeMap.csv
12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv
Create the public folder mailboxes on Exchange Online
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders
15) Export mail-enabled public folders from Active Directory
16) LegacyExchangeDN Administrator
17) LegacyExchangeDN Public Folder Server
18) External Name Outlook Anywhere
19) Set the XML file
20) Give the CSV file to start the Migration
21) Public Folder Migration Status
Lock down the public folders on the legacy Exchange server for final migration (downtime required)
22) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required)
23) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration
24) Add Public Folder to Test User
25) Unlock the public folders for all other users
26) Public Folder Migration Complete (Legacy Exchange Server)
27) Public Folders Enabled Local
Final Check
28) Take a snapshot of the original source folder structure.
29) Take a snapshot of the public folder statistics such as item count, size, and owner
30) Take a snapshot of the permissions
99) Exit 
Download: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Migratie-to-25bd50a0
This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
This update also includes new daylight saving time (DST) updates for Exchange Server 2010 SP3. For more information about DST, go to the following Microsoft website:
Daylight saving time Help and Support Center
Download Update Rollup 9 for Exchange Server 2010 SP3 (KB3030085).
Exchange Team had an oops moment today
This KB was publish today hihi 
but now offline 
Android devices can’t set up an Exchange account after you install Exchange Server 2010 SP3 RU9 or Exchange Server 2013 CU8
Just waiting!!!
Apple released iOS 8.2 update for iOS 8 with fixes, amongst other things, some Exchange-related issues.
The release notes notes these Exchange-related fixes:
So, you want to test and accept this iOS update before giving it the green light for your Exchange environment.
More information on current issues with Exchange ActiveSync and 3rd party devices can be found in support article KB2563324.
I see a lot problems with to small log disks. Sizing Exchange is a very imported thing!! Today there a lot of problems with Thiry-Party Devices. They can create a lot of log files if you run a oudated Exchange Server. Transaction logs are truncated when backup software successfully backs up an Exchange server. The ‘Backup/Truncation Failure Tolerance’ field in the Backup Configuration section, allows a value to be set that specifies how much capacity will be available for logs in the event of backup failures or issues with Thirth party devices. The default value is 3 days. Change This!! This ensures that the server will continue to function and you have the ability to restore from transaction logs for x days, if the backup fails & and if some thirth party device give some trouble. Logs disk & backup should be monitored to ensure that they are successful.
After a customer migrated to Exchange Online some time ago.
They wanted not a hybrid situation. but they are using still DirSync!
After reading: Decommissioning your Exchange 2010 servers in a Hybrid Deployment a I read its not a real problem.
Changed DirSync & After that Uninstalling Exchange 2013 was very easy.
I had only to disable the Arbitration mailboxes: I did that with the following powershell command:
Get-Mailbox -Arbitration | disable-Mailbox -arbitration -RemoveLastArbitrationMailboxAllowed
I did not publish this article because i has still some doubts!!
I had still a question: Do want to remove the last Exchange Server? Have you a supported Environment without a local Exchange Server and still using DirSync??
Yes & No!!
After reading Concerning Trends Discovered During Several Critical Escalations
Microsoft Says:
You may remove the last Exchange Server locale when you move totally to Office 365/Exchange Online, but change Exchange Attribuuts trough ADSI is not supported.
If you don’t have a third party tool for that. The only way is trough ADSI and that is not supported.
My Conclusion:
You have a support issue when you dropped a Call at Microsoft and they investigate your environment.
Don’t remove the last Exchange Server even when all mailboxen exist in Office 365/Exchange Online and keep them up to date!
You can always install a Exchange Server but most of the times it will be always to late!
Microsoft recommends adopting a software update strategy that ensures all software follows N to N-1 policy, where N is a service pack, update rollup, cumulative update, maintenance release, or whatever terminology is used by the software vendor. Microsoft strongly recommend that our customers also adopt a similar strategy with respect to hardware firmware and drivers ensuring that network cards, BIOS, and storage controllers/interfaces are kept up to date.
Software patching is not simply an issue for Microsoft software. You must also ensure that all inter-dependent solutions (e.g., Blackberry Enterprise Server, backup software, etc.) are kept up-to-date for a specific release as this ensures optimal reliability and compatibility.
Customers must also follow the software vendor’s Software Lifecycle and appropriately plan on upgrading to a supported version in the event that support for a specific version is about to expire or is already out of support.
For Exchange 2010, this means having all servers deployed with Service Pack 3 and either Rollup 7 or Rollup 8 (at the time of this writing). For Exchange 2013, this means having all servers deployed with Cumulative Update 6 or Cumulative Update 7 (at the time of this writing).
For environments that have a hybrid configuration with Office 365, the servers participating in the hybrid configuration must be running the latest version (e.g., Exchange 2010 SP3 RU8 or Exchange 2013 CU7) or the prior version (e.g., Exchange 2010 SP3 RU7 or Exchange 2013 CU6) in order to maintain and ensure compatibility with Office 365. There are some required dependencies for hybrid deployments, so it’s even more critical you keep your software up to date if you choose to go hybrid.
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish further updates to this blog post regarding RU8.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
Check: http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
Updated: Update Rollup 8 v2 For Exchange 2010 SP3 (KB2986475) has been released