Enabling Bitlocker through MDT 2013

October 20, 2016, 12:20 pm

≫ Next: MDT 2013 U2 installing OS a second time.

≪ Previous: MDT 2013 Install Language Packs

Guys/Gals,

Could someone help me with getting my task sequence setup to enable bitlocker during deployment? I found an article that says a way to do it but it doesnt get specific on the steps. I posted the part of the article below. Has anyone configured theirs this way? I would like to see exactly how to accomplish these steps. Thanks!

Configure the Windows 8.1 task sequence to enable BitLocker

When configuring a task sequence to run any BitLocker tool, either directly or using a custom script, it’s helpful if you also add some logic to detect whether the BIOS is already configured on the machine. In this task sequence, we are using a sample script (ZTICheckforTPM.wsf) from the Deployment Guys web page to check the status on the TPM chip. You can download this script from the Deployment Guys Blog post, Check to see if the TPM is enabled. In the following task sequence, we have added five actions:

Check TPM Status. Runs the ZTICheckforTPM.wsf script to determine if TPM is enabled. Depending on the status, the script will set the TPMEnabled and TPMActivated properties to either true or false.
Configure BIOS for TPM. Runs the vendor tools (in this case, HP, Dell, and Lenovo). To ensure this action is run only when necessary, add a condition so the action is run only when the TPM chip is not already activated. Use the properties from the ZTICheckforTPM.wsf.
Note
It is common for organizations wrapping these tools in scripts to get additional logging and error handling.
Restart computer. Self-explanatory, reboots the computer.
Check TPM Status. Runs the ZTICheckforTPM.wsf script one more time.
Enable BitLocker. Runs the built-in action to activate BitLocker.

Note
It is common for organizations wrapping these tools in scripts to get additional logging and error handling.

Daniel F. Willingham

↧

MDT 2013 U2 installing OS a second time.

October 22, 2016, 7:18 am

≫ Next: Windows 7 SP1 Convenience Update (KB3125574) and reference image - issues?

≪ Previous: Enabling Bitlocker through MDT 2013

I had this issue on another Task Sequence and recreated the entire VM, Capture and Deploy TS. It's doing it again on a TS I just built.

Drivers get injected, Image gets applied. Then, when it gets to DISM.EXE, it sits there a while, then I see the progress bar again while it installs the OS a second time. This time, it goes much faster. If i check the live log, I can see % increase to 98%....99%....100%.....then 100%......100%..... endlessly.

I'm about to rebuild the entire Hyper-V VM again, recreate a whole new TS, Capture the WIM and make a whole new Deploy TS. I'm just wondering if anyone has seen this happen and if there's a much shorter fix than doing all of this. I have 9 other TS's built and running just fine. Some are Win7E, Win8E and Win10E 1607. This one doing it now is one I just made from scratch.

↧

Windows 7 SP1 Convenience Update (KB3125574) and reference image - issues?

October 22, 2016, 12:44 pm

≫ Next: Adding a prestart command to MDT Boot Image?

≪ Previous: MDT 2013 U2 installing OS a second time.

Does anyone are there issues nowdays when using Convenience Rollup update when building Windows 7 reference images? Johan Arwidmark wrote earlier in his blog about the issues:

http://deploymentresearch.com/Research/Post/521/Back-to-Basics-Building-a-Windows-7-SP1-Reference-Image-using-MDT-2013-Update-2

Heads up: Putting the Windows 7 SP1 Convenience Update (KB3125574) in your image will currently show a lot of failed updates once Windows update runs on the machine. The image seems still be ok, in my testing, but I don’t know for sure, and it sure doesn’t feel good deploying it. Microsoft is currently researching the issue, I will update the post once I have more info. Workaround for now: Just install the July 2016 rollup to get a working Windows Agent, and allow it to install the 300+ updates.

↧

Adding a prestart command to MDT Boot Image?

October 23, 2016, 3:46 am

≫ Next: Network Drivers Missing on Sysprep & Capture

≪ Previous: Windows 7 SP1 Convenience Update (KB3125574) and reference image - issues?

When using ConfigMgr there is possible to add prestart command when generating boot images. Is there a way to add prestart commands to MDT Boot images? I'm trying to run command that syncs time against domain controller before running any task sequences.

↧

Network Drivers Missing on Sysprep & Capture

October 24, 2016, 7:55 am

≫ Next: Out of Box Drivers

≪ Previous: Adding a prestart command to MDT Boot Image?

