Requirement : Populate custom variables or inbuild variables by calling powershell or vbs script from customsetting.ini.

Example : i want to set OSDComputerName MDT variable after calling a script from customsetting.ini.

The script have necessary logic to create the computer name value and script will return computer name.

The customsetting.ini should receive the return value from script and update OSDComputerName variable

Is it possible to achieve ?

Could you please give me some pointers or blogs which explain how we can call powershell or vbs from customsetting.ini and manipulate the data based on the return value from script ?

verification

Hi all,

I do admit I am in a learning phase concerning MDT 2013 U2, so please bear with me on this probably simple issue.

Whenever I build a fresh Windows 7 x64 and insert a "Restart Computer" task sequence, it does reboot, but it always start up with a blank Litetouch wizard window and never resumes. This has been tested on a virtual PC as well as physical. Also with and without drivers. In fact I just tried to deploy a vanilla Windows 7 x64 with just that Restart Computer step added in State Restore and it fails too. Disk 0 is cleaned at every test. Network card is OK and access to Deployroot is fine too after the restart.

If needed I've uploaded the recent smsts.log here: SMSTS.log

Also a screenshot that shows that the Wizard.hta is trying to run from a local folder (C:\Users\...\Temp\DeploymentScripts\Wizard.hta), but that folder is empty:

In BDD.log it also seem to have trouble resuming:

About to run command: "C:\MININT\Tools\X64\TsmBootstrap.exe" /env:SAContinue	LiteTouch	14-06-2016 15:19:44	0 (0x0000)
Property LTIDirty is now = TRUE	LiteTouch	14-06-2016 15:19:44	0 (0x0000)
Command completed, return code = -2147467259	LiteTouch	14-06-2016 15:19:45	0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	14-06-2016 15:19:45	0 (0x0000)
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	14-06-2016 15:19:45	0 (0x0000)

Sometimes we need to be able to use a USB Media to deploy Windows. Everything works well when booting to the Deployment server using the boot ISO on a USB stick. But when we do this from a full USB Media, with the exact same Task Sequences, it fails at the"Copy Scripts" step in Preinstall just after the "Format and Partition Disk" step. Same result for both BIOS and UEFI formatting. It works if I format the disk in DISKPART from the console.

How can this be?

I'm posting this because I cannot seem to get a handle on this problem and I hope someone can lead me in the right direction.

I am using MDT 2013 Update 2 and deploying Windows 10 x64 Pro via USB to UEFI based computers (Surface Pro 3, Dell Latitude E7275, HP Elite 1012, etc...). The USB drive has been prepared in the same manner as described in MDT Media Deployment USB drive for UEFI computer. Taking it a step further I've also modified the process via powershell. The script is as follows:

Set-ExecutionPolicy Unrestricted

# The following command will set $Disk to USB drive selected with >60 GB of storage
Write-Output “Looking for a target”

$Disk = Get-Disk | Where-Object –FilterScript {$_.Bustype -Eq "USB" -and $_.Size -gt 60Gb} |Out-Gridview -PassThru
Write-Output “Target found: “$Disk

#Purge Entire Partition Table
Get-Disk -Number ($Disk.number) | Get-Partition | Remove-partition -confirm:$true -ErrorAction SilentlyContinue
Clear-Disk -Number $Disk.Number -RemoveData -RemoveOEM -confirm:$false -ErrorAction SilentlyContinue

#Initialize Disk
Initialize-Disk –InputObject $Disk[0] -PartitionStyle MBR -ErrorAction Stop

#Create 4096MB (FAT32) Boot Partition
$BootPartition = New-Partition –InputObject $Disk[0] -Size (4096MB) -IsActive -ErrorAction Stop
Format-Volume -NewFileSystemLabel “PE-BOOT” -FileSystem FAT32 -Partition $BootPartition –Confirm:$True -ErrorAction Stop

#Create 2nd Partition (NTFS) of maximum size
$DeployPartition = New-Partition –InputObject $Disk[0] -UseMaximumSize -ErrorAction Stop
Format-Volume -NewFileSystemLabel “Litetouch-USB” -FileSystem NTFS -Partition $DeployPartition –Confirm:$True -ErrorAction Stop

