anyweb

excellent post Marcus thanks for sharing

When using the Use Toolkit Package task in a Configuration Manager 2007 task sequence, the Microsoft Deployment Toolkit 2010 Update 1 files package specified in the Use Toolkit Package task may not download correctly when the Distribution Point is on a Windows Server 2008 or newer server. The behavior will be different depending on the download method chosen under the Distribution Points tab in the properties of the advertisement: Download content locally when needed by running task sequence When the Task Sequence reaches the Use Toolkit Package task, the files for the package specified in the Use Toolkit Package will start to download and the progress bar will reach about 27%. The download will then all of a sudden stop, restart from the beginning, only to reach 27% again, and then restart again. On the third attempt it will the progress bar will get past 27% and finish downloading successfully. Reviewing the SMSTS.log on the client PC will show the following error: Downloaded file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe InstallSoftware dwStatusCode>=200 && dwStatusCode<=299, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1090) InstallSoftware WinHttpQueryHeaders() returns status code 404 (Not Found) InstallSoftware Download() failed with 0x80004005 InstallSoftware DownloadFile(sSourceFile, sDestinationFile, ulTotalSizeRequired, ulDownLoaded), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1175) InstallSoftware Error downloading file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe.config to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe.config InstallSoftware DownloadFiles(sSource, setDirs, setFiles, sDestination), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2434) InstallSoftware Retrying download... InstallSoftware The above error will be displayed a second time, followed by the following line after the second failure: Tried all the available http based locations. SMB based locations will be attempted now. InstallSoftware After the second error and the above message, the download will be tried a third time and will then succeed. Examining the IIS logs on the distribution point server will reveal the following error: <GMT_Date> <GMT_Time> <DP_Server_IP> GET /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> SMS+TS 404 7 64 15 Download all contents locally before starting task sequence When the advertisement is initiated either manually via the Run Advertised Programs control panel or automatically via a mandatory assignment, the download for the packages of the Task Sequence begins but never completes. Because the download for the Task Sequence packages never completes, the Task Sequence never begins or launches and the SMSTS.log is never created on the client PC. Reviewing client logs associated with downloading packages and executing the Task Sequence (execmgr.log, CAS.log, DataTransferService.log, ContentTransferManager.log) will not contain any errors. The client logs indicate that the downloads for the packages have begun, but the downloads never complete. Some of the client logs may have messages indicating that the downloads are in a pending or waiting state such as: DataTransferService.log Execute called for DTS job '{GUID}'. Current state: 'PendingDownload'. execmgr.log Execution Request for package <Task_Sequence_ID> program * state change from WaitingDependency to WaitingContent execmgr Persisting task sequence request for program * package <Task_Sequence_ID> in state WaitingContent execmgr If the advertisement for the Task Sequence was initiated manually via the Run Advertised Programs control panel, the Program Download Status window will show a progress bar that initially shows progress, but eventually stops and does not complete. The percentage complete will fail at a randomly different point each time the download is attempted. Examining the IIS logs on the distribution point server will reveal the following error: <GMT_Date> <GMT_Time> <DP_Server_IP> HEAD /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> Microsoft+BITS/7.5 404 7 0 218 Running Bitsadmin.exe on the client PC with the following command line: bitsadmin.exe /list /allusers /verbose while the download is in the hung state will reveal the following error: ERROR FILE: http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>$/<Pacakge_ID>/Tools/OSDResults/OSDResults.exe.config -> C:\Windows\system32\CCM\Cache\<Pacakage_ID>.<Source_Version>.<GUID>\Tools/OSDResults/OSDResults.exe.config ERROR CODE: 0x80190194 - HTTP status 404: The requested URL does not exist on the server.ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed. Access content directly from a distribution point when needed by the running task sequence No download issues are experienced when the advertisement for the Task Sequence is set to run from the distribution point (DP). Cause This issue is caused by the default configuration of IIS in Windows Server 2008 blocking the ability to download files that end in the extension .config. The Microsoft Deployment Toolkit 2010 Update 1 files package created by the Create Microsoft Deployment Task Sequence wizard and used in the Use Toolkit Package contains a file that ends in .config. The file is called OSDResults.exe.config and is located in the Tools\OSDResults directory of the package source files. When the option "Download content locally when needed by running task sequence" or "Download all contents locally before starting task sequence" is set on the advertisement for the Task Sequence, this will cause the file OSDResults.exe.config to be attempted to be downloaded via HTTP/HTTPS/BITS. However IIS will block this attempt since files ending in .config are blocked. When using the option "Download content locally when needed by running task sequence", it will attempt the download two times using HTTP/HTTPS/BITS before failing over to SMB. Since SMB does not use IIS, the third download attempt will then succeed. When using the option "Download all contents locally before starting task sequence", the BITS job gets hung on the error of not being able to download OSDResults.exe.config and does not fail over to SMB. This causes the whole download job to get in a hung state. Since the download for the packages of the Task Sequence never complete due to the hung state, the Task Sequence never launches. When the option "Access content directly from a distribution point when needed by the running task sequence" is used, HTTP/HTTPS/BITS is not used and all data transfers use SMB instead. Because SMB does not utilize IIS, the data transfers will succeed. Resolution To resolve the problem, follow the section "Configure the requestFiltering section on distribution points" in the following article: How to Configure Windows Server 2008 for Site Systems http://technet.microsoft.com/en-us/library/cc431377.aspx Specifically, on the Distribution Point server, configure IIS to allow files that contain the .config extension to be downloaded. This is done by changing the following line in the <requestFiltering> section of the applicationHost.config file from: <add fileExtension=".config" allowed="false" /> to <add fileExtension=".config" allowed="true" /> ===== The information above was published today in the following Microsoft Knowledge Base article written by Frank Rojas: via > http://blogs.technet.com/b/configurationmgr/archive/2011/02/23/configmgr-2007-quick-fix-a-package-specified-in-the-use-toolkit-package-mdt-task-does-not-download-correctly.aspx

