MDT 2012 - Windows ADK Issue

If this is the wrong place, let me first apologize but I am curious is anyone has seen the following issue when installing MDT 2012 Update 1 and Windows ADK:
After installing MDT 2012 Update 1 and Windows ADK, I am unable to create a share in the Deployment Workbench, all I get is the box telling me:
Either the Windows Automated Installation Kit(AIK) or the Assessment and Deployment Kit(ADK) is required for interacting with deployment shares. Please install version 6.1.7600.0 or later.
I setup a new laptop (Lenovo x220 with Windows 7 Pro x64) to use and installed MDT 2012 Update 1 and then did the full install of the ADK (including SQL 2012 Express) and it does not work.
I can open the Windows System Image Manager from the ADK and create a share and do everything without issue but I cannot do anything from the Deployment Workbench as it only says that the AIK or ADK is required.
I tried installing on a Windows 8 Pro x64 machine as well and get the same error so I am inclined to think I am missing something. Any help would be appreciated.
Thanks.

Previously I was able to setup MDT and WAIK on a desktop running Windows 7 as a full blown server was not available and create DVD discs. I was hoping to do the same using a Windows 8 machine. Everything works if I install the WAIK, MDT just does not recognize
the ADK install. I have imaged the laptop several times now with Windows 7 and with Windows 8 and I originally installed MDT first and then the ADK but then found a document sating install the ADK first so I started over and installed the ADK and then MDT
but still get the same result.
I have 2 spare laptops that I wanted to use for testing as I have not bought a desktop in years because I have a NAS device and save most item there so the 2 laptops I have with 4GB RAM and 300GB hard drives can be used to test almost anything. I may
create a VM or Hyper-V machine running 2008 R2 Server to see if everything works in the mean time.
Thanks.
Darryl Dison

Similar Messages

Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0

Hi,
I need your help to sort out the following issue.
I have installed MDT 2012 +ADK 8.0 and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
Image from the machine,even the sysprep failed. This is the error
Your PC needs to restart.
Please hold down the power button.
Error Code:0x0000005D
Parameters:
0x030F0209
0x746E6547
0X49656E69
0X6C65746E
So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
D530 is the maximum available HW model in client environment so your help will be much appreciated.
Thanks in Advance!!

I have never seen that error before (see identical post). I did a quick internet search and found the following:
http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
Either:
1) Upgrade your machines with modern processors that support the ADK.
or
2) Downgrade to the WAIK
http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
Keith Garner - keithga.wordpress.com

MDT 2012- windows update not working

Windows 2008 r2
MDT 2012
Steps I have completed:
1.applied patch for WSUS sp 3
2. made sure folder browsing is disabled in IIS7
3. restarted server
4. looking at the wsus console I see the new computer. they are listed in "Unassigned Computers" which is correct. These workstations have not been added to the domain yet.
Also, I am running LUP on the WSUS server
Any suggestions appreciated!
Ran solar winds WSUS diagnostic utility and received the error below
Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)

thanks for the reply,
When deploying an Image, get an ZTI error "Unhandled error return by ZTI windowsupdate. Object does not support this property or method?
Also, I noticed error message on WSUS server "Client computers are installing updates with a higher than 25 percent failure rate. This is not normal."
I ran the solar diag on the client and got this message:
Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)
I ran the solar diag on the server:
# Solarwinds® Diagnostic Tool for the WSUS Agent
# 3/26/2013
Machine state
User rights:                                       User has
administrator rights
Update service status:                             Running
Background Intelligent Transfer service status:    Running
OS Version:                                        Windows
Server 2008 R2 Standard Service Pack 1
Windows update agent version:                      7.6.7600.256 (WU Agent is OK)
Windows Update Agent configuration settings
Automatic Update:                                  Not found (There is no such key)
Options:
Not found (There is no such key)
Use WSUS Server:                                   Not found (There is no such key)
Windows Update Server:                             Not found (There is no such key)
Windows Update Status Server:                      Not found (There is no such key)
WSUS URLs are identical:                           Values are empty
WSUS Server Connectivity -- Connectivity check is impossible
Error description:                                 Connectivity check is impossible because
of invalid Windows Update Agent configuration

MDT 2012 Windows 7 Deployment Stops At User Account and Computer Name Setup Page

