Skip to main content

Latitude 10 Ste2 Enterprise Deployment with MDT 2012 and USB Media

Latitude 10 Ste2 Enterprise Deployment with MDT 2012 and USB Media

 
The Latitude 10 uses a Unified Extensible Firmware Interface (UEFI). UEFI is meant to replace the Basic Input/Output System (BIOS) firmware interface. The Latitude 10 does not have legacy support, so as a result SCCM 2007, MDT 2010, WinPE 3.0, and WDS (2008) infrastructure is not supported.

To deploy a Windows 8 image without 2012 infrastructure the use of a standalone MDT 2012 deployment share to create USB stick media is neccessary.

The finished media does not contain any sensitive credentials or product keys. The administrator is prompted for credentials to connect to the MDT database; it is here the Task Sequence is able to find/generate its computer name and join to the correct OU in AD.

Post SCCM collections will target these Latitude tablets and activate Office and Windows respectively.
 
Step A: Boot mode: UEFI Options1. Connect an Ethernet cable, USB keyboard, mouse and the USB media created to the cradle.
2. Slot the tablet on the cradle and power on using the top right button.
3 Press F12 until the UEFI Boot options appear and select the UEFI USB drive.
Step B: Installation Wizard1. The Litetouch wizard will automatically launch at which point the customsettings.ini and bootstrap.ini files are read.
2. Click begin to start the deployment
3. Shortly after clicking 'begin' you will be prompted for your WA.USERNAME credentials. Without valid input the Task Sequence will not proceed.
4. The build will take approx 25 minutes to complete. Once the post installation task have completed the system is rebooted. Only once the tablet waits at the login screen has the build finished.
5. If any errors occur during the build they will be logged in the BDD.log file and a RED summary screen is produced at the end. Otherwise the system reboots ready for the first user.
The steps below detail how the Deployment share, Task Sequence and media are created.

Step 1 - Create a deployment share
1.Within MDT, Deployment Workbench, right-click Deployment Shares and select New Deployment Share. Use the following settings for the New Deployment Share Wizard.
a.Deployment share path: C:\MDTProduction
b.Share name: MDTProduction
c.Deployment share description: MDT Production
d.Options:

Step 2 - Import the Windows 8 operating system
1.Using the Deployment Workbench, expand the MDT Production node, and select the Operating Systems node.
2. Right-click on the Operating Systems node, and select Import Operating System. Use the following settings for the Import Operating System Wizard.
a.Full set of source files D:\Setup\Windows 8 Enterprise x86
b.Destination directory name: Windows 8 Enterprise x86
3.After adding the operating system, change the Operating System name to Windows 8 Enterprise x86.
Step 3 - Import the drivers Download the Dell Cab file for the Latitude 10 STe2 from here and expand to C:\temp\ST2E-win8-A04-N86KN
1.Using the Deployment Workbench, in the MDT Production node, select the Out-Of-Box Drivers node, and create a folder named Windows 8 x86. Then, in the Windows 8 x86 folder, create a subfolder named 'Latitude10-Auto'.
2. Right-click the 'Latitude10-Auto' folder and select Import Drivers, use the following settings for the Import Driver wizard:
a.Driver source directory: C:\temp\ST2E-win8-A04-N86KN
3. .Using the Deployment Workbench, in the MDT Production node, select the Out-Of-Box Drivers node, and create a named 'Latitude10-Forced.
2. Right-click the 'Latitude10-Forced' folder and select Import Drivers, use the following settings for the Import Driver wizard:
a.The following drivers must be imported/copied in to this folder.
Name Manufacturer Version
AuthenTec BiometricDevice oem44.inf 4.0.0.89 AuthenTec 4.0.0.89
Broadcom Net bcmdhd63.inf 5.93.97.113 Broadcom 5.93.97.113
Broadcom Sensor oem6.inf 19.14.6362.4 Broadcom 19.14.6362.4
Broadcom System bcmfn2.inf 5.93.97.113 Broadcom 5.93.97.113
Broadcom System oem5.inf 19.14.6362.4 Broadcom 19.14.6362.4
Broadcom System oem50.inf 12.0.0.6100 Broadcom 12.0.0.6100
Intel Corporation System oem55.inf 6.2.9200.26576 Intel Corporation 6.2.9200.26576


Intel Corporation System oem57.inf 6.2.9200.26576 Intel Corporation 6.2.9200.26576