I know there are a million of these threads because I've read through nearly all of them, and none of them seem to be fixing my problem. I'm going to try to be as descriptive as possible, let me know if there is anything else that you need to know.

My company is about to start our PC Refresh schedule (giving users new PCs). Our goal is to capture the image of the current machine and deploy it to the new laptops using MDT. Whenever I try to capture an image of the current machine, I get "unable to connect to \\server\share. No network driver found for xxxxxxx."

I'm using MDT 2013 Update 2. The target OS is Windows 7 Enterprise 64 bit. We are a Dell shop, so both machines are Dells. I'm testing on an optiplex but the machines will be latitudes (mostly). My MDT deployment share is located on a remote shared drive that I have full admin rights to. I downloaded the network driver from Dell and uploaded just the ONE driver for the PCs NIC into Out-Of-Box Drivers. I have MDT only creating a boot file for x64 and the selection profile is All Drivers and Packages>Include All Drivers From The Selection Profile. The task sequence is just the vanilla Sysprep and Capture. I have updated the deployment share with completely new boot files.

Can anyone lend a hand with this?

↧

Out of Box Drivers

October 24, 2016, 10:50 am

≫ Next: Sysprep and Capture in Audit Mode

≪ Previous: Network Drivers Missing on Sysprep & Capture

Hello

Im new to the Deployment Workbench.

Is there any way to have a powershell script in MDW to point to a network share to grab drivers ( during the deployment), looking up the model of the computer (wmic computersystem get model )?

Ideally, While deploying an image, the above command would get the model of the computer, then search my network share for that exact match (foldername), then grab all the drivers to install. The drivers are separated into video, audio, network etc.

I would rather not have to put all 56GB of drivers into an image.

Thank You

Terry

↧

Sysprep and Capture in Audit Mode

May 9, 2016, 8:12 am

≫ Next: MDT ConfigMgr Integrated - MDT Settings Package Clarification

≪ Previous: Out of Box Drivers

Let me begin by saying I know this is not the ideal way of imaging, but my hand is forced by others. Here is the scenario. I am being, "asked" to update an image and have it deployed through MDT. I normally create, modify, and capture image using MDT, so I am a bit lacking in the, "older" method of image sysprep and capture and am looking for some help. I have an image loaded. It is in Audit mode and I have made my customizations. Everything looks great. I run the sysprep command, (generalize, oobe, shutdown, unattend.xml). I boot into WinPE and capture the image. Import it into MDT. Deploy through MDT. Works flawlessly if I do not use the copyprofile setting, but if I use copyprofile, I get the dreaded, "could not parse..." message. I can get past this by opening the registry and changing the childcompletion setting from 1 to 3. Finally,,,, my question! Any idea what is happening,,, and what does changing the childcompletion setting do? Why is the childcompletion setting at 1 to begin with? Sorry if this sounds like rambling. Thanks for the help.

↧

MDT ConfigMgr Integrated - MDT Settings Package Clarification

October 25, 2016, 10:28 am

≫ Next: ZTIWindowsUpdate error - Incorrect function

≪ Previous: Sysprep and Capture in Audit Mode

Hi,

We are moving from Standalone MDT environment to ConfigMgr integrated with MDT environment. In our current standalone MDT environment, we have 6 different task sequences. Each custom image has an unattended associated with it.

With MDT integrated with ConfigMgr, would it be that if we were to have 6 different task sequences, that I should at the least generate new settings package for each task sequence.

I am confused as in standalone MDT there is one customsettings.ini which is part of deployment share. With MDT integrated customsettings.ini and unattend.xml are part of MDT Settings Package. I can't use a single unattend.xml for all 6 different images. I need clarification as to what is needed here.

I thank you in advance to who that will reply. Thanks.

↧

ZTIWindowsUpdate error - Incorrect function

October 25, 2016, 1:30 pm

≫ Next: Is there any way to make WDS pxe boot to local harddisk UEFI OS

≪ Previous: MDT ConfigMgr Integrated - MDT Settings Package Clarification

Hello all.

I am trying to run through MDT to create an updated Win7 Ent x64 golden image. All of the sudden I am seeing errors when it hits the ZTIWindowsUpdate with an incorrect function.

I have attached part of the windowsUpdate.log (too big to paste the whole thing) from the VM that I am using to create my golden image on. This process has worked great before.

WINDOWSUPDATE.LOG