I was given a sysprepped custom Windows 7 WIM image that was set up by a third party that didn't use MDT to create the WIM.
I created a task sequence to deploy it, but it never finishes. After the OS installs and it reboots, it comes up to the white setup page asking for a user name and computer name that looks like this image:
Is there a setting in MDT that can change that behavior?

Are you joining the computer to a domain?
It sounds like MDT did not create the unattend.xml file itself (or is there an unattend file already in the image itself?)
MDT needs to be able to autologin with the local admin account
From MDT in your task sequence - OS info - Edit unattend.xml you can check if your unattended file is correct.
Check what's in there for:
- computer name in 4 Specialize area - Windows-Shell-Setup_neutral (it should be empty if you want MDT to handle it).
- Also i think you need to have in the Specialize section, under Microsoft-Windows-Deployment_neutral - Run Synchronous an EnableAdmin insert
This will enable the local admin account
- Also check in phase 7 oobe System in Shell-Setup_neutral
There should be an autologon with a count of 999
Check if you have any Local Accounts there.
Finally read this:
When I am joining clients to a domain, can I avoid creating a local user
account on the computer?
Yes. To do this, create an image unattend file that adds a domain account to the Administrators group. In addition, you must delete the <LocalAccounts> section if it is present in your
unattend file (simply commenting it out will not work). An example file is below. Note that if domain join fails, Windows Deployment Services will not use the unattend file so you will be able to create a local account. For more information about creating
unattend files, see Automating Setup.
<?xml version='1.0' encoding='utf-8'?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:ms="urn:schemas-microsoft-com:asm.v3" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
<DomainAccounts>
<DomainAccountList wcm:action="add">
<DomainAccount wcm:action="add">
<Group>Administrators</Group>
<Name>DomainAdmin</Name>
</DomainAccount>
<Domain>DomainName</Domain>
</DomainAccountList>
</DomainAccounts>
</UserAccounts>
</component>
</settings>
</unattend>
I tried opening the unattend.xml from the MDT workbench, but it errors out saying it cannot be done because the captured image is x86.

MDT 2012 Windows update Process

Hi
I'm using the Windows update Pre & post steps in my sequences. It always worked ok but now It see in the log:
"The action (Windows Update (Pre-Application installation)) initiated a reboot request
After reboot my TS isn't working correct anymore because it now needs an extra reboot and the autoadmin logon only allows 2.
I could raise this value to 3 but if one day I decide to add those updates in the image, it will auto logon 1 time to many so you see my problem.
Is there a way to supress the reboot of this process?
Or how do you guys handle this?
Thanks
Jan
jgs

Hi,
I don't use autoadmin logon at all. Don't use that at all. The system will login every time, until the TS is done.
The problem with that is that is stays loged in once the TS is complete.
To solve this, your final line in CustomSettings.ini should read "FinishAction=LOGOFF" or even "FinishAction=REBOOT". The TS will then do one final logoff/reboot once it is done and just be at the "C+A+D" login screen when done.
As for the WSUS reboot, just leave that; it's by design...
Hope this helps,
Martin
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

MDT 2012 - Failure 9701: Unable to find any version of USMT, unable to perform user state migration. Failed to run the action Restore User State. DNS Record does not exist. (Error: 000025E5; Source: Windows)

I am having trouble trying to capture a new Windows 8 image with WDT 2012.
My Setup -
Server 2012
WDS
MDT 2012
Windows 8 ADK
Hyper-V
I have created a new task and I can get the image to successfully deploy the image to a VM but it seems to fail at the Restore User State task.
Once the install Applications task has finished I added a Suspend task so I could customize the image a little. Upon resuming the task sequence is where the above failure message appears. I can see it gets to the next step (which is 'Restore User State')
but that seems to be where is crashes.
Does anyone have any advice on what I might be doing wrong or what I can do to resolve the above issue?

WAIK being installed was probably your issue so I wouldn't bother disabling the restore task. It is used to migrate user data, docs, and settings on refreshes, not new builds. It doesn't affect CopyProfile, just note that data will be migrated on refreshes so
some aspects may change, ie wallpaper, shortcuts, etc but what gets migrated with USMT can also be configured.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

MDT 2012 + WinPE 4.0 + VMWare ESXi - Hangs "Windows is loading files" booting into PE

