Configuration Manager Operating System Deployment Forum

USMT in SCCM State Store path Error

Thu, 26 Nov 2009 05:39:35 Z

Hi,

I am trying to migrate from Windows XP to Windows 7 using SCCM 2007.

My SCCM is ready with SP2, MDT 2010,WAIK and USMT 4.0

I use the below steps in the task sequence to capture user state to the SMP

Request State Store
Capture(Run Command Line)
Release State Store

the command line is as below.

x86\scanstate.exe /o /i:MigApp.xml /i:MigUser.xml /config:config.xml /v:13 /l:d:\scanstate.log /localonly /ue:*\* /ui:systems\* /uel:0

but it fails with the below error in the log file d:\scanstate.log.

2009-11-26 08:31:40, Info                  [0x000000] USMT Started at 2009/11/26:08:31:40.212
2009-11-26 08:31:40, Info                  [0x000000] Command line: <servername>\SMSPKGC$\101000D3\x86\scanstate.exe /o /i:MigApp.xml /i:MigUser.xml /config:config.xml /v:13 /l:d:\scanstate.log /localonly /ue:*\* /ui:<domain>\* /uel:0
2009-11-26 08:31:40, Status                [0x000000] Activity: 'MIGACTIVITY_COMMAND_LINE_PROCESSING'
2009-11-26 08:31:40, Info                  [0x000000] Failed.[gle=0x00000006]
2009-11-26 08:31:40, Info                  [0x000000]   An error occurred processing the command line.
The store parameter is required but not specified[gle=0x00000006]
2009-11-26 08:31:40, Info                  [0x000000] USMT Completed at 2009/11/26:08:31:40.228[gle=0x00000006]
2009-11-26 08:31:40, Info                  [0x000000] Entering MigShutdown method
2009-11-26 08:31:40, Info                  [0x000000] Leaving MigShutdown method

no other log files are there in ccm\logs. i checked the smsts.log. but it says nothing useful.

Any idea why it fails?

Tx
Peer

Importing Win 7 Drivers - .inf files

Tue, 03 Nov 2009 09:26:46 Z

Is anyone having any problems importing Windows 7 drivers into ConfigMgr Sp2? I have download a number of Windows 7 drivers from Dell and Lenovo and SCCM SP2 (RC) reports that the driver does not contain any supported platforms. Checking the .inf files shows that the Windows version is specified as NTx86.6.1.1. Other Win 7 drivers that are importing OK specify version NTx86.6.1.

I am not running SP2 RTM just yet so I am not sure if this is a ConfigMgr SP2 RC issue or whether incorrect version information has been put into the INF files. Most of the incorrect ones seem to be Intel drivers.

Is anyone else having similar problems?

Thanks.

"The selected driver is not applicable to any supported platforms" issue still occur on SCCM SP2+R2 for Win7 Drivers

Mon, 16 Nov 2009 10:26:02 Z

Hi there,

when I try to import some Win7 Drivers into SCCM SP2+R2, I still get the following error message:

"The selected driver is not applicable to any supported platforms"

I heard it was fixed in SP2? any idea?

problematic Driver example: Dell NIC driver for Intel 825xx 10.0.6.0 - R235484

Blue screen because of AHCI drivers when running sysprep to prepare OS

Fri, 11 Sep 2009 15:47:00 Z

I'm having a problem capturing my source computer which uses the Intel(R) ICH9M-E/M SATA AHCI Controller. I'm able to install my scratch OS fine because I'm inserting a step "Apply device drivers" and manually specifying the Intel(R) ICH9M-E/M SATA AHCI Controller driver. However, once I'm finished building my image the "prepare OS" step of my task sequence runs the sysprep command. In turn this uninstalls my driver and I'm back at the bluescreen.

Here are some things that I've already tried:

1. Tried adding the following lines to sysprep.inf and copying the driver to c:\drivers\msd\imv89\
[Sysprep]
BuildMassStorageSection=No
[SysprepMassStorage]
PCI\VEN_8086&DEV_2929&CC_0106=C:\Drivers\MSD\IMv89\iaAHCI.inf ; Intel(R) ICH9M-E/M SATA AHCI Controller

2. Tried adding the checkbox on the capture task sequence under "Prepare OS" step that says "Automatically build mass storage driver list"

3. After capturing the image in which I knew would bluescreen if deployed I tried creating a new task sequence to inject the drivers. I believe this is failing because the sysprep portion of unrolling occurs after the apply device drivers, which I do not think I can change. Here are my steps
a. Restart in PE
b. Partition Disk 0
c. Apply operating system(using the image that bluescreens)
d. Apply windows settings
e. Apply network settings
f. Apply device drivers(this step scans the machine for compatible drivers)
g. Apply driver package(this step specifically tells it to use the Intel(R) ICH9M-E/M SATA AHCI Controller driver. This is what I had to do to originally get my OS to load.
h. Setup Windows and configmgr
i. Install software(Office etc., this step is not really relevant)
j. Restart computer
k. Install software updates
l. Refresh group policy

Hopefully someone has run into this before and can point me in the right direction. Thanks in advance.

Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

SCCM 2007 R2 with Integration of MDT 2010 for deploying a custom WIM of Windows XP SP3

Wed, 25 Nov 2009 21:07:49 Z

Hi,

I have a custom Windows XP WIM image that I use to deploy with MDT 2008. I import this WIM image on the SCCM R2 SP2 with MDT2010 integration.

When I advertise my task sequence to deploy this image, the format and the copy of image file work, but the computer stay and the screen Wizard Assistant of Windows Xp installation. I need to conitnue manually and accept the eula, the licence key....

What can I do to deploy this image silently. With MDT 2008, the sysprep.inf file is created a copied automatically on the computer to silently install the custom image. What is different with OSD with MDT 2010 integration ?

Thanks,

Steve

Steve

OSD Problems with a client with Bit Locker enabled

Tue, 24 Nov 2009 04:57:34 Z

Hi:
We have SCCM 2007 SP2 R2 in a box with W2008 R2 x64. Native Mode.
I have a TS that works well in replace and bare metal pxe scenaries.
Now, I have a sccm client that has bit locker enabled (TPM+PIN, recovery key on ADDS). When I advertised the TS to replace the OS, the TS was returning this error just before restart to boot on WINPE with my boot image:

"<![LOG[Deleting a pause cookie from registry key HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent]LOG]!><time="14:37:07.789+000" date="11-23-2009" component="TSManager" context="" type="1" thread="692" file="utils.cpp:2778">
<![LOG[kTaskSequence.DeleteValue(sComponent.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,2782)]LOG]!><time="14:37:07.789+000" date="11-23-2009" component="TSManager" context="" type="0" thread="692" file="utils.cpp:2782">
<![LOG[Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent. Error code 0x80070002]LOG]!><time="14:37:07.789+000" date="11-23-2009" component="TSManager" context="" type="2" thread="692" file="utils.cpp:2782">
<![LOG[Opening the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence]LOG]!><time="14:37:07.789+000" date="11-23-2009" component="TSManager" context="" type="1" thread="692" file="utils.cpp:2920">
<![LOG[Deleting the access handle from registry key HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle]LOG]!><time="14:37:07.789+000" date="11-23-2009" component="TSManager" context="" type="1" thread="692" file="utils.cpp:2926">
<![LOG[Stopping Task Sequence Manager service]LOG]!><time="14:37:08.148+000" date="11-23-2009" component="TSManager" context="" type="1" thread="692" file="tsmanager.cpp:487">"

As a work around, I configured Bit Locker with Suspend Protection. Now, the client can boot in WINPE but when the TS is going to format and partition the disk, this error appears:

"The task sequence execution engine failed executing the action (Partition Disk) in the group (Install Operating System) with the error code 2148270085
Action output: ss paths
Found a VDS pack
Querying for IVdsPack
Querying for volumes
Found a VDS volume
Querying for IVdsVolumeMF
Querying for access paths
Found a volume with access path 'D:\'
Querying for IVdsVolume
Querying for IVdsVolumeMF
Checking volume 'E:' for BitLocker
Checking volume 'X:' for BitLocker
Command line for extension .exe is "%1" %*
Set command line: "X:\windows\system32\diskpart.exe" /s "X:\windows\TEMP\osddiskpart.txt"
Executing command line: "X:\windows\system32\diskpart.exe" /s "X:\windows\TEMP\osddiskpart.txt"
Process completed with exit code 2148007941
0, HRESULT=800c0005 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,1456)
diskpart script: ?????????????????????????????????
Diskpart.exe STDOUT:
Microsoft DiskPart version 6.1.7600
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: MININT-ARRQLNF
Diskpart.exe STDERR:
Diskpart.exe failed (2148007941). Script file, stdout, and stderr saved in TS log directory.
OSDDiskPart.exe failed: 0x800c0005."

