Hi,

I want to display a dialog with a countdown (not new program notification balloon) prior to an OSD Deployment to warning users about the impending update.

I am pretty sure it worked in the past by ticking the following check box on the advertisement interaction tab of the task sequence advert.

"Use custom countdown notification length (minutes)"

But ticking this box doesn't work for me right now.

Do I have this completely wrong, I am sure I used to be able to get a dialog box with countdown, but I might have just got ton confused as I haven't don't a mandatory OSD deployment in a while.

Any other steps I am missing? I have played around with Reminders Tab on theComputerAgent properties dialog, and also the Notification tab on the Advertised Programs Properties Dialog which can make the "new Program available" balloon pop up and even do a countdown but I am sure I used to be able to get a full blown OSD Dialog warning about the impending upgrade...

Thanks in advanced

George

Hello,

I am stuck at applying a Dell driver packages with SCCM 2007. 

It's for the Dell Optiplex 7010 & Dell Latitude E6530
82579LM Gigabit Network Connection

I tried the Dell driver package but it kept failing and I ended up in creating a driver package with just the network driver but it also keeps failing.

I don't know what to do anymore because I really need to have a successful network driver installation to continue the deployment. The driver is working fine in WINPE because there I have an IP and Windows7 is installed(PXE deployment) but it fails installing the driver on Windows7. I have also tried the latest driver from Intel (18.2).

Part of the log file (Driver package download successful):

Download done setting progress bar to 100 OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\01bee370-65be-4cbc-839c-0b6441b97f5d is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\01d4b3f7-a1ce-443e-9eb0-51700e8ee227 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\03d386cd-4c3b-44d6-b1c2-b85d6d6cd5ff is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\15cff229-cbb6-43a3-add3-e2262505afbb is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\18d880d1-075f-4450-8ad3-45aa4be29cec is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\1e0c9d57-d6b1-462a-8cf2-b95d1b857380 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\b58a6ac7-d015-4041-9378-654497f30d94 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\de771279-76ba-4609-a634-0b4c4349b04c is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\e25063c2-235e-43df-970b-50d7f236cbb3 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\e32fee5c-4b0e-4fd3-8ec2-8b55db9eecdd is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\ebacac22-5cfb-42ac-817c-7da025fa14a6 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\f7aed134-7da1-47d8-a2b6-0a51cf618f6b is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
c:\_smstasksequence\packages\p010010f\ffe0e94f-7a7e-4cad-8293-1c069cfbf782 is a directory. Setting directory security OSDDriverClient 17/05/2013 10:33:09 1676 (0x068C)
Content successfully downloaded at C:\_SMSTaskSequence\Packages\P010010F OSDDriverClient17/05/2013 10:33:10 1676 (0x068C)
Adding "C:\_SMSTaskSequence\Packages\P010010F\01BEE370-65BE-4CBC-839C-0B6441B97F5D" to Windows driver store. OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Setting %SystemRoot% to "C:\Windows" OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Added list item with key value '1' OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Calling Package manager to add drivers to the offline driver store. OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Command line for extension .exe is "%1" %* OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Set command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Executing command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 17/05/2013 10:33:10 1676 (0x068C)
Process completed with exit code 0 OSDDriverClient 17/05/2013 10:33:12 1676 (0x068C)
Dism successfully added drivers to the offline driver store. OSDDriverClient 17/05/2013 10:33:12 1676 (0x068C)
Successfully added "C:\_SMSTaskSequence\Packages\P010010F\01BEE370-65BE-4CBC-839C-0B6441B97F5D" to the Windows driver store. OSDDriverClient 17/05/2013 10:33:12 1676 (0x068C)
Adding "C:\_SMSTaskSequence\Packages\P010010F\01D4B3F7-A1CE-443E-9EB0-51700E8EE227" to Windows driver store. OSDDriverClient 17/05/2013 10:33:12 1676 (0x068C)
Setting %SystemRoot% to "C:\Windows" OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Added list item with key value '1' OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Calling Package manager to add drivers to the offline driver store. OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Command line for extension .exe is "%1" %* OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Set command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Executing command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 17/05/2013 10:33:13 1676 (0x068C)
Process completed with exit code 2149711899 OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
uExitCode == 0, HRESULT=8022001b (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,558) OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Dism failed with return code -2145255397 OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=8022001b (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,668) OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Failed to add driver to driver store. Code 0x8022001b OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=8022001b (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557) OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\P010010F OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
reference count 1 for the source C:\_SMSTaskSequence\Packages\P010010F before releasing OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Delete source directory C:\_SMSTaskSequence\Packages\P010010F OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Released the resolved source C:\_SMSTaskSequence\Packages\P010010F OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=8022001b (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409) OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Failed to provision driver. Code 0x8022001b OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Exiting with return code 0x8022001B OSDDriverClient 17/05/2013 10:33:16 1676 (0x068C)
Process completed with exit code 2149711899 TSManager 17/05/2013 10:33:16 1644 (0x066C)
!--------------------------------------------------------------------------------------------! TSManager 17/05/2013 10:33:16 1644 (0x066C)
Failed to run the action: Apply Driver Package.
Unknown error (Error: 8022001B; Source: Unknown) TSManager 17/05/2013 10:33:16 1644 (0x066C)
Sending status message . . . TSManager 17/05/2013 10:33:16 1644 (0x066C)