I'm trying out using MDT 2012 and WinPE 4.0, upgrading things. I've recreated things following templates in MDT 2012. I'm also using ADK and WinPE 4.0.
Issue I'm seeing is upon restarting into WinPE I see the screen showing Windows is Loading Files and the progress bar. I see the first one load through and then the second slower one load through. Once progress bar fills, it just does nothing and I'm left
looking at a complete progress bar.
I was trying obviously first using VMWare ESX 5.0 with no success, subsequently tried a couple of physical machines and those had no problems. I still want to get working on ESX since that will help speed up development and testing of the rest of the stuff
I need to upgrade. Tried a variety of SCSI controllers within ESX vms. I tried VMWare Workstation 9 with the mixed results as with the LSI Logic Parallel SCSI controller had success but not the others.
I of course at first tried making sure drivers were added with no change, although that still could be an issue with drivers I found to put in being incorrect.
More interestingly though is that I can of course install Windows 8 from install media just fine on these hardware, as well as if I create an ISO from the deployment share and boot to that it works just fine, so it seems to just be an issue when booting
to WinPE on disk.
Any ideas are greatly appreciated. Thanks.

I did have the same problem with ESXI 4.1 and Windows 8.
I found a full solution with the following:
download the linked file at the bottom of this post and add the following options to your vmware-configuration
file:
bios440.filename =
"<full path to rom image>" --> if file in folder of vm only "bios.440.rom
mce.enable = TRUE
cpuid.hypervisor.v0 =
FALSE
vmGenCounter.enable =
FALSE
This worked for me for several environment with an older ESXI-invironment and Windows 8.
http://communities.vmware.com/servlet/JiveServlet/download/2139717-98102/bios.440.rom
I can confirm that this works also! Many thanks!
ESXi 4.1 with WinPE4.0

SCCM 2012 RTM to SP1 Upgrade - Windows ADK 8.1

Hello,
I am after some advice. We have two physical locations containing a single SCCM 2012 primary site server in one location and distribution point server in the other location.
Both servers are also configured as DHCP Servers and DHCP scope options have been configured correctly to allow both DHCP and Windows Deployment Services to co-exist.
OSD was working fine, until I upgraded the primary site server to SCCM 2012 SP1. During the upgrade process, I installed Windows ADK 8.1 which would appear is not supported however no errors were reported during the upgrade process.
Issues I have encountered;
- I can no longer PXE boot with the following error 'PXE-E55: ProxyDHCP service did not reply to request on port 4011'
- The x:\remoteInstall\Boot\Fonts directory is empty suggesting the boots images were not finalised.
- When updating the distribution points with the boot images i get the following error via the wizard;
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"UKS0003B\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889
SMSPXE.log contains the following errors;
Failed to copy X:\RemoteInstall\SMSTempBootFiles\XXX00014\WINDOWS\Boot\PXE\wdsmgfw.efi to X:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi
InstallBootFilesForImage failed. 0x80070002
Warning: Failed to copy the needed boot binaries from the boot image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)
Failed adding image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim. Will Retry..
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read ADK installation root registry value
I am looking for some advice on the best way to rectify this issue. Options I am considering are as follows, however I am unsure of the outcome should I attempt these;
1 - Upgrade to SCCM 2012 R2 which supports ADK 8.1
2 - Uninstall Windows ADK 8.1, install 8.0
3 - Attempt to restore back to SCCM 2012 RTM using file system backups and SCCM backups.
Any help or suggestions would be much appreciated.

Thank you both for your replies and advice
The configMgr 2012 environment is primarily used for OSD, and software updates for Servers only.
I have followed Peter’ advice, and uninstalled WADK 8.1 and installed 8.0 and I am currently investigating errors within the SMSPXE.log, and I have seen other posts elsewhere within these forums
with the same issue with suggested solutions which I shall investigate.
With regards to DHCP on the ConfigMgr site servers – I could not agree with you more.
Unfortunately, my company use a third party DHCP solution which was incapable of supporting PXE-boot for OSD.
We were therefore required to have a separate Microsoft DHCP solution on the site servers to by-pass this issue.
The intention is to upgrade to Configmgr 2012 R2.
My understanding is that there is no direct upgrade process from SCCM 2012 RTM to R2, therefore I have upgraded to SP1 and would prefer all features are working correctly before progressing to R2.
Many thanks again,
Regards,
JohnRox

Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share

Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.

Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives.

Windows Vista is not installing using MDT 2012 update 1

