This script will install the needed prerequisites for the Mailbox Role of Exchange 2016 “Preview” on Server 2012 R2 .
It will install the following:
– Windows Componets
– .NET Framework 4.5.2
– Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
You can download the script here:
https://gallery.technet.microsoft.com/scriptcenter/Exchange-2016-prerequisites-9a0b5e17
This post is to serve as the release notes and known issues list for the current release of MDT 2013 Update 1 (v6.3.8290). Source: http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx
The list of known issues below provides a number of workarounds that are currently available to help unblock affected customers. We will revise the list as needed. Given the number of issues with this build we will release a newer build of MDT 2013 Update 1 in the next several weeks to address as many of these issues as we can. Watch this blog for more information.
The MDT product documentation published on TechNet is current as of MDT 2013; it has not yet been updated for MDT 2013 Update 1.
MDT 2013 Update 1 Preview should be uninstalled before installing the final MDT 2013 Update 1. Do not attempt to upgrade a preview installation or deployment share. Although the product documentation is not updated for MDT 2013 Update 1, the information on upgrading an installation still holds true.
The Windows System Image Manager (WSIM, a component of the Windows ADK used to create and modify unattended installation answer files) does not allow blank values which exist in the default MDT Unattend.xml templates. MDT removes blank values before injecting the file during deployment, so Windows always receives a valid XML answer file.
When integrating MDT with Configuration Manager, follow the version of the Windows ADK. MDT 2013 Update 1 only works with the Windows 10 ADK, so make sure it is used with a version of Configuration Manager that supports and also uses the Windows 10 ADK.
Split image (.SWM) support is now off by default. It must be enabled by modifying %DeployRoot%\Control\Settings.xml with the following:
<SkipWimSplit>False</SkipWimSplit>
The behavior of the HideShell option changed with Windows 10. Michael Niehaus explains this in great detail on his blog.
Symptoms:
Workarounds: Keith Garner provides some suggestions on his blog: uberbug06 and uberbug07.
When doing a media deployment and using a static IP the static IP does not get restored.
Workarounds:
When initializing a deployment in Windows PE and clicking Configure Static IP Address, if you uncheck Enable DHCP and enter static IP information, the following Network Settings Error will display:
WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147467259
This warning may also be seen in the results screen and log files during a deployment.
Workaround: a static IP can be manually set from Windows PE using netsh, but otherwise there are no workarounds at this time.
After successfully upgrading a system to Windows 10 the MDT monitoring fails to report information. You will see the following warnings:
Unable to create WebService class
Workaround: None.
This is a known bug with DISM; it is external to MDT. DISM can sometimes fail to add the MDAC component to WinPE boot images. This seems to be a timing issue which most commonly occur when you are using SSD disks.
Workarounds:
NOTE: we are also aware of reports of similar issues regarding Windows PowerShell and WMI components in Windows PE (as well as some functional issues with these components). We have not been able to reproduce these issues, and are working with the Windows team to investigate further. If you have a reproducible issue with these components in Windows PE, please open a case with Microsoft Support to troubleshoot.
Windows 10 upgrade task sequences are available when starting a deployment from Windows PE or on a non-matching architecture, however the in-place upgrade scenario is only supported when started from the full OS (it cannot be started from Windows PE) and from the correct architecture.
Workaround: Modify your upgrade task sequence properties to exclude client platforms that are not applicable. On the task sequence properties, General tab, select This can run only on the specified client platforms and then choose platforms that you want to target, for example, All x86 Windows 7 Client. This example will exclude Windows PE and Windows 7 x64 systems.
If you have an application that uses a command file (.cmd) as the installation command line it will be launched from C:\Windows\System32 instead of the application’s working directory.
Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.
Application bundles will successfully install but the following warning is logged in ZTIApplications.log:
SelectSingleNodeString(CommandLine) Missing Node.
as well as the following error:
Application <app bundle name> returned an unexpected return code: 87
Workaround: See the associated bug on Connect for sample edits to ZTIApplications.wsf.
Changing the keyboard locale in the Deployment Wizard will result in a script error:
Type mismatch: 'SetNewKeyboardLayout'
This error is non-fatal. Click Yes and continue.
Workarounds:
onchange="SetNewKeyboardLayout" from line 62. Using the “Install Language Packs Offline” or “Install Updates Offline” step in an MDT-integrated task sequence in Configuration Manager results in the language packs or updates not injected, and the following errors in the ZTIPatches.log:
ZTI ERROR - Unhandled error returned by ZTIPatches: Object required (424)
This error is only seen in logs, the deployment appears to be successful otherwise.
Workaround: apply updates and language packs online
If you split a large image file to create .SWM file(s), then applying this split image file will fail.
Workaround: edit %DeployRoot%\Scripts\LTIApply.wsf, both lines 915 and 918, to add a colon and remove a space, for example on line 915 change:
sCmd = sCmd & " /SWMFile """ & sRWMPath & """"
tosCmd = sCmd & " /SWMFile:""" & sRWMPath & """"
Do the same on line 918.
If you have edited unattend.xml and then start a deployment with the wizard page for administrator password enabled, or specified AdminPassword in CustomSettings.ini, the deployment will fail during Windows OOBE:
Windows could not parse or process Unattend answer file [C:\Windows\Panther\unattend.xml\ for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows=Shell-Setup].
Workaround: edit %DeployoRoot%\Scripts\ZTIConfigure.wsf lines 343 and 344 to append unattend: before PlainText. For example, on line 344 change:
oCurrent.parentNode.selectSingleNode("PlainText").text = "true"
tooCurrent.parentNode.selectSingleNode("unattend:PlainText").text = "true"
Do the same on line 343.
Towards the end of a MDT-integrated task sequence deployment in Configuration Manager a Windows Script Host popup will appear with a message similar to the following:
Can not find script file "C:\LTIBootstrap.vbs".
(The drive letter may be different depending upon the specific scenario.)
Workaround: Script changes are possible but difficult and challenging. Johan Arwidmark provides an option on his blog (see Issue #2).
After capturing an image and rebooting back to the drive, autologon is still configured and an error will appear about LTIBootstrap is not found. This is a minor, non-fatal error that does not affect the captured image.
Workaround: Script changes are possible but difficult and challenging, especially given the minor severity of the issue.
A deployment fails with the following error from DISM:
Error: 87 (The parameter is incorrect)
With further detail in the dism.log:
Failed to get the filename extension of the image file
Workarounds: This is seen when the server name is only two characters, for example DC, such that the /ImageFile parameter is similar to the following:
"\\dc\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\sources\install.wim"
Use a deployment share on a server whose name is three or more characters.
If you must use a server with a two-character name, specify its fully qualified domain name in bootstrap.ini, for example
DeployRoot=\\DC.contoso.com\DeploymentShare$
The Microsoft Deployment Toolkit (MDT) 2013 Update 1 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. (Scroll to the bottom of the page to the section, “Customize, assess, and deploy Windows on your hardware.” The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)
Significant changes in MDT 2013 Update 1:
Here is a more detailed list of some specific changes in this release:
Office Lens trims, enhances and makes pictures of whiteboards and docs readable, and saves them to OneNote. You can use Office Lens to convert images to PDF, Word and PowerPoint files too. Office Lens is like having a scanner in your pocket. Like magic, it will digitalize notes on whiteboards or blackboards. Always find important documents or business cards. Sketch your ideas and snap a picture for later. Don’t lose receipts or stray sticky notes again!
What’s new:
– Now you can convert your pictures to PDF files with selectable text, in addition to Word and PowerPoint files, and save them to OneDrive.
Scenarios:
– Capture and crop a picture of a whiteboard or blackboard and share your meeting notes with co-workers.
– Make digital copies of your printed documents, business cards or posters and trim them precisely.
– Printed text will be automatically recognized (using OCR) so you can search for words in images and copy and edit them.
Features:
– With Whiteboard mode, Office Lens trims and cleans up glare and shadows.
– With Document mode, Office Lens trims and colors images perfectly.
– Pictures are saved to your camera roll and also directly into OneNote, so you can see the images across all your devices.
– Choose to convert images to PDF (.pdf), Word (.docx), or PowerPoint (.pptx) files that are automatically saved to OneDrive.
Note: Office Lens requires logging in with your Microsoft Account. Your Microsoft Account must be same as the one registered on your device.
Microsoft has released the Windows 10 Group Policy (.ADMX) templates . These .ADMX templates are released as a separate download package so you can manage group policy for Windows 10 clients more easily.
This new package includes additional (.ADMX) templates which are not included in the RTM version of Windows 10.
To download the Windows 10 Group Policy (.ADMX) templates, please visit http://www.microsoft.com/en-us/download/details.aspx?id=48257
To review which settings are new in Windows 10, review the Windows 10 ADMX spreadsheet here:http://www.microsoft.com/en-us/download/details.aspx?id=25250
ownload the Windows Assessment and Deployment Kit (ADK) for Windows 10 to get the new and improved deployment tools used to automate a large-scale deployment of Windows 10. The Windows ADK includes:
Windows 10 build 10240 has been released to the Fast Ring. That’s what I’m running on my laptop now. There were heavy rumors yesterday that this is the to Release To Manufacturing (RTM) build and is the one to be publically available on July 29th. But there is no hard confirmation on this by Microsoft yet Build 10240 now available for Windows Insiders in Fast and Slow rings.
“Over the past few days we’ve been preparing our release pipelines and processes, and this build is one step closer to what customers will start to receive on 7/29 …
On Monday we announced that builds from here on will only be available through Windows Update, so to get this one you can either wait and it will be installed automatically.”
Here’s how you prepare to roll it out in your company.
In a previous blog post I wrote about the update you needed for your KMS server to be able to activate Windows 10 clients. Read about that in KB3058168: Update that enables Windows 8.1 and Windows 8 KMS hosts to activate a later version of Windows
Meanwhile Microsoft has also published the Windows 10 client KMS activation which keys can be found here Appendix A: KMS Client Setup Keys
Operating system edition
KMS Client Setup Key
Windows 10 Professional: W269N-WFGWX-YVC9B-4J6C9-T83GX
Windows 10 Professional N: MH37W-N47XK-V7XM9-C7227-GCQG9
Windows 10 Enterprise: N: NPPR9-FWDCX-D2C8J-H872K-2YT43
Windows 10 Enterprise N: DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4
Windows 10 Education: NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
Windows 10 Education N: 2WH4N-8QGBV-H22JP-CT43Q-MDWW
Windows 10 Enterprise 2015 LTSB: WNMTR-4C88C-JK8YV-HQ7T2-76DF9
Windows 10 Enterprise 2015 LTSB N: 2F77B-TNFGY-69QQF-B8YKP-D69TJ
Do note this is the key you use when you activate the Windows 10 Client against a KMS server. It is not the KMS license server key. That one you’ll need to obtain from your valid Microsoft licenses.
Windows 10 will be available on July 29th 2015. Microsoft has prepared for this by already making an Update(KB3058168) that enables Windows 8.1, Windows Server 2012 R2, Windows 8, and Windows Server 2012 Key Management Service (KMS) hosts to activate a “later version of Windows”. This must means Windows 10. I do not know if this means that is even for Windows Server 2016. Windows 10 will be activated by a KMS server running this update but it might.
Select the version you need for the KMS server or servers you use and install them.
Microsoft has released a free ebook of “Introducing Windows 10 for IT Professionals, Preview Edition”. You can download the ebook here. Special thanks to Mark Swinkels
All drivers are stored in the so called DriverStore, which is located under %SYSTEMDRIVE%\Windows\System32\DriverStore.
With the built-in command line tool pnputil you can add or remove drivers.
How does it work?