Peter33

Well, seems like rocket man is right and the problem breaks down to the ethernet driver, but in a different way. Which chipset does the NIC have, broadcom or intel? And did you try the drivers of the NIC manufacturer? Good luck and happy weekend

In your first post you had the lines included for the file which was causing the trouble. <![LOG[ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 44% of file C:\_SMSTaskSequence\Packages\COL0000C\boot/bcd]LOG]!><time="14:55:11.157-120" date="09-11-2012" component="ApplyOperatingSystem" context="" type="3" thread="1100" file="downloadcontent.cpp:1037"> Check the IIS log for the file BCD and make sure that the status code at the end of the line is like "200 0 0 xx". Anything like 401 or 404 would be bad.

Can you check the IIS log (C:\inetpub\logs\LogFiles\W3SVC1) for the BCD file? And are you sure that the error is caused by the same file (missing the important lines there)?

Hi Wolfgang, you don't need to reinstall SCCM. Just go to your Software library and delete theOperating System installer for the OS you tried to build and capture in your TS. Then recreate and redistribute it. The log you posted up there is telling you the file name failed with 0x80072ee2 when downloading 44% of file C:\_SMSTaskSequence\Packages\COL0000C\boot/bcd I would recommend you to get a new ISO of your Windows installation source, extract that and use it as source for your package.

