Failed to run the action: Enable BitLocker. Unspecified Error: (80004005)

Issue:-

When you run a Configuration Manager 2007 OSD Task Sequence that has the "Enable BitLocker" task in it, the task fails to run and BitLocker is not enabled on the PC. Looking the SMSTS.log reveals the below error message:

SMSTS.log

Executing command line: OSDBitLocker.exe /enable  /wait:False /mode:TPM /pwd:AD

==============================[ OSDBitLocker.exe ]==============================

Command line: "OSDBitLocker.exe" /enable /wait:False /mode:TPM /pwd:AD

Initialized COM

Command line for extension .exe is "%1" %*     OSDBitLocker   

Set command line: "OSDBitLocker.exe" /enable /wait:False /mode:TPM /pwd:AD

Target volume not specified, using current OS volume

To get Model String

For Drivers deployment , we need to find the exact Manufacturer and Model to deploy using SCCM. s We need to create WMI Query to install the Driver Package based on Make & Model.


Set objShell = CreateObject("WScript.Shell")
Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
strWinDir = objShell.ExpandEnvironmentStrings("%WinDir%")

Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_ComputerSystem")
For Each objItem In colItems
        Manufacturer = objItem.Manufacturer
        Model = objItem.Model
Next

strThisComputer = Manufacturer & " - " & Model

intRetVal = InputBox("Use model string below for Drivers.xml", "Get Make and Model", strThisComputer)

How to add Drivers in MDT 2012

How to add drivers in MDT
Select the deployment share you wish to add the drivers to (C:\Deployment Share)

How to Import Packages in MDT 2012

Importing OS Packages or Hotfixes

In our example, we will import a hotfix kb2028749 within our MDT Packages console. Similarly you can add any other package like Language packs.

1.       Download the OS Package and Import it in a folder on MDT server

MDT: Deploy Windows 7 without DHCP

We came across a scenario at one of our esteemed clients where we needed to deploy Windows 7 on hundreds of machine without the DHCP environment. So all the clients had Static IP assigned to it. When system boots into WinPE it doesn’t get the IP. It is easy in NEW COMPUTER scenario as when the system boots up into WinPE you can assign the Static IP from Welcome screen. But in case of REFRESH scenario we don’t get the Welcome screen in MDT 2010. To achieve the above requirement i have done the customization in the Task Sequence with script as shown below.

Create WinPE boot disk with ImageX

To create a build of Windows 7 we need to capture Windows 7 image from the reference machine with required configurations. We can do this using MDT or SCCM but here I am going to demonstrate you how you can create WinPE image with ImageX and use it to capture Windows 7 image. Below are the steps to create WinPE image using WAIK tools.

1.       Install Windows Automated Installation Kit (WAIK) on your technician machine

Unable to load DLL "wimgapi.dll" the specified module could not be found ( Exeption 0X800700E7 )

Issue:-

When you try to import OS in MDT Workbench you receive an error: Unable to load DLL "wimgapi.dll" the specified module could not be found (Exception 0X800700E7)

Resolution:-

After you installed Windows AIK you'll find wimgapi.dll is located in C:\Program Files\Windows AIK\Tools\x86

Copy the wimgapi.dll file to this location C:\Windows\System32. Then everything works fine as expected.

Hope this helps!!!

MDT: Custom Settings for Refesh Deployment

Below is the MDT 2010 Update 1 Custom Settings for Refresh (XP to Windows 7) scenario automated Deployment

[Settings]
Priority=Default
Properties=MyCustomProperty

MDT: Custom Settings for New Computer Deployment

Below is the MDT 2010 Update 1 Custom Settings for New Computer scenario automated Deployment

[Settings]
Priority=Default
Properties=MyCustomProperty

MDT: XP to Windows 7 Migration (Refresh)

Steps to perform upgrade user data from Windows XP to Windows 7

When doing the Windows 7 installation on a Windows XP machine through MDT LiteTouch.vbs script to upgrade the user data and settings, Please follow the below steps:

Start the Windows XP machine and open the deployment share folder located on MDT Server. Navigate to DeploymentShare$ -> Scripts -> LiteTouch.vbs and run LiteTouch.vbs.

MDT 2010 Deployment and Configuration

In this blog we will cover step by step process to install and configure Microsoft Deployment Toolkit for Windows 7 Deployment.

Pre-requisite:-

Windows Automated Installation Kit (WAIK) Installation Procedure

Please note that installing WAIK for Win7 on Windows Server 2008 doesn’t need these pre-requisites to be installed.

Launch Startcd.exe utility and install MSXML6.0 and .NET Framework 2.0 if you have not already installed via Windows Update or any other means.

SCCM 2007 R3 OSD Deployment

Through SCCM, OS can be deployed on multiple numbers of computers simultaneously. In SCCM, operating system can be deployed on machines using PXE boot method. This method is used to deploy OS on bare metal machines. OS deployment feature can be also used to upgrade an existing OS on the system. Multiple set of customised OS images can be created. As per the requirement, different OS images can be used for deploying on a particular set of computers.

In this section, the complete procedure for deploying OS is provided. Operating System deployment consists of the following configurations which have to be carried out as given below:-

· Installation of Pre-requisites for PXE boot method

· Installing PXE Service point role on SCCM server

· Creating a separate Collection for OS deployment

· Configuration of Boot Images

· Creating Computer Association for bare metal computers

· Capturing customised OS image from a reference computer

· Creating OS image package

· Creating Task Sequence for OS image

· Advertising Task Sequence on the Collection for deploying OS

ACT 5.6 Database Process Logs

Issue: The Application Compatibility Toolkit version 5.6 log processing server does not process logs gathered from Windows 7 or Windows Server 2008 R2 machines with Service Pack 1 installed. These logs are moved to the Failed folder on the log share and the data is not entered into the database.

To resolve this problem, an entry describing Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1 must be added to the ACT database's Dbo.OS table. To do so, run the following SQL statement against the database that the ACT log processing service is using:
1.       Go to Start menu and open SQL Server Management Studio.
2.       Select Databases and select your ACT database.
3.       Click New Query and copy the below code as per the ACT server OS.
4.       Execute the Query.

Disk Configuration Wizard Customization: MDT (WSIM)

This is regarding the activity recently I have completed at global IT services and consulting company . Their IT manager had a requirement that after creating the media when we boot up as per the LTI automation it automatically formats the drive and install new OS. But they want to see thewizard for format and partition during installation so that their IT engineer can manually decide on the partition to install and proceed with Windows 7 installaion.

Where is smsts.log located?

To troubleshoot the SCCM OSD deployment issues we can enable the F8 feature in our Windows PE boot images. Below is the process for the same:-

ü Enable the Command Prompt on your boot image
Boot images have an option to enable a command shell while running in Windows PE. This is turned off by default for security reasons but can be enabled on the “Windows PE”property page.