Install Application during Task Sequence based on Application name

June 20, 2015, 11:40 am

≫ Next: Run Command Line MDT Task in WinPe Phase of Deployment.(HPbiosConfigUtility)

I am in need of installing multiple, possibly random, applications at two different points during the Task Sequence to deploy Windows 7 and the applications. I have some applications that can only be install while connected to the domain, but if I am connected to the domain, other applications fail because of when policy starts kicking in and installing software. It seems policy trumps MDT as far as software install, so I decided to move application installation before joining the domain, which has worked perfectly.

Now, I have some applications that only deploy properly if the computer is joined to the domain because of what seems to be a permissions issue to a network share other than the MDT server, but I can't find any thing wrong. So, I was hoping to set some checking on the Options tab of the Install Applications item and say "If applications do not start with 'X', install applications". Then after the computer was joined to the domain, add another Install Applications step, but reverse the check and install ONLY applications that begin with 'X'. There could be 1-16 applications selected that would fit into the second criteria, so I can't just say install this application only, sixteen different times because not all are needed and it would add more time to the imaging process.

Is this even doable? It seems like it is, but I don't know what variables to look for. I look on multiple web pages and found a few other things in the forums, but nothing follows what I am asking.

Thanks for any advice.

↧

Run Command Line MDT Task in WinPe Phase of Deployment.(HPbiosConfigUtility)

June 29, 2015, 6:06 am

≫ Next: MDT 2013 UEFI Deployment for Windows 7

≪ Previous: Install Application during Task Sequence based on Application name

Hi Folks

I was hoping someone may well be able to help me with the following task. Currently we are introducing a USB MDT deployment solution within our organisation. So far it works great and we are quite happy with it. In our estate we have a mix of Toshiba laptops and HP desktops which work reasonable well with the USB solution.

However, one of the niggles we have concern the HP Desktops (EliteDesk 800 G1) model, which by default will try to boot using a USB device if one is plugged in. This is great for the intial start of a deployment but not so good once the deployment boots out of the WinPE phase into the Windows phase, as if you leave the device in and forget, the pc will then reboot into the MDT deployment again. I know we could manually change the boot order before running the USB deployment and all is well, but I would like to automate this process so that this is not necessary.

Over the weekend I had a look at the HP BiosConfigUtility.exe app and after a bit of head scratching I was able to get the current bios config.txt, make changes to the boot order and then reset them using the utility. I am pretty happy with the results. Now I would like to add the manual command to a task before the MDT USB deployment reboots into the Windows phase, so that when the device reboots it will boot to the System drive and not to the USB drive.

The command to achieve this is BiosConfigUtility.exe /SetConfig:config.txt with config.txt being the new bios config with the new boot order.

My plan was to create a command line task that referenced this command, however when testing I have had many different errors, mostly file not found, sometimes network path not found, occasionally "Windows tried to load an app with an incorrect format"

Things I have done:

I have added an extra folder into the boot wim with the files included.

I have mounted the boot.wim file and copied the files in manually into the X:\Deploy\Scripts folder

I have tried to access various variables to run the command but no success.

So my main question is what would the command line be to reference the file within the Winpe environment. I am sure I have tried varuous pemations. eg

X:\BiosConfigUtility.exe /SetConfig:config.txt

X:\Deploy\Scripts\BiosConfigUtility.exe /SetConfig:config.txt

%SCRIPTROOT%\BiosConfigUtility.exe /SetConfig:config.txt

BiosConfigUtility.exe /SetConfig:config.txt and start in X:\DeployScripts

I have tried quotations around the command but still not really getting anywhere.

I am wondering, what variables are current in the WinPE phase, I looked at the logs and it seems to reference the DeployDrive as X:\

Also I can run the command manually from the command prompt within Winpe and the command completes. So I am hopeful this can be achieved.

If there is anyone that can point me in the right direction to help run this command in the WinPE phase I would be grateful.

↧

MDT 2013 UEFI Deployment for Windows 7

June 30, 2015, 1:15 am

≫ Next: Litetouch deployment failed , Return code =-2147467259 0x80004005

≪ Previous: Run Command Line MDT Task in WinPe Phase of Deployment.(HPbiosConfigUtility)

