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 & Lync Admin Script created by Ward Vissers
www.wardvissers.nl
Tool to Manage Active Directory & Exchange & Lync
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 admin area you require
1. Active Directy Users Tasks
2. Active Directy Computers Tasks
3. Active Directy Groups Tasks
4. Active Directy Protected From Accidental Deletion Tasks
5. Active Directy FSMO Tasks
6. User Profile Tasks
7. Exchange Tasks
8. Lync Tasks
9. Quit and exit
Enter Menu Option Number:
Download: https://gallery.technet.microsoft.com/scriptcenter/Exchange-Lync-Script-c079133e
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
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.
KEMP gives away the LoadMaster for free. Now the virtual appliance is available in a free edition too. Available for all supported hypervisors (VMware, Hyper-V, enz).
The free VLM has some limitations, for instance the HA setup with an active and hot stand-by unit is not supported. Another important limitation is that the free LoadMaster doesn’t come with the awesome support paying customers receive. Also there are some bandwidth and SSL TPS limitations, all in all not much special for most home, lab, testing and other non-production deployments.
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!
Move Public Folder script from 2007/2010 to Exchange 2013 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)
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 Exchange 2013
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 the Exchange 2013 server
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)
Migrating the Public Folders
15) BadItemLimit (Exchange 2007 Only)
16) Migrate Exchange 2010 public folders
17) To verify that the migration started successfully (AutoSuspend is Compleet)
Lock down the public folders on the legacy Exchange server for final migration (downtime required)
18) Lock the legacy public folders for finalization
Finalize the public folder migration (downtime required)
19) Finalize the public folder migration (downtime required)
Test and unlock the public folder migration
20) Add Public Folder to Test User
21) Unlock the public folders for all other users
22) Public Folder Migration Complete (Legacy Exchange Server)
23) Public Folders Enabled Local
Final Check
24) Take a snapshot of the original source folder structure.
25) Take a snapshot of the public folder statistics such as item count, size, and owner
26) Take a snapshot of the permissions
99) Exit
Download the script here: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Move-Script-49126418