I have created a media using selection profile in MDT 2012 update 1, but it is not deploying my physical machine. I get error message that Windows Cannot copy files required for installation. Make Sure all files required for installations are available.
However i have successfully deployed Windows & and Windows XP with MDT 2012.
I also used different iso image of vista but still i get same error message.

Looks like you have a *NEW* issue that is unrelated to this thread. Generally I recommend that you open a new thread.
How to Debug missing Drivers in MDT Litetouch
I see that you say there are *Problems* but you don't list which devices or drivers are missing.
From your Bdd.log file I can see that the following drivers are getting copied locally:
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6" "C:\Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315" "C:\Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A" "C:\Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "C:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4" "C:\Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4"
However I can't tell what the problem is.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2012 'Failed to save Environment to (80070057) Error during Windows 7 x64 Pro Deployment

Hi There,
I've been using MDT for a little while now, but I'm having problems successfully deploying an image to a batch of new laptops. The laptop HDD's are completely blank, and I am PXE booting using an x64 Litetouch Image via WDS. I have successfully captured
my image from a reference laptop (the same model that I'm trying to image), and I am now trying to deploy it using a standard client task sequence.
The 'Install operating System' phase seems to go ok, but then sits for quite some time at the 'Applying Unattend.xml' stage, then eventually, I get a general error 'Task Sequence Failed - 80004005'. I then exit MDT (it doesn't reboot as it should), and let
the laptop boot, which it does, and logs straight on into Windows, but gives me error along the lines of 'can't find the litetouch script', which I assume means MDT hasn't been able to copy it across. The laptop is however joined to our domain, and I pretty
much just have to tick the 'require a password to log on to this computer' box in user accounts, and all looks ok.
So in summary, the image is applying, but the laptop is not rebooting and running the final cleanup scripts.
I have already changed the SATA mode to IDE, instead of AHCI, having read this sometimes causes problems. I also read that systems with UEFI BIOS can also cause problems with MDT, but I'm not sure if this is the case.
I have edited my customsettings.ini, to copy log files back to my server, which it has done for me. Having looked at the logs (with CM Trace), I can see these errors:
Failed to save environment to (80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to persist execution state. Error 0x(80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save execution state and environment to local hard disk
TSManager 26/03/2014 15:48:09
1820 (0x071C)
The task sequence execution engine can not reboot the machine because we failed to persist execution environment
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Fatal error is returned in check for reboot request of the action (Restart computer).
Unspecified error (Error: 80004005; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
An error (0x80004005) is encountered in execution of the task sequence
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Task Sequence Engine failed! Code: 80004005
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Any help you can give me would be great, as I'd like to get this process running properly.
Thanks,
Sarah

You don't mention what kind of OS this is (Windows 7 Pro x64?)
This is a known issue/FAQ.
I would recommending using MDT 2012 (update 1) for UEFI machines.
Machines with uEFI 2.3.1 only support Windows 8.x.
http://technet.microsoft.com/en-us/library/hh824898.aspx
Recomendation: Convert the BIOS to CSM and/or upgrade to Windows 8.1 :^)
Keith Garner - keithga.wordpress.com

MDT 2012 upd 1 and Windows / Component updates

I am trying to create a deployment for Win 7 x64 in MDT 2012, and it is going quite well. My problem is with the Windows Update passes -- for some reason it misses many Office and Component updates until I go to deploy. Then it takes another
hour to grab and install those. I don't understand why it does not grab them during the TS process.
I am doing a staged capture in a VM environment, starting with a zero-touch capture that includes Office 2010 and all the updates. This is my thin image and it takes about 5.5 hours through capture. Then I take this thin image, add standard apps
that cannot be silently installed, customize desktop options that cannot be easily automated (another huge pain, but another topic), and, I was hoping, install all the updates for Office 2010 and other non-OS components.
In the first TS, I run the updates pre-installation, use the TS step to install Office, and run them again post-installation. It does pick up a few, but then the logs say the system is fully updated and goes on to the next step.
In the second TS, I use the post-installation update step. One of the apps I use installs SQL components, and the TS picks up on this and installs several updates it finds. Then it decides the machine is up to date and moves on, skipping about
40 updates as of this writing.
As a test, I inserted a reboot step between app installation and the post-install Update step, but it still ignored the Office updates. Research on the issue turned up the idea that at some point ZTIWindowsUpdate turns on the extra updates, and also
several suggestions that this is how it is supposed to work (and why the standard TS is designed this way).
I rolled my VM back to the suspended point and I'm running WU manually at the console. I had to enable "Microsoft Update" manually, and now it is happily pulling down the updates. I just hope there's enough smarts left in the VM to
run to the task to completion.
I'm hoping that some whiz with the process can enlighten us on how to force ZTIWindowsUpdate to search for critical updates for all Microsoft components, not just the OS ones.
UPDATE:
Digging into the code and logs, it seems that a certain condition is not occurring to trigger the Microsoft Update service; bFoundMU must be true for this to happen. A ServiceID hard coded is not being matched--the reason escapes me. Near as
I can tell, after a magic reboot it finally finds a match for this ServiceID. Hopefully this snippet does not get munged...
    On Error Resume Next
           Item = oFSO.GetFileVersion ( ees("%SystemRoot%\System32\WUAUENG.DLL" ) )
           oLogging.CreateEntry "Ready to Opt-In to Microsoft Update: WUA Version: " & Item , LogTypeInfo
           Set ServiceManager = nothing
           Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
       On Error Goto 0
       If ServiceManager is nothing then
           oLogging.CreateEntry "Failed to Create Object: Microsoft.Update.ServiceManager" , LogTypeWarning
       Else
           bFoundMU = False
           For each Item in ServiceManager.Services
               WScript.Echo "Registered Update Service: " & Item.ServiceID & "   " & Item.Name
               If Item.ServiceID = "7971f918-a847-4430-9279-4a52d1efe18d" then
                   bFoundMU = True
               End if
           Next
           oLogging.CreateEntry "Microsoft Update Service: Enabled = " & bFoundMU, LogTypeInfo
           If not bFoundMU then
               On Error Resume Next
                   Err.clear
                   ServiceManager.ClientApplicationID = "My App"
                   If Err.Number <> 0 then
                       oLogging.CreateEntry "There was an error getting Windows Update to opt into Microsoft Update. Please verify you are running the latest version
of Windows Update Agent." , LogTypeWarning
                   End if
The logs look virtually identical between the two runs. This is getting way deeper than I understand the update process or about service IDs.
UPDATE 2:
Digging further, it seems that the the condition of bFoundMU has no bearing on whether or not MU is used, but possibly the existence of muauth.cab. From the deploy log where it actually started, bFoundMU is still false, but at that point the Office
updates started to come in:
<![LOG[Property MSIT_WU_Count is now = 1]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Archive NoAUtoUpdate State: Was [<empty>].]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Property NoAutoUpdate_Previous is now = <empty>]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.5.7601.17514]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Microsoft Update Service: Enabled = False]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
thread="" file="ZTIWindowsUpdate">
<![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ Status: 3]LOG]!><time="11:05:35.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[Command Line Procesed Query=False Registered=False UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
thread="" file="ZTIWindowsUpdate">
<![LOG[Start Search...]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
__bunch of skipped updates__
<![LOG[ SKIP - 258b6ca1-a8ec-4dfa-b619-fb8cecac6e2e - Turkish Language Pack - Windows 7 Service Pack 1 for x64-based Systems (KB2483139) - 56 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 48f7e3b7-2c8f-4900-ae32-f3d8f29c988d - Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332) - 55 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - d68e0cb2-9501-405e-af9c-156f352d6735 - Security Update for Microsoft Visual C++ 2010 Redistributable Package (KB2467173) - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 719584bc-2208-4bc9-a650-d3d6347eb32e - Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063) - 9 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - eb7a169f-6bca-4e00-a52a-623c063c162d - Update for Office File Validation 2010 (KB2553065), 32-bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - f51a0e5b-24a9-4be1-8b36-0f22f99949e7 - Security Update for Microsoft SharePoint Workspace 2010 (KB2566445), 32-Bit Edition - 17 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 35eb79df-cb34-491c-ab0a-34b63f32b45c - Update for Microsoft Office 2010 (KB2553092), 32-Bit Edition - 9 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - a6309b2e-7ee4-4b02-8ce9-cf39796a2411 - Update for Microsoft OneNote 2010 (KB2553290) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - f5202a56-ff34-401d-a040-f97c7f70891c - Update for Microsoft Office 2010 (KB2553310) 32-Bit Edition - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 33a4aa0a-cb01-4326-85f4-4a7d33d8782b - Update for Microsoft Outlook Social Connector 2010 (KB2553406) 32-Bit Edition - 1 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - aae5e2c7-3498-4f43-af66-aec06a59713f - Microsoft Silverlight (KB2636927) - 12 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - c8077d6d-00c2-421b-89f6-30828574519a - Update for Microsoft Office 2010 (KB2767886) 32-Bit Edition - 271 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f - Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition - 395 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - b8fcacb4-add0-4cc9-8551-675b59965798 - Update for Microsoft Office 2010 (KB2825640) 32-Bit Edition - 18 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 5923c276-0628-4ba4-be3d-e56aa029a14b - Security Update for Microsoft Office 2010 (KB2687423) 32-Bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[INSTALL - 79b27019-3090-4309-bfdc-c8be9b21ab96 - Update for Microsoft Access 2010 (KB2553446) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
After the subsequent reboot, bFoundMU was set to true.

Another detail I neglected to mention is that I am using two separate deployment shares, one for building the deploy image and the other for actual deployments. I think I found another clue in the log, muauth.cab:
<![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
The next stanza in ZTIWindowsUpdate.wsf is this:
If oEnvironment.Item("WsusServer") = "" then
                          iResult = oUtility.FindFile("muauth.cab", strCabPath)
                       If iResult <> Success then
                           '// "" will force a internet search for cab file
                           strCabPath = ""
                       End if
                       oLogging.CreateEntry " about to begin add service ["+ strCabPath +"]", LogTypeInfo
                       Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",6,strCabPath)
                       oLogging.CreateEntry " Status: " & NewUpdateService.RegistrationState, LogTypeInfo
                   End if
Indeed, the muauth.cab file was present in my first one, but not the deployment one. As the log says, since there is no muauth.cab file, the code will then go download it.
I don't know how, when, or why this happened (why is it in my first DS and not my second?), but a simple test this evening will confirm my suspicion that if the file is not present it will update as expected.

MDT 2012 - DaRT 7.0 Integration Issue

Hello everyone,
I have successfully configured a new MDT 2012 environment from Release-To-Web versions of MDT. (Clean environment, no remnants of MDT 2010, etc.)
1 - I have copied the DaRT 7.0 Tools.cab file from both an x86 and x64 installation of Windows 7 Enterprise from the tutorial posted here:
http://blogs.technet.com/b/mniehaus/archive/2011/11/28/mdt-2012-new-feature-dart-integration.aspx
I enabled DaRT, updated my boot WIMs, and tried PXE booting to my deployment share. I connect to my deployment share with no issues.
I then open the DaRT toolset from the intro menu.
Problem: The Standalone System Sweeper fails to run. Clicking on it displays "The tool failed to run. Try choosing another tool." The only option is to click OK and takes you back to the main DaRT menu selection.
Tests I have performed so far: For kicks and giggles, I have also rebuilt the boot WIMs with all of the contents from (Admin PC's hard drive) C:\Program Files\Microsoft DaRT 7\v7\ folder into the X:\DeploymentShare\Tools\(x64 or x86)\ .
I thought "Sweeper.cab" might do it, but no success.
Also, I know DaRT is partially working. Remote Connection starts automatically when the PC is booted to WinPE. I also know my DaRT media is not corrupted because I was able to generate a DaRT.iso image on my admin PC, extract the .WIM from the ISO and PXE
boot that with NO issues. (Everything in that DaRT media works without issues, which leads me to believe it is something in MDT 2012.)
FYI, if it helps any, the "Version.txt" file from the DaRT 7.0 installation says: 7.0.291.0
I have my scratch space on my WinPE media set to "128"
My WAIK version is 7.1 (7.0 with SP1 Supplement)
Also to the MDT 2012 team: Thanks, this version is much more polished out-of-box versus the 2010 initial release. I don't have to use extra scripts to clean up the "dirty" environment at the end of a Task Sequence anymore (it just works now), and I don't
get the odd partitioning scheme that 2010 used (BitLocker reasons). So, thumbs up!!!
Thanks,
stealthfield
Cory | Find me: Wordpress | Twitter:
@stealthfield

Run the following command from an Elevated Command Prompt:
DISM.exe /Get-WimInfo /WimFile:C:\Path\To\Wim\winpe.wim /Index:1
x86 - Windows AIK 3.0:
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Details for image : C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim
Index : 1
Name : Microsoft Windows PE (x86)
Description : Microsoft Windows PE (x86)
Size : 721,731,007 bytes
Architecture : x86
Hal : <undefined>
Version : 6.1.7600
ServicePack Build : 16385
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 2004
Files : 8868
Created : 7/13/2009 - 7:51:36 PM
Modified : 7/13/2009 - 7:51:42 PM
Languages :
en-US (Default)
The operation completed successfully.
amd64 - Windows AIK 3.0:
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Details for image : C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim
Index : 1
Name : Microsoft Windows PE (x64)
Description : Microsoft Windows PE (x64)
Size : 865,104,595 bytes
Architecture : x64
Hal : <undefined>
Version : 6.1.7600
ServicePack Build : 16385
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 2046
Files : 9079
Created : 7/13/2009 - 8:13:01 PM
Modified : 7/13/2009 - 8:13:32 PM
Languages :
en-US (Default)
The operation completed successfully.
x86 - Windows AIK 3.1:
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Details for image : C:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim
Index : 1
Name : Microsoft Windows PE (x86)
Description : Microsoft Windows PE (x86)
Size : 723,041,329 bytes
Architecture : x86
Hal : <undefined>
Version : 6.1.7601
ServicePack Build : 17514
ServicePack Level : 1
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 2009
Files : 8902
Created : 11/20/2010 - 7:54:47 AM
Modified : 11/20/2010 - 7:54:51 AM
Languages :
en-US (Default)
The operation completed successfully.
amd64 - Windows AIK 3.1:
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Details for image : C:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim
Index : 1
Name : Microsoft Windows PE (x64)
Description : Microsoft Windows PE (x64)
Size : 875,839,691 bytes
Architecture : x64
Hal : <undefined>
Version : 6.1.7601
ServicePack Build : 17514
ServicePack Level : 1
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 2051
Files : 9137
Created : 11/20/2010 - 9:15:41 AM
Modified : 11/20/2010 - 9:15:44 AM
Languages :
en-US (Default)
The operation completed successfully.

MDT 2012 Errors - Won't Run My Windows 8.1 Activation Script/Task Sequences Fail

Hello all,
I've been using MDT 2012 for a while now to image machines in our environment with success for the most part. Just recently, however, I've been running into issues at the point where the deployment is supposed to be activating Windows where it will just fail the deployment. It outputs a number of errors, including:TextWindows cannot remove Microsoft.VCLibs.120.00_12.0.20812.1_x86__8wekyb3d8bbwe because the current user does not have that package installed. Use Get-AppxPackage to see the list of packages installed.NOTE: For additional information, look for [ActivityId] 5f3738f0-b9a2-0001-0581-375fa2b9d001 in the Event Log or use the command line Get-AppxLog -ActivityID 5f3738f0-b9a2-0001-0581-375fa2b9d001]LOG]!+ Get-AppxPackage -AllUsers | Remove-AppxPackage+ ~~~~~~~~~~~~~~~~~~]Which I'm familiar with because I've seen this...
This topic first appeared in the Spiceworks Community

Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

Windows ADK and MDT 2013 components

Hi
I noticed that Windows ADK is
installed in its 32 bit version even though I have
Windows 8.1 Update 64 bit.
It is correct?
Then, I installed MDT 2013
64 bit.
Now, where can I find a detailed description
about the components of this MDT?
Having to customize, deploy and create some
DVDs of Windows 8.1 Update
32/64 bit, what components
should I download?
Thanks
Bye
Balubeto

Yes, there are some weird historical reasons why the AIK goes to "\Program Files (x86)" and MDT goes to "\Program Files". Don't over think it too much, yes it's confusing.
Some recommendations (what I install on my machine):
Your deployment Server box should be running Windows Server 2008 R2 x64 or Server 2012 x64.
You should be deploying only Windows 7 or newer (Windows 8.1) or Server 2008 R2 or newer (2012)
Use the latest AIK
http://www.microsoft.com/en-us/download/details.aspx?id=39982 the ADK is platform agnostic, it will install on x86 or x64, but of course your server should only be x64
Install the latest MDT 2013
http://www.microsoft.com/en-us/download/details.aspx?id=40796 x64 version.
MDT documentation *.chm is in the MDT install directory.
AIK documentation *.chm is in the ADK install directories.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2012 - Windows ADK Issue

Similar Messages

Maybe you are looking for