Hi Guys

I have recently rebuilt our WDS / MDT setup onto a new Windows Server 2012 R2 Virtual Machine (Vmware) We are trying to recreate images to work with UEFI.

We are deploying HP Elitebook 820 machines and have enabled secure boot in the BIOS and UEFI Native.

I have created the task sequence and set the disk type to GPT - However when deploying Windows 7 upon booting we get "selected boot image did not authenticate" All forums are telling us to turn off secure boot and go into Legacy BIOS mode. I know Windows 7 supports UEFI so why are we getting this error?

When deploying Windows 8.1 - we do not get this error and deployment is successful.

Any help or guidance is appreciated.

↧

Litetouch deployment failed , Return code =-2147467259 0x80004005

June 30, 2015, 7:14 am

≫ Next: DART in MDT 2013

≪ Previous: MDT 2013 UEFI Deployment for Windows 7

Failed to run tjhe action : Execute Sysprep

Incorrect function. ( Error:00000001; Source ; Windows)

The execution of the group ( capture Image) has failed and the execution has been

Operation aborted ( Error :80004004: source : Windows)

Chiddy

↧

DART in MDT 2013

November 28, 2013, 6:03 am

≫ Next: WinPE Drivers for VMware Workstation 11

≪ Previous: Litetouch deployment failed , Return code =-2147467259 0x80004005

So I recently upgraded our MDT server from MDT 2012u1 to MDT 2013 (on a Windows Server 2012 R1), during the process I also removed ADK 8 and replaced it with ADK 8.1.

I had DART8 already installed, but I uninstalled it and made sure to reinstall DART 8 SP1 from MDOP 2013.

I also added Windows Server 2012 R2 and Windows 8.1 full sources from vanilla images from MS VLSC to MDT.

I do get the DART option in my boot images but I don't get the Windows Recovery Wizard and the Registry Editor, Locksmith, Comp Mgmt, etc are disabled. as it seems to be using the Windows PE WIM image from ADK and not those from the Windows 8.1 or 2012 source.

Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim will be used.WIM file mounted.