Intel Corporation System oem64.inf 6.2.9200.33472 Intel Corporation 6.2.9200.33472
Intel Corporation System oem65.inf 6.2.9200.33472 Intel Corporation 6.2.9200.33472
Intel Corporation System oem66.inf 6.2.9200.33472 Intel Corporation 6.2.9200.33472
Intel MEDIA oem61.inf 6.2.9200.33148 Intel 6.2.9200.33148
Microsoft HIDClass hidi2c.inf 6.2.9200.16461 Microsoft 6.2.9200.16461
Microsoft HIDClass msgpiowin32.inf 6.2.9200.16497 Microsoft 6.2.9200.16497
Microsoft SDHost sdbus.inf 6.2.9200.16548 Microsoft 6.2.9200.16548
Microsoft SecurityDevices tpm.inf 6.2.9200.16548 Microsoft 6.2.9200.16548
REALTEK MEDIA oem62.inf 6.2.9200.3067 REALTEK 6.2.9200.3067
Step 4 - Add the application 1.Using the Deployment Workbench, in the MDT Production node, select the Applications node.
2.Right-click the Applications node, and select New Application, Use the following settings for the New Application Wizard.
Microsoft Office Professional Plus
a.Application with source files
b.Application name: Microsoft Office Professional Plus
c.Version: 2013
d.Source Directory: Example C:Temp\Setup\Microsoft Office Professional Plus 2013
e.Specify the name of the directory that should be created: Microsoft Office Professional Plus 2013
f.Command Line: Setup.exe
g.Working directory: .\Applications\Microsoft Office Professional Plus 2013
-------------------
Dell Wireless Drivers
a.Application with source files
b.Application name: Dell Wireless Drivers
c.Version: 2013
d.Source Directory: Example C:Temp\Setup\Dell Wireless Drivers
e.Specify the name of the directory that should be created: Dell Wireless Drivers
f.Command Line: setup.exe /S /v/qb!
g.Working directory: .\Applications\Dell Wireless Drivers
-----------------------
SEP 12.1.3
a.Application with source files
b.Application name: SEP
c.Version: 12.1.3
d.Source Directory: Example C:Temp\Setup\SEP 12.1.3
e.Specify the name of the directory that should be created: SEP 12.1.3
f.Command Line: msiexec /i sep.msi /qn /l*v "C:\Windows\Contoso\Logs\Symantec_EndpointProtection_12.1.3001.165.log" IDCENABLE=0
g.Working directory: .\Applications\SEP 12.1.3
-----------------------
Microsoft Configuration Manager Client 2007 4.00.6487.2000
a.Application with source files
b.Application name: Microsoft Configuration Manager Client
c.Version: 2007 4.00.6487.2000
d.Source Directory: Example C:Temp\Setup\Microsoft Configuration Manager Client
e.Specify the name of the directory that should be created: Microsoft Configuration Manager Client 2007 4.00.6487.2000
f.Command Line: ccmsetup.exe
g.Working directory: .\Applications\Microsoft Configuration Manager Client 2007 4.00.6487.2000

Step 5 - Create Selection Profile1. Using the Deployment Workbench, in the MDT Production deployment share, right click the Advanced Configuration/Selection Profile node, and select 'New Selection profile'.
2. Under the General Settings input:
i.Selection Profile name: Latitude10-Auto
ii.Folder: All Applications
iii. Operating Systems: Windows 8 Enterprise x86
iii. Out-of-Box drivers: 'Latitude10-Auto' and 'Latitude10-Forced'
iiii.All Task Sequences
---
3. Using the Deployment Workbench, in the MDT Production deployment share, right click the Advanced Configuration/Selection Profile node, and select 'New Selection profile'.
4. Under the General Settings input:
i.Selection Profile name: Latitude10-Forced
ii. Out-of-Box drivers: 'Latitude10-Forced'

Step 6 - Create a task sequence
1.Using the Deployment Workbench, in the MDT Production deployment share, select the Task Sequences node.
2.Right-click on the Task Sequences node, and select New Task Sequence. Use the following settings for the New Task Sequence Wizard.
a.Task sequence ID: W8-X86-001
b.Task sequence name: Windows 8 Enterprise x86
c.Task sequence comments: Production Deployment
d.Template: Standard Client Task Sequence
e.Select OS: Windows 8 Enterprise x86
f.Do not specify a product key at this time
g.FullName: Contoso
h.Organization: Contoso
i.Internet Explorer home page: about:blank
j.Do not specify an Administrator password at this time and complete the wizard.
3. Double click Task sequence ID: W8-X86-001, and select the Task Sequence tab.
4. Within the 'Preinstall' node after 'Enable Bitlocker (offline) add two general tasks.
i. Inject Drivers: Selection Profile: Latitude-Auto
ii. Install Only matching drivers from selection profile
iii.Inject Drivers: Selection Profile: Latitude-force
iiii.Install all drivers from the selection profile.