Any suggestions on this issue?

Hy,
i need to install sccm 2012 client in a ts into 2007 cause we are migrating and we want that the new pc goes into the new site.
The ts works fien but after installing the new client the ts doesn't go on and stops without any errors.

Any ideas?

Thanks

Hello All.

I am getting an error stating the Task Sequence has failed to run action: “Apply Data Image 1”, Please see the logs below:-

The task sequence execution engine failed executing the action (Apply Data Image 1) in the group (Install Operating System) with the error code 21475000037

Action Output: Command line for extension .exe is "%1"%*Set Command line:" "OSDApplyOS.exe" /data:CEN00006, ISearching for next available volume: Volume A:\ IS not a local hard drive. Volume c:\ has already used. Volume f:\ has already used. Volume E:\ is not alocal hard drive. Volume X:\ is not a local hard drive. It ! = volumes, end0,

There are no more volumes available for use. the requested target could not be resolved to a valid volume on this computer

Check your task sequence to ensure this drive is correct and that it is being created the parameter is incorectt.

Happy

Hi.

I need to show all machines of each collection.
Showing the collection to which it belongs and the total number of machines such as:

Employee 1 = 197
Employees 2 = 19
Employees 3 = 14

Thanks for your help!!!

Best Regards - Saludos cordiales Juan Carrillo Vaccaris Engineer - Management, IT Professional Services, DATCO Chile S.A. E-Mail: Juan.Carrillo@datco.cl Website: http://www.datco.cl

HI everyone,

i am using sccm 2007 r3. i make standalone media for Bare metal deployment. i have to add script to rename computer name after disk partition that work fine..i want to add another task to prompt domain credential during OSD (Windows PE Phase) i mean to say they showing domain account pop-up and then after go further process...  which changes required ?  or any script to add task sequence .... thanks in advance

Says it all really

I've looked in the boot wim and had a quick look through some of the packages and I can't find where the task sequence is located.

Can someone assist please?

Thanks, Phil

Hi there,

I am at the momento trying to deploy Windows XP by capturing an OS image from a reference computer. At this stage all I have done is ditributed the boot image to the distribution point, and then I started the Create Task Sequence Media wizard to try to burn a cd to capture the image from the reference system.

However, I am seeing the following error upon completing the wizard:

"Error creating media. Error message is: The directory is not a subdirectory of the root directory."

I have so far tried to save this iso image on C:, in a subfolder on C, on each other partition on the site server and in a shared folder on the site server, all of which produced that same error message.

Here is an excerpt from the CreateTsMedia.log:

<![LOG[---------------------------- CreateTsMedia ----------------------------]LOG]!><time="13:25:17.230+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="createtsmedia.cpp:138">
<![LOG[Requested output path: \\sccm-srv\package\capture.iso (CD)]LOG]!><time="13:25:17.230+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="createtsmedia.cpp:146">
<![LOG[Temp Directory C:\DOCUME~1\ADMINI~1.SCC\LOCALS~1\Temp\1\tsmedia_5588 created]LOG]!><time="13:25:17.230+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="tempdirectory.cpp:64">
<![LOG[Setting up Install Toolkit]LOG]!><time="13:25:17.290+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="mediatoolkit.cpp:207">
<![LOG[Opening image file C:\DOCUME~1\ADMINI~1.SCC\LOCALS~1\Temp\1\tsmedia_5588\Cache\LFC00001\boot.LFC00001.wim]LOG]!><time="13:25:24.250+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="wimfile.cpp:255">
<![LOG[Applying image 1 to volume C:\DOCUME~1\ADMINI~1.SCC\LOCALS~1\Temp\1\tsmedia_5588\Toolkit]LOG]!><time="13:25:24.340+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="wimfile.cpp:445">
<![LOG[Unable to apply (0x80070090)]LOG]!><time="13:25:24.360+360" date="01-02-2008" component="CreateTsMedia" context="" type="3" thread="5588" file="wimfile.cpp:491">
<![LOG[Closing image file C:\DOCUME~1\ADMINI~1.SCC\LOCALS~1\Temp\1\tsmedia_5588\Cache\LFC00001\boot.LFC00001.wim]LOG]!><time="13:25:24.370+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="wimfile.cpp:291">
<![LOG[Failed to create media generator (0x80070090)]LOG]!><time="13:25:24.370+360" date="01-02-2008" component="CreateTsMedia" context="" type="3" thread="5588" file="createtsmedia.cpp:203">
<![LOG[CreateTsMedia failed with error 0x80070090, details=""]LOG]!><time="13:25:24.370+360" date="01-02-2008" component="CreateTsMedia" context="" type="1" thread="5588" file="createtsmedia.cpp:214">

What is the most popular way to capture an image from a reference system, and what is the easiest way? On the one previous occasion I used this approach I was able to perform this step in exactly the same way without problems, but later ran into permission issues on the client.

