I While ago i blogd about MDT Displaying The Task Sequence Name
This is still ongoing issue in MDT 2013 Update 2
Sow:
oEnvironment.Item(“_SMSTSPackageName”) = “Lite Touch Installation”
And change it like so:
oEnvironment.Item(“_SMSTSPackageName”) = oEnvironment.Item(“TaskSequenceName”)
Change this please Microsoft 
Exchange Analyzer is a PowerShell tool that scans an Exchange Server 2013 or 2016 organization and reports on compliance with best practices.
Exchange Analyzer is a community project, and is currently a beta release seeking feedback and results from real world environments.
To read the latest information about Exchange Analyzer click here to visit the project’s ReadMe on Github. More information can also be found in the Exchange Analyzer Wiki.
1. Download the latest Zip file
2. Extract or copy the following files and folders to a computer that has the Exchange 2013 or 2016 management shell installed. For example, place all of the files and folders in a C:\Scripts\ExchangeAnalyzer folder.
3. Copy the folders in the \Modules folder to C:\Windows\System32\WindowsPowerShell\v1.0\Modules\
4. Open a new Exchange Management Shell
Important Note: if you are updating your copy of Exchange Analyzer please make sure you copy the updated module in step 3.
To run the Exchange Analyzer open an Exchange management shell, navigate to the folder with the script files (e.g. C:\Scripts\ExchangeAnalyzer) and run:
Exchange Analyzer produces a HTML report with a simple “Passed/Failed” indicator and a list of passed and/or failed objects. Links to more info are provided to assist you with further interpretation of the report.
Before submitting feedback or questions please review the Exchange Analyzer FAQ.
You can help with bug fixes by submitting issues on Github. If you would like to contribute fixes or other code please review theExchange Analyzer Wiki.
You can also send email to feedback@exchangeanalyzer.com.
14/01/2016 – v0.1.0-Beta.1
28/01/2016 – v0.1.1-Beta.2
This security update resolves a vulnerability in Microsoft Exchange Server that could allow information disclosure if Outlook Web Access (OWA) doesn’t handle web requests, sanitize user input and email content correctly.
To learn more about the vulnerability, see Microsoft Security Bulletin MS16-010.
Download:
Microsoft Exchange Server 2013 Service Pack 1 (3124557)
Microsoft Exchange Server 2013 Cumulative Update 10 (3124557)
Microsoft Exchange Server 2013 Cumulative Update 11 (3124557)
Microsoft Exchange Server 2016 (3124557)
Office 2010/2013/2016 supports integration of Updates by placing the MSP files in the Updates folder of the installation medium.
The challenge is more in getting all the update files. Fortunate there are a few great community users that have created WHDownloader for downloading these files and they also maintain the list of applicable updates for Office 2010 and Office 2013 and 2016
Saving a lot of time 
There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:
Configuration.xml
<Configuration>
<Add SourcePath=”d:\2016\” OfficeClientEdition=”32″ Branch=”Current”>
<Product ID=”O365ProPlusRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
<Product ID=”VisioProRetail”>
<Language ID=”en-us” />
<Language ID=”nl-nl” />
</Product>
</Add>
<!– <Updates Enabled=”TRUE” Branch=”Current” /> –>
<Display Level=”Full” AcceptEULA=”TRUE” />
<Logging Name=”OfficeSetup.txt” Path=”%temp%” />
<Property Name=”AUTOACTIVATE” Value=”1″ />
</Configuration>
Download
D:\2016\setup.exe /download d:\2016\configuration.xml
Install / Configure Office 365 (2016)
D:\2016\setup.exe /configure d:\2016\configuration.xml
Source: https://technet.microsoft.com/en-us/library/jj219424.aspx
The Microsoft Deployment Toolkit (MDT) 2013 Update 2 (6.3.8330) is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (Note that there are known issues with the v1511 release of the Windows 10 ADK and System Center Configuration Manager; these issues do not directly affect MDT although may still impact ZTI or UDI scenarios.)
MDT 2013 Update 2 is primarily a quality release; there are no new major features. The following is a summary of the significant changes in this update:
There are no other new release notes or significant known issues. See the previous post for more information as much of it is still applicable (other than the fix list above).
See the following post on How to get help with MDT.
Frequently Asked Questions
In anticipation of some questions that you may have about this release (or MDT in general):
Q: Should I expect a release of MDT with every new Windows 10 and/or Configuration Manager build release?
No. We shipped multiple MDT releases this year due to the timing of Windows 10 and Configuration Manager releases, but do not intend to keep that same cadence going forward.
Q: What branches of Windows 10 does MDT support?
MDT supports both the current branch of Windows 10 as well as the long-term servicing branch.
Q: What branches of System Center Configuration Manager does MDT support?
For ZTI and UDI scenarios MDT 2013 Update 2 supports the current branch of System Center Configuration Manager (currently version 1511) for an integrated solution for deploying Windows 10 current branch as well as prior Windows versions.
Q: When is the next planned release of MDT?
We do not currently have a timeframe. We will release any tactical changes as needed which may be required to support new builds of Windows 10 or Configuration Manager, but do not currently expect this to be needed.
Q: Is this the last release of MDT?
No, we will continue to iterate and invest in the product.
Q: Why is it still “MDT 2013” when the year is almost 2016?
Two primary reasons. First, we have only made minor changes to MDT which in our opinion does not constitute a major version revision. Second, per the MDT support lifecycle, a new major version will drop support for MDT2012 Update 1 which still supports legacy platforms.
The Skype for Business Team released Skype for Business 2015 Planning Tool. This tool asks you a series of questions about your organization and the features that you are interested in. The planning tool will then use your answers to recommend a topology based on the tested Skype for Business 2015 user model.
Your organization may have a different user model. If so, you should adjust the recommended topology as necessary to fit your organization’s needs.
What’s in the Planning Tool for Skype for Business 2015?
Get it: https://www.microsoft.com/en-us/download/details.aspx?id=50357
The MCSE: Communication certification is being updated to support Skype for Business skills.
Starting 28-December, 2015, the following two new Skype for Business exams (currently in beta) will fulfill the MCSE: Communication requirements, provided that the candidate has already earned a qualifying MCSA credential:
The following Microsoft Lync Server 2013 exams retire on 31-March, 2016, but will remain an accepted path towards earning MCSE: Communication until 31-July, 2016:
Please see the MCSE: Communication web page for more details after 28-December.
Cumulative Update 11 for Microsoft Exchange Server 2013 was released on December 15, 2015. Several nonsecurity issues are fixed in this cumulative update or a later cumulative update for Exchange Server 2013.
This cumulative update fixes the issues that are described in the following Microsoft Knowledge Base articles:
This update also includes new daylight saving time (DST) updates for Exchange Server 2013. For more information about DST, go to Daylight Saving Time Help and Support Center.
Download Cumulative Update 11 for Exchange Server 2013 (KB3099522) now.
Update Rollup 12 for Microsoft Exchange Server 2010 Service Pack 3 (SP3) was released on December 15, 2015. This update rollup fixesvarious issues. Before you install this update, you must remove all interim updates for Exchange Server 2010 SP3. Also, see this important information about how to install this update.
This update fixes the issues that are described in the following Microsoft Knowledge Base article:
This update also includes new daylight saving time (DST) updates for Exchange Server 2010 SP3. For more information about DST, go toDaylight Saving Time Help and Support Center.
Download Update Rollup 12 for Exchange Server 2010 SP3 (KB3096066).