Is there something wrong ? Do I have to wait for the new DART/new MDOP ? (why don't those things get updated at the same time?) or is there a way to make sure it uses the WinRE from Windows 8.1 or 2012 for the boot image ?

Another question: Will DART and the Recovery Wizard on a Windows RE 5.0 boot image work for a Windows 7 installed system ?

↧

WinPE Drivers for VMware Workstation 11

June 30, 2015, 5:19 am

≫ Next: Multiple MDT Shares using one Location for OS,Applications,Packages,etc-Is it possible?

≪ Previous: DART in MDT 2013

Hi,

I am trying to use VMware Workstation 11 to create a master image for distribution by MDT 2013/WDS. I've added the VMware drivers to the deployment share and configured it to inject drivers by the detected platform, "VMware Virtual Platform." Each time I try to capture an image, it takes forever... Forever, I mean days, until the process times out and fails. I added the VMware Tools to the VM, and set the NIC to bridged mode (1Gbps). This time, the capture wizard takes an additionally long time to complete. When it reboots into Windows PE, I get an error message.

File: \Windows\System32\drivers\pvscsi.sys

Status: 0xc0000359

Info: The operating system couldn't be loaded because a critical system driver is missing or contains errors.

Pvscsi.sys is a VMware driver. Surely, I cannot be the first person who has tried to use Workstation 11 as a tool to create master images for MDT 2013. How can I fix this driver issue? I'll try disabling the driver in MDT, but that kind of defeats the point of having them there in the first place. I am trying to create an image of Windows 7 Professional x64.

Thanks in advance.

Jason

↧

Multiple MDT Shares using one Location for OS,Applications,Packages,etc-Is it possible?

June 30, 2015, 10:10 am

≫ Next: LItetouch installation of Windows 10 stops waiting for PK

≪ Previous: WinPE Drivers for VMware Workstation 11

Hi everyone, I was wondering if someone could tell me if its possible to have Multiple MDT shares on a server, but only use one File Repository?

For instance. I want to have one MDT share for development, and one MDT share for Deployment. Obviously I don't want to duplicate the exact same thing in to one share.

Another question, perhaps have the file repository on another server, say my SCCM Server. Is it possible to use the share from there for MDT?

Thanks

↧

LItetouch installation of Windows 10 stops waiting for PK

June 30, 2015, 9:44 am

≫ Next: Changing user account from administrator to domain user during OSD using MDT

≪ Previous: Multiple MDT Shares using one Location for OS,Applications,Packages,etc-Is it possible?

Hi,

I'm testing the Litetouch installation of Windows 10 TP. This installation stops waiting for user to insert the product key. Blank key is not allowed

On the contrary, the direct Windows 10 installation (from .iso file) does not stop waiting for it.

I did a check on MDT 2013 U1 scripts and I'm guessing if DeployWiz_ProductKeyVista.vbs has not been updated yet to check correctly the Windows 10 version (10.0 instead of 6.x)

moreover, the litetouch deployment of Windows 7 through the same tools (MDT 2013 U1, wadk for Windows 10 build 10075) waits for PK input, but it accepts blank key.

Thanks in advance for any suggestions

↧

Changing user account from administrator to domain user during OSD using MDT

June 30, 2015, 6:53 am

≫ Next: Exclude E: Drive while using USMT

≪ Previous: LItetouch installation of Windows 10 stops waiting for PK

hi,

I want to switch user account from administrator to domain user during osd using mdt. By default MDT do all the process using administrator account. But there are some policy settings which will be only applied if domain user login. I want OSD to be started with local administrator account and for certain time it switches to domain account. How can i switch user account in the middle of task sequence. Please suggest.

↧

Exclude E: Drive while using USMT

July 1, 2015, 1:37 am

≫ Next: MDT Offline media creation and missing applications

≪ Previous: Changing user account from administrator to domain user during OSD using MDT

Hello,

is it possible to exclude the second Partition (E: Drive) in the MigDocs.XML and include in a custom.XML. In the custom.XML I want to do a RelativeMove to C:\DataFromE\.

If I just use the custom.XML the RelativeMove works, but if I use the the MigDocs.XML and the custom.XML together the exclude of E:\ doesn't work. So I have migrated the data twice. The exclude in the MigDocs.XML works only with an unconditionalExclude, but now it is not possible to migrate the data to C:\DataFromeE\ anymore.

Please help me on this issue.

↧

MDT Offline media creation and missing applications

November 13, 2014, 8:34 am

≫ Next: Prerequisites to build a new image for UEFI systems.

≪ Previous: Exclude E: Drive while using USMT

When I create offline media from MDT result is that offline media doesn't contain application install files.

Is it a bug or what?

↧

Prerequisites to build a new image for UEFI systems.

July 1, 2015, 3:54 am

≫ Next: Cannot Parse Answer File

≪ Previous: MDT Offline media creation and missing applications

I am working on Image creation for new UEFI device and selected the normal client Task sequence with GPT Disk Format option. Deployment works fine but after OS installation system get stuck with an error “ Operating system Loader signature not found in SecureBoot database (‘db’)

I am currently using MDT 2013 with ADK.

Please suggest!

↧

Cannot Parse Answer File

June 24, 2015, 11:33 am

≫ Next: Does MDT 2013 U1 work with WADK 8.1?

≪ Previous: Prerequisites to build a new image for UEFI systems.

Hi,

I have a task sequence that deploys an image. I made one change to the unattend.xml file and that was to copy the default user profile. After the task copies the image to the HDD and reboots, Iget an error stating the unattend file could not be parsed at the exact same step I modified. Unattend files are a bit of an issue. After I create the task sequence, I cannot open the unattend.xml file from its properties. It just sits there, until I stop it, creating the catalog file. After I stop it, I can go back in and forcibly open the utility that edits the unattend.xml file. That seems like the wrong way to go about it. I just want to change that one setting, which has to be done this way. What is the correct way to generate a catalog file, so that the unattend.xml can be opened in a timely fashion? Can I copy the catalog file from one task to another? They're all descended from the same Windows 7 ISO?

Thanks

Jason

↧

Does MDT 2013 U1 work with WADK 8.1?

July 1, 2015, 7:19 am

≫ Next: Imaged device managed through config manager and Intune

≪ Previous: Cannot Parse Answer File

Hi,

is it planned that MDT 2013 U1 will support WADK 8.1 to create the Litetouch engines or will it work only with the new WADK for Windows 10?

Thanks in advance for any answers

↧

Imaged device managed through config manager and Intune

July 1, 2015, 11:04 pm

≫ Next: Windows 8 activation through MDT

≪ Previous: Does MDT 2013 U1 work with WADK 8.1?

Hi Team,

I am looking for some guidance as to requirements for device to be managed through config manager and intune while deploying image through MDT ? Do we need to add any application that is needed for MDM specifically that should go as part of image while deploying image on devices? Generally , we include only config manger client package as part of deployment TS, what about devices that need to be managed through intune, any specific software need to be installed as past of image deployment TS?

Regards

↧

Windows 8 activation through MDT

December 3, 2012, 3:00 pm

≫ Next: Strange error when creating USB deployment

≪ Previous: Imaged device managed through config manager and Intune

I haven't had a chance to test very much but from what I have read, you should be able to install a retail copy of Win 8 on an OEM machine and it will pick up the key stored in the BIOS automatically. I'm trying to deploy Windows 8 to an OEM PC and it is not picking up any product key at all.

Am I reading this wrong?

For a comparison, we used to deploy a thick image to our Lenovo laptops and use the COA key (post install) to activate Windows. Obviously this is not possible with Windows 8 as the COA sticker is not provided.

EDIT:: Installing with the DVD works and seems to pick up the OEM product key, but deploying the same DVD with MDT 2012 U1 doesn't. Anyone have any advice on this please?

↧

Strange error when creating USB deployment

July 2, 2015, 6:18 am

≫ Next: MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

≪ Previous: Windows 8 activation through MDT

Im currently using win 10 b10061 with MDT 6.2.5019.0

When i go to create my usb , it fails with the following error :

Starting MDT Media Update
Opened the media deployment share.
Folders to be copied to the media deployment share: 4

System.Management.Automation.CmdletInvocationException: Unable to cast object of type 'System.Management.Automation.RuntimeDefinedParameterDictionary' to type 'Microsoft.PowerShell.Commands.CopyItemDynamicParameters'. ---> System.InvalidCastException: Unable to cast object of type 'System.Management.Automation.RuntimeDefinedParameterDictionary' to type 'Microsoft.PowerShell.Commands.CopyItemDynamicParameters'.
   at System.Management.Automation.SessionStateInternal.CopyItem(String[] paths, String copyPath, Boolean recurse, CopyContainers copyContainers, CmdletProviderContext context)
   at Microsoft.PowerShell.Commands.CopyItemCommand.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.GenerateMediaProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

Any help will be greatly appreciated.

thanks

Flucato, New Orleans

↧

MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

July 3, 2013, 11:53 am

≫ Next: MDT 2013 Windows 8.1 Sysprep & Capture not working

≪ Previous: Strange error when creating USB deployment

Unable to deploy any image with WIM file. Vanilla or Custom Image gives the following error:

ZTI Error – Unhandled error returned by LTIApply: invalid procedure call or argument (5)

Litetouch deployment failed, Return code = -2147467259 0x80004005

Failed to run action: Install Operating System.

Access is denied (Error: 00000005; Source: Windows)

Tried Giving Everyone Full rights to the deployment share

Rebooted Server

Updated Deployment Share

Any ideas would be great!

Thanks

Rick

Richard Ray

↧

MDT 2013 Windows 8.1 Sysprep & Capture not working

July 3, 2015, 1:58 am

≫ Next: Applying tattoo in OSD using MDT 2013

≪ Previous: MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

Hi,

I have this weird issue whereby i can't sysprep and capture a Windows 8.1 (Korean Language) where after it runs the "Execute Sysprep" stage it reboots but doesn't continue with the Task sequence after the reboot.

THe LTISysprep log shows that there is some "Pending File Rename Operations" and the last entry was "Initiating reboot to clear pending file rename operations".

BDD log shows below after the LTISysprep part. There is not error in entries so i can't tell whats wrong! The image i want to capture is running on a VM and has a 500MB boot partition so i don't think the not enough space issue with boot partition is the cause of it.