Add-PartitionAccessPath -DiskNumber $Disk.Number -PartitionNumber 1 -AssignDriveLetter -ErrorAction Stop
Add-PartitionAccessPath -DiskNumber $Disk.Number -PartitionNumber 2 -AssignDriveLetter -ErrorAction Stop
$BootDriveLetter = Get-Volume -FileSystemLabel PE-BOOT -ErrorAction Stop
$DeployDriveLetter = Get-Volume -FileSystemLabel Litetouch-USB -ErrorAction Stop

$BootDriveLetter = [string]$BootDriveLetter.DriveLetter
$DeployDriveLetter = [string]$DeployDriveLetter.DriveLetter

Write-Output “BootDriveLetter is now $BootDriveLetter” -Verbose
Write-Output “DeployDriveLetter is now $DeployDriveLetter” -Verbose

I am able to deploy Windows 10 using a Standard Task Sequence to a Legacy based machine using this USB drive with no problems at all. On UEFI based machines, PE will boot successfully, and the image will deploy successfully. The problem comes after the deployment ends. If you shutdown the machine and remove the USB drive, the operating system will not boot and you receive the error "No Operating System Found". If you insert the USB drive and reboot, the OS loads just fine. Could this be related to the BCD store or the way the task sequence is partitioning the hard drive?

We have a highly segmented and geographically diverse network which makes a centralized deployment server not feasible.  So, we deploy Litetouch images via USB flash drives.  We create a C drive for the OS, a D drive for the data drive and the E drive is generally the CD/DVD drive.  The deploy drive winds up being F or higher.  This has worked fine until Server 2012 R2/MDT 2013.  Now, during the deployment, the USB drive is taking the drive letter of D which causes apps to be installed onto it instead of the data drive.  I have tried talking people here into moving to a single C drive deployment which would greatly simplify the build and get around this problem but that is not a desired option.  I am not currently using custom WIMs but am not against it if it will solve this problem.  We are deploying onto Dell PE-RX20 series servers. 

VMs, using the same build do not experience the problem.  The deploy drive comes up as F and everything installs as it should.  My thoughts there are that the image is mounted as an ISO and the OS cannot write to it so it treats it differently but the physical servers see it as a hard drive and install apps to it.

Any assistance would be appreciated.

Hi All, 

Since upgrading to MDT2013u2 for my ConfigMgr CB1602 server and deploying a test Windows 10 MDT TS (with the updated MDT package) the Application Discovery preflight registers an error (below), and the post flight Applications Installed tab for OSD Results is empty. Tried running OSDRESULTS.EXE after an OSD; also blank despite Apps being matched according to the logs (again, below)

The earlier MDT package (2013) used for my W7 works perfectly and I have a pretty good knowledge of creating and mapping applications in UDI Designer etc, and haven't tampered with the TS relating to UDI.

This is a new computer scenario, and I select a few applications from the Wizard.

Thanks

UDI Designer (untouched)

UDI Wizard

OSD_InstalledAppsLookUp.log

Deserialize Application Xml
Clearing selected applications...
Finished clearing selected applications, saved file to <?xml version="1.0"?>
<Applications RootDisplayName="Applications">
<SelectedApplications>
<SelectApplication Application.Id="1"/>
<SelectApplication Application.Id="2"/>
<SelectApplication Application.Id="4"/>
</SelectedApplications>
<ApplicationGroup Name="Core Software">
<Application DisplayName="Adobe Acrobat Reader DC (15.0)" State="enabled" Id="2" Name="Adobe Acrobat Reader DC (15.0)" Guid="ScopeId_BEBD3B8D-19A8-422B-BBE9-9ECCE2A830DC/Application_846a9a5a-20a9-4cca-9ca5-fcb972541014">
<Setter Property="description"/>
<Dependencies/>
<Filters/>
<ApplicationMappings>
<Match Type="WMI" OperatorCondition="OR" DisplayName="Adobe Acrobat Reader DC (15.0)">
<Setter Property="Name">Adobe Acrobat Reader DC (15.0)</Setter>
</Match>
<Match Type="MSI" OperatorCondition="OR" DisplayName="Adobe Acrobat Reader DC (15.0)">
<Setter Property="ProductId">{1A0C46FA-6980-42F9-9631-1B822D459405}</Setter>
</Match>
</ApplicationMappings>
</Application>

[SNIP SNIP]

Hello all,

i have this new Dell's laptop (Latitude E7470) that I'm trying to deploy. when deploy starts, right after I click on "Run the depoyment wizard to install a new computer deployment",  it immediately shout on missing drivers (PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21 which is the Intel(R) Ethernet Connection I219-LM device).