Thanks a lot.

There are 10 updates that windows seams not to be able to install downloads them part installs them then when it re-starts to configer them it gets to about 98%-100% then says failed updates reverting changes then about 20mins or so it gets back to windows login screen i have looked at the log file this is what the error is

(WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032)

any help on this matter would be very thankful 

thanks

Hi,

I have a task sequence for Windows 7 image deployment and I use Report 146 '"All Task Sequence Advertisements" to track and monitor the status of the deployment. Most of the times the task sequence goes through fine without any issues. However of late, I have observed that the task sequence as a whole succeeds but a  couple of apps fail due to some package issue. Since, I would be deploying images on considerably high number of machines simultaneously, it's hard to keep an eye on each task of the TS status for each machine.

Therefore, I was just thinking of an email trigger automation. It goes something like this: A script which keeps track of return code of each task in the task sequence for each machine and as soon as it observes a 'non-zero' return code, it fires an email to a preconfigured mailbox including some kind of details to troubleshooot.

I am not sure if this is possible out of box.  Can somebody please guide me towards achieving my goal and saving me from the pain of going through TS report for each machine.

Thanks in advance.

Madhu

I am testing a HP Z620 for our company.  I am trying to lay down our Win 7 X64 image on it using SCCM 2007.

i tried to deploy when the storage is set to IDE and its work fine but when i tried to set the storage to AHCI + RAID (Defualt setting) it failed after the winPE downloaded, in the first step in the task sequence (partition Disk) with error code 80070490.

I assumedthat this is drivers issue so i imported into the boot image the storage drivers, but it still doesnt work.

Can anyone help me?

Hey there! 

I need some help concerning WDS on Server 2008 R2. WDS is running, everything is ok. 

Additionally I need in PXE boot the option to boot a non-Windows-program like Acronis Backup & Recovery 10.

Is there any chance to solve this problem? I'm at the end of my knowledge...

Cheers

/Tobi

Hi All

I have added the drivers for a HP Z800 into our Windows XP SP3 sccm deploy.

I have done everything the same as when I added a HP Z400 i n a while ago and selected the Mass storage driver which is as LSI adapter. I even checked on the HP image of it that the Mass Storage driver I have selected corresponds and supports the same model as listed in the device manager.

However I get an error Code 0x80070490 and have to reboot. The Task Sequence log shows in parts

"C:\_SMSTaskSequence\Packages\CCG001CB Failed to find driver for 'PCI\VEN_1000&DEV_005E' Failed to install mass storage driver. Code 0x80070490 Released the resolved source C:\_SMSTaskSequence\Packages\CCG001CB pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80070490 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409) Unloading offline SOFTWARE registry hive Unloading offline SYSTEM registry hive Exiting with return code 0x80070490 Failed to provision driver. Code 0x80070490. The operating system reported error 2147943568: Element not found."

However PCI\VEN_1000&DEV_005E is not the hardware device ID when I look at the LSI or Intel storage adapters in the device manager.

I have updated the boot image with the mass storage drivers as well as updated the driver package. Am I missing something here?

Thanks.

hi,

This was the error i am receiving while deploying new machine :-

An error occurred while retrieving policy for this computer (0x80004005)

checked the smsts.log and it shows an error message "NO MP Certificate"

Checked all the pxe and boot certificates and they are all upto date & the certificates are not missing.

the lab was working perfectly fine before...

the smspxe.log shows the error message :-

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

WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode.

It's set mixed mode still i receive this warning message in the log file.

what should i do to fix this problem....

Thnaks

Pranay.

Hello, I've walked into an organization that hasn't installed the PXE service points on their SCCM servers.  Instead it seems they've taken the boot.wim and imported it into WDS.  Just recently the boot media certificate expired and PXE booting from WDS no longer works as you get the error message stating you must have a valid certificate.  I generated a new task sequence media, and selected the boot media, USB Media and generated a new cert.  I was hoping the that the PXE boot would start working, but that was not the case, it seems the new cert only works for the USB boot media.

I found the blog below on how to import MDT images to WDS and figure it should be the same process.

http://fbinotto.blogspot.com/2012/04/import-sccm-boot-image-to-wds.html.

After importing the boot.wim I did notice the name gets changed to boot-(2).wim, because boot.wim already exists from another image, but that should be ok.  When PXE booting, the image gets as far as loading WinPE, and then preparing network connections, after that it reboots.  Any thoughts on how to get the existing boot media certificate working, or importing a new image into WDS?  Eventually the goal in the next month or two is to get away from WDS, but since i've just come on board here I'd rather slow migrate things vs doing a cut over and then being under the gun to get it working.

Thanks for reading

Hi all,

-SCCM 2012

-Used Install.wim from  windows 7 installation disk

I'm trying to deploy WIN7 using a task sequence. It's hanging at the very end of the build on "Setup is preparing your computer for the first use".  When looking at the task the deployment status I see :The task sequence execution engine failed executing and action with an error code 11135. This appears to be happening when it's preparing the operating system. Any thoughts?