2016-10-25 13:29:21:593 876 9e4 Service *************
2016-10-25 13:29:21:609 876 9e4 Service ** START ** Service: Service startup
2016-10-25 13:29:21:609 876 9e4 Service *********
2016-10-25 13:29:22:843 876 9e4 Agent   * WU client version 7.6.7601.23435
2016-10-25 13:29:23:031 876 9e4 Agent   * Base directory: C:\windows\SoftwareDistribution
2016-10-25 13:29:23:031 876 9e4 Agent   * Access type: No proxy
2016-10-25 13:29:24:093 876 9e4 Agent   * Network state: Connected
2016-10-25 13:29:36:546 876 9e4 AU Sending shutdown notification
2016-10-25 13:29:36:546 876 9e4 AU AU initiates service shutdown
2016-10-25 13:29:36:609 876 9e4 Report WARNING: InitializeWriteBufferTimestamp failed with hr = 8024f001.
2016-10-25 13:29:36:609 876 9e4 Report CWERReporter::Init succeeded
2016-10-25 13:29:37:171 876 9e4 Report *********** Report: Initializing static reporting data ***********
2016-10-25 13:29:37:171 876 9e4 Report   * OS Version = 6.1.7601.1.0.65792
2016-10-25 13:29:37:171 876 9e4 Report   * OS Product Type = 0x00000004
2016-10-25 13:29:37:250 876 9e4 Report   * Computer Brand = Microsoft Corporation
2016-10-25 13:29:37:250 876 9e4 Report   * Computer Model = Virtual Machine
2016-10-25 13:29:37:250 876 9e4 Report   * Bios Revision = 090006
2016-10-25 13:29:37:250 876 9e4 Report   * Bios Name = BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06
2016-10-25 13:29:37:250 876 9e4 Report   * Bios Release Date = 2012-05-23T00:00:00
2016-10-25 13:29:37:250 876 9e4 Report   * Locale ID = 1033
2016-10-25 13:29:37:640 876 9e4 AU ########### AU: Uninitializing Automatic Updates ###########
2016-10-25 13:29:37:828 876 9e4 Service *********
2016-10-25 13:29:37:828 876 9e4 Service ** END ** Service: Service exit [Exit code = 0x240001]
2016-10-25 13:29:37:828 876 9e4 Service *************
2016-10-25 13:33:08:328 892 16c Misc =========== Logging initialized (build: 7.6.7601.23435, tz: -0500) ===========
2016-10-25 13:33:08:343 892 16c Misc   = Process: C:\windows\system32\svchost.exe
2016-10-25 13:33:08:343 892 16c Misc   = Module: c:\windows\system32\wuaueng.dll
2016-10-25 13:33:08:328 892 16c Service *************
2016-10-25 13:33:08:343 892 16c Service ** START ** Service: Service startup
2016-10-25 13:33:08:343 892 16c Service *********
2016-10-25 13:33:08:640 892 16c Agent   * WU client version 7.6.7601.23435
2016-10-25 13:33:08:875 892 16c Agent   * Base directory: C:\windows\SoftwareDistribution
2016-10-25 13:33:09:015 892 16c Agent   * Access type: No proxy
2016-10-25 13:33:09:046 892 16c Agent   * Network state: Connected
2016-10-25 13:33:45:847 892 16c Report CWERReporter::Init succeeded
2016-10-25 13:33:45:988 892 16c Report *********** Report: Initializing static reporting data ***********
2016-10-25 13:33:45:988 892 16c Report   * OS Version = 6.1.7601.1.0.65792
2016-10-25 13:33:45:988 892 16c Report   * OS Product Type = 0x00000004
2016-10-25 13:33:46:050 892 16c Report   * Computer Brand = Microsoft Corporation
2016-10-25 13:33:46:050 892 16c Report   * Computer Model = Virtual Machine
2016-10-25 13:33:46:050 892 16c Report   * Bios Revision = 090006
2016-10-25 13:33:46:050 892 16c Report   * Bios Name = BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06
2016-10-25 13:33:46:050 892 16c Report   * Bios Release Date = 2012-05-23T00:00:00
2016-10-25 13:33:46:050 892 16c Report   * Locale ID = 1033
2016-10-25 13:33:46:472 892 16c AU ########### AU: Uninitializing Automatic Updates ###########
2016-10-25 13:33:46:613 892 16c Service *********
2016-10-25 13:33:46:613 892 16c Service ** END ** Service: Service exit [Exit code = 0x240001]
2016-10-25 13:33:46:613 892 16c Service *************
2016-10-25 13:33:48:269 892 568 Misc =========== Logging initialized (build: 7.6.7601.23435, tz: -0500) ===========
2016-10-25 13:33:48:269 892 568 Misc   = Process: C:\windows\system32\svchost.exe
2016-10-25 13:33:48:269 892 568 Misc   = Module: c:\windows\system32\wuaueng.dll
2016-10-25 13:33:48:269 892 568 Service *************
2016-10-25 13:33:48:269 892 568 Service ** START ** Service: Service startup
2016-10-25 13:33:48:269 892 568 Service *********
2016-10-25 13:33:48:269 892 568 Agent   * WU client version 7.6.7601.23435
2016-10-25 13:33:48:269 892 568 Agent   * Base directory: C:\windows\SoftwareDistribution
2016-10-25 13:33:48:269 892 568 Agent   * Access type: No proxy
2016-10-25 13:33:48:269 892 568 Agent   * Network state: Connected
2016-10-25 13:33:50:316 892 9e0 Report CWERReporter::Init succeeded
2016-10-25 13:33:50:316 892 9e0 Agent *********** Agent: Initializing Windows Update Agent ***********
2016-10-25 13:33:50:316 892 9e0 Agent   * Prerequisite roots succeeded.
2016-10-25 13:33:50:316 892 9e0 Agent *********** Agent: Initializing global settings cache ***********
2016-10-25 13:33:50:316 892 9e0 Agent   * WSUS server:http://WSUS-ServerName
2016-10-25 13:33:50:316 892 9e0 Agent   * WSUS status server:http://WSUS-ServerName
2016-10-25 13:33:50:316 892 9e0 Agent   * Target group: WIM Update
2016-10-25 13:33:50:316 892 9e0 Agent   * Windows Update access disabled: No
2016-10-25 13:33:50:347 892 568 Report *********** Report: Initializing static reporting data ***********
2016-10-25 13:33:50:347 892 568 Report   * OS Version = 6.1.7601.1.0.65792
2016-10-25 13:33:50:347 892 568 Report   * OS Product Type = 0x00000004
2016-10-25 13:33:50:347 892 9e0 DnldMgr Download manager restoring 0 downloads
2016-10-25 13:33:50:347 892 568 Report   * Computer Brand = Microsoft Corporation
2016-10-25 13:33:50:347 892 568 Report   * Computer Model = Virtual Machine
2016-10-25 13:33:50:347 892 568 Report   * Bios Revision = 090006
2016-10-25 13:33:50:347 892 568 Report   * Bios Name = BIOS Date: 05/23/12 17:15:53 Ver: 09.00.06
2016-10-25 13:33:50:347 892 568 Report   * Bios Release Date = 2012-05-23T00:00:00
2016-10-25 13:33:50:347 892 568 Report   * Locale ID = 1033
2016-10-25 13:33:50:394 892 9e0 Agent Attempt 0 to obtain post-reboot results.
2016-10-25 13:33:50:488 892 9e0 Handler Using CBS interface ICbsSession7
2016-10-25 13:33:50:957 892 9e0 Handler Post-reboot status for package Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4: 0x00000000.
2016-10-25 13:33:51:238 2472 70c Misc =========== Logging initialized (build: 7.6.7601.23435, tz: -0500) ===========
2016-10-25 13:33:51:238 2472 70c Misc   = Process: C:\windows\system32\cscript.exe
2016-10-25 13:33:51:238 2472 70c Misc   = Module: C:\Windows\system32\wuapi.dll
2016-10-25 13:33:51:238 2472 70c COMAPI -------------
2016-10-25 13:33:51:253 2472 70c COMAPI -- START -- COMAPI: Search [ClientId = <NULL>]
2016-10-25 13:33:51:269 2472 70c COMAPI ---------
2016-10-25 13:33:51:332 892 a44 Agent *************
2016-10-25 13:33:51:332 892 a44 Agent ** START ** Agent: Finding updates [CallerId = <<PROCESS>>: cscript.exe]
2016-10-25 13:33:51:332 892 a44 Agent *********
2016-10-25 13:33:51:332 892 a44 Agent   * Online = Yes; Ignore download priority = No
2016-10-25 13:33:51:332 892 a44 Agent   * Criteria = "IsInstalled = 0 and IsHidden = 0 and Type = 'Software'"
2016-10-25 13:33:51:332 892 a44 Agent   * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
2016-10-25 13:33:51:332 892 a44 Agent   * Search Scope = {Machine}
2016-10-25 13:33:51:332 2472 70c COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
2016-10-25 13:33:51:519 892 a44 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-10-25 13:33:51:519 892 a44 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =http://WSUS-ServerName/ClientWebService/client.asmx
2016-10-25 13:33:51:566 892 a44 PT WARNING: RegisterComputer failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2016-10-25 13:33:51:566 892 a44 PT WARNING: PTError: 0x80244019
2016-10-25 13:33:51:566 892 a44 PT WARNING: ClientWebService->RegisterComputer failed, hr=0x80244019, Not Fatal
2016-10-25 13:33:51:582 892 a44 PT WARNING: SyncUpdates failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2016-10-25 13:33:51:582 892 a44 PT WARNING: PTError: 0x80244019
2016-10-25 13:33:51:582 892 a44 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244019
2016-10-25 13:33:51:582 892 a44 PT WARNING: Sync of Updates: 0x80244019
2016-10-25 13:33:51:582 892 a44 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2016-10-25 13:33:51:582 892 a44 Agent   * WARNING: Failed to synchronize, error = 0x80244019
2016-10-25 13:33:51:597 892 a44 Agent   * WARNING: Exit code = 0x80244019
2016-10-25 13:33:51:597 892 a44 Agent *********
2016-10-25 13:33:51:597 892 a44 Agent ** END ** Agent: Finding updates [CallerId = <<PROCESS>>: cscript.exe]
2016-10-25 13:33:51:597 892 a44 Agent *************
2016-10-25 13:33:51:597 892 a44 Agent WARNING: WU client failed Searching for update with error 0x80244019
2016-10-25 13:33:51:597 2472 820 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = <NULL>]
2016-10-25 13:33:51:644 2472 820 COMAPI   - Updates found = 0
2016-10-25 13:33:51:722 2472 820 COMAPI   - WARNING: Exit code = 0x00000000, Result code = 0x80244019
2016-10-25 13:33:51:785 2472 820 COMAPI ---------
2016-10-25 13:33:51:832 2472 820 COMAPI -- END -- COMAPI: Search [ClientId = <NULL>]
2016-10-25 13:33:51:894 2472 820 COMAPI -------------
2016-10-25 13:33:51:941 2472 70c COMAPI WARNING: Operation failed due to earlier error, hr=80244019
2016-10-25 13:33:52:003 2472 70c COMAPI FATAL: Unable to perform synchronous search. (hr=80244019)
2016-10-25 13:33:52:050 2472 70c COMAPI ISusInternal::DisconnectCall failed, hr=8024000C
2016-10-25 13:33:52:066 2472 70c COMAPI waiting for worker thread to complete
2016-10-25 13:33:55:613 892 a44 Report REPORT EVENT: {E0864B6B-EB86-41B4-8C2C-180144890018} 2016-10-25 13:33:51:035-0500 1 183 101 {5A44EA4D-9446-49BC-AB5F-71C9A8FE21B4} 501 0 wusa Success Content Install Installation Successful: Windows successfully installed the following update: Update for Windows (KB3125574)
2016-10-25 13:33:55:613 892 a44 Report REPORT EVENT: {E2217D0B-8085-47DE-86A5-A6099EF5FF91} 2016-10-25 13:33:51:597-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 <<PROCESS>>: cscript.exe Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
2016-10-25 13:33:55:738 892 a44 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2016-10-25 13:33:55:738 892 a44 Report WER Report sent: 7.6.7601.23435 0x80244019(0) 0000000-0000-0000-0000-000000000000 Scan 0 0 <<PROCESS>>: cscript.exe {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
2016-10-25 13:34:33:300 892 568 AU ########### AU: Initializing Automatic Updates ###########
2016-10-25 13:34:33:316 892 568 AU   # WSUS server:http://WSUS-ServerName
2016-10-25 13:34:33:316 892 568 AU   # Detection frequency: 22
2016-10-25 13:34:33:316 892 568 AU   # Target group: WIM Update
2016-10-25 13:34:33:316 892 568 AU   # Approval type: Scheduled (User preference)
2016-10-25 13:34:33:316 892 568 AU   # Scheduled install day/time: Every day at 3:00
2016-10-25 13:34:33:316 892 568 AU   # Auto-install minor updates: Yes (User preference)
2016-10-25 13:34:33:316 892 568 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2016-10-25 13:34:33:347 892 568 AU Setting AU scheduled install time to 2016-10-26 08:00:00
2016-10-25 13:34:33:347 892 568 AU Successfully wrote event for AU health state:0
2016-10-25 13:34:33:347 892 568 AU Initializing featured updates
2016-10-25 13:34:33:347 892 568 AU Found 0 cached featured updates
2016-10-25 13:34:33:347 892 568 AU Successfully wrote event for AU health state:0
2016-10-25 13:34:33:347 892 568 AU Successfully wrote event for AU health state:0
2016-10-25 13:34:33:347 892 568 AU AU finished delayed initialization
2016-10-25 13:34:33:347 892 568 AU #############
2016-10-25 13:34:33:347 892 568 AU ## START ## AU: Search for updates
2016-10-25 13:34:33:347 892 568 AU #########
2016-10-25 13:34:33:347 892 568 AU <<## SUBMITTED ## AU: Search for updates [CallId = {1F668623-48AC-488D-B126-4286976C0F81}]
2016-10-25 13:34:33:347 892 a44 Agent *************
2016-10-25 13:34:33:347 892 a44 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-10-25 13:34:33:347 892 a44 Agent *********
2016-10-25 13:34:33:347 892 a44 Agent   * Online = No; Ignore download priority = No
2016-10-25 13:34:33:347 892 a44 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2016-10-25 13:34:33:347 892 a44 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2016-10-25 13:34:33:347 892 a44 Agent   * Search Scope = {Machine}
2016-10-25 13:34:33:378 892 a44 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
2016-10-25 13:34:33:378 892 a44 Agent *********
2016-10-25 13:34:33:378 892 a44 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-10-25 13:34:33:378 892 a44 Agent *************
2016-10-25 13:34:33:378 892 6c8 AU >>## RESUMED ## AU: Search for updates [CallId = {1F668623-48AC-488D-B126-4286976C0F81}]
2016-10-25 13:34:33:378 892 6c8 AU   # 0 updates detected
2016-10-25 13:34:33:378 892 6c8 AU #########
2016-10-25 13:34:33:378 892 6c8 AU ## END ## AU: Search for updates [CallId = {1F668623-48AC-488D-B126-4286976C0F81}]
2016-10-25 13:34:33:378 892 6c8 AU #############
2016-10-25 13:34:33:378 892 6c8 AU Featured notifications is disabled.
2016-10-25 13:34:33:378 892 6c8 AU Setting AU scheduled install time to 2016-10-26 08:00:00
2016-10-25 13:34:33:378 892 6c8 AU Successfully wrote event for AU health state:0
2016-10-25 13:34:33:378 892 6c8 AU Successfully wrote event for AU health state:0
2016-10-25 13:34:38:347 892 a44 Report REPORT EVENT: {0DD7A86E-1217-4461-BD60-AB56A2E17F7E} 2016-10-25 13:34:33:347-0500 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.

↧

Is there any way to make WDS pxe boot to local harddisk UEFI OS

October 13, 2016, 6:17 pm

≫ Next: Problems updating Windows 7 with MDT 2013

≪ Previous: ZTIWindowsUpdate error - Incorrect function

Here is the background.
We want to ZTI deployment. So we keep PXE as the first bootloader.
But after installing windows, we need it to automatically chain to local harddisk OS.
I know the legacy pxe boot has such method via syslinux or some other way. But for UEFI PXE and UEFI local boot, i still find no solution.
Thanks

↧

Problems updating Windows 7 with MDT 2013

October 14, 2016, 2:00 am

≫ Next: Anyone else working with HP SoftPaq-based driver files?

≪ Previous: Is there any way to make WDS pxe boot to local harddisk UEFI OS

Does anyone else have Problems, updating their Windows 7 SP1 (x64 or x86) with the latest (September or October 2016) Windows Updates in MDT 2013?

I know that there are issues in Terms of the Windows Update Agent, when updating a fresh Windows 7. That's why I already installed the July 2016 Rollup for Windows 7, which includes the latest WUA Agent, before the Task Sequence reaches the "Windows Update (Pre-Application Installation)" Step.

I can see in the Progress Bar that Updates are actually getting installed, but get the following Error after 1-2 hours:

I can see in the WindowsUpdate.log that Windows is trying to install multiple different Updates, which failed at some Point.

The weird thing is, when I close the Error, Start the VM again and search for Updates, it will find 1 Update which gets installed successfully. At this Point Windows already lists 246 Updates, which were successfully installed during the Task Sequence

The last time I ran this Task Sequence was with the July 2016 Updates, which worked without any issues.

Does anyone have an idea what could possibly casue this?

Thanks in advance.

Simon Dettling | msitproblog.com | @SimonDettling

↧

Anyone else working with HP SoftPaq-based driver files?

February 25, 2010, 10:52 pm

≫ Next: deploying to vmware vm's - use MDT?

≪ Previous: Problems updating Windows 7 with MDT 2013

If anyone else here is dealing with HP computers you know what I mean. They offer their drivers in the form of these little .EXE-based files called SoftPaqs. They tend to be named something like ""SPxxxxx.exe". I have been setting these up in the MDT as APPLICATIONS and I'm running a set of silent install commands on each one to get them installed. If anyone wants to know here's the supported command syntax:

"SPxxxxx.exe is the SoftPaq to unpack
"-pdf" is a runtime switch that overrides the build parameters
"-f" is a runtime switch that overrides the default path set at build time
"-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
"-e" instructs the package to extract only, that is, do not run the component installation program.
-s -a -silent -reboot (Good for silent installs.)

My question is this:

Is anyone else doing this differently (specifically for HP SoftPaqs)?

I've read a few other posts and I've noticed that many people tend to go for a process that involves extracting drivers from vendors and getting them integrated into Out-Of-Box drivers. I'm just wondering if my method is the best. mainly because I need to associate a specific set of these drivers with specific task sequences and that is probing difficult when they are set up as Applications. Any thoughts/advice?

↧

deploying to vmware vm's - use MDT?

February 11, 2010, 11:52 am

≫ Next: Stuck on "Sysprep is working...Processing generalize phase Sysprep plugins..."

≪ Previous: Anyone else working with HP SoftPaq-based driver files?

Hello,

general discussion here... I'm thinking treating VM's like physical machines by deploying from MDT is not a good idea... the start to end time will be just like physical machines... yet virtualization offers so many performance gains that would go unutilized by doing that... right? I have not researched deployment options specific to vmware vm's, but I'm hoping starting this discussion thread here will give me some good insight as to what people are doing out there for deploying vm's... to clarify, I mean production deployments of vmare vm's, not just a setup for building images that will be deployed to physical machines.

1. has anyone been using MDT for this? as in the typical LTI deployment over the network?

2. how about using MDT media? that would cut out the network part, anyone doing that?

3. what else is out there?

comments?

↧

Stuck on "Sysprep is working...Processing generalize phase Sysprep plugins..."

June 18, 2016, 11:07 am

≫ Next: MDT CustomSettings.INI and Connection-specific DNS Suffix

≪ Previous: deploying to vmware vm's - use MDT?

Windows Server 2012 R2

MDT 2013 Update 2

Windows 10 Pro 64-bit

I built a new server, and I was able to install a brand new Windows 10 Pro 64-bit image on a laptop (HP EliteBook 850 G3) with no errors at all. Although, it was missing 3 drivers (bluetooth drivers, and NXP NewFieldProximity Provider driver, which were later found by a Microsoft update). I built my reference computer, and then progressed to capturing it by launching LiteTouch.vbs from my deploymentshare$. It runs successfully until the "Running action: Execute Sysprep" part. At this point, I am still able to ping the server, and browse to all folders and files in the deploymentshare$. However, when I look in Device Manager, I don't see any network adapters (except for the MS Kernel Debug Network Adapter). When I end the SysPrep tool from task manager, I get the following error message: "Can not find script file '\\SERVER\DeploymentShare$\Scripts\LTICleanup.wsf'." Then I can no longer ping the server or browse the deploymentshare$ I also get the following Deployment Summary:

FAILURE ( 6111 ): 1: Run Sysprep.exeLitetouch deployment failed, Return Code = -2147467259 0x80004005
No networking adapters found, The network drivers for your device are not present
SetNamedSecurityInfo() failed.SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful. 0x80070002.
Failed to run the action: Execute Sysprep.Unknown error (Error: 000017DF; Source: Unknown)
The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Execute Sysprep. Execution of task sequence failed.
Unknown error (Error: 000017DF; Source: Unknown)Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueEsW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramGetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

↧

MDT CustomSettings.INI and Connection-specific DNS Suffix

October 26, 2016, 11:17 am

≫ Next: Updates from WSUS Stuck Downloading for Server 2016 Reference Image Build

≪ Previous: Stuck on "Sysprep is working...Processing generalize phase Sysprep plugins..."

I have an environment with 2 domains. No trust between the domains.

I have a WSUS server in each domain.

My server hosting the MDT 2013 U2 deployment share is allowed through the boarder firewall between the two domains.

Basically I need to be able to deploy images to both domains (works) but depending on the "Connection-specific DNS Suffix" of the target, have it choose one of two WSUS servers.

I have my primary WSUS server defined in CustomSettings.ini today, but it fails at that step on the 2nd domain.

Instead of fighting the long battle to add a linked deployment share in my 2nd domain, is there away to leverage a UserExit script or other logic to choose which WSUS server to contact, based off of the "Connection-specific DNS Suffix"?

Thanks,

-Matt

There's no place like 127.0.0.1

↧

Updates from WSUS Stuck Downloading for Server 2016 Reference Image Build

October 25, 2016, 5:28 pm

≫ Next: A connection to the deployment share could not be made. DHCP lease was not obtained for any networking device!

≪ Previous: MDT CustomSettings.INI and Connection-specific DNS Suffix

Hello MDT Friends,

I am building my first reference image for Server 2016 and I am running into a similar issue I faced with Windows 10. During the Windows Update step, the process is stuck on Downloading updates for hours (so far 5 hours and counting). I was able to fix this issue for Windows 10 by adding a cumulative update as a package in MDT as described in this thread:

https://social.technet.microsoft.com/Forums/en-US/9941646e-648d-49e2-97a4-088e5cc0d917/windows-10-1607-stuck-when-downloading-updates-from-wsus-in-mdt-windows-update-task-sequence?forum=win10itprosetup

Has anyone been able to deploy a Server 2016 reference image with Windows Updates from WSUS?

As a stab in the dark I am trying to get https://support.microsoft.com/en-us/kb/3192366 added as a package. So far it is the latest Cumulative Update I was able to search google for.

I am using the latest official volume license image for server 2016.

Regards,

DLofstedt

↧

A connection to the deployment share could not be made. DHCP lease was not obtained for any networking device!

October 27, 2016, 7:17 am

≫ Next: MDT 2013 u2 WAIK 10 - Unable to create a Media

≪ Previous: Updates from WSUS Stuck Downloading for Server 2016 Reference Image Build

Error screen:

We are getting this error prompt after windows 7 OS TS completion during first boot of the laptop .Also laptop not installed with NIC & bluetooth drivers.

Issue is only in a single site laptops in which Imaging worked perfectly until last week.i have found only below errors in BDD.log and setupact.log

BDD.log

i have gone through some solution in msforum link below which says to add sleep time in litetouch.wsf file but unfortunately i cannot test that script changesin my environment .

https://social.technet.microsoft.com/Forums/en-US/5656b654-3f6d-444f-b650-f8dd2ff933d5/mdt-2010-deploy-dhcp-error?forum=mdt

Is issue really from DHCP or MDT 2013 bug ? if its MDT bug then the above sleep time update will really work .Seeking your help to understand and to isolate this issue better.

Nisajudeen

↧

MDT 2013 u2 WAIK 10 - Unable to create a Media

August 10, 2016, 12:18 am

≫ Next: MDT 2013 U1 install appx

≪ Previous: A connection to the deployment share could not be made. DHCP lease was not obtained for any networking device!

Hello Community,

I meet a problem while creating a Media from the DeploymentShare - Advanced Configuration - Media - Media001 - Update Media Content.

I use this method to create a USB MDT media for the Branch Office where there is no server.
It worked in the past but from the upgrade to WAIK 10 / WinPE 10, I'm unable to create a new Media...

Find below the message when I try to Update the media contents :

Starting MDT Media Update
Opened the media deployment share.

System.Management.Automation.CmdletInvocationException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.BDD.PSSnapIn.GenerateMDTMedia.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Of course, the Media folder is not inside the DeploymentShare, it's at the root of my D: drive.

How could I solve this problem? An idea?

Thanks by advance ! :)

↧

MDT 2013 U1 install appx

October 27, 2016, 8:21 am

≫ Next: usb port

≪ Previous: MDT 2013 u2 WAIK 10 - Unable to create a Media

Hello everybody !

I want install VLC store apps in my MDT Windows 10 master.

Then I've create businessstore account and I've download APPX, XLM license and APPX dependency files.

How to integrate APPX bundle installation in MDT 2013 U1 ?

I've tried create new application and in command line put path of APPX but dosen't work :(

My source is : https://blogs.technet.microsoft.com/mniehaus/2016/01/11/using-the-windows-store-for-business-with-mdt-2013/

Please help me :) !

Thanks ;)

↧

usb port

October 26, 2016, 8:21 pm

≫ Next: MDT 2013 U2 Database question with sccm 2012 1602 integration.

≪ Previous: MDT 2013 U1 install appx

My printer stopped working. I uninstalled and reinstalled about 4 times. I troubleshot it and it says the 2.0 usb printer device is not working on a usb 3.0 port. What does that mean> it was working at first. HELP

↧

Latest Images