And in adittion:

"The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned."

I have doubts about OSD with a client with Bit Locker enabled. And I can't find an answer to these errors.

Do you know what I can do to fix my issue?
Is it supported what I'm trying to do?

Thanks in advance for your answers.
Best Regards,

Windows 7 deployment using sccm 2007 R2 SP2

Wed, 25 Nov 2009 17:36:23 Z

Previously we have deployed XP with Zero Touch Imaging in the following way:

created a boot image, I'm not sure of the version of PE but in launches like vista.
Created a flat OS image from the install.wim off the installation media.
Created a task sequence, containing product key, domain to join, local admin password etc. plus extra packaged applications, such as MS Office. We then add necessary drivers for various builds of PC to the driver catalogue. With this method we are able to deploy XP using just the one image, adding necessary drivers as needed.

Is it possible to do the same for windows 7 ?
I've done the same as above but using the windows 7 install.wim & advertised it to a test PC. The 1st portion of the task sequence runs without any errors, PE launches & the drive is formatted & the image file downloaded. However after the 1st reboot, I just get the error "Windows failed to start, A recent harware or software change might be the cause. Error 0xc0000001"

Does anyone have any ideas where I am going wrong or indeed is it possible to deploy windows 7 the same way as XP.

Thanks
Kathryn

Windows XP crash when deploying WIM on a different type of computer

Mon, 23 Nov 2009 23:36:24 Z

This issue has been causing me a lot of grief. I've built and captured an XP SP3 image as a wim file on a certain computer. When I then create the task sequence to deploy it, I can get it to deploy successfully on a computer that is the exact same model. However, if I deploy it to any other different models, it goes through the TS, applying the OS image, applying the Windows settings, applying drivers and then installing the CM client where it downloads the files and then in a few seconds reboots the computer (the first reboot). As Windows comes back up within 1 or two seconds is crashes, maybe a blue screen, I can't tell, because it only displays for half a second or less and then the computer reboots again and this time comes up with the "Windows failed to start successfully, do you want to start in safe mode, etc.". If I try any of the options, it loads a couple seconds then instantly reboots without warning.

By pulling the HDDs and looking on another computer I've retrieved and looked at the logs I know about, smsts.log, ccmsetup.log etc, but nothing appears amiss. These other computers, which are known good computers and can load Windows successfully either as a standard install from a disk or as a Build and Capture machine don't appear to have any hardware problems. Where should I look to troubleshoot what is happening?

I tried disabling the Setup Windows and Config Mgr step, computer still crashed on reboot. Disabled the Apply Drivers, it still crashed. The only driver I installed when I captured the image was the Network driver.

Any log files that would be helpful to post, let me known and I can put them up.

SCCM 2007 - PXE Booting

Wed, 25 Nov 2009 19:01:07 Z

Hello,

I have seen many posts on SCCM and PXE, but have not seen any specific answers to how this is handled.

Current setup:
We are running SCCM 2007 SP1 (planning to go to R2 and SP2 soon). Currently we boot off CD/USB into PE. From there we have an HTA page that allows us to customize the task sequence with variables, and then it kicks off our Vista install TS. We are looking to use PXE, and eliminate the need for actual boot media. I have PXE working as intended, but I have two questions regarding this.

1. I have two "optional" advertisements for Task Sequences assigned to the machine we are testing PXE on. Each TS calls a specific PE boot image. PXE works, but it only pulls down one of the boot images, and never gives me an option of with PE image to pull down. The reason for this is that two different groups manage different images, and both want to use PXE. I'm not sure how it's automatically choosing which boot image to use, but want it to prompt.

2. From PXE, once an unknown machine gets added to the unkown collection, can it determine the local distribution point to pull down that PE boot image? I would not not a remote site that has a local DP to come all the way back to the Primary site to grab it's image, since it is 150MB, and that could take forever, negating the advantage of PXE vs. media boot.

If anyone has any answers to this or if they know of a different post that explains it, I'd appreciate the help.

SMP question

Wed, 25 Nov 2009 19:45:24 Z

When I use a regular TS that has capture state, deploy OS and restore TS, the TS fails at the very first step with these errors:

unknown host (gethostbyname failed)
sending with winhttp failed; 80072ee7
Failed to send root share info request to SMP. Code 0x80072EE7
ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80072EE7).
ClientRequestToSMP::DoRequest failed. error = (0x80072EE7).
Request to SMP 'servername' failed with error (Code 0x80072ee7). Trying next SMP.
Failed to find an SMP that can serve request after trying 4 attempts.
ExecuteCaptureRequestSMP failed (0x80004005).
Failed to run the action: Request State Store.
Unknown error (Error: 00004005; Source: Unknown)

When I remove everything else from the TS and only keep the capture user state and restore user state steps, the TS succeeds without any errors. I dont know what to conclude from this.

Mayur

PXE Booting Question

Wed, 25 Nov 2009 18:17:25 Z

Hi everyone, I was able to get PXE booting and imaging working from docs and these forums (thanks everyone), however I have a question regarding how things work with PXE.

