BB24

Andy, What is the base image - is it based on English or another language? You may have to have two different images depending on the languages. For example, my company supports 4 different languages in our Win 10 build (English, Chinese Trad, Chinese Simp and Japanese). For Japanese we need to build a separate image, but it is built upon from the English build. We use a script to modify it to change it into Japanese. However we are not using MDT exclusively, so this may not apply. Extract of powershell script: #This script will take a captured WIM file (US English) and add the Japan system Locales. Resulting in a Japan image for OSD DISM /Mount-Image /ImageFile:$Path0\$Image /Index:1 /MountDir:$Path3 dism.exe /image:$Path3 /set-UILang:ja-JP /set-SysLocale:ja-JP /set-UserLocale:ja-JP /set-LayeredDriver:6 /set-AllIntl:ja-JP dism.exe /image:$Path3 /cleanup-image /checkhealth Dism /unmount-image /MountDir:$Path3 /Commit For our Chinese, we run a couple of powershell scripts to change the display language during the task sequence (nothing more than registry key settings). TS Step 1 - c:\windows\system32\cmd /c "c:\windows\system32\windowspowershell\v1.0\powershell.exe .\ChangeUILanguage_zh-TW.ps1" (Extract of ChangeUILanguage_zh-TW.ps1) Rename-Item -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -NewName zh-TW-old -Force Rename-Item -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\en-US -NewName zh-TW -Force Set-Location HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW New-ItemProperty -Name DefaultFallback -PropertyType string -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -Value "en-US" -Force TS Step 2 - Restart computer TS Step 3 - c:\windows\system32\cmd /c "c:\windows\system32\windowspowershell\v1.0\powershell.exe .\ChangeUILanguage_en-US.ps1" (Extract of ChangeUILanguage_zh-TW.ps1) Set-Location HKLM:\System\CurrentControlSet\Control\MUI\UILanguages Remove-ItemProperty -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -Name "DefaultFallback" -Force Rename-Item HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -NewName en-US -Force Rename-Item HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW-old -NewName zh-TW New-ItemProperty -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -Name "DefaultFallback" -PropertyType string -Value "en-US" -Force New-ItemProperty -Path HKLM:\System\CurrentControlSet\Control\MUI\UILanguages\zh-TW -Name "en-US" -PropertyType MultiString -Force

Guessing here, but perhaps your TPM is not set to enabled or active, and as your third slide shows - Pre-provision Bitlocker will be skipped if TPM is not enabled. Introduce a pause before the Pre-Provision step, then run debug window (F8) with the following command: wmic /namespace:\\root\cimv2\security\microsofttpm path win32_tpm get * /format:list You want to see: IsActivated_InitialValue=TRUE IsEnabled_InitialValue=TRUE IsOwned_InitialValue=FALSE

Not tested, but couldn't you set a local group policy that defines your proxy and home pages for you? When you login to the domain, the domain, site or OU policies should take precendence over the local settings. Since policy should apply in the order of OU, Domain, Site, Local and you are only going to get OU, Domain and Site when you are connecting to the domain, it might work out. However you would still have to define what the home page and proxy are (set them as not defined or disabled) on the local policy so they are rewritten when you drop from the domain. You might also have to apply a gpupdate /force for it to take effect.

I would bet that it is your problem. HK is 14/15 hrs ahead of US so the TS is looking at something in the future....

Not certain this is it, but what version of TPM chip is installed on the Panasonics?

Morrell, You'll need to provide some details about your situation. 1) What type of package is the application (.msi, setup.exe, etc). 2) Have you created a SCCM package for the application and pushed to the DPs (presumably you have if it installs via collection). What does the program look like for your application package? 3) Have you looked at the smsts.log files at the point it fails to install? a) recommend adding "pauses" (http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/?hl=%2Bpause+%2Btask+%2Bsequence) in your task sequence before and after the installation step so you can enter the debug mode (F8) and look at the error or manually run the install command to see the result.

