Hi,

What would be the best way to install Office 2016 via MDT (2013 Update 1)? I cannot add Office16 as an application with source files. All I have is setup32.exe and setup64.exe files which I believe download files during installation. So what would be the best way to include install Office 2016 during deployment? Is Office 2016 supported?

Thanks,

Here are other issues I am having with MDT 2013 Update 1 when deploying Windows 8.1 Enterprise x64.  Anybody else seeing these?

1) If the admin passwords in Unattend.xml are hashed using "Hide Sensitive Data", and the password is changed using the Wizard at deployment, or customsettings.ini, the password passed to Unattend.xml does not get hashed, yet the protected value stays as true, so Windows thinks the value is hashed.  This causes deployment to completely die.

There may be other circumstances where this happens but this is where I have encountered it.  A fix is to turn off Hide Sensitive Data and enter non-hashed passwords into Unattend.xml so that protected gets changed to false. (Credit to 'Josh' in the comments sections of the TechNet blog post about the MDT 2013 Update 1 release for pointing me in this direction.)

2) I set the default locale, keyboard, language and time zone in my customsettings.ini.  The Deployment wizard does not pickup the time zone anymore though, and instead gives Pacific Standard Time as the default.  Here is what I have in my customsettings.ini:

SkipTimeZone=NO
TimeZoneName=Singapore Standard Time

I am guessing that perhaps the name of "Singapore Standard Time" has changed in WinPE with Windows ADK 10, and that is the reason is isn't being picked up...  But I can't find any updated listing of time zones for Windows 10 on TechNet or elsewhere, and do not presently have any Win 10 VMs running to use the tzutil /l command.  If someone can post an output from Win10 of that command that would be greatly appreciated!

I am trying to deploy Windows 10 and getting this error relating to windows-shell-setup. pass specialize. Any ideas? I have tried with and without productkey. Checked company name,registered owner, organization and timezone all seem correct. The only one I am unsure about is DoNotCleanTaskBar.I am using a completely standard xmlfile, I have not modified it in anyway.

    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
      <ComputerName></ComputerName>
      <ProductKey></ProductKey>
      <RegisteredOrganization>Organization</RegisteredOrganization>
      <RegisteredOwner>Name</RegisteredOwner>
      <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
      <TimeZone>Pacific Standard Time</TimeZone>
    </component>

More information. Setuperr.log

2015-10-07 15:40:51, Error                        [setup.exe] ReAgentXMLParser::ParseConfigFile (xml file: \Recovery\ReAgentOld.xml) returning 0X3
2015-10-07 15:41:02, Error                        [setup.exe] [Action Queue] : Unattend action failed with exit code 4
2015-10-07 15:41:02, Error                        [setup.exe] Execution of unattend GCs failed; hr = 0x0; pResults->hrResult = 0x8030000b

I created a VM, installed Microsoft Office 2013 and rearmed the installation. I had been deploying without activation issues up until I installed service pack 1 for Office 2013.

I now receive the error: "This copy of Microsoft Office is not activated." with the error code: "0x4004F00D". 

The only fix seems to be to run the command: "cscript ospp.vbs /act" 

Has anyone else had this issue after updating Office to SP1?

Hey guys,

We are manipulating MDT to perform our system images for our new machine deployments for our retail front. The only thing I've run into at this stage which is causing a bit of a headache is the below screen;

"Your computer's name is managed by your organization's system administrator"

This is the scenario;