Hi Wolfgang, this is not a problem with the driver. Seems your package is damaged or even your package source. <![LOG[Error downloading file from http://SCCM.ck.lab.l.../sccm?/boot/bcd to C:\_SMSTaskSequence\Packages\COL0000C\boot/bcd ]LOG]!><time="14:55:11.157-120" date="09-11-2012" component="ApplyOperatingSystem" context="" type="3" thread="1100" file="downloadcontent.cpp:1596"> Other files can be downloaded without a problem. <![LOG[Downloaded file from http://SCCM.ck.lab.l...cm?/autorun.inf to C:\_SMSTaskSequence\Packages\COL0000C\autorun.inf ]LOG]!><time="14:54:07.758-120" date="09-11-2012" component="ApplyOperatingSystem" context="" type="1" thread="1100" file="downloadcontent.cpp:1598"> Here is the key problem. This file looks damaged. <![LOG[ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 44% of file C:\_SMSTaskSequence\Packages\COL0000C\boot/bcd]LOG]!><time="14:55:11.157-120" date="09-11-2012" component="ApplyOperatingSystem" context="" type="3" thread="1100" file="downloadcontent.cpp:1037"> I would completely recreate this installation source.

Nope, offline servicing only supports the original Windows components. So the OS itself, IE8 and .NET 3.5. For everything else you need an additional update step in your task sequence.

Actually you don't need the roles in your case, because you can define everything in the details section of your Locations rule. In you customsettings.ini you have to make sure to add the Locations Database connection settings and set the priority of Locations higher than the default. The property you are looking for is named JoinDomain and not ServerA.

If you use MDT and run 'use toolkit package' followed by the 'gather' step, you can use the variable DefaultGateway001. You can also apply the proper OU in your customsettings.ini this way, by setting the variable OSDOUName. This way you save a lot of TS steps. Another benefit is that you can test it without starting the Imaging sequence on any computer. Just run the ZTIGather.wsf from the command line.

The easiest way is probably to use the deafult gateway value of the network adapter configuration. A class c network would give you 253 clients. You can also use the system OUs of your AD.

All these settings are user settings and can be applied to the default user profile before the capture of the base image during the sysprep phase. MDT 2010/2012 is the key here. Before capturing restart your computer with sysprep.exe to "Audit" mode. Then apply all the settings to the local Administrator account. You need a unattended.xml file with the copy profile set to true in the specialize section. Copy this file to c:\windows\system32\sysprep and then open a cmd. Change the directory to c:\windows\system32\sysprep and launch the sysprep.exe with "/oobe /generalize /restart /unattend:unattend.xml" as argument. After the restart login as administrator again and capture the machine by calling the litetouch.wsf from your MDT script share.

You can also extract the zip files with a short powershell script. $Path = Split-Path $script:MyInvocation.MyCommand.Path Set-Location $Path $unzipPath = "C:\Program Files" $zipFile = Join-Path -Path $Path -ChildPath "your.zip" $shell = New-Object –ComObject Shell.Application $zip = $shell.Namespace($zipFile) $dest = $shell.Namespace($unzipPath) $dest.CopyHere($zip.items(),0x14)

Are you sure that your Network Access Account has the permission to read from the share?

Hi japijap, no, the name from you csv file will not be used during the OSD. You can either script this and read the name from the file, or use the MDT database to apply the name (if you have MDT integrated).

How do you assign the computer name in your task sequence? During OSD the computer name is not being set to the value you have assigned by importing into SCCM. If you want to go this way and use predefined values for the name, you should use the MDT database and define the computer name there in the field for OSDComputerName.

If you want to use the application model, you need to create a script wrapper (vbscript or powershell) which starts the install.exe and returns the exit code. Then you can create a custom app using this script.

Did you read this before? Check out the prerequisites for site system roles section, and make sure you got all needed IIS roles installed. "3 In some scenarios, such as when IIS is installed or reconfigured after the .NET Framework version 4.0 is installed, you must explicitly enable ASP.NET version 4.0. For example, on a 64-bit computer that runs the .NET Framework version 4.0.30319, run the following command: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i –enable"

When did you deploy the Reader to your machines? The SCCM Inventory gets updates according to the Hardware Inventory cycle of your clients. So it may take a while to see some results. The standard value is 7 days. Anyways, the query in your collection could also be wrong.

You can't apply the variable directly to the unattended xml, because your newly installed OS does'nt know these variables. Just let MDT do the work for you and apply the settings by the configure step.

Make sure that your router supports the PXE protocol. You can still disable DHCP on the router and enable the DHCP on the SCCM server.

Hi Hans, Orca is a nice little tool, but very basic. You can only edit the msi tables with it. There is no workflow for adding files, registry entries, shortcuts .... etc. For the long run you should look out for some more advanced packaging tool. (Admin Studio, Package Studio) There is also a free SCCM Edition of Admin Studio.

For updating of already deployed installations, you would actually only need a single step in your task sequence. First create a package with the update and a program to install the update. Then create your task sequence and add a "install software" step. Chose your update package as source. In the options tab of this step add a "WMI query" which defines when this step is going to be executed. Here you could actually query 4 different WMI classes. I prefer the SMS_InstalledSoftware class in the Namespace root\cimv2\sms , because the other 3 have some disadvantages. The query would look like this: SELECT * From SMS_InstalledSoftware WHERE ProductCode = '{productcode}' AND ProductVersion != 'productversion' ... where the productversion has to be the version of your patch. Regarding the license file question. Just put the license file in the source folder of your package. The create a new program in your package to copy the file using the xcopy command. xcopy ".\filename" "DSTINATIONPATH" /y /s In the advanced tab chose to run another program first and pick your install program from the package. Also tick the "always run first" checkbox. Then advertise the copy command instead of the install command.

Well, since you have MDT 2012 already installed you are ready to go. Make sure you have checked the "use unattended sysprep answer .." step in the apply OS step. Also make sure the unattended.xml is valid for your system architecture (x86, x64) Edit your personal customsettings.ini in the settings package of MDT and add these variables. OSDSystemLocale="en-GB" OSDInputLocale="en-GB" OSDUserLocale="en-GB" OSDUILanguage="en-US" OSDUILanguageFallback="en-US" Assuming you have created a MDT2012 client task sequence,activate the "process local data and process rules" option in your "gather" steps. Chose the cusomsettings.ini from your settimgs package. You should also have already an "configure" step in your task sequence, which will actually modify the unattended.xml and apply you language settings.

Add "pushd %~dp0" as first line to your batch file and "popd" as last line. Otherwise your source files won't be found. Should fix your problems. Also make sure that unopkg delivers a 0 as return code for success. Best solution would be though to apply your customizations into a transforms file. This way you don't need a batch at all.

Well, there are always multiple approaches possible. 1) create a new package for the update containg the msp file and a script wrapper. The script performs a wmi query to check if the base package is installed and if the latest patch is already applied. Then it conditionally launches the install. You can do the same via a task seqence if you are not into scripting. 2) You can create a transforms file and add the license file dircet to the installer package, but only if it is an MSI installer. You need a packaging program for this though. You could also use a script wrapper which performs the install and copies the license file to the destination, if the installation has been successful. ... or, you can create a task sequence which performs the installation a sfirst step and copies the files as second step.

Unfortunately you need all the extracted files, even the eula.txt and the bitmap files . Just by the way, for anyone who is using VSTOR3, you also need the Service Pack 1 for VSTOR3.