I added an app (Junos Pulse) to the application for post install. It fails.

Deployment summury :

Détails: Application Juniper Junos Pulse returned an unexpected return code 193

APPs Properties

Standard Application

Quiet install command: JunosPulse-x64.msi      (I tried with no switches and with /quiet /passive

Working directory: .\Applications\Juniper Junos Pulse

In my CS.ini I have a commands for redirecting logs to the server. For some reason this machine deployment folder is not listed. Don`t know why... So cannot look into the log.

Any idea how to fix?

HERE is msi HELP. May be I need to add some other switches?

Windows ® Installer. V 5.0.9600.17415

msiexec /Option <Required Parameter> [Optional Parameter]

Install Options
 </package | /i> <Product.msi>
  Installs or configures a product
 /a <Product.msi>
  Administrative install - Installs a product on the network
 /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
  Advertises a product - m to all users, u to current user
 </uninstall | /x> <Product.msi | ProductCode>
  Uninstalls the product
Display Options
 /quiet
  Quiet mode, no user interaction
 /passive
  Unattended mode - progress bar only
 /q[n|b|r|f]
  Sets user interface level
  n - No UI
  b - Basic UI
  r - Reduced UI
  f - Full UI (default)
 /help
  Help information
Restart Options
 /norestart
  Do not restart after the installation is complete
 /promptrestart
  Prompts the user for restart if necessary
 /forcerestart
  Always restart the computer after installation
Logging Options
 /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
  i - Status messages
  w - Nonfatal warnings
  e - All error messages
  a - Start up of actions
  r - Action-specific records
  u - User requests
  c - Initial UI parameters
  m - Out-of-memory or fatal exit information
  o - Out-of-disk-space messages
  p - Terminal properties
  v - Verbose output
  x - Extra debugging information
  + - Append to existing log file
  ! - Flush each line to the log
  * - Log all information, except for v and x options
 /log <LogFile>
  Equivalent of /l* <LogFile>
Update Options
 /update <Update1.msp>[;Update2.msp]
  Applies update(s)
 /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
  Remove update(s) for a product
Repair Options
 /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
  Repairs a product
  p - only if file is missing
  o - if file is missing or an older version is installed (default)
  e - if file is missing or an equal or older version is installed
  d - if file is missing or a different version is installed
  c - if file is missing or checksum does not match the calculated value
  a - forces all files to be reinstalled
  u - all required user-specific registry entries (default)
  m - all required computer-specific registry entries (default)
  s - all existing shortcuts (default)
  v - runs from source and recaches local package
Setting Public Properties
 [PROPERTY=PropertyValue]

Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.

Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

When starting a virtual machine with WIndows 7 Pro 64 bit into audit modus (pressing CTRL-SHIFT-F3 when starting Windows) WIndows is showing a message: U are possible the victun of illegal software, u must activate windows is the next screen.

Because i am preparing the installation for imaging capture later when finished but never had this message before when working with 32 bit Windows. The version is off course legal, the productkey MAK is put in during deployment of the image.

I work in audit mode but restarting several times. After restarting i come automatically again in audit modus? I press ctrl-shift-f3 every time after a restart but is this nessesairy?

How can i get rid of the message from WIndows that the versionis illegal, or must i ignore the message?

freddie

Hi,

When botting WinPE 5 the drivers are beeing injected really slow. We are deploying Windows 200r2 and Windows 2012 R2. There is about 180 MB of drivers files to inject for different server models Hp Proliant G6, G7, IBM 3650 M4, IBM 3650.

Most of the drivers are for Windows 2008 R2 and the IBM 3650 M4, all others needs really few drivers (NIC, Storage).It's takes over 2 hours to copy all drivers on th IBM 3650 M4 and Windows 2008 R2

I know there are probably to many drivers being injected, but in my lab envierment, I had the same amount of drivers being injected and it worked just fine. No errors in the log files, it's just very slow.

Anyone has an idea or hits.

Is there a .log file in the MININT folder that shows that drivers are being deployed from a certain path in MDT. For example, will it show in the logs drivers coming from Out-of-Box Drivers\Win7x64\Dell Inc.\Precision Tower T7810, which is one particular folder in my MDT setup.

Hello,

I am enabling bitlocker in my MDT deployment using the code below in the CS.ini as well as enabling the bitlocker step in the task sequence, this config does half the job for me. I am hoping someone can help with the rest, below are my current and desired results.

Current Result: Bitlocker begins on the HD, the recovery key is copied to the share drive. However my finish action is to reboot and if I do that bitlocker prompts for the recovery key. I need to be able to reboot the computer while bitlocker is running and not prompt for the recovery key.

Desired Result: Bitlocker begins, the recovery key is copied to the shared drive, and I can reboot the computer as many times as I want while bitlocker is running without prompting me for recovery key.

[Laptop-True] 
SkipComputerName=Yes
OSDComputerName=%AssetTag%  
BDEInstall=TPMKey
BDEInstallSuppress=NO
BDEWaitForEncryption=FALSE
BDEDriveSize=3000
BDEDriveLetter=S:
BDERecoveryKey=AD
BDEKeyLocation=\\server\share

BDEAllowAlphaNumericPin=YES

Hi,

I am trying to deploy Windows 7 Professional 64-bit with MDT. Some of my areas have abhorrent bandwidth, so imaging over the network is not practical. I created a USB boot key with a complete MDT setup on it. Deploying my image from that key doesn't complete. On the first reboot, the machine blue screens amazingly quickly (I can't see what it says). I'm 99.9% sure it is a driver that is causing the problem, but I don't know which one. I booted the stricken PC with a Linux disk and tried to look for a Minidump file, but there wasn't any. This exact same image works fine on many models when I deploy it regularly over the network with MDT. It is just not working from the USB key. I created a separate deployment share to create the USB key's selection profile. I copied the drivers from the exact same place, and disabled all of the ones that were disabled in the production share, but that didn't seem to work. How can I determine what is causing the blue screens?

Thanks in advance!

Jason

Hi,

I'm trying to use MDT 2013 to deploy a custom WIM into a VMware workstation virtual machine. I've done this in the past and it worked fine with other images. The file copy part of the deployment works fine until it gets to the first reboot. Then, Windows 7 fails to load with the following message.

"Windows failed to start. A recent hard or software change might be the cause. To fix the problem..."

The file in question is pci.sys (no path given)

Status: 0xc0000098

I have the drivers mapped by hardware model from WMI. VMware virtual platform is not among those models. I tried adding the VMware drivers to Windows PE and my deployment share, but WinPE couldn't even boot the VM at that point, so I had to remove them. How can I edit/diagnose a problem with a file if I can't get the image deployed. The image won't deploy to physical hardware either, blue screens result.

Thanks in advance

Jason

Jason

Hi guys,

I am running Windows Server 2012R2 and have MDT 2013. I am up to the capture part of my deployment process. I created a VM, installed windows onto it using MDT, then put a pause in the task sequence, I then have customised Windows the way I want now I am trying to capture the image by continuing the deployment. It gets right to the end and spits out the .wim file which is the captured image but then errors and says "No networking adapters found, the network drivers for your device are not present". I have looked in log files, I have tried adding drivers directly into the boot image, I have tried everything I can think of but it continues to error. I want it to finish capturing properly so I know I deploying a stable image once the image is captured.

Can anyone through some suggestions around why this is happening and what I could do to fix it?

Cheers

Joel

Hello All,

We have Windows 2012 ISO built using MDT 2013. This ISO is perfect with all necessary applications, packages, drivers, etc and deployment is fine on all hardware on local disk.

I am required to deploy this ISO over ISCSI LUN on dell hardware...and I am having no idea as to how to make what changes in BIOS settings and MDT ISO.

what I understood is that :

When LUN is presented to physical server and mapped with ISCSI, then, this LUN needs to be selected as primary disk within BIOS settings so that windows can be installed over it (because our MDT is configured to run OS over "disk 0").

once this is done in BIOS - nothing is done from MDT ISO side as it will be as same as installing it over local HDD.

Please see if my understanding is correct..and suggest 

Thanks all!

I am having an issue when trying to run a Litetouch OEM Task Sequence from a USB stick.  I am using the RTM version of MDT 2012 and have followed another post which sounds the same as mine http://social.technet.microsoft.com/Forums/en-US/mdt/thread/11fcdbf7-4b4c-41e8-a71c-345f4293857e.  Unfortunately I was not able to make it work by recreating the task sequence, media, etc.

I have tried recreating the .iso, and formatting the USB stick, manually partitioning and formatting the partition on the computer.  Somehow it did work one time, but I am not sure why and cannot reproduce the results.

Here is my LTIOEM.log

Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Microsoft Deployment Toolkit version: 6.0.2223.0 LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
---------------- Begin OEM Preperation Script. ---------------- LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Unable to yield a target Partition (Special Recovery option for Litetouch). LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
DestinationDisk and Partition did not yield a target Partition. LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
New ZTIDisk : \\MININT-1CD5LF7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found Possible OS TargetDisk: \\MININT-1CD5LF7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
GetPartitions: 2 LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found Possible OS Target Partition: \\MININT-1CD5LF7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
New ZTIDiskPartition : \\MININT-1CD5LF7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"   \\MININT-1CD5LF7\root\cimv2:Win32_LogicalDisk.DeviceID="W:" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Target Partition not big enough: \\MININT-1CD5LF7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found Possible OS Target Partition: \\MININT-1CD5LF7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
New ZTIDiskPartition : \\MININT-1CD5LF7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"   \\MININT-1CD5LF7\root\cimv2:Win32_LogicalDisk.DeviceID="C:" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found Drive: C: LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
New ZTIDisk : \\MININT-1CD5LF7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found Possible NonOS Disk: \\MININT-1CD5LF7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1" LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Found FirstPossibleSystemDrive: C: LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Property DestinationOSInstallType is now = BYDRIVELETTER LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Property DestinationOSDriveLetter is now = C: LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Target volume for OEM staging (first possible) = C: LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
About to run command: robocopy.exe /E /A-:R /NP /LOG+:C:\MININT\SMSOSD\OSDLOGS\ltioem.txt M:\Deploy C:\Deploy LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Command has been started (process ID 1772) LTIOEM 6/7/2012 2:47:54 PM 0 (0x0000)
Return code from command = 1 LTIOEM 6/7/2012 2:49:30 PM 0 (0x0000)
Disable the OEM Task Sequence here! LTIOEM 6/7/2012 2:49:30 PM 0 (0x0000)
FAILURE ( 6010 ): False: Test for TSGUID LTIOEM 6/7/2012 2:49:30 PM 0 (0x0000)

Here is the information from the Results.xml

FAILURE (Err): 68: Ran diskpart to change drive letter - Device unavailable
FAILURE ( 6010 ): False: Test for TSGUID
Litetouch deployment failed, Return Code = -2147467259  0x80004005
Failed to save environment to  (80070057)
Failed to run the action: Copy Media CD to Local Hard Disk for OEM pre-installation.
The directory has been disabled for encryption. (Error: 0000177A; Source: Windows)
Failed to run the action: Copy Media CD to Local Hard Disk for OEM pre-installation. Execution has been aborted
Failed to run the last action: Copy Media CD to Local Hard Disk for OEM pre-installation. Execution of task sequence failed.
The directory has been disabled for encryption. (Error: 0000177A; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Any ideas would be greatfully accepted.  Would it help if I provided additional log information?

I deploy images using MDT 2013 (LiteTouch) and WDS on a Windows 2008 R2 server.  I can deploy Windows 7 with no problems.  When I try to deploy Windows 8.1 using an image I created from a VM reference box on the same server, I get to 62% (the reboot after the OS is installed) and then it stops.  Once the machine has rebooted, it doesn't even try to complete the task sequence.  Rebooting again has the same result.

In my research about this question, it was suggested that there was a UAC issue with the local administrator account, but I resolved that issue, and I still have the same result.  I was looking at the issue some people have where the network card isn't up when the imaged machine tries to contact the deployment server, but I get no error - the imaged machine never picks up the TS after reboot.  The image successfully completed sysprep during the capture process. 

Does anyone have any ideas on what could be causing this?  Thanks in advance for any help you can give me.

We are using an MDT 2012 UDI deployment Task Sequence  in Config Mgr 2012. I have attempted to create and add a local account to the administrators group during deployment using both the default unattend.xml and a custom answer file. In both cases this setting is ignored. I am a little confused because other settings I specify in the answer file such as IE home page are preserved after deployment, but the local account is never created.

Is this possible to do via the method I am describing or is there another method I must use?

I'm currently using - MDT 2010 on Windows 7 on a Virutal Machine. I deploy my images using a USB stick. (Advanced Configuration / Media). The process of creating a selection profile, Creating Media, and updating my media works perfectly.

I wanted to move to MDT 2012 SP1 on Server 2008 R2 platform. So I installed AIK, MDT 2012 SP1, etc on a Server 2008 R2 Virtual Machine. I setup the MDT same way as my current working model and it was looking good. Next I created my Selection Profile and Media. Then when I ran "Update Media" it seems to work until it gets stuck at the last process "Reset Read Only Attributes"

Looking for any advice on why it might keep getting stuck here. The only way I can exit the process it to "Stop Execution"

Reminder - on my Win 7 / MDT 2010 box, it works fine and this process completes.

Thanks for any feedback.

I can complete the copy phase of the content from USB to Local drive without any problem.

The drive configurations is like below ; But it does not boot from local drive. I need to plug the usb and select the deployment task sequence to start the deployment. Is that by design or should it boot from the local drive ?



Hello all,

I've captured a Windows 8.1 Reference Image as shown in following document: technet.microsoft.com/de-de/library/dn744290.aspx

The Reference Image contains only Microsoft Office 2013 and the latest Windows Updates. When I import the Reference Image into my deployment share and deploy it to one client, the operating system will be installed correctly, but after the restart, I get to the Windows 8.1 login screen and nothing happens anymore.

Did you ever heard of that issue? Is there a solution?

Thanks in advance.

Hello,

I'm in a migration process from Windows XP to Windows 7. I use USMT 4 to transfer user files and configurations. However, we have a policy that change the wallpaper with one blank with custom information about the computer.

When I run scanstate, it restores everything fine, but it restore also the old wallpaper with the wrong informations. Then, new informations are applied on this wallpaper, and everything is unreadable.

I would like to force USMT to not backup the old wallpaper. Any ideas ?

Thanks!

When starting a virtual machine with WIndows 7 Pro 64 bit into audit modus (pressing CTRL-SHIFT-F3 when starting Windows) WIndows is showing a message: U are possible the victun of illegal software, u must activate windows is the next screen.

Because i am preparing the installation for imaging capture later when finished but never had this message before when working with 32 bit Windows. The version is off course legal, the productkey MAK is put in during deployment of the image.

I work in audit mode but restarting several times. After restarting i come automatically again in audit modus? I press ctrl-shift-f3 every time after a restart but is this nessesairy?

How can i get rid of the message from WIndows that the versionis illegal, or must i ignore the message?

freddie

Hi ,

Getting this error --Warning "Failure (5210): ValidateDeployRootWithRecovery: Cancel" -- after deploying the Media from USB created using MDT 2013 to capture  an image of Windows 8.1 Pro to 64-bit machine.  Task Scheduler is set to Sysprep and Capture, and I can get past the credentials to create a network share.

Hi

How do Iinstall the WindowsADK componentfromMDT2013Update 1 Preview?

Thanks

Bye

Balubeto