1. Our system builders deploy a custom image to the hardware.
2. They then install any drivers that MDT may have missed (as the hardware is always different and we don't always have the drivers ready in MDT) and install any updates from the time of the image capture.
3. Run general testing tools/scripts within the windows environment.
4. Re-seal the machine via sysprep (OOBE and shutdown).
5. when the end user run through OOBE, they run into the above image.

**While we understand MDT is not designed for this it has helped a substantial amount thus far.

The only thing I need to accomplish here which is making my brain hurt (this seems like such a simple task) is make the operating system, once re-sealed via sysprep, understand that the computer name is NOT managed by a system administrator and thereon allow the end user to enter a computer name.

I've also attempted when re-sealing the machine to run sysprep with a custom answer file but the system still thinks the system name is managed.

Any help would be awesome.

Hello Guys

We have upgraded our MDT 2013 to Update 1 build 8298.

And we have quite a few issues that we didn't have before.

We have some pretty simple task sequences we use to build images, one for each OS. Currently
Windows 7x64, Windows 8.1x64 and Windows 10x64. Each os has a separate virtual machine in our VMware environment. We don't capture the image in MDT since our deployment system requires and older WinPE to run (Capasystems.com).

I pick the Syspreb task so it does what needs to be done at the end of the build. Shutdown the machine when it's done, pxe boot into capa and then proceed to capture the image.

This is pretty basic and has worked in the past.

After the upgrade I boot from the litetouch ISO like we normally do and using a VMxnet3 driver make the connection to the share and this runs smoothly all the way to the sysprep part. 

When the machine is done syspreping it completely "drops all network connections" and the build "fails". 

I'm having a hard time figuring out why this happens - Any ideas?

Tried with different drivers, old and new. Even tried running it on hyper-v but it yields the same results. Every task sequence was built from scratch since the format part was changed.

Hi

I´m getting this error all the time. I try to setup an offline media with ADDS configuration but everytime I deploy the image this error appears.  Can somebody please help me :)

ERROR - ADDS role configuration with DCPromo failed, rc = 22 

ZTI ERROR - Non-zero return code by ZTIConfigureADDS, rc = 22 

Litetouch deployment failed, Return Code = 2137467259 0x80004005

Rules:

Properties=MyCustomProperty


[ByVMType]
Subsection=IsVM-%ISVM%

[IsVM-TRUE]
OSInstall=Y

[Default]
SkipBDDWelcome=YES
OSInstall=NO
SkipCapture=YES
SkipAdminPassword=YES
SkipDeploymentType=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipTimeZone=Yes
TimeZoneName=W. Europe Standard Time
TimeZone=110
SkipLocaleSelection=Yes
UILanguage=en-us
UserLocale=041d:0000041d
KeyboardLocale=041d:0000041d
SkipDomainMembership=YES
USMTOfflineMigration=FALSE
UserDataLocation=NONE
DoNotCreateExtraPartition=YES
WsusServer=http://10.99.99.101:8530

;Install AD-DS with static IP
[00:0C:29:36:97:57]
_SMSTsOrgName=TEST-DomainControllerInstall
OSDComputerName=TEST-dc-01
OSDAdapter0EnableDCHP=false
OSDAdapter0IPAddressList=10.99.99.150
OSDAdapter0SubnetMask=255.255.255.0
OSDAdapter0Gateways=10.99.99.254
OSDAdapter0DNSServerList=10.250.1.1
OSDAdapter0Name=TEST-NET
OSDAdapter0DNSSuffix=TEST.orgl
OSDAdapter0EnableDNSRegistration=True
OSDAdapter0EnableFullDNSRegistration=True
OSDAdapter0TcpipNetbiosOption=0
;ADDS
ServerType=DC
;ADDSLogPath=%DestinationLogicalDrive%\Windows\NTDS
;ADDSPassword=Passw0rd
;ADDSUserDomain=TEST.org
AutoConfigDNS=YES
ConfirmGC=YES
;DatabasPath
DomainLevel=4
DomainNetBiosName=TEST
ForestLevel=4
NewDomain=Forest
NewDomainDNSName=test.org
ReplicaOrNewDomain=Domain
SafeModeAdminPassword=Passw0rd
SiteName=TEST-Site1
;SysVolPath

SkipTaskSequence=YES
SkipComputerName=YES

SkipCapture=YES
DoCapture=NO
SkipAdminPassword=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipTimeZone=YES
SkipLocaleSelection=YES
SkipApplications=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipRoles=YES
SkipSummary=YES
SkipBitLocker=YES
TaskSequenceID=WINSTH
AdminPassword=Passw0rd
OSDComputerName=TEST-dc-01
;ComputerBackupLocation=%DeployRoot%\captures
;BackupFile=w10ent-ref.wim
BackupFile=%TaskSequenceID%-#year(date) & "-" & month(date) & "-" & day(date)#.wim
FinishAction=SHUTDOWN
SkipFinalSummary=NO

