So this fast-publish post is more of a reference page for the regional settings for Australia based Windows deployments
Locale, keyboard and language settings for Australia. This is a basic oobe.xml file found under c:\windows\system32\oobe\info\default\1033
12 1033 0c09:00000409 AUS Eastern Standard Time true Technet reference for these settings: http://technet.microsoft.com/en-au/library/dn621901.aspx
Language: 1033 (Full list found here) Location: 12 (Full list found here) Locale: 1033 (Full list found here) Keyboard: en-AU: United States - English (0c09:00000409) (Full list found here) Hope this helps my fellow aussies.
Disabling hibernation is simple enough (âpowercfg.exe -h offâ) but how would we do this in MDT.
As with all things MDT, there is often more multiple ways to achieve the same goal. The two methods I would use are by the modifying the unattend.xml as described here or using a command line step in the deployment sequence.
A recent MDT project found the clients needs were more aligned with the task sequence step option.
Using MDT 2013 I wanted a sequence that automatically installs, sysprepâs and captures my reference image.
For ease of management, I choose to have a dedicated MDT Deployment Share for my reference build process and use Powershell wherever possible.
A more detailed process using the GUI can be found here
Steps:
Install ADK 8.1 Install MDT 2013 Install and configure WSUS Build the reference build share Configure build sequence Execute sequence in a VM Downloads required:
On a recent MDT project the client requested to finish all builds with volume set at 30%.
Being committed to doing everything in Powershell, I jumped on the book of knowledge looking for some inspiration. As luck would have it, I found this response from knuckle-dragger that performed the complete task perfectly for me.
Below is the PowerShell script that meets my clients âneedââŚ
Function Set-Speaker($Volume){ $wshShell = new-object -com wscript.
A recent MDT project a client was using USB media to do the builds. This is easy enough to accomplish but something they couldnât handle was during the build, the USB drive gets assigned D and devices with optical drives ended up with E and so forthâŚ
This wasnât acceptable for various reasons in their environment so we had to force the USB builds to assign an appropriate drive letter.