First, here is our configuration. We have two network vlans, the server and the workstation vlans. We have our SCCM and WDS server (SCCM1) on the server vlan. We have a separate DHCP server (DHCP1) also on the server vlan. We have the ip helper pointed to DHCP1 so that clients on the workstation vlan know to look to the DHCP server for ip addresses.

So, according to the KB http://support.microsoft.com/kb/259670 we needed to add the WDS server ip address to the ip helper table as well. Now we have two ip addresses in ip helper. (DHCP1 and SCCM1) My understanding of how the ip helper works is that neither of the addresses will have a priority.

My question is this. When a machine initially boots up to the network, what is stopping the machine from looking to the SCCM1 server and failing to get an ip address from that server? I would assume that 50% of the time the machine would try our SCCM1 and fail.

Thanks for any info on this.
Mike

Client installation failed in OSD TS with error code 16389

Sun, 12 Oct 2008 06:55:53 Z

During OS Deployment TaskSequence some computers do not installing the SCCM client. When I look in to the advertisement status it shows the follwing errors.

The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group () with the error code 16389.

The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned.

Not all computer have this issue. But few failed with this error. Any idea about this error.

SMSTS.log file not big enough.

Tue, 19 Aug 2008 05:14:41 Z

I know I have seen other discussions about this topic before but can not find any reference to it.

Is there a way to extend the size of the SMSTS.log file?

Is it possible to stop it truncating to 2 files or is it possible to allow it to store more than 2 smsts.log files?

At the moment I have dozens of packages installing at build time and the SMSTS.log file fills up and renames itself to SMSTS.log and SMSTS-########-####.log, but even the archived log file does not go back far enough.

Can anyone provide a link to a solution or post an answer here?

WDS and PSP and PXEboot

Wed, 25 Nov 2009 17:00:56 Z

How can I verify that PSP configured WDS properly?
I installed WDS and did not configure it. I installed PSP on the same server with no errors.
I checked Services and WDS and TFTP is started.
Is there a way to tell that PSP did its job?

I am trying to pxeboot to image a machine and I get the PXE-E53: No Boot File Name Received.
SMSPXE.Log never reports the MAC ID I imported.

I have a Primary(SCCM 2007 SP2) and secondary site (DNS,DHCP,WDS,PSP Co-hosted)
Secondary Site is a DC with a static class C address Hosting DHCP Class A addresses
Primary Site is on a Static Class C address.
All Clients boot to a Class A address.

OS: Windows 2003 R2 SP2
SCCM 2007 SP2
SQL 2005 SP2

Boot Image Selection on a PXE Service Point with Multiple Boot Images

Wed, 22 Oct 2008 19:39:33 Z

I have a PSP (PXE Service Point) with 3 boot images. The normal SCCM x86 and 2 boot images created using the MDT Wizard. One MDT boot image support unknown computer and the other one does not.

When I initiate a PXE boot from an unknown computer, I want the MDT boot image with unknown computer support to take control and create the appropriate computer entry in SCCM before SCCM perform its correlation between the computer entry and the OSD advertisements.

Unfortunately, I have found no mechanism to select which boot image WDS will choose upon the first F12 key press. Is there a way to get prompted for the boot image to select on the initial PXE boot?

OS Deployment in Native mode - Client will not get his certificate

Wed, 25 Nov 2009 16:53:33 Z

Hello,

We are setting up a solution using the MDToolkit integration in SCCM 2007 R2 SP2 (native mode)
We are in the process of troubleshooting the MDT task sequence that creates a reference computer automatically by (VERY schematically):
1- Installing W7
2- Joining the machine to the domain
3- Installing Config Mgr client
4- Installing Updates
5- Installing SW
6- Finalizing and capturing the image

We are stuck just before step 4. It seems to me that the machine does not get the config mgr client certificate (though configured for autoenrollment and deployed for autroenrollment by gpo), hence does not speak to sccm server, does not install any updates or sw, and we end up with a perfectly virgin image.
What's anooying is that if we stop the task sequence before capture, then do a gpupdate /force, the certificate arrives, and the Config Mgr client is all happy. Only it's too late for the task sequence...

I've tried to add a GOUpdate /force by Command Line in the task sequence, but it does not work.
Has anyone encountered that kind of issue before ?

Thanks in advance for your help,
V.

Failed to open the Task Sequencing Environment. Code 0x80220005

Wed, 25 Nov 2009 12:54:01 Z

Hello All,

A problem has cropped up during my (previously working) OSDs.
The background: My Task Sequence has a couple of scripts (computer naming and OS and application installation options) and then, depending on the TSVariable supplied launches the OSD proper. I have three unattended answer files (Vista_x86.xml, Windows7_x86.xml and XP_x86.SIF) contained with a package. For each TS group I have Apply Operating system and then Apply Windows Settings. On the Apply Windows Settings I select the package and then enter the relevant answer file.

The problem : As I say, this has been working perfectly but now for Vista and Windows 7 i get the following TS failure:

2\SMI\Store\Machine Closing image file C:\_SMSTaskSequence\Packages\CNP0003A\sources\install.wim Setting hive location to "C:\_SMSTaskSequence\OSD\Vista\Windows\System32\SMI\Store\Machine" Loading existing answer file "C:\_SMSTaskSequence\unattend.xml"Getting namespace "Microsoft-Windows-Setup" for architecture "x86" Added list item with key value '/IMAGE/INDEX' Getting namespace "Microsoft-Windows-Deployment" for architecture "x86" Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "x86" Getting namespace "Microsoft-Windows-International-Core-WinPE" for architecture "x86" Writing configuration information to C:\_SMSTaskSequence\unattend.xml Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml Preparation completed sucessfully. Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\CNP0003A reference count 1 for the source C:\_SMSTaskSequence\Packages\CNP0003A before releasing Released the resolved source C:\_SMSTaskSequence\Packages\CNP0003A

interface.cpp,1126) m_pSMIInterface->setValue( SetupPassValue[eSetupPass], pszComponentName, pszPath, pszValue ), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,768) this->SetValue( Specialize, XML::Shell::ComponentName, XML::Shell::ComputerName::Element, pszComputerName ), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,884) m_pImpl->SetComputerNameW(pszComputerName), HRESULT=80220005 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,1780) pAnswerFile->SetComputerNameW(sValue), HRESULT=80220005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,376) ConfigureWinSettings(), HRESULT=80220005 (e:\nts_sms_fre\sms\client\osdeployment\osdwinsettings\osdwinsettings.cpp,637) Exiting with return code 0x80220005 Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence. Unknown error (Error: 80220005; Source: Unknown)

My Answer files for Vista and 7 are extremely simple, being fundamentally the same - change to UK locale:

<?xml version="1.0" encoding="utf-8" ?>
- <unattend xmlns="urn:schemas-microsoft-com:unattend">
- <settings pass="specialize">
- <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0809:00000809</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
</settings>
<cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

If I remove the answer file I have no problem in deploying... It WAS ok... Any ideas?

Thanks

Nickcx