Bootstrap.ini

Hello,

i have installed the latest version of ADK and MDT 2013 Update 1.

Some task sequences are failed with the following :

I have regenerated the deploymentshare for the boot-files, but are is not fixed.

What can i do to fix this issue?

Thx

Hi All,

I recently ran into some issues deploying Windows 10 using MDT, since then I've installed Server 2012 R2 on to a new machine and created my new deployment share with MDT 2013 Update 1 installed. I'm trying to deploy a standard Windows 10 image after carefully following the instructions at the following:

https://technet.microsoft.com/en-us/library/mt297533(v=vs.85).aspx

As far as I can see the image almost completes however it then prompts me with the following error: 

"Windows could not complete the installation. to install windows on this computer restart the installation."

The only option it offers is to hit OK which will see you become stuck in a continuous rebooting loop until this error re-appears. Having done some digging online I have explored possible areas such as user access privileges, services etc however all to no avail.

At this point I opened command prompt and located the log files which are attached to the following link:

https://onedrive.live.com/redir?resid=CA9A267610999001!144&authkey=!AMtUXoIVCLnwnyw&ithint=folder%2clog

Can anybody possibly explain this problem or provide some additional advice on this error. 

Thanks in advance.

Ad

Using MDT 2013/8.1 ADK on Win2012 R2 x64. I am trying to build a reference Windows 7 SP1 Enterprise x64 image in a VM with updates/office and then capturing that as a WIM and importing it back to my DS so I can run it through another TS on a VM that adds frequently updated software programs, injects drivers, and other customization and capturing that WIM to deploy to hardware manually with a WinPE usb stick. After creating the partitions in diskpart and applying the 2nd captured WIM to the hdd it boots up and goes through the normal setup process but the OOBE prompt is coming up. I have tried all combos of OOBE configuration phase settings in my unattend.xml. Tried with SkipUserOOBE and SkipMachineOOBE true/false and not included in the unattend.xml at all with the same results. Rebooting the VM after capturing the WIM boots to the proper Logon prompt with no OOBE prompts, which is what I want. I've poured over my logs and put in pauses to make sure the correct unattend.xml is being used for the sysprep and it is but no matter what I can't get the OOBE prompt to go away even after providing answers for everything.

The reason I am applying it manually back to the hardware instead of using MDT to deploy is because we are looking to FTP the WIM to a vendor so they can preload our equipment with our image so we only need to turn on the machines and join them to the domain and login as the user and go about our business. My reference image is good it's just the 2nd part that seems to be having the issue if I am not using MDT to deploy the WIM to the hardware. Any help or a better way to do this would be much help been racking my head over various MDT issues the last 2 weeks and eventually downgrading from MDT 2013 U1 back to MDT 2013 because of some other issues. Thinking maybe I just need to deploy the REF WIM to the VM like a normal deployment and then manually installing the software and do a manual sysprep and capture just to get away from some of the stuff MDT does.

diskpart
select disk 0
clean
create partition primary size=499
format quick fs=ntfs label="System"
assign letter="S"
active
create partition primary
format quick fs=ntfs label="Windows"
assign letter="C"
exit