I think I misled you a bit. I don't think en-UK is inherently a language pack (lp.cab) unto itself. It is part of the English language pack so the dism isn't needed. If you needed to add a true lp.cab (think Japanese ja-JP or Chinese zh-CN/zh-TW for example, the dism command would be the way to go). I think what you want to do is localize your build so that it comes out as default en-uk, thus the date/time values are presented correctly, pounds instead of dollars are represented and the keyboard is localized as well. To do this you will want to set the system locale, user locale and the display locale to en-UK (perhaps the keyboard as well). Here is an example of the xml file you would create and place on the system you are building up: <gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend"> <!--User List--> <gs:UserList> <gs:User UserID="Current" CopySettingsToDefaultUserAcct="true" CopySettingsToSystemAcct="true"/> </gs:UserList> <!--location--> <!--United Kingdom = 242--> <gs:LocationPreferences> <gs:GeoID Value="242"/> </gs:LocationPreferences> <!--System Locale--> <gs:SystemLocale Name="en-UK"/> <!--User Locale--> <gs:UserLocale> <gs:Locale Name="en-UK" ResetAllSettings="true" SetAsCurrent="true"/> </gs:UserLocale> <!--Display Language--> <gs:MUILanguagePreferences> <gs:MUILanguage Value="en-UK"/> <gs:MUIFallback Value="en-US"/> </gs:MUILanguagePreferences> </gs:GlobalizationServices> Then run a command line in the SCCM task sequence and call the .xml file: control.exe intl.cpl,, /f:"C:\Temp_Location_For_Files\Locale_UK.xml" It is really the control.exe intl.cpl that is doing the work. Note that this has to be run after the OS is installed for the .cpl to function.

Morrell, Can you be more specific on what you are trying to do? Are you looking to add a language pack (lp.cab) to the en-us .wim or are you trying to add an additional display language or are you trying to modify the locale information. The later can be done with registry settings, a locale.xml and/or an unattend.xml file. The former can be done with a couple of dism commands like: c:\windows\system32\dism.exe /image:c:\tempfolder /Add-Package /PackagePath:lp.cab /noRestart dism.exe /image:c:\tempfolder /set-UILang:en-UK /set-SysLocale:en-UK /set-UserLocale:en-UK /set-LayeredDriver:1 /set-AllIntl:en-UK Validate with: c:\windows\system32\dism.exe /image:c:\tempfolder /Get-Intl Ref: https://sccmentor.wordpress.com/2013/06/11/add-language-packs-to-an-offline-wim-file/ https://technet.microsoft.com/en-us/library/hh824893.aspx

Recommend looking at these if you are planning on using the customsettings.ini https://social.technet.microsoft.com/Forums/en-US/8fe17352-a20c-496c-83fd-cf9b9fdfa199/customsettingsini-bootstrapini-settings?forum=mdt https://anothermike2.wordpress.com/2012/04/21/back-to-basic-customsettings-ini-explained/ https://mdtguy.wordpress.com/2013/07/12/mdt-customsettings-ini-tips-tricks/ https://anothermike2.wordpress.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt/

Ok. So how will you capture the username? Through an .hta? http://www.windows-noob.com/forums/index.php?/topic/3476-introducing-the-windows-noobcom-frontend-hta-ver-10/

Hope you found your answer, if not.... .ps1 script http://blogs.technet.com/b/heyscriptingguy/archive/2013/12/25/powertip-add-computer-to-security-group-with-powershell.aspx .vbs http://it.peikkoluola.net/2013/04/23/join-a-computer-to-an-active-directory-security-group-vbs/

There are several ways to do that, how do you intend to input the logged in user name and are you doing this in WinPE or after the OS is installed? Outline of a couple script ways below. You can also create the variable within the TaskSequence through the Add - General - Set Task Sequence Variable; but I don't think that was your intent.... ---- .vbs file 'Setup the environment Set oTSEnv = CreateObject("Microsoft.SMS.TSEnvironment") strName = strInputName 'Write the TSVariable oTSEnv("genericTSvariablename") = strUserName Then call %genericTSvariablename% as you do in your example ----- .ps1 #Call SMS environment $Tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment $strName = $Tsenv.value("genericTSvariablename") Then call %genericTSvariablename% as you do in your example