SCCM2007 R2 SP2

Failed to make a copy of source WIM file due to error 5 - Custom boot.wim file stopped working after sp2 upgrade

Wed, 25 Nov 2009 11:00:41 Z

Hi!

After upgrading to SP2 our custom boot.wim file has stopped working. When you try to update the distribution point you get the following error:

Error: Boot image to update:
    Microsoft Windows Vista PE (x86)

   Error: Actions to perform:
    Add ConfigMgr binaries
    Enable Windows PE command line support
    Add drivers

   Error: Failed to import the following drivers:
    VMware Accelerated AMD PCNet Adapter
    VMware PCI Ethernet Adapter

   Error: The wizard detected the following problems when updating the boot image.
    The ConfigMgr Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    {
        Description = "Failed to make a copy of source WIM file due to error 5";
        ErrorCode = 5;
        File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
        Line = 4219;
        ObjectInfo = "CSspBootImagePackageInst::PreRefreshPkgSourceHook";
        Operation = "ExecMethod";
        ParameterInfo = "SMS_BootImagePackage.PackageID=\"DKV00058\"";
        ProviderName = "WinMgmt";
        StatusCode = 2147749889;

Any ideas on what this problem is about? I know that error 5 is access denied but the share right has not been changed and this wokred flawlessly before the upgrade.

Cannot create Stand Alone Task Sequence DVD

Tue, 24 Nov 2009 21:25:03 Z

Guys I am having an extremely strange issue on a customer site whereby when I try to create a Standalone Task Sequence DVD the list of Task sequences do not appear in the Standalone task sequence wizard. I have used this facility plenty of times before without issue but recently added updated software and wanted to recreate the Task sequence DVD deploying an OS to smaller sites in the hierarchy to preserve the network bandwidth at the customer site.

Baically the steps I run whilst logged on as a user that has full control over the entire SCCM environment are:

1. Right click Task Sequences under OS deployment and choose create Task Sequence Media
2. On the screen that appears I choose Standalone Task Sequence Media.
3. I set a name for the ISO image file.
4. I set a password to protect the DVD
5. I am then prompted to choose the task sequence, I choose browse and the screen appears to choose the Task sequence none of them appear, and I do have quite a few Task Sequences created.

Anyone got any ideas as to what might be going on here??

Failed to read PXE settings

Mon, 26 Oct 2009 17:33:04 Z

In the smspxe.log

"Failed to read PXE settings.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"

This starting appearing everytime the windows deployment service starts on this system after installing SP2. Prior to the upgrade it worked fine.

I did remove the PXE role and re-add which had no effect.
Any ideas?

OSD Task Sequence Fails on requesting state storage

Tue, 20 Oct 2009 17:55:59 Z

We did a side by side upgrade of our SMS 2003 environment last spring. All seemingly went well until lately. Over the past few months we have been testing OSD with SCCM. This worked flawlessly everytime...until we tried it on some clients that had been upgraded and moved over to the new site heirarchy. When the task sequence gets to the point of requesting state storage we received the following in the smsts.log:

<![LOG[Failed to import the client certificate store (0x80092024)]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="OSDSMPClient" context="" type="3" thread="5948" file="smpclient.cpp:880">
<![LOG[ClientRequestToMP::DoRequest failed (0x80092024).]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="OSDSMPClient" context="" type="3" thread="5948" file="smpclient.cpp:1160">
<![LOG[ExecuteCaptureRequestMP failed (0x80092024).]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="OSDSMPClient" context="" type="3" thread="5948" file="smpclient.cpp:2688">
<![LOG[ExecuteCaptureRequest failed (0x80092024).]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="OSDSMPClient" context="" type="3" thread="5948" file="smpclient.cpp:2762">
<![LOG[OSDSMPClient finished: 0x00002024]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="OSDSMPClient" context="" type="1" thread="5948" file="main.cpp:120">
<![LOG[Process completed with exit code 8228]LOG]!><time="09:44:38.471+240" date="10-15-2009" component="TSManager" context="" type="1" thread="4472" file="commandline.cpp:1102">

This seems to point to a certificate problem on those clients that were upgraded. I've tried to find a solution that will work on even one machine, let alone thousands. Has anyone else encountered this?

Thanks.

Is there no way to do a simple capture of a reference computer?

Mon, 16 Nov 2009 22:14:20 Z

Hello all,

I want to do a simple capture of an already configured reference computer. I do not want to do a build and capture and I do not want to have to use a CD on each machine I want to capture. Is there no way to simply config the reference computer, sysprep it then capture and save the .wim file to the server? This was such a simple task in WDS but now seems next to impossible in SCCM. I have tried using the Build and capture task removing everything but the capture step but it does not work. I have posted about this previously and tried all suggestions with no luck. This should be a very simple procedure. Can anyone point me it the right direction?

Thanks.

MDT 2010 - Install Roles and Features - File Server Greyed Out?

Tue, 24 Nov 2009 19:09:42 Z

Hi all - seems like the "Install File Server" role doesn't work in the integrated MDT steps on Server 2008 R2. Am I missing something? Here's an output from the advertisement.

The task sequence execution engine successfully completed the action (Installing File Server Roles...) in the group (File Server) with exit code 0

Action output: nd line: Run command line

Microsoft (R) Windows Script Host Version 5.8

Microsoft Deployment Toolkit version: 5.0.1641.0

The task sequencer log is located at C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.

No roles were requested.

Role services requested for installation:

FS-FileServer

FS-DFS-Namespace

FS-DFS-Replication

FS-Replication

FS-Indexing-Service

No features were requested.

Preparing to install roles for Windows Server 2008 using ServerManagerCmd

Saved role answer file to C:\Windows\TEMP\Roles.xml

About to execute command: C:\Windows\sysnative\ServerManagerCmd.exe -inputpath "C:\Windows\TEMP\Roles.xml" -LogPath C:\Windows\TEMP\ServerMgr.log

Process completed with exit code 0

ERROR - Role installation with ServerManagerCmd.exe failed, rc = 4

FAILURE: 4: Server 2008 R2 Role Installation

ZTIOSRole processing completed successfully.

Command line returned 0.

XP Sysprep Issues Capture TS

Tue, 24 Nov 2009 19:58:37 Z

I have been able to capture and sysprep images from windows 7 and vista fine, but with XP I get this error when using the same capture task sequence that works on other OS's.
The task sequence execution engine failed executing the action (Prepare OS) in the group (Capture the Reference Machine) with the error code 87
Action output: t
Initializing answer file "C:\sysprep\sysprep.inf"
Adding build mass storage drivers section to answer file successful
Unable to delete file C:\WINDOWS\temp\Perflib_Perfdata_550.dat (0x80070020). Continuing.
Unable to delete file C:\WINDOWS\temp\Perflib_Perfdata_66c.dat (0x80070020). Continuing.
Unable to delete file C:\WINDOWS\temp\WFV1.tmp (0x80070020). Continuing.
Failed to delete contents of directory 'C:\WINDOWS\temp', hr=80070020
Unable to delete file C:\WINDOWS\TEMP\Perflib_Perfdata_550.dat(0x80070020). Continuing.
Unable to delete file C:\WINDOWS\TEMP\Perflib_Perfdata_66c.dat (0x80070020). Continuing.
Unable to delete file C:\WINDOWS\TEMP\WFV1.tmp (0x80070020). Continuing.
Failed to delete contents of directory 'C:\WINDOWS\TEMP', hr=80070020
Administrator account name = 'Administrator'
ResetPassword operation successful
Exiting with error code 87
Failed to pre-stage WINPE image, hr=0x80070057
Unable to sysprep the machine, hr=80070057
Sysprep'ing the machine failed, hr=80070057. The operating system reported error 87: The parameter is incorrect.

What is the root of this problem? I have blanked the administrator PW and copied the necessary sysprep folder to c:\sysprep.

conditional statements on error

Tue, 24 Nov 2009 20:34:41 Z

I am trying to excute a backup plan, and I have the ztibackup.wsf script working beautifully. The only issue- I want to append if possible which can only be done one at a time.

If the .wim is in use when another computer tries to append to the file, it errors with error code 0x000000002. I want to be able to specify in my task sequence, IF ERROR = 0x000000002, THEN run ZTIbackup.wsf without specifying an image name so it will just make a new file.

Any ideas on how to add a conditional option step like this?

MDT Integration and ZTIbackup.wsf

Mon, 23 Nov 2009 16:58:18 Z

Does anyone have any instructions on how to implement and use the ztibackup.wsf script in a task sequence?

Thanks

UILanguage variable also sets System Locale in Windows 7 OS deployment with SCCM

Fri, 20 Nov 2009 17:23:56 Z

I'm using the UILanguage variable to set the display language during OS deployment and this works great. However, it's also setting the language for non-Unicode programs / System Locale. I want to have the default installation language set to english with a localized display language. The user can achieve this with logging in and changing the display language themselves - log off -> log on and have a localized display language while to installation language is english.

The image is english and without use of UILanguage it installs an english OS. Using just the UILanguage variable results in a "fully" localized OS. I've tried with SCCM and with MDT 2010.

Does anyone know if this is by design, or have a remedy for this ? Hopefully that someone have ;)

Import MDT Task Sequence Error - The ConfigMgr Provider Reported and Error -error

Thu, 14 Aug 2008 18:25:08 Z

Hi,

I'm working on importing a Microsoft Deployment Task Sequence.. After completing the wizard (after sysprep), it tries to go to summary but then displays an error on the screen:

Error while importing Microsoft Deployment Toolkit Task Sequence: Details: The ConfigMgr Provider reported an error.

Not sure what this means... anyone know?

Or where to look for more information?

Task Sequence for patching not available on client

Tue, 24 Nov 2009 15:29:01 Z

Hi,

I am using the Task Sequence in OSD to push out our Software Updates (with a number of pre and post patching tasks).

I have set up the TS and advertised it to a test collection that has one machine in it, but the advertisement does not appear in Run Advertised Programs on the client server, I have run a Machine Policy Retrieval.

Advert config is: Start time is current, end time is in a few hours, mandatory assignment was for 30 minutes after creation. DP is set to access directly from DP. Interaction is set to Allow users to run program independently (though in production this will not happen, for testing I just wanted to see the advert appear on the client).

If I look at the collection the new Advert is listed in the Properties. Checking the Advertisement System Status, there are no entries in relation to the client machine.

Can anybody help me identify the cause of the problem? I did find another post that mentioned the client needed to be approved to receive adverts, this has now been done.

Thanks
Andrew

Problem with SCCM monitoring compliance status on target 64bit Windows 2008 servers

Tue, 24 Nov 2009 18:37:21 Z

When I use the MS security compliance package for server 2008 with SCCM DCM to monitor the compliance status on 64bit 2008 servers, I found there was an interesting thing: The compliance report tells me there were 2 settings are reported as non-compliant, but they are compliant for sure. After a further digging, I found the system went checking the "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon" key in registry instead of "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon", and the values under the two paths differ. That's the reason, but how can make the system to check the right path in registry to avoid this happening?

The two settings are:
Interactive logon: Number of previous logons to cache (in case domain controller is not available)
Source = Registry, Location = HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon, Property = cachedlogonscount

Interactive logon: Require Domain Controller authentication to unlock workstation
Source = Registry, Location = HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon, Property = ForceUnlockLogon

Any one knows about this? Thanks!

Auto Select Language Pack during OSD

Wed, 04 Nov 2009 11:04:40 Z

I'm deploying Windows 7 using a ConfigMgr Task Sequence. I have created a Build & Capture task sequence that creates an image containing Windows 7 with four language packs and base applications.
When trying to deploy this image it stops in the Setup Windows & ConfigMgr step, where a dialog to select which of the available languages to use as default is shown.

I have integrated MDT into ConfigMgr and I have tried using both Unattend.xml and CustomSettings.ini to set the language but can't get it to apply.

My Unattend.xml contains these settings:

    <settings pass="specialize">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" 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>0414:00000414</InputLocale>
            <SystemLocale>nb-NO</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>nb-NO</UserLocale>
        </component>
.....

My CustomSettings.ini contain these settings:
SkipLocaleSelection=YES
UILanguage=en-us
UserLocale=nb-no
SystemLocale=nb-no
KeyboardLocale=0414:00000414

Can someone please help me with what I have forgotten?
What do I need to do to automatically select English UI language during deployment of an image containing 4 language packs?

Deploy image to a retired computer?

Fri, 20 Nov 2009 14:39:12 Z

Hope this isnt too dumb of a question, I just havent been able to find a good (easy) way to do this.

We are a typical organization running SCCM 2007 R2 SP1 with MDT 2008 U1. When an end user gets a new computer our help desk team would deploy a new image to the new computer, copy over the users personality (profile, apps, etc.). Then put the old computer in a cabinet to be re-deployed to someone else at a later time.
The whole SCCM/MDT ZTI works fine for new computers that SCCM has never seen before. No problems there.

The problem I am having is when the help desk team wants to image that old computer they put in the cabinet. If they just pop in the ZTI cd and try to deploy the image, it failes with errors about not being able to find a task sequence. I understand this, because SCCM still has that old computer registered and its not in any collection with the task sequence advertised to it.

What I have to have the help desk team do in order to get this to work is get the MAC address, put that into a report to find out what computer name SCCM has assigned to that computer/MAC, then move that computer into a collection that has my ZTI task sequence advertised to it. Needless to say this is a big pain in the ____, and they are giving me all kinds of flak over it.

Is this the only way to handle this kind of scenario? How does everyone else do this? Do I need to enable/disable something in SCCM/MDT that would take care of this?

thanks in advanced for anyones help,
Eric

SCCM 2007 R2 SP2 - Create Microsoft Deployment Task Sequence

Fri, 20 Nov 2009 09:41:38 Z

Hi!

I'm about to create a task sequence for Windows 7 deployment. Today we are running SCCM and Windows XP deployment. In my lab I have installed SCCM 2007 R2 and SP2, MD Tools 2010, WAIK 2.0. When Importing MD Task Sequence, Client Task Sequence I get in Details when entering Capture Operating System Image settings, Object reference not set to an instance of an object. What needs to be entered in Capture Destionation?

Kind regards, Katrin

PXE Service Point not working after everytime PXE server restarted

Thu, 19 Nov 2009 06:30:50 Z

Hi,

Everytime the PXE service point/sccm server being restarted, then it wont be working anymore. It has the error as following:-

PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 16389.

Network Account set, smsts.log says not

Thu, 19 Nov 2009 20:33:00 Z

After a restore of a SCCM 2007 SP2 environment I experience the following: after adding network access account and credentials we tried to run Task Sequence. This failed due to not recognizing the network access account information. see exerpt smst.log

<![LOG[(!sNetworkAccessAccount.empty()) && (!sNetworkAccessPassword.empty()), HRESULT=80040101 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1518)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tspolicy.cpp:1518">
<![LOG[Found empty NetworkAccessUsername/NetworkAccessPassword from NAAConfig CCM_NetworkAccessAccount]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="2" thread="1900" file="tspolicy.cpp:1518">
<![LOG[GetEncodedNetworkAccessAccount (sEncodedAccount, sEncodedPassword), HRESULT=80040101 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1544)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tspolicy.cpp:1544">
<![LOG[Network Access Account is not set]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="2" thread="1900" file="tspolicy.cpp:1554">
<![LOG[GetNetworkAccessAccount( sNetworkAccessAccount, sNetworkAccessPassword ), HRESULT=80040101 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1597)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tspolicy.cpp:1597">
<![LOG[pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040101 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tspolicy.cpp:2330">
<![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040101 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tspolicy.cpp:2862">
<![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040101 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1208)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="0" thread="1900" file="tsmediawizardcontrol.cpp:1208">
<![LOG[Failed to resolve selected task sequence dependencies. Code(0x80040101)]LOG]!><time="15:22:39.617+-60" date="11-19-2009" component="TSPxe" context="" type="3" thread="1900" file="tsmediawizardcontrol.cpp:1208">

We have tried other accounts but all fail. The operator who executed the restore could not verify if he did a site reset after the restore. Could this be the issue?

Thanks,

Omar

Omar

unknown host (gethostbyname failed)

Mon, 23 Nov 2009 11:56:25 Z

Hi all,

I have been deployed the OS to a test machine using the same TS. Then I clear the PXE advertisement, tried to pxe boot the test machine again, then I have these error. But then I didn't do any changes on the drivers, boot images and etc. What is the problem?

Requesting client identity TSPxe 23/11/2009 3:59:51 PM 608 (0x0260)
Formatted header: TSPxe 23/11/2009 3:59:51 PM 608 (0x0260)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>0dee474a-9a1a-427a-9515-0d211f6d6ee9</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-11-23T23:59:51Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSPxe 23/11/2009 3:59:51 PM 608 (0x0260)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/request TSPxe 23/11/2009 3:59:51 PM 608 (0x0260)
Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 23/11/2009 4:00:03 PM 608 (0x0260)
unknown host (gethostbyname failed) TSPxe 23/11/2009 4:00:15 PM 608 (0x0260)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 23/11/2009 4:00:15 PM 608 (0x0260)
sending with winhttp failed; 80072ee7 TSPxe 23/11/2009 4:00:15 PM 608 (0x0260)
Will retry in 5 second(s) TSPxe 23/11/2009 4:00:15 PM 608 (0x0260)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 23/11/2009 4:00:21 PM 752 (0x02F0)
The command completed successfully. TSBootShell 23/11/2009 4:00:21 PM 752 (0x02F0)
Successfully launched command shell. TSBootShell 23/11/2009 4:00:21 PM 752 (0x02F0)
Retrying... TSPxe 23/11/2009 4:00:21 PM 608 (0x0260)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/request TSPxe 23/11/2009 4:00:21 PM 608 (0x0260)
Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 23/11/2009 4:00:33 PM 608 (0x0260)
unknown host (gethostbyname failed) TSPxe 23/11/2009 4:00:45 PM 608 (0x0260)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 23/11/2009 4:00:45 PM 608 (0x0260)
sending with winhttp failed; 80072ee7 TSPxe 23/11/2009 4:00:45 PM 608 (0x0260)
Will retry in 12 second(s) TSPxe 23/11/2009 4:00:45 PM 608 (0x0260)
Retrying... TSPxe 23/11/2009 4:00:57 PM 608 (0x0260)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/request TSPxe 23/11/2009 4:00:57 PM 608 (0x0260)
Error. Received 0x80072ee7 from WinHttpSendRequest. TSPxe 23/11/2009 4:01:10 PM 608 (0x0260)
unknown host (gethostbyname failed) TSPxe 23/11/2009 4:01:22 PM 608 (0x0260)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSPxe 23/11/2009 4:01:22 PM 608 (0x0260)
sending with winhttp failed; 80072ee7 TSPxe 23/11/2009 4:01:22 PM 608 (0x0260)
Will retry in 21 second(s) TSPxe 23/11/2009 4:01:22 PM 608 (0x0260)
Retrying... TSPxe 23/11/2009 4:01:43 PM 608 (0x0260)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.test.com.my:80 CCM_POST /ccm_system/request TSPxe 23/11/2009 4:01:43 PM 608 (0x0260)

SCCM 2007 SP2 with MDT 2010 Integration (ZTIMediaHook new computer provisioning...where have you gone?)

Wed, 04 Nov 2009 22:25:18 Z

After performing the MDT Integration, I created the MDT Boot Images thinking the ZTIMediaHook was still being used to provision new/unknown systems as long as you didn't select the unknown computer support check box. Unfortunately, this is not the case. In fact, the ZTIMediaHook.wsf was missing and the SCCM_Bootstrap.ini was completely changed (no longer references the webservice (GetAssigned Site, IsComputerKnown, AddComputer, HasAdvertisement) to provision new computers. I realize there is the new UnknownComputer Support in R2 but that method doesn't allow you to choose a unique provisioning collection which is required in our environment especially when you have 50 different departments and 100 different SCCM Admins performing their own OS deployments. The ZTIMediaHook with the Webservice allowed each department to enter a computername and then provision their new computers directly into their Collection ID where they have their Task Sequences Advertised. Sounds like it's back to the drawing board (SDK) for me to create a custom front end? The old ZTIMediaHook worked great for us so why not leave it as an option?

Unable to install MDT 2010

Tue, 24 Nov 2009 00:22:54 Z

We have just upgraded our SCCM server to SCCM 2007 SP2. Now I am trying to install MDT 2010 on the server to replace MDT 2008, however the MDT 2010 install fails with the following error "Microsoft Deployment Toolkit 2010 (5.0.1641.0) Setup Wizard ended prematurely".

Below is a copy of the installed log:
=== Logging started: 24/11/2009 10:57:58 ===
Action 10:57:58: INSTALL.
Action start 10:57:58: INSTALL.
Action 10:57:58: AppSearch. Searching for installed applications
Action start 10:57:58: AppSearch.
AppSearch: Property: DISTRIBUTIONDIR, Signature: DistributionDirSearch
AppSearch: Property: INSTALLDIR, Signature: InstallDirSearch
AppSearch: Property: FRAMEWORK50727, Signature: Framework50727Registry
Action ended 10:57:58: AppSearch. Return value 1.
Action 10:57:58: LaunchConditions. Evaluating launch conditions
Action start 10:57:58: LaunchConditions.
Action ended 10:57:58: LaunchConditions. Return value 1.
Action 10:57:58: PrepareDlg.
Action start 10:57:58: PrepareDlg.
Info 2898. DlgFont8, Tahoma, 1
Info 2898. VerdanaBold13, Verdana, 1
Action 10:57:58: PrepareDlg. Dialog created
Action ended 10:57:58: PrepareDlg. Return value 1.
Action 10:57:58: FindRelatedProducts. Searching for related applications
Action start 10:57:58: FindRelatedProducts.
FindRelatedProducts: Found application: {075C79BF-3C29-4CAD-9398-F7DE614D9F2D}
Action ended 10:57:58: FindRelatedProducts. Return value 1.
Action 10:57:58: ValidateProductID.
Action start 10:57:58: ValidateProductID.
Action ended 10:57:58: ValidateProductID. Return value 1.
Action 10:57:58: CostInitialize. Computing space requirements
Action start 10:57:58: CostInitialize.
Action ended 10:57:58: CostInitialize. Return value 1.
Action 10:57:58: FileCost. Computing space requirements
Action start 10:57:58: FileCost.
Action ended 10:57:58: FileCost. Return value 1.
Action 10:57:58: CostFinalize. Computing space requirements
Action start 10:57:58: CostFinalize.
Action ended 10:57:58: CostFinalize. Return value 1.
Action 10:57:58: MigrateFeatureStates. Migrating feature states from related applications
Action start 10:57:58: MigrateFeatureStates.
Action ended 10:57:58: MigrateFeatureStates. Return value 0.
Action 10:57:58: WelcomeDlg.
Action start 10:57:58: WelcomeDlg.
Action 10:57:58: WelcomeDlg. Dialog created
Info 2898. DlgFontBold8, Tahoma, 1
Action 10:57:59: LicenseAgreementDlg. Dialog created
Action 10:58:01: CustomizeDlg. Dialog created
Action 10:58:01: VerifyReadyDlg. Dialog created
Action ended 10:58:02: WelcomeDlg. Return value 1.
Action 10:58:02: ProgressDlg.
Action start 10:58:02: ProgressDlg.
Action 10:58:02: ProgressDlg. Dialog created
Action ended 10:58:02: ProgressDlg. Return value 1.
Action 10:58:02: ExecuteAction.
Action start 10:58:02: ExecuteAction.
Action ended 10:58:02: ExecuteAction. Return value 3.
Action 10:58:02: FatalError.
Action start 10:58:02: FatalError.
Action 10:58:02: FatalError. Dialog created
Action ended 10:58:03: FatalError. Return value 2.
Action ended 10:58:03: INSTALL. Return value 3.
Property(C): InstallMode = Custom
Property(C): UpgradeCode = {42D9191C-0C0E-45E5-BB94-2DF35BB6C10C}
Property(C): DISTRIBUTIONDIR = F:\MDT_Distribution\
Property(C): INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit\
Property(C): FRAMEWORK50727 = 50727-50727
Property(C): DIST_Template = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\
Property(C): DOCS_DIR = C:\Program Files\Microsoft Deployment Toolkit\Documentation\
Property(C): DOCS_Html = C:\Program Files\Microsoft Deployment Toolkit\Documentation\html\
Property(C): DOCS_scripts = C:\Program Files\Microsoft Deployment Toolkit\Documentation\html\scripts\
Property(C): DOCS_images = C:\Program Files\Microsoft Deployment Toolkit\Documentation\images\
Property(C): TOOLS_Samples = C:\Program Files\Microsoft Deployment Toolkit\Samples\
Property(C): TOOLS_Sccm = C:\Program Files\Microsoft Deployment Toolkit\SCCM\
Property(C): TOOLS_Sccm_Extensions = C:\Program Files\Microsoft Deployment Toolkit\Templates\Extensions\
Property(C): TOOLS_Sccm_Actions = C:\Program Files\Microsoft Deployment Toolkit\Templates\Extensions\Actions\
Property(C): TOOLS_Sccm_Forms = C:\Program Files\Microsoft Deployment Toolkit\Templates\Extensions\Forms\
Property(C): TOOLS_Sccm_TaskSequences = C:\Program Files\Microsoft Deployment Toolkit\Templates\Extensions\Actions\f428b123-4f99-49eb-babd-40fd3eb6ac4f\
Property(C): TOOLS_Sccm_BootImages = C:\Program Files\Microsoft Deployment Toolkit\Templates\Extensions\Actions\b0b9625f-7afe-409e-9b65-5cb973a82a2c\
Property(C): TOOLS_Templates = C:\Program Files\Microsoft Deployment Toolkit\Templates\
Property(C): TOOLS_Bin = C:\Program Files\Microsoft Deployment Toolkit\Bin\
Property(C): TOOLS_Downloads_Manifest = C:\Program Files\Microsoft Deployment Toolkit\Downloads\{00000000-0000-0000-0000-000000000000}\
Property(C): TOOLS_Control = C:\Program Files\Microsoft Deployment Toolkit\Control\
Property(C): DIST_Scripts = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Scripts\
Property(C): DIST_Oem = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\$OEM$\
Property(C): DIST_Applications = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Applications\
Property(C): DIST_Captures = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Captures\
Property(C): DIST_Control = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Control\
Property(C): DIST_Os = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Operating Systems\
Property(C): DIST_Obd = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Out-of-Box Drivers\
Property(C): DIST_Packages = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Packages\
Property(C): DIST_Tools = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\
Property(C): DIST_Tools_x86 = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86\
Property(C): DIST_Tools_x86_00000409 = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86\00000409\
Property(C): DIST_Tools_x64 = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64\
Property(C): DIST_Tools_x64_00000409 = C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64\00000409\
Property(C): BannerBitmap = bannrbmp
Property(C): TARGETDIR = D:\
Property(C): IAgree = Yes
Property(C): TOOLS_Downloads = C:\Program Files\Microsoft Deployment Toolkit\Downloads\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): BDDVistaShortcutDir = C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft Deployment Toolkit\
Property(C): ProgramMenuFolder = C:\Documents and Settings\All Users\Start Menu\Programs\
Property(C): SourceDir = C:\Documents and Settings\SMS Service\Desktop\
Property(C): Manufacturer = Microsoft
Property(C): ProductCode = {65F921C5-8EA2-488B-B77E-CEC1757FF166}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft Deployment Toolkit 2010 (5.0.1641.0)
Property(C): ProductVersion = 5.0.1641.0
Property(C): DefaultUIFont = DlgFont8
Property(C): ErrorDialog = ErrorDlg
Property(C): ALLUSERS = 1
Property(C): ButtonText_No = &No
Property(C): ButtonText_Install = &Install
Property(C): Setup = Setup
Property(C): ButtonText_Browse = Br&owse
Property(C): CustomSetupIcon = custicon
Property(C): ButtonText_Next = &Next >
Property(C): ButtonText_Back = < &Back
Property(C): ButtonText_Print = &Print
Property(C): Progress2 = installs
Property(C): Wizard = Setup Wizard
Property(C): RemoveIcon = removico
Property(C): ExclamationIcon = exclamic
Property(C): ProductID = none
Property(C): ButtonText_Reset = &Reset
Property(C): ButtonText_Remove = &Remove
Property(C): CompleteSetupIcon = completi
Property(C): ButtonText_Yes = &Yes
Property(C): ButtonText_Exit = &Exit
Property(C): ButtonText_Return = &Return
Property(C): DialogBitmap = dlgbmp
Property(C): DlgTitleFont = {&DlgFontBold8}
Property(C): ButtonText_Ignore = &Ignore
Property(C): RepairIcon = repairic
Property(C): ButtonText_Resume = &Resume
Property(C): InstallerIcon = insticon
Property(C): ButtonText_Finish = &Finish
Property(C): PROMPTROLLBACKCOST = P
Property(C): PIDTemplate = 12345<#######>@@@@@
Property(C): Progress1 = Installing
Property(C): ButtonText_Cancel = &Cancel
Property(C): InfoIcon = info
Property(C): ButtonText_Repair = &Repair
Property(C): ButtonText_Retry = &Retry
Property(C): ButtonText_OK = &OK
Property(C): SecureCustomProperties = BDDPATCH1FOUND;BDDRTWFOUND;MDTFOUND;NEWERVERSIONDETECTED
Property(C): MDTFOUND = {075C79BF-3C29-4CAD-9398-F7DE614D9F2D}
Property(C): PackageCode = {5934AA24-BECE-412E-ADE4-F1085C75B757}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): CURRENTDIRECTORY = C:\Documents and Settings\SMS Service
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 13580
Property(C): VersionDatabase = 200
Property(C): VersionMsi = 3.01
Property(C): VersionNT = 502
Property(C): VersionNT64 = 502
Property(C): WindowsBuild = 3790
Property(C): ServicePackLevel = 2
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 3
Property(C): MsiNTSuiteEnterprise = 1
Property(C): WindowsFolder = C:\NOSW2K3\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\NOSW2K3\system32\
Property(C): SystemFolder = C:\NOSW2K3\SysWOW64\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\DOCUME~1\SMSSER~1\LOCALS~1\Temp\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Documents and Settings\SMS Service\Application Data\
Property(C): FavoritesFolder = C:\Documents and Settings\SMS Service\Favorites\
Property(C): NetHoodFolder = C:\Documents and Settings\SMS Service\NetHood\
Property(C): PersonalFolder = C:\Documents and Settings\SMS Service\My Documents\
Property(C): PrintHoodFolder = C:\Documents and Settings\SMS Service\PrintHood\
Property(C): RecentFolder = C:\Documents and Settings\SMS Service\Recent\
Property(C): SendToFolder = C:\Documents and Settings\SMS Service\SendTo\
Property(C): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(C): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(C): LocalAppDataFolder = C:\Documents and Settings\SMS Service\Local Settings\Application Data\
Property(C): MyPicturesFolder = C:\Documents and Settings\SMS Service\My Documents\My Pictures\
Property(C): AdminToolsFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
Property(C): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(C): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(C): FontsFolder = C:\NOSW2K3\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 20478
Property(C): VirtualMemory = 3077
Property(C): AdminUser = 1
Property(C): LogonUser = sms service
Property(C): UserSID = S-1-5-21-1166029338-121055372-2978170129-143270
Property(C): UserLanguageID = 3081
Property(C): ComputerName = Server1
Property(C): SystemLanguageID = 3081
Property(C): ScreenX = 1024
Property(C): ScreenY = 768
Property(C): CaptionHeight = 19
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): ColorBits = 16
Property(C): TTCSupport = 1
Property(C): Time = 10:58:03
Property(C): Date = 24/11/2009
Property(C): MsiNetAssemblySupport = 2.0.50727.3053
Property(C): MsiWin32AssemblySupport = 5.2.3790.3959
Property(C): RedirectedDllSupport = 2
Property(C): Privileged = 1
Property(C): USERNAME = xxx
Property(C): COMPANYNAME = xxx
Property(C): DATABASE = C:\DOCUME~1\SMSSER~1\LOCALS~1\Temp\dfa66fb.msi
Property(C): OriginalDatabase = C:\Documents and Settings\SMS Service\Desktop\MicrosoftDeploymentToolkit2010_x64.msi
Property(C): SOURCEDIR = C:\Documents and Settings\SMS Service\Desktop\
Property(C): VersionHandler = 3.01
Property(C): UILevel = 5
Property(C): ACTION = INSTALL
Property(C): EXECUTEACTION = INSTALL
Property(C): ROOTDRIVE = D:\
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
Property(C): INSTALLLEVEL = 1
=== Logging stopped: 24/11/2009 10:58:03 ===
MSI (c) (0C:1C) [10:58:03:727]: Product: Microsoft Deployment Toolkit 2010 (5.0.1641.0) -- Installation failed.

Has anyone got the task variable "OSDSuffixSearchOrder" working?

Wed, 24 Jun 2009 12:25:07 Z

I've got all other Network related task variables working to set a static IP etc but the OSDSuffixSearchOrder just isn't working.

The SCCM SDK has nothing on this and Google shows 4 results from a OSDSuffixSearchOrder search, 3 of which are the same Microsoft page! :-)

Anyone?

Thanks

Tony

Capture Image

Mon, 23 Nov 2009 18:57:24 Z

I am trying to capture an XP SP3 image using the capture media task. I have used a task sequence to create the task sequence media, used the correct boot image, copied the ISO image and burnt the files to a CD.

The reference PC is fully built with all installed applications, drivers and windows updates. It is a member of a workgroup, has a blank Administrator password and has all necessary files in the C:\Sysprep folder. When the image capture wizard runs from the CD, I point the image to be saved to a network location (on the SCCM Server) by using the IP address and share name, connect using a domain admin account and then the wizard finishes.

From this point, nothing else happens on the reference PC - there is simply no activity whatsoever. Task manager also shows nothing running relevant to the capture media. It just sits there doing nothing.

Please could some assistance be offered to this problem?

Many thanks