imagex /apply N:\WIN7X64ENTDVD_2015_10.wim 1 C:\

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="windowsPE"><component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"><ImageInstall><OSImage><WillShowUI>OnError</WillShowUI><InstallTo><DiskID>0</DiskID><PartitionID>1</PartitionID></InstallTo><InstallFrom><Path>.\Operating Systems\WIN7X64ENTDVD_REF\WIN7X64ENTDVD_REF.wim</Path><MetaData><Key>/IMAGE/INDEX</Key><Value>1</Value></MetaData></InstallFrom></OSImage></ImageInstall><Display><ColorDepth>16</ColorDepth><HorizontalResolution>1024</HorizontalResolution><RefreshRate>60</RefreshRate><VerticalResolution>768</VerticalResolution></Display><ComplianceCheck><DisplayReport>OnError</DisplayReport></ComplianceCheck><UserData><AcceptEula>true</AcceptEula><ProductKey><Key>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</Key></ProductKey></UserData></component><component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SetupUILanguage><UILanguage>en-US</UILanguage></SetupUILanguage><InputLocale>0409:00000409</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component></settings><settings pass="generalize"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><DoNotCleanTaskBar>true</DoNotCleanTaskBar></component></settings><settings pass="specialize"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"><ComputerName>*</ComputerName><ProductKey>33PXH-7Y6KF-2VJC9-XBBR8-HVTHH</ProductKey><RegisteredOrganization>TEST</RegisteredOrganization><RegisteredOwner>TEST</RegisteredOwner><DoNotCleanTaskBar>true</DoNotCleanTaskBar><TimeZone>Pacific Standard Time</TimeZone><CopyProfile>true</CopyProfile></component><component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><RunSynchronous><RunSynchronousCommand wcm:action="add"><Description>EnableAdmin</Description><Order>1</Order><Path>cmd /c net user Administrator /active:yes</Path></RunSynchronousCommand><RunSynchronousCommand wcm:action="add"><Description>UnfilterAdministratorToken</Description><Order>2</Order><Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path></RunSynchronousCommand><RunSynchronousCommand wcm:action="add"><Description>disable user account page</Description><Order>3</Order><Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path></RunSynchronousCommand></RunSynchronous></component><component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>0409:00000409</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component><component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TapiConfigured>0</TapiConfigured><TapiUnattendLocation><AreaCode>""</AreaCode><CountryOrRegion>1</CountryOrRegion><LongDistanceAccess>9</LongDistanceAccess><OutsideAccess>9</OutsideAccess><PulseOrToneDialing>1</PulseOrToneDialing><DisableCallWaiting>""</DisableCallWaiting><InternationalCarrierCode>""</InternationalCarrierCode><LongDistanceCarrierCode>""</LongDistanceCarrierCode><Name>Default</Name></TapiUnattendLocation></component><component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><DisableSR>0</DisableSR></component></settings><settings pass="oobeSystem"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"><UserAccounts><AdministratorPassword><Value>*REMOVED*</Value><PlainText>false</PlainText></AdministratorPassword><LocalAccounts><LocalAccount wcm:action="add"><Password><Value>*REMOVED*</Value><PlainText>false</PlainText></Password><DisplayName>NEWadmin</DisplayName><Group>Administrators</Group><Name>NEWadmin</Name><Description>Local Admin</Description></LocalAccount></LocalAccounts></UserAccounts><AutoLogon><Enabled>true</Enabled><Username>Administrator</Username><Domain>.</Domain><Password><Value>*REMOVED*</Value><PlainText>false</PlainText></Password><LogonCount>999</LogonCount></AutoLogon><FirstLogonCommands><SynchronousCommand wcm:action="add"><CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine><Description>Lite Touch new OS</Description><Order>1</Order></SynchronousCommand></FirstLogonCommands><OOBE><HideEULAPage>true</HideEULAPage><NetworkLocation>Work</NetworkLocation><ProtectYourPC>3</ProtectYourPC><HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE></OOBE><RegisteredOrganization>TEST</RegisteredOrganization><RegisteredOwner>TEST</RegisteredOwner><TimeZone>Pacific Standard Time</TimeZone></component><component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>0409:00000409</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component></settings><settings pass="offlineServicing"><component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><DriverPaths><PathAndCredentials wcm:keyValue="1" wcm:action="add"><Path>\Drivers</Path></PathAndCredentials></DriverPaths></component></settings><cpi:offlineImage cpi:source="catalog://mdtsrv01/deploy$/operating systems/win7x64entdvd_ref_bst/win7x64entdvd_win7x64entdvdcdrive.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

Hi Guys,