i include it because my hta has scripts that depend on some of the other scripts within the scripts sub directory of the toolkit package, and because it's an easy way of doing it

does %SYSTEMDRIVE%\ = x: ? or c:\ have you checked ? by attaching the hta to the toolkit package i know that my hta plus the scripts it has will always be available when i have the mdt scripts available (which is what the use toolkit package step does), it downloads the content (the files/scripts) and sets some variables (path etc) I will do a webcast on this soon to clarify the steps involved

good stuff i look forward to our next session

have you copied the hta file itself into that path ? via the extrafiles method ? otherwise how can mshta.exe find the file ? sounds to me like mshta.exe is indeed running, but displaying nothing as it doesnt know where the hta file is you see, i refer to my hta file by adding it in the Use Toolkit package step

good points all round Marcus, i'll make sure my post links to this

and what's in your Start HTA step ? i see you are not using the mdt toolkit so how are you specifying the path to the actual hta file ?

where in the ts is it ? can we see a screenshot of the step in the ts

i guess the 64 bit version requires more ram, amazing but true interesting info Marcus how the testing going ? (contact me via mail about that)

are you trying to launch the HTA in winPE or in Windows ?

yup, and the moral of the story is if you are using language packs, add lots of ram, i found 1gb works but that was with virtual machines was this a vm or real hardware Marcus ?

Jason (ConfigMgr MVP) has very kindly put together a list of hotfixes for SCCM 2007 sp2, http://myitforum.com/cs2/blogs/jsandys/archive/2011/02/20/configmgr-2007-post-sp2-hotfixes.aspx and here's another one from another ConfigMgr MVP, Raphael - http://blog.dotnetwork.com.br/?page_id=2204 cheers niall

nice list of hotfixes required if you are installing SCOM 2007 http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx cheers niall

if you use R2 or R3 it will give you the unknown computers collection, you can advertise task sequences to that and when you boot an unknown pc it will see the task sequence, does that help ?

thanks for the kind words Paul, we do our best to help cheers niall

