Deploy Windows 10 with MDT 2013 Update 1 “Preview”

Deploying Windows 10 with MDT 2013 Update 1 Preview

Next you need the MDT 2013 Update 1 Preview. To get the preview, you need to first join the MDT Group on Microsoft Connect, if you’re not a member already. Then, prior to downloading the actual preview bits, you’ll need to grab the Windows ADK for Windows 10 Technical Preview, which is a prerequisite for running MDT.

The Build number which the best to use is the Windows 10 Technical Preview with build number 9926 Winking smile

So i installed some apps automaticly Winking smile
image

Doing some bug check/feature check Winking smile Keep you posted Winking smile

Cumulative Update 8 for Exchange Server 2013

The Exchange team is announcing today the availability of Cumulative Update 8 for Exchange Server 2013. The Cumulative Update Package and UM Language Packsare now available on the Microsoft Download Center. Cumulative Update 8 represents the continuation of our Exchange Server 2013 servicing and builds upon Exchange Server 2013 Cumulative Update 7. The release includes fixes for customer reported issues, minor product enhancements and previously released security bulletins. A complete list of customer reported issues resolved can be found in Knowledge Base Article KB3030080. Customers running any previous release of Exchange Server 2013 can move directly to Cumulative Update 8 today. Customers deploying Exchange Server 2013 for the first time may skip previous releases and start their deployment with Cumulative Update 8 directly.

We would like to call your attention to a few items in particular about the Cumulative Update 8 release:

  • Calendar and Contact Modern Public Folders favorites added in Outlook are now accessible in OWA
  • Batch Migration of Public Folders to 2013 improves migration throughput and PF migration experience
  • Smoother migration for EAS clients to O365 with automatic profile redirect upon successful Hybrid migration to O365 (EAS client must support HTTP 451 redirect)

For the latest information and product announcements please read What’s New in Exchange Server 2013, Release Notes and product documentation available on TechNet.

Cumulative Update 8 includes Exchange related updates to Active Directory schema and configuration. For information on extending schema and configuring the active directory please review the appropriate TechNet documentation. Also, to prevent installation issues you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the machine being upgraded. If the policies are NOT set to Unrestricted you should use the resolution steps in KB981474 to adjust the settings.

Reminder: Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., CU8) or the prior (e.g., CU7) Cumulative Update release.

Rollup 9 for Exchange Server 2010 Service Pack 3

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 Server 2010 SP3 RU9 and Exchange Server 2013 CU8 are coming

Exchange Team had an oops moment today

This KB was publish today hihi Smile but now offline Winking smile 
Android devices can’t set up an Exchange account after you install Exchange Server 2010 SP3 RU9 or Exchange Server 2013 CU8

Just waiting!!!

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:

  1. Download the installer from the MDT Connect portal.
  2. Download the prerequisite Windows ADK for Windows 10 Technical Preview from the Microsoft Download Center.
  3. 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.)

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!

Translate »