I'm still searching for the best way to go about upgrading about 200 user computer from Windows 7 Ent to Windows 10 Ent (most of which I don't have physical access to). This is my first time working with MDT, and I still believe an MDT task seq can do exactly what I need it to do, simply upgrade the machine OS, I don't need anything else. All my users are local administrators on their respective machines and I was simply going to have them run litetouch.vbs and have it fully automated from there the only problem seems to be that when they log back in with their user account they are prompted "Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed." (even thought they are set as a local administrator on the machine) and the task fails although windows has been upgraded to windows 10. The same thing seems to happen even when running lightouch as the domain admin. From what I gather upon upgrade of the OS you must login in as the actual .\administrator account which is currently set different on each machine for the task to complete. I've tried using the "administrator password" wizard panel in MDT which should set the administrator password to something of my liking but it doesn't seem to change the current password. What would be the easiest way to set this up to have my end user simply run a file to upgrade their OS? Is there any way to have the task sequence not require the final login after the OS has been upgraded already as the OS seems to function however the prompt that the sequenece failed comes up after every reboot until you log back in as .\administrator. Is there some easier way to do this outside of MDT? Thanks so much!

Hi

We are having issues with the latest MDT update in that it won't take ownership of TPM Machines. Just getting FAILURE ( 6743 ): TPM P@ssword missing at the end of the deployment process. Looking at the logs it looks like the script takes ownership of TPM but then when it checks to confirm it reports TPMOwner as false.

<![LOG[Success TPM Enabled]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[Success TPM Is Activated]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[Success TPM Is Owned]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[Success TPM Ownership Allowed]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[Check for Ensorsement Key Pair Present = 0]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[TpmEnabled: True]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[TpmActivated: True]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[TpmOwned: False]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[TpmOwnershipAllowed: True]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[EndorsementKeyPairPresent: True]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[TPM P@ssword missing. Please provide P@ssword via TpmOwnerP@ssword or AdminP@ssword]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="1" thread="" file="ZTIBde">
<![LOG[FAILURE ( 6743 ): TPM P@ssword missing.]LOG]!><time="12:29:11.000+000" date="10-14-2015" component="ZTIBde" context="" type="3" thread="" file="ZTIBde">

I cannot work out what is going on or how to fix, any help would be greatly appreciated.

I am struggling with drivers for some time now with my Latitude Laptops. Downloaded Dell cabinet with all drivers in it and imported the drivers in MDT. Because the laptop was not starting after deploy there is a problem with the drivers so i started with troubleshooting which drivers cause the error after the deploy. It was some the chipset drivers  the DPTF chipset drivers.

Tried to download newer drivers from Dell but keep getting problems with those drivers. Sometimes after deploy when go to deivemanager and adding those drivers manually there is no problem, the drivers are installed. So it is a problem with MDT / driver deploy.

Anyway i am searching for a easy fast way to add those drivers after Deploy. When deploy is finished go to devicemanager and i want with one click to remove all yellow marks with the drivers.

Is this a possiblility: fast way to install the drivers with one step after Deploy?

Tried already to update thru Windows update drivers but that's not a solution..

freddie

Hi,

I injected a bunch of Windows OS patches into a really old Windows 7 WIM file but when I deploy the image via MDT to a machine the patches are not applying. I've slipstreamed over 190 updates into the WIM so I'd be expecting to see a few apply. SP1 is installed and when I run a get-packages via DISM it lists all the patches as installed.

Is there a log file or way of troubleshooting why this is happening?

Thanks!

www.techielass.com

I am creating a test task sequence. Any help is appreciated.

Error while importing Microsoft Deployment Toolkit Task Sequence.

System.FormatException: Input string was not in a correct format.

  at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)

  at System.Version.TryParseComponent(String component, String componentName, VersionResult& result, Int32& parsedComponent)

  at System.Version.TryParseVersion(String version, VersionResult& result)

  at System.Version.Parse(String input)

  at System.Version..ctor(String version)

  at Microsoft.BDD.Core.Utility.GetVersion(String strVersion)