i followed this forum guide (http://en.community.dell.com/support-forums/laptop/f/3518/p/19676051/20898909?rfsh=1460360493687) which basically direct me to download the Intel driver from there site and extract it, and added all of the 32 and 64-bit drivers to their respective driver management locations (both their regular install folders and the winpe folder for the boot images).

For that i follow this guy guide (http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management) which basically tell me to create 1 folder under out of the box drivers for windows 7 drivers and 2 additional folders for WinPE 64 and WinPE 86. then make 2 selection profiles, 1 for the x64 and 1 for x86 and direct them to their designated folders under out of the box...

then i went to MDT Deployment share properties and at the Windows PE tab go to the Drivers and Patches and there configure for each platform which selection profile to use.

when booting for deployment i still have the same error.

under MDT Deployment share properties i went to Windows PE and under General tab i changed the background bitmap. when boot again i still getting the default bitmap and not what i choose. So i start thinking whether my new setup is working or not.

the strange thing is that i'm using VM to mount my basic windows installation and to patch it with new microsoft updates and then recapture it, for this I disjoin from the domain, and net use to the deploymentshare$ folder and run the litetouch.vbs.when doing this i do see the bitmap file I configured.

can any1 help pls? why when booting from WinPE and do not pull the MDT Deployment share properties and when running the litetouch.vbs it does.

Thanks a lot for your help.

We already have it up and running. When I PXE boot a new laptop before it gets to the first screen where I enter my credentials, I get a the following error message: “Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart. (100% complete)

If you'd like to know more you can search online later for this error system thread exception not handled (ndis.sys)”

 All I can find on this is related to BSOD which this really isn’t. I’m thinking maybe because the drivers needed for this new laptop aren’t in the boot.wim since this is a new model in our environment.

Does anyone know or run into this type of error: There is not enough space to create a RamDisk Device?

I am trying to PXE Boot into MDT 2013 and I am getting the above error. I have checked the scratch space inside MDT and it is set to 512.

The system has 2TB drives and 32GB ram, so I am unsure of what could possibly be happening to not allow me to deploy the image to the system.

Hi Guys,

I am running an in place upgrade task sequence on MDT 2013 Update 2 from windows 7 to windows 10.  95% of the workstations complete successfully with about 5% (so far) failing to complete.  When the devices that are getting stuck reboot I experience the dirty environment prompt, which from most of my research appears to be due to an unexpected reboot.  I am not installing any applications which would trigger such a reboot, I am however running the pre and post application windows update tasks which installs windows patches and drivers that have been posted to windows update for the device. I am thinking this may be due to the multiple driver updates taking place after the upgrade though I am unable to identify why (As this is all handled through windows update, I am not injecting any drivers loaded into MDT).  Any ideas here? I do notice on the devices failing I am receiving the following errors in the BDD.log which I am not receiving on the successful devices.

FAILURE (Err): -2147024770  0x8007007E: CreateObject(Microsoft.BDD.Utility) - ZTIGather 6/26/2016 9:41:41 PM	0 (0x0000)
FAILURE (Err): 424: GetVirtualizationInfo for Gather process - Object required ZTIGathe 6/26/2016 9:41:41 PM	0 (0x0000)

And the ZTI!GetAllFixedDrives on the successfully devices returns C: D: E:  / where on the failures only returns C: D:

Failure

ZTIUtility!GetAllFixedDrives =   C:  D:	LiteTouch	6/26/2016 9:48:33 PM	0 (0x0000)

VS.

Sucess

ZTIUtility!GetAllFixedDrives =   C: D: E:	LiteTouch	6/24/2016 6:32:37 PM	0 (0x0000)

Any assistance would be greatly appreciated as I try to move the success rate closer to 100%.  I can post more of the logs if needed. Thanks in advance!

Hello!

I've been having an issue of not being able to log in as Administrator after the Windows 7 image deployment completes successfully.  The password is set in the DeploymentShare\Control\DeployID\Unattend.xml file, as shown below, but I'm still getting"The user name or password is incorrect" error.   I'm not joining the system to a domain.  Can someone please give me some guidance as to what is going wrong?  Thank you!

<UserAccounts><AdministratorPassword><Value>Passw#rd123</Value><PlainText>true</PlainText></AdministratorPassword></UserAccounts><AutoLogon><Enabled>true</Enabled><Username>Administrator</Username><Domain>.</Domain><Password><Value>Passw#rd123</Value><PlainText>true</PlainText></Password><LogonCount>999</LogonCount></AutoLogon>



Hello,

I'm currently using MDT 2012 to deploy Windows 7 to Dell 3010 and 3020 workstations. I"m currently testing MDT with the Dell OptiPlex 3040. I downloaded the cab driver files from Dell's website and imported them into my out of box drivers. Several system devices including the USB 3 hub are not installed automatically however. After the fact I can go into device manager and manually install from the downloaded drivers so I know they are correct. Can you let me know where I should begin to troubleshoot why they aren't being installed by MDT? Thanks in advance for you help.

I am getting error while deployment going on, at 37% operating system installation I am getting attached error.

I already done several steps but not working at all. WDS server is installed on 2012 STD on Hyper-V.

Without our organization we are running about 40 Windows Server 2008 R2 servers with WDS installed. I would like to remotely manage the boot image of WDS on those servers.

However, whatever I try, I can't get WDS remotely manageable. For instance, invoke-command returns:

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:

Hi

I'm doing a deployment purely from USB onto a brand new machine and after the first reboot following the OS installing I get an error about dirty enviroment found. The google results all point to this being due to files left over from a previous deployment but this is happening to brand new machines.

The USB drive is the first boot device and I'm trying to install Windows 8.1 using MDT 2013.

If I dont make the USB first boot device, after the OS install it just boots into Windows and fails to carry on.

Any suggestions?

Thanks

Chris

We are imaging Lenovo laptops in our school district. There are several different models and they all image perfectly except for one model, the Edge 15. We use the same 64 bit image on all of these. The task sequence starts then after the os is applied the laptop shuts down. Restarted the laptop and pxe booted again to see if the ts would continue. It fails and trying to start windows normally doesn't work either. I looked at the sms log and noticed a red error line stating: Error Task Sequence Manager failed to execute task sequence. Code 0x80004005.

Accessing these logs are not a problem, understanding what they mean is something else. Anyone that can offer any advice would be deeply appreciated. Thanks in advance for the help.

/Bob

Hi there,

I built a test environment to get OSD working at my organization and the UDI Wizard Designer's Preview function worked well. It was running on a Hyper-V Server 2012 R2 Standard. Now that I've migrated things over to production I'm finding that the Preview function isn't working. The server it's running on is also Server 2012 R2 Standard. I've gone through the pages contained in the UDI Wizard to ensure I've moved every reference from the test enviro to the production enviro. I saw someone elsewhere claim that this function doesn't work in a server OS, but I don't think that's correct. Any ideas?

Hey everyone, this is my first time setting and using MDT. I'd appreciate any help getting set up!

Our setup:

 - Windows Server 2008 R2

 - also being used to host 1 sharepoint site (wss 3.0)

 - MDT 2013 Update 1/ Windows 10 ADK

 - no AV installed 

I'm following the Quick Start Guide for Lite Touch Installation for MDT 2013 (https://technet.microsoft.com/en-us/library/dn781086.aspx). Basically, I'm able to do everything (created a deployment share, imported device drivers, created a task sequence, enabled lte monitoring), up until the final step where I need to update the deployment share and generate bootable media. I receive the following error regardless of which option I choose to update the deployment share (i.e. optimize or generate new).

"Unable to Mount the WIM, so the update process cannot continue."

First I tried mounting the WIM directly with imagex to see if I could get any additional information. Strangely enough however, I was able to mount the WIM successfully without errors! (Well, initially I received an error stating the destination mountpoint didn't exist, however I solved that by creating the destination directory.

This is the command I used:

C:\Program Files (x86)Windows Kits\10\Tools\bin\i386\imagex.exe /mountrw "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim" 1 C:\mounted_images

I also tried updating the deployment share from the local Administrator account (I read some had success with this method). Unfortunately I encountered the same error.

Finally I tried modifying our default domain policy to permit the following for our domain Administrator (located atComputer Configuration/Policies/Windows Settings/Security Settings/Local Policies/User Rights Assignments):

 - Backup Files and Directories

 - Restore Files and Directories

 - Create Token Object

Unfortunately I'm still encountering the same error.

I would greatly appreciate any help anyone can offer!