Step 7 - Configure the deployment share settings
1.The Bootstrap.ini file has the following content
[Settings]
Priority=Default
[Default]
SkipBDDWelcome=YES
KeyboardLocale=en-US

2.The CustomSettings.ini file has the following content (controlling the MDT deployment wizard behavior and other deployment settings):
[Settings]
Priority= Default
Properties=MyCustomProperty
[Default]
_SMSTSOrgName=Windows 8
UserDomain=ops
OSInstall=YES
SkipAdminPassword=YES
AdminPassword=password
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=YES
SkipComputerBackup=YES
SkipUserData=YES
UserDataLocation=NONE
ComputerBackupLocation=NONE
SkipDeploymentType=NO
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
JoinDomain=ops.Contoso55.com
SkipProductKey=YES
SkipTaskSequence=YES
TaskSequenceID=W8-X86-001
SkipPackageDisplay=YES
SkipSummary=NO
SkipFinalSummary=YES
FinishAction=REBOOT
SkipTimeZone=YES
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
3.Right-click the MDT Production Deployment Share and select Properties.
4.In the Windows PE tab, in the Platform dropdown list, make sure x86 is selected.
5.In the General sub tab, configure the following settings:
a.In the Lite Touch Boot Image Settings area.
i.image description: MDT Production x86
ii.Clear the Generate a Lite Touch bootable ISO image check box
b.In the Windows PE Customizations area, set the Scratch space size to 256.
6.Click OK.
7.Right click the deployment share and select 'Update Deployment Share'
#----------------------------------------------------------------------------------------------------#
Requires 2012 infrastructure
Step 8 - Add the MDT 2012 Update 1 boot image to WDS 2012
1.In the WDS Console, expand DC01.com, right-click Boot Images and select Add Boot Image
2.Browse to the D:\MDTProduction\Boot\LiteTouchPE_x86.wim file and add the image with the default settings.

Step 9 - Deploy the Windows 8 Image
1.
Start your Latitude 10 Tablet, press F12 for PXE boot, and complete the Deployment Wizard using the below settings:
a.Password: P@ssw0rd
b.Select a task sequence to execute on this computer: Windows 8 Enterprise x86
c.Computer Name: LeaveDefault
#------------------------------------------------------------------------------------------------------------#
Step 8: Create Windows 8 Full source files USB media.
1.Within MDT 2012 update 1 Expand 'Advanced Configuration' and right click 'Media' and select 'New Media'.
2. On the General Settings page specify the following details:
i. Media Path: c:\temp\Latitude10Media
ii. Comments: Windows 8 Enterprise x86
iii. Selection Profile: Latitude10-auto
3. Right click 'MEDIA001' and click Properties'. Use the following settings.
i.Untick 'Generate x64 boot image
ii. Untick 'Generate a lite Touch bootable ISO Image'
iii. On the rules tab, copy the Customsettings.ini and Bootstrap.ini settings from STEP 6.
iii. Scratch space size: 256
4. Click Ok, Then Right click 'MEDIA001' and click 'Update Media Content'
Step 9: Deploy the Windows 8 Image.
Set up your USB flash drive. Important note that UEFI cannot read NTFS so it needs to be FAT formatted:
UEFI firmware interface requires 2012 infrastructure or a FAT32 formatted USB stick to boot from. The batch file below will list all available disks and prompt for the correct disk number to format into Fat32.
#USE WITH CAUTION#
@echo off
:loop
echo list disk|diskpart|find "Online"
set "disk=."
set /p "disk=Pick disk number above to destroy/reformat: "
echo.
echo list disk|diskpart|find "Disk %disk%"
if errorlevel 1 (
echo Invalid drive selection!
pause
goto :loop
) else (
pause>con
echo select Disk %disk%
echo clean
echo create partition primary
echo select partition=1
echo active
echo format fs=fat32 Label="Win8ISO" quick
echo assign
echo exit
)| Diskpart​
for /f %%D in ('wmic volume get DriveLetter^, Label ^| find "WIN8ISO"') do set usb=%%D
echo %usb%
robocopy c:\temp\Latitude10Media\Content %usb% /e /copy:DAT /r:1 /w:1
1.Once the USB stick has been formatted correctly, RoboCopy the Media files created in STEP 7 on to the root of the stick. The command below assumes the media directory specified was 'c:\temp\Latitude10Media' and the USB stick has been assigned the letter G:.
robocopy c:\temp\Latitude10Media\Content g:\ /e /copy:DAT /r:1 /w:1
Step A: Boot mode: UEFI Options
1. Connect an Ethernet cable, USB keyboard, mouse and the USB media created to the cradle.
2. Slot the tablet on the cradle and power on using the top right button.
3 Press F12 until the UEFI Boot options appear and select the UEFI USB drive.
Step B: Installation Wizard1. The Litetouch wizard will automatically launch at which point the customsettings.ini and bootstrap.ini files are read.
2. Click begin to start the deployment
3. Shortly after clicking 'begin' you will be prompted for your WA.USERNAME credentials. Without valid input the Task Sequence will not proceed.
4. The build will take approx 25 minutes to complete. Once the post installation task have completed the system is rebooted. Only once the tablet waits at the login screen has the build finished.
5. If any errors occur during the build they will be logged in the BDD.log file and a RED summary screen is produced at the end. Otherwise the system reboots ready for the first user.
Step 10: Capture a reference Windows 8 WIM
NOTE: A Reference Windows 8 wim should be captured with all available update.
1. Windows 8 Enterprise should now be deployed using the source media created in STEP 7
2.Install all available updates.
3. The addition of Hotfix 'Windows8-RT-KB2756872-x86.msu' must be installed to address a device driver/hardware issue.
4.Once the reference image has beenupdated run 'Sysprep with generalize (shutdown)'
i.Reference: C:\Windows\System32\sysprep\sysprep.exe.
5. Restart the tablet into WinPE. This can be achieved by loading the USB media detailed in STEP 8. Once the wizard begins press F8 to bring up a command prompt (DO NOT DEPLOY THE TASK SEQUENCE).
The following command will capture the syspreped Windows 8 image (located C:\) to the root of the USB stick (Assumed G:\).
Dism /Capture-Image /ImageFile:G:\Windows8.wim /CaptureDir:C:\ /Name:"Windows 8 Enterprise"
NOTE: FAT32 is limited to a maximum of 4GB files. Currently a standard image with updates will total 3.8GB without the compression switch. Until 2012 infrastructure is implemented the image should not contained any other preinstalled applications.
Step 11: Import the Captured Windows 8 operating system
1.Using the Deployment Workbench, expand the MDT Production node, and select the Operating Systems node.
2. Right-click on the Operating Systems node, and select Import Operating System. Use the following settings for the Import Operating System Wizard.
a.Custom image file: G:\Windows8.wim (destination drive used in STEP 9)
b.Destination directory name: Windows 8 Enterprise x86 -Captured