Environment: SCCM 2012 R2 SP1 CU1

Console version 5.0.8239.1206

Site version 5.00.8239.1000

MDT2013 Update1

WADK for Windows 10

Hi,

Is it possibly and if so how can i create a Customsettings.ini script to make a random local admin password? stored somewhere safe? The problem occurs when I install a pc, and then the pc user is somewhere in the country where they don't have access to our AD. Then I could handout the admin password for that pc? I don't want to give out the current local admin password. So this way we have two local admin accounts?

So is would be very nice if customsettings created a local admin with the username admin and put a random password and stored it with the pc name in any document or is this to hard?

And why don't the alert me function work?

best regards Kjell

All, I have found that these updates for "August 2015" App updates are blowing things up in our environment.  I am having the issue when trying to rebuild and capture my Windows 8.1 Enterprise (11-21-2014 download from vlsc).  The updates are for "built- in" Appx Packages. 

In our build sequence we uninstall these applications:

Get-AppxProvisionedPackage -Online | Remove-AppxProvisionedPackage -Online -Verbose

Get-AppxPackage Microsoft.BingFinance | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingFoodAndDrink | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingHealthAndFitness | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingMaps | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingNews | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingSports | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingTravel | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.BingWeather | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.HelpAndTips | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.Office.OneNote | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.Reader | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.SkypeApp | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.WindowsAlarms | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.WindowsCalculator | Remove-AppxPackage -Verbose
Get-AppxPackage microsoft.windowscommunicationsapps | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.WindowsReadingList | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.WindowsScan | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.WindowsSoundRecorder | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.XboxLIVEGames | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.ZuneMusic | Remove-AppxPackage -Verbose
Get-AppxPackage Microsoft.ZuneVideo | Remove-AppxPackage -Verbose

These are the updates that are failing:

• KB3080457 - August 2015 Communications Apps update for WSUS for Windows 8.1
• KB3081397 - August 2015 Bing Finance app update for WSUS for Windows 8.1
• KB3081398 - August 2015 Bing Travel app update for WSUS for Windows 8.1
• KB3081399 - August 2015 Bing Sports app update for WSUS for Windows 8.1
• KB3081401 - August 2015 Bing News app update for WSUS for Windows 8.1
• KB3081402 - August 2015 Bing Maps app update for WSUS for Windows 8.1
• KB3081403 - August 2015 Bing Health & Fitness app update for WSUS for Windows 8.1
• KB3081405 - August 2015 Bing Weather app update for WSUS for Windows 8.1

If they are removed from Pre-provisioning and removed from the only user account (Administrator), why are these applications being detected as needing updates instead of being skipped as not installed?

Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

hi,

I can't succeed in deploying windows 7 to the C-drive.

Can someone please advice how to be able to install windows to the C-drive?

I'am using the following config:

OS:Windows 7

MDT version: MDT 2013 Update 1

Image: install.wim from original ISO source

I have added the variable OSDPreserveDriveLetter=False right before the step "Install Operating System"

The "Install Operating System" step has the following option: location: Specific Logical Drive Letter - Drive Letter: C:

The format and partition Disk step (both Bios and UEFI) are unchanged.

The device I'm deploying to is an UEFI device.

Many Thanks in advance

Hello,

I've run into the following problem twice now. We have an HP revolve 810 G3 and an HP Workstation Z640.  When trying to deploy an image to these computers we get the following message "A connection to the deployment share could not be made.  The following networking device did not have a driver installed.  PCI\VEN_8086&DEV_15A0&SUBSYS_2129103C&REV_05"

I searched through all of the drivers I have in the Deployment Share folder which we have split out by manufacturer and then model number and none of the drivers list that exact device ID.  The closest I was able to get was a driver with "PCI\VEN_8086&DEV_15A0" listed. I was able to confirm that this is the driver that is being used by the computer when it is shipped to us from HP.

After some more  investigation it looks like MDT will not use the driver unless the device ID matches exactly.  Is there anyway around this?  Is there a way to force it to use that specific driver on these devices?