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!!!
Tag: Microsoft
iOS 8.2 fixes Exchange related issues
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:
- – Fixes stability of Mail
- – Addresses an issue that caused certain events in a custom reoccurring meeting to drop from Exchange calendar
- – Fixes an certificate error that prevented configuring an Exchange account behind a third-party gateway
- – Fixes an issue that could cause an organizer’s Exchange meeting notes to be overwritten
- – Resolves an issue that prevented some Calendar events from automatically showing as “busy” after accepting an invite.
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.
Microsoft Deployment Toolkit 2013 Update 1 Preview Now Available
The Enterprise Client Management team is happy to announce the availability of the Microsoft Deployment Toolkit (MDT) 2013 Update 1 Preview!
What’s new with MDT 2013 Update 1 Preview:
- Support for the Windows 10 Technical Preview (LTI only) and the Windows Assessment and Deployment Kit (ADK) for Windows 10 Technical Preview
- Split WIM support for UEFI media scenarios
- Completely revised Windows version logic including changes from string to integer comparison (“10” !> “6” but 10 > 6) and a new ZTIUtility function, GetMajorMinorVersion
- Minor revisions to Deployment Workbench console interface
To Do List:
- Download the installer from the MDT Connect portal.
- Download the prerequisite Windows ADK for Windows 10 Technical Preview from the Microsoft Download Center.
- Try MDT 2013 Update 1 Preview (lab only!) and then submit suggestions, bugs and feedback via the Connect portal. (You are welcome to post comments here, but make your feedback actionable by posting on Connect.)
(New members must first join the MDT group of the Client Management program on Connect.)
Kemp LoadMaster for Free Awesome!! A Free Load Balancer for Any Workload
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.
- The Free LoadMaster Includes:
- Layer 4/7 load balancing
- Content switching
- Caching, compression engine
- MS Exchange 2010/2013 optimized
- Pre-configured virtual service templates
- IPS engine
- High Availability
- Edge Security Pack (ESP) – a Microsoft TMG replacement
- GSLB multi-site load balancing
- RESTful API
Exchange Sizing Calculator & Backup Configuration
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.
Configure your Exchange 2013 server with Configure-Echange2013.ps1 Updated to V2.5
I love Powershell <3.
Configure & maintaining your Exchange 2013 can be a hell… I do the most things with powershell…
I have a lot of standard scripts to configure an Exchange 2013 server or DAG cluster.
So i created a freaky nice script i my say so!! :
Updated to V2.5
Change List:
# V1.0 Begin
# V1.1 Added Some New Options 12-10-2014
# V1.2 Added Hyper-V Best Practise & NTFS Partition Offset
# V1.3 Added KB2995145 .NET Framework 4.5 garbage collector heap Fix
# V1.4 Added Set Minimum Disk Space Warning level (180GB Default CU6 200GB CU5)
# V1.5 Added Some new features
# V1.6 Changed the Layout & Add Move Arbitration Mailbox
# V1.7 Added PST Export & KB2990117
# V1.8 Added Full backup, Database in GB and Mailbox Size in GB Export CSV
# V1.9 Added Outlook AnyWhere & SafetyNetHoldTime
# V2.0 Added Check DatacenterActivationMode, Get-DatabaseAvailabilityGroupNetwork, Add Static Route, Disable Replation Network on DAG, Database Copies Per Volume (AutoReseed)
# V2.1 Added Edge Subscription
# V2.2 Added Check Transaction Log Growth
# V2.3 Changed the Menu to Submenu’s
# V2.4 Added Check Database White Space
# V2.5 Added MAPI HTTP External URL & Fixed some things
Save the Script as configure-Exchange2013.ps1
Download: https://gallery.technet.microsoft.com/scriptcenter/Configure-Exchange-2013-e0ffb2a6
Microsoft Ignite first things about Exchange Server v.Next & Skype for Business
Microsoft Ignite will be hell add may 4-8. The session catalog contains 275 sessions, covering products like Exchange (49), Office 365 (85) and Skype for Business (26). It will be the first major Microsoft event where details will emerge on the next version of Exchange, Exchange v.Next.
The next version of Exchange Server is arriving in the second half of 2015. A short heads-up as the session catalog for Microsoft Ignite has been published. So, if you are still undecided or already want to pick ‘must see’ sessions for your schedule, you can check the session catalog here.
I will not attend Ignite. But i hope the sessions wil be publishd on Channel 9 here.
Short List of sessions:
Tools and Techniques for Exchange Performance Troubleshooting
Meet Exchange Server v.Next
Choosing between Server, Online and Hybrid with Skype for Business
Deploying Exchange Server v.Next
Deep Dive into How Microsoft Handles Spam and Advanced Email Threats
Exchange Server Preferred Architecture
Experts Unplugged: New Exchange Scenarios
Exchange on IaaS: Concerns, Tradeoffs, and Best Practices
Moved al mailboxen to Office 365 & Still using dirsync! Can you remove the last Exchange 2010/2013 Server. Yes It Can! Just don’t do it!! You will have a support issue when you have problems!!
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!
MDT Create your own Default Task Sequence
MDT is a greate tool, You can create your own Default Task Sequence for Clients Servers!!
Normal i need to customize every Task Sequence that i create and that is so boring!!
I Create in this example a task sequence (ID & NAME) Server and Changed some things things like Windows Update.
So now go to to that Folder \\DeploymentShare\Control\Server
Copy the TS.XML
Go to: C:\Program Files\Microsoft Deployment Toolkit\Templates & save the TS.XML File
Rename the TS.xml file. I my demo Ward Server Deployment.xml
Edit the Name and the Description:
When you maken now what to make a new Task Sequence, You will see Ward Server Deployment Listed. Freaking Awesome!!
Bulk import applicaties in MDT
Mikael Nystrom created i freaking nice script.
Often I need to import applications into the Deployment workbench and that is fine. The process is easy and fast, but it is boring and if you have more then 5 apps it is really boring. Based on the fact that almost all my apps in MDT is deployed using VB or PowerShell wrappers its is just one file in a folder and then there is a subfolder with the content. You don’t need to be a genius to figure out that 90% of all the apps pretty much have the same folder and file structure in the root of the application folder, so why don’t we use PowerShell to import all the apps based on some guessing?
The command line:
This is the tricky part, since there is no way to know that it will be a guessing game and the command line might need to be modified after import, but I rather modify 2-3 applications instead of importing all of them manually.
The default cmdline for all imported apps will be:
.EXE “$Install /q”
.MSI “msiexec.exe /i $Install /qn”
.MSU “wusa.exe $Install /Quiet /NoRestart”
.PS1 “PowerShell.exe -ExecutionPolicy ByPass -File $Install”
.WSF “cscript.exe $Install”
The Script:
The script is rather easy, it takes 2 parameters. The folder from where to import and the deployment share. You need to have MDT installed since it is using PowerShell cmdlets from MDT. The syntax for the script looks like this:
.\Import-MDTApps.ps1 -ImportFolder d:\APPS -MDTFolder D:\DeploymentShare
You can download the script here: http://1drv.ms/1pGTvkA mirror: Import-MDTApps.7z