Have you tried using Powershell? Get-ADComputer -identity <system name> | Select-Object -property DistinguishedName Should return the DistinguishedName parameter http://ss64.com/ps/get-adcomputer.html

Sorry, Kevin, I don't have experience with deploying Applications this way. We install our apps in OSD as Packages and based on bare metal provisioning assumptions. You might look at the following posts: https://social.technet.microsoft.com/Forums/en-US/b26f9b2b-e196-4323-99fb-6b0ad2595a3d/sccm-2012-sp1-task-sequence-installing-applications?forum=configmanagerosdand http://blogs.technet.com/b/inside_osd/archive/2011/06/20/configuration-manager-2012-user-device-affinity-and-os-deployment.aspx Looks like they are leveraging the pre-deploy option. Also look at the last post, where fusiongroup is querying a collection and then creating a list of apps to install. However I believe both of these methods are predicated on the computer object existing before you start the OSD and being a member of the application collections.

This might be the issue. Instead of using the General step "Install Applications" try using "Install Package".

I think I misunderstood what you are trying to do. Are you trying to install the package using the OSD process or are you trying to use the CCM client to pull the install? I am not sure that you can do the later until the system has completed the OSD process and the client has fully "checked in" with the SCCM servers/inventory. If you are doing the former, select the Task Sequence you are using and ensure that the References tab shows that your Software package is listed,the compliance is at 100% and the PackageID value matches. For packages that are installed during the OSD you should have a folder structure like: c:\_smstasksequence\packages\<pkgid> where you can find your application install.

You are saying the SCCM package itself never gets copied to your client? I.e. you don't see a directory name that matches the PackageID number on the HD of the client?

Can you add a "pause" prior and after your application install. Create a "Run command line" with: cmd /c start "cmd" /wait cmd Then when it is paused, you can open a command prompt (F8) From the command prompt find your application package that should be downloaded to your system, then manually run the install command (same as your program statement). Or: msiexec.exe /i <application.msi> /limev c:\logs\application.log Hopefully you will see why the application is not installing.

Ok, you will need to look at the SMSTS.log and find the section where it is supposed to be installing the app. It should give you an indication of what is going on, if it is skipped or failing to install, etc. I recommend viewing the .log with cmtrace, and then searching (CTRL+F) for the step (use the name of your step as the search item). Copy that snippet here if you need further help....

What does your Program line look like? I assume you are installing this as a SCCM Package.

What kind of install is it? .msi based? If so, I recommend setting your package install to include some install logging options. E.g. /limev c:\logs\application.log

You would create a second policy that sets the password to never expire. Link it before the policy that sets the password policy to change every x days. Since it is set prior it will be applied first thus following policy settings will be "ignored" (unless you implement loopback). Computer Configuration | Policies | Windows Settings | Security Settings | Account Policies | Password Policy Set the Max pwd age to 0 Set the Min pwd age to 0 Obviously you are running at risk by implementing this policy.

Are you referring to the locale parameters? http://technet.microsoft.com/en-us/library/cc766421(v=ws.10).aspx

Shooting from the hip on question 2, but I think you should be able to use an unattend.xml file to define the resolution parameters. The format looks like this post: https://social.technet.microsoft.com/Forums/windows/en-US/fbb5f946-1ab0-49a3-bafc-d19f5845b54d/optimal-screen-resolution-and-refresh-rate-during-unattended-install-of-windows-7-x64?forum=w7itproinstall

How about using a wmi query? >wmic /namespace:\\root\cimv2\security\microsofttpm path Win32_tpm get * /format:list Result: IsActivated_InitialValue=TRUE IsEnabled_InitialValue=TRUE IsOwned_InitialValue=TRUE ManufacturerId=1229346816 ManufacturerVersion=3.17 ManufacturerVersionInfo=0311000800 PhysicalPresenceVersionInfo=1.2 SpecVersion=1.2, 2, 2