installing the language pack online takes place AFTER logging in for the first time and can only be done using Administrative permission, downside of this is that a gui pops up installing the language pack after the user logs on, and takes many minutes before completion, far better (in my opinion) to install the LP during the os installation, so that when the user does get to login that nothing delays their ability to use the computer straight away, here's a snippet from the MDT documentation If you want to install language packs online, you can use the MDT step in your task sequence or indeed add the Language specific code in your unattend.xml by clicking on Insert, choose Pass 7 oobeSystem And paste the following line in Lpksetup.exe /I %OSDUILanguage% /r /p C:\LangPacks\x86\%OSDUILanguage%\ The Lpksetup tool does not process language packs in any configuration pass other than auditUser and oobeSystem. After the installation of Windows 7 (right at the end after you login for the first time…) You’ll see – (if deploying Language Pack online and if you login as an administrator) long story short the following will end up in your unattend.xml if doing an language pack ONLINE installation cheers niall

yes you can right click on the task sequence and choose create standalone media and make usb or dvd/cd media

good point, we will try as much as possible to do this in the future !

you'd have to combine the logic of all three task sequences into one ts, and give the technician some choices in the beginning in order to start the right one, that can be achieved via MDT 2010 Update 1 udi or a front end HTA the task sequence will then have groups inside it to detect what variable you set via the choices in your front end and take appropriate action cheers niall

thanks for sharing

Some of you probably noticed a new download showed up today: The Windows® Automated Installation Kit (AIK) for Windows® 7 SP1 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=696dd665-9f76-4177-a811-39c26d3b3b34 Be sure to read the “readme” that goes along with this at: Windows Automated Installation Kit for Windows 7 Readme http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx A quick Q&A that I assembled from information in this readme and our own MDT testing: Q: Do I have to use this to deploy Windows 7 SP1 and Windows Server 2008 SP1? This supplement is optional. If you do not need to modify the SP1 boot.wim and winre.wim files, you can continue to use the Windows 7 RTM tools, including WinPE 3.0, without installing this supplement. (So MDT and ConfigMgr can deploy WIndows 7 SP1 just fine using Windows PE 3.0.) Q: How do I install this on a machine currently running the Windows 7 RTM version of Window AIK? There’s no installer provided with this. You need to extract the contents of the download and then XCOPY the files over the top of your existing Windows AIK installation. See the details in the readme. Q: What’s changed in this Windows AIK supplement? * The number in the Version registry value is 3.1 to reflect the new Windows PE version. * The Windows PE 3.1 base image contains Remote Network Driver Interface Specification (RNDIS) binaries. These binaries are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 979265 (http://go.microsoft.com/fwlink/?LinkId=206678). * Windows PE 3.1 includes 802.1x binaries as an optional component. The file name of this package is WinPE-Dot3Svc.cab. This optional component is also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID 972831(http://go.microsoft.com/fwlink/?LinkId=206072). * The Windows PE 3.1 base image contains fixes that are related to 4k/512e drive support. These fixes are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 982018 (http://go.microsoft.com/fwlink/?LinkId=206679). * Windows PE 3.1 includes bug fixes that are related to the Windows PE version that is included with Windows 7 SP1. Q: Does Windows 7 SP1 and Windows PE 3.1 work with MDT 2010 Update 1? Yes, this is fully supported. (There is one small issue involving Windows 7 SP1, Windows PE 3.1, and having Windows RE included in your MDT-generated Lite Touch boot images, but if you don’t mind Windows RE not being there, you don’t need to worry about this.) Q: Does Configuration Manager 2007 SP2 support Windows 7 SP1 and Windows PE 3.1? The Configuration Manager team is still testing Windows 7 SP1 and Windows PE 3.1, so this is unsupported until that testing is completed. Q: Does this supplement include the recently-released USMT 4 update for Office 2010 support? No, you need to download and apply that one (http://blogs.technet.com/b/mniehaus/archive/2011/02/02/usmt-4-0-support-for-office-2010.aspx) separately. via > http://blogs.technet.com/b/mniehaus/archive/2011/02/17/windows-aik-for-windows-7-sp1-released.aspx

I would agree with Peter and Lucid, do Build and Capture from virtual machines, keep the image hardware agnostic, add all your drivers to the deploy task sequence based on wmi queries, much cleaner and less hassle that said, you could try bios updates and/or newer video drivers from the video card manufacturer..

it will get automatically deleted by default in 7 days, you can change that in Site Maintenance, Tasks, Delete Obsolete Client Discovery Data

hi did you create a Computer Association between source and destination pc's before capturing the data ?