3.After adding the operating system, change the Operating System name to Windows 8 Enterprise x86- Captured
Step 12 - Update task sequence
1.Using the Deployment Workbench, in the MDT Production deployment share, select the Task Sequences node.
2. Double click Task sequence ID: W8-X86-001, and select the Task Sequence tab.
3. Within the 'Initialization' node before 'Gather local Only' add two general tasks.
i. Set Task Sequence Variable: UserID
ii. No Value
ii. Set Task Sequence Variable: UserPassword
iii.No Value
4. Within the 'Initialization' node After 'Gather local Only' create a Group called 'Set Computer Name'.
5. Create command beneath group called 'CMD MDTDatabase.ini' with the following command
i. cscript x:\deploy\scripts\ZTIGather.wsf /inifile:x:\deploy\control\MDTDatabase.ini
6. Create a group called 'Get Computer Name' with the following options defined.
i. If none of the condtions are true > Task sequence variable ContosoComputerName exists
7. Create Run Command Line called ''WS: Get Computer Name' with the following options
i Continue on error
ii. cscript.exe "x:\deploy\scripts\ZTI_ExecuteWebService.wsf" /wsIniFile:x:\deploy\control\WebServiceSettings.ini /wsSection:GetComputerNameByUUID /wsProperty:ContosoComputerName /wsOverwrite:False
8. Create a group called 'Generate New Name' with the following options defined
i. If none of the condtions are true > Task sequence variable ContosoComputerName exists
9. Create Run Command Line called 'WS: Generate Computer Name' with the following options
i. cscript.exe "x:\deploy\scripts\ZTI_ExecuteWebService.wsf" /wsIniFile:x:\deploy\control\WebServiceSettings.ini /wsSection:GenerateComputerName /wsProperty:ContosoComputerName /wsOverwrite:True
10. Create a group called 'Check Computer OU'
11. Create Run Command Line called 'WS: Get Parent OU' with the following options defined
i. cscript.exe "x:\deploy\scripts\ZTI_ExecuteWebService.wsf" /wsIniFile:x:\deploy\control\WebServiceSettings.ini /wsSection:GetComputerOU /wsProperty:ADObjectOU /wsOverwrite:True
12. Beneath this group add 'Set Task Sequence Variable'
i. Task Sequence Variable: MACHINEOBJECTOU
ii. Value: %ADObjectOU%
iii. If all conditions are true >
Task sequence variable AdObjectOU not equals %MACHINEOBJECTOU%
Task sequence variable AdObjectOU exists

Comments

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...