OSD & Built-in Deco

Device: Sound?Blaster Audigy 2 ZS - NoteBooksSoftware Updates: All available from support/webpage are installed. Hi peeps, i'm sure many of us have seen that almost 95% of the digital AV Recei'vers, Pre-Amps, Decoders, Sorrund Controllers have some OSD with an AutoDetect for the Type Of Signal Stream their are processing/decoding. Is there is any way to add that capability to the OSD of the Audigy 2 ZS (NoteBook) so we can be sure its built-in-decoder is receiving and processing what it should?Cause I remember a common issue with some DVD Players, sometimes the AUDIO Setting should be on PCM or BitStreem in order my AV Recei'ver get the correct signal, it is, DB Digital, DTS, DTS-ES, DB Digital EX, etc... and the only way I can know something is not fine/correct is by watching the OSD of my AV Recei'ver?cause it'sadvices me if the connections are fine or not, DVD really contains the Digital Audio Track? or not, etc, by putting it'son its OSD. In resume, if the OSD of the Audigy 2 ZS (NoteBook) is able to display the kind of Audio Track it is decoding/processing would be very helpfull for many situations.

Are you sure you installed all? The ?"Onscreen Display Engine update for Creative PCMCIA Sound Blaster? Audigy? 2 ZS Notebook version .0.08" available on the download section for the A2ZSNB should display a small rectangle with the DD/DTS/DVD-A logo when the drivers detect the bitstream. http://us.creative.com/support/downl...ype=0&x=37&y=7

Similar Messages

  • Newly Imaged Devices Stuck in Provisioning Mode, why?

    I've imaged a few new devices with an OSD built into MDT 2013 on SCCM 2012 R2 CU1 and they get stuck in provisioning mode once I'm able to log in.
    The following articles explain the issue and a workaround:
    http://www.toolzz.com/?p=1278
    http://www.danielclasson.com/how-to-force-an-sccm-2012-client-out-of-provisioing-mode-during-osd/
    I'm more concerned with why this is happening and how I can stop it from even happening as I am starting to suspect that the "Install Software Updates" task is causing this symptom.
    I'm attaching a sample smsts.log to show an error I keep seeing:
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:49.178+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:49.459+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:49.474+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:49.786+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:49.786+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:50.067+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:50.083+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:50.364+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:50.379+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:50.660+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:50.676+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:50.956+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:50.972+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:51.268+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:51.284+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:51.580+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:51.580+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:51.877+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:51.877+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:52.173+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:52.189+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:52.470+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:52.470+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:52.766+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:52.766+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:53.062+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:53.078+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:53.390+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:53.406+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:53.702+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:53.718+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:54.030+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:54.045+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:54.326+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:54.342+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:54.622+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:54.638+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:54.934+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:54.950+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:55.231+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:55.246+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:55.543+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:55.543+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:55.839+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:55.855+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:56.136+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:56.151+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:56.432+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:56.448+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:56.760+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:56.760+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:57.056+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:57.072+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:57.352+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:57.352+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:57.633+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:57.649+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:57.945+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:57.961+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:58.226+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:58.242+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:58.522+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:58.538+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:58.834+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:58.850+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:59.146+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:59.162+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:59.474+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:59.490+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643]LOG]!><time="13:43:59.770+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">
    <![LOG[ Update with CIID Site_272C7E81-26C2-42D1-A5BE-36182483E280/SUM_5ff8a0b5-0efc-4f1c-b71a-f58971a14ab3 failed with hr = 0x80240017]LOG]!><time="13:43:59.786+360" date="01-21-2015" component="InstallSWUpdates" context="" type="0" thread="2716" file="installswupdate.cpp:370">

    There's not a lot you can do there, Office simply isn't designed to be serviced offline necessarily. If you have the MSP files though, simply adding them to the Updates folder of the Office installation files will cause them to be installed automatically
    with no additional configuration. There's no easy way to get all of the MSP files (to my knowledge) except for downloading them one by one from Microsoft Update.
    I've never seen office updates cause issues in a TS though so the traditional method works also.
    Jason | http://blog.configmgrftw.com | @jasonsandys
    It just might be risky because the Software Update task might grab some new update that requires 2 reboots.
    I'll just need to create a new base image as I pre-installed Office on it, but moving forward I'll look into using MSP files.

  • SCCm 2012 R2 - OSD fails when multiple computers are getting built

    Hi everyone,
    I ran into a weird issue with my SCCM 2012 R2. I noticed when I build one computer with SCCM OSD, it works fine. But when I try to run more than one built at a time, only one usually works. The rest usually doesn't get apps installed in the task sequence,
    some don't get added to the domain etc. Any idea what it might be? Could it be that simultaneous connections to the distribution point are getting terminated and imaging fails?
    Appreciate your help! 

    Ok guys, this seems to be a false alarm here. It turns out I was missing a driver for ethernet card on my Dell T1600. I kicked off 3 Dell Optiplex 9020 and they all worked flawlessly. This is weird though, since I did install OS on some T1600 before and
    they all worked fine...
    Anyway, I downloaded the driver and added it to SCCM. I will kick off the install again today and see if that solved it.

  • How to monitor OSD TS failure and get alert or report?

    How to monitor OSD TS failure and get some alert or generate an report?
    We have SCCM 2012 R2 CU1 with MDT 2013.
    I have checked the OSD reports in SCCM and everyone is emty, where do SCCM get data to the what to activate?
    (I thinking of "Task Sequence - Deployment Status" reports)
    I am not sure people read report manually or lock at the MDT monitor view. So best I think that generate an email or incident in Service Manager when an TS fails.
    We do have SCOM, SCSM, SCO.
    Is there anyone that can point what way or what option I have?
    /SaiTech

    Specifically you could use this Status Message Query syntax to monitor your Task Sequences for errors:
    select stat.*, ins.*, att1.*, att1.AttributeTime from SMS_StatusMessage as stat left join SMS_StatMsgInsStrings as ins on stat.RecordID = ins.RecordID left join SMS_StatMsgAttributes as att1 on stat.RecordID = att1.RecordID inner join SMS_StatMsgAttributes
    as att2 on stat.RecordID = att2.RecordID where att2.AttributeID = 401 and att2.AttributeValue = "DOJ200A1" and stat.SiteCode = "DOJ" and att2.AttributeTime >= ##PRM:SMS_StatMsgAttributes.AttributeTime## order by att1.AttributeTime desc
    Just replace DOJ200A1 with the Deployment ID of your Task Sequence and DOJ with your SiteCode.
    If you want to generate an alert if the TS fails then you could run a script that calls a utility (or similar) which sends a pre-configured email to a specified address (as an alternative to Torten's response). This could be placed in the built in error
    logging section of the SCCM integrated MDT Task Sequence when it fails which I assume you are using (right at the bottom, called Gather Logs and StateStore on failure).
    There are heaps of ways of generating an email from a TS and controlling error logging just do a search - as you have Service Manager you could even use your instance of Orchestrator and call a run book in your TS which does the email?
    Cheers
    Damon

  • OSD Failure - Windows 7 - Blue Screen on First Boot in Full OS

    Hi,
    We are experiencing a really strange problem with our OSD which is hard to pin down. Our setup is SCCM 2012 R2 with 4 PXE enabled DP's (VMWare VMs) across 2 data centers and on seperate hosts and we are delivering Windows 7 (32 and 64) with recaptured WIM
    files. Ouor deployments work fine for around a week and then they suddenly start experiencing a reboot look and blue screening at the first boot into the full OS.
    This occurs on multiple different physical machines and we inject driver packages for different builds with WMI filters on motherboard as is common. The really weird part is that this will work for days then stop working. The only workaround we have is to
    recapture the WIM file (we have a build and capture task sequence for this) and then it works again, even though the content and drivers are exactly the same from the same B+C task sequence. Even the windows updates are the same with no new ones. It doesn't
    seem to be the drivers themselves but rather the process of DISM injecting them offline in windows PE which appears to break the registry. The last thing we see before blue screen is "Updating registry" in windows 7 boot.
    These are the things we have tried are...
     - Recapturing the WIM (works for around a week but not a fixed period)
     - Host the WIM on a physical DP (to rule out VMWare) with only the WIM and a single driver package. Again this worked fine for a week or so.
     - Built several different physical machines. All fine but when this stops, it stops for all of them
     - If we remove all drivers but the LAN driver it can work but our testing has ruled out a specific bad driver as we have used different models of machine and if it was, then it would never work.
     - We have set the TFTP block size to default of 1024 (we had it higher as 8192) to rule out the boot image being corrupted on download. It made no difference other than being a lot slower.
     - Compared MD5 hashes for the WIM to rule out corruption.
     - Removed and redistributed the WIM and drivers to different DP's (that it had never been on before)
    The DISM.log on a failed device shows entries like
    CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
    Any advice would be greatly appreciated. This question on
    Dell's forum sounds very similar.
    What we are really struggling with is why would the same WIM, with the same driver package, from the same distribution point, to the same physical machine, work every day for a week the permanently break? Aaargh!
    Thanks everyone,
    Shaun

    Hi,
    Have this problem been resolved? How?
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Renaming offline computer account on AD as part of OSD

    I am looking for an automated solution to a Windows 7 "rebuild" problem and here is the story:
    We periodically have computer hard disk failures and the machines will be rebuilt on a new hard disk at the build center using the model-specific hardware "carcass". Once the hard disk is built, it will be sent over to the affected user and a field
    engineer will swap the hard disks onsite and do the domain join work and anything else necessary so as to have the old computer name back.
    To explain this further, say if the computer which had a hard disk failure is 123 (i.e. the computer name), we build a new Windows 7 machine on a new hard disk with the computer name as 123X. Once this machine is fully built, we need to delete the old 123
    account from the AD and rename the newly built 123X to 123 (and do the domain re-join etc...).
    However, the requirement is that the old 123 computer account should still stay in the domain for some time after the new machine is built (i.e. for data recovery/bit locker operations purposes if needed) which means we do not ideally want to delete the
    old 123 computer account on the AD immediately, instead, we want to rename it as 123XY even though the old 123 computer is no longer physically active.
    Is this technically possible? If so, can it be automated as part of SCCM OSD TS?
    Hope I have not introduced too much of confusion. The problem has been reported by the build team and they have asked me to come up with an automated solution and I have tried to explain the problem above to the extent I have understood it. Currently what
    they do is before deleting the computer account 123 from the AD, they back up its bitlocker recovery key information manually in order to use it later on should the need arise.
    Thanks in advance.

    Hi Garth,
    Owing to the complexity it would have introduced into the build process to differently process new builds/rebuilds/hard disk replacement etc. we ended up ditching that option, instead went for a PowerShell scheduled task which runs every week and dumps the
    bitlocker recovery info into a super-secret location :)
    Below is the script if you are interested....
    #Tweak the below line to point to the OU in your AD org where all the bitlockered computer objects reside
    #It will run recursively against all sub-OUs.
    $SearchBase = "ou=workstations,dc=contoso,dc=ad,dc=local";
    #check if the output folder exists;Create it if it doesn't
    If ((Test-Path -path "$(Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent)\Reports" -PathType Container) -eq $false) {
    New-Item -path (Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent) -name 'Reports' -itemtype directory | Out-Null;
    #set up the output csv name. An example output csv name will be BLR_15032015_Sunday.csv
    $OutputCSV = "$(Split-Path $SCRIPT:MyInvocation.MyCommand.Path -parent)\Reports\BLR_$(Get-Date -format "ddMMyyyy")_$((Get-Date).DayOfWeek).csv"
    Get-ADComputer -filter * -SearchBase $SearchBase -SearchScope Subtree -ResultSetSize $null -ErrorAction SilentlyContinue | Foreach-Object {
    $Compname=$_.name;
    Get-ADObject -Filter 'ObjectClass -eq "msFVE-RecoveryInformation"' -SearchBase $_.DistinguishedName -Properties created,name,msFVE-RecoveryPassword -ResultSetSize $null -ErrorAction SilentlyContinue |
    Select-Object @{Name="Computer Name";Expression={$Compname}},
    @{Name="Date Added";Expression={$_.created}},
    @{Name="Password ID";Expression={$_.name -match '\{.+\}' | Out-Null;($matches[0]).Trim();}},
    @{Name="Recovery Password";Expression={$_."msFVE-RecoveryPassword"}}
    } | Sort-Object -Property @{Expression="Computer Name";Descending=$false},@{Expression="Date Added";Descending=$true} | Export-CSV -force -Path $OutputCSV -NoTypeInformation
    Probably not what you would have been hoping for but it has worked really well for us in the last 6 months and there has never been a lost bitlocker key related incidence escalated by the customer as we always have the backup reports to go back to.
    Apologies, it was impolite of me not to update this thread clarifying what I ended up doing.

  • Win XP to Win 7 - Using OSD - Capturing User data from Profiles

    Hi All,
    I'm having a few issues with capturing users profiles using USMT moving from Windows XP to Windows 7 as part of a task sequence - we use a SMP to save the data but strangely it wont apply the data on Apply state store. The OS deployment works fine but saving
    user's data and moving it too new PC doesnt seem to apply. I am using Stock requests for the task sequence Find user state storage capture user state etc and like wise at the end apply user state and release user state but doesnt seem to work. Are there any
    variables that need to be added to get this working or am i missing something stupid? We do use same PC to image and have mentioned about hardlinking but powers that be want to use SMP. How would this work also if when using Computer association(due to the
    Windows 7 pc not being setup yet)?
    Apologies if im missing something simple

    You are doing what is called a "refresh" OSD scenario...refreshing the OS on the computer while maintaining user state. SCCM automatically creates a computer association in that instance. If an existing Replace (Old to New) computer association
    does not already exist, then it will create a Refresh Computer Association to allow the user state to be restored to the same computer. You wouldn't need to do anything special.
    The key is that you need to have your task sequence be capable of both capturing the user state at the beginning of the task sequence, then laying down the new OS, then doing the restore of the user state...all within the same task sequence.
    If you utilize the MDT integration with SCCM and build an MDT integrated task sequence, this functionality is already built in. Although for simple testing purposes to show the concept, you can simply add to your existing task sequence.
    Your task sequence would need to include the following major sections:
    Capture user state (including the request/release state store tasks)
    Lay down the OS (essentially the components of your regular bare metal imaging task sequence)
    Restore user state (including the request/release state store tasks)
    <p>Jarvis </p>
    <b>Blog:</b> <a href="http://verbalprocessor.com/feed/" target="_blank">
    <img src="http://aka.ms/gmvm2k" border="0"></a> <a href="http://verbalprocessor.comhttp://verbalprocessor.com">http://verbalprocessor.com</a>
    <b>Twitter:</b> <a href="https://twitter.com/VerbalProcessor" target="_blank"><img src="http://aka.ms/iejgcv" border="0"></a>
    <p><font size="1">Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.</font></p>
    <p><font size="1">The postings on this site are my own and don’t necessarily represent my employer’s positions, strategies or opinions.</font></p>

  • UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

    This is kind of long, but here goes...
    We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images.  We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
    thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002  during what appears to be the "Use Toolkit Package" step.  This is after the OS image has already been laid down and after the ConfigMgr
    client has been installed/configured.  The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence.  Error code 0x8007002"  Among other errors...I will post the entire log below...
    After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
    but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure. 
    Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment.  We have a few OSD task sequences built without UDI and those all still work just fine. 
    So, I am at a loss for where the root problem lies.  Any suggestions or assistance would be greatly appreciated.
    Here is the entire SMSTS.log and BDD.log...
    https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
    Thanks
    Richie Tenhet

    your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
    Use Toolkit Package step...
    "Starting Task Sequence Engine . . . "
    "Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
    "Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
    "unknown host (gethostbyname failed)"
    "sending with winhttp failed; 80072ee7"
    "Tried all the available http based locations. SMB based locations will be attempted now."
    "Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
    "Failed to run the action: Use Toolkit Package.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)"
    that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
    around the time of the failure.
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

  • OSD Exits to Ctl-Alt-Del after Reboot from Software Update, leaves Clients in provisioning mode

    We are seeing a problem where the Windows 7 SP1 OSD wrongly exits to the Ctl-Alt-Del screen:  This problem is occuring with about %25 of our Newly Imaged PCs during the Software Updates step of the Task Sequence (of which there is about 9
    outstanding updates), the PCs are rebooted as 4 of these updates finish with COMPLETE_SOFT_REBOOT_NEEDED.
    After the Software Updates Reboot the following errors are found:
    SMSTS.log reports:
      Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)
    UpdatesDeployment.log reports:
      Failed to save an instance of CCM_TargetedUpdateEx1, error 80041033 UpdatesDeploymentAgent 3/04/2013 4:56:39 PM 3080 (0x0C08)
      Failed to get class instance for CCM_TargetedUpdateEx1, error 80041033 UpdatesDeploymentAgent 3/04/2013 4:56:39 PM 3080 (0x0C08)
    ExecMgr.log Reports:
      Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
      Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
      Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
      Failed to connect to machine policy name space. 0x8007045b execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
      Failed to connect to user policy name space execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
    I have checked the logs based on other forum suggestions I can say the following:
    -Network adapter is getting valid address;
    -I do not have a step for "Install Roles and Features";
    -I can apply registry changes for each machine to take them out of Provisioning mode, and after that I dont have any problems - this is far from the solution that I hope for.

    Any update on this as I am struggling with this issue for the past few days ?
    Our image was built last year so when I want to recreate it, it has to do 150 updates. We don't have WSUS updates into SCCM so I had to use a wsf script to get the updates from our WSUS server.
    If I image the computer without doing the updates and do them manually by running the script here is what happens :
    1st execution of the script : 137 updates installed and a reboot is required
    I manually reboot
    2nd execution of the script : 13 updates installed and a reboot is required
    I manually reboot
    3rd execution of the script : 4 updates installed
    I manually reboot
    4th execution of the script : no updates required.
    If I only do 1 execution of the script in my TS : it works fine, it installs the 137 updates but then when the PC is done imaging, it still needs the 13+4 other updates which I don't really like.
    At first, I tried adding this in my TS:
    WSUS 1/3
    System restart (triggered by the TS)
    WSUS 2/3
    System restart (triggered by the TS)
    WSUS 3/3
    System restart (triggered by the TS)
    This stops at step #2, I see it do the 137 updates and then when it reboots, it goes into provisioning mode and doesn't continue. Looks like there is an issue with the reboot so...
    I have tried removing the reboot as follows
    WSUS 1/3
    WSUS 2/3
    WSUS 3/3
    This installs the 137 updates in step #1 and downloads the 13 updates in step 2 and 3 but log file says a reboot is required to install them. The TS then continues but once it meets a System restart triggered by the TS, it doesn't resume the TS and goes
    also in provisionning mode.
    Any idea on why it goes into provisioning mode after installing the updates ? To me, it looks like there is a probably with the state that WSUS puts the computer in, like it is pending reboot but the System restart by the TS doesn't seem to work when trying
    the reboot ?
    Thanks!!!!

  • SCCM 2012 OSD; Not finding driver package during deployment

    I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction.  Specifically I am having trouble with device driver deployment while deploying my reference image. 
    I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image.  I am not sure if it matters, but I manually built a reference
    PC and using capture media (USB stick), I successfully captured my reference image.  I have imported my drivers for the target PC into Config Manager and into a driver package.  The driver package has been deployed to the distribution point
    (DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim.  Within the TS, I added an "Apply
    Driver Package" step and pointed it to the aforementioned driver package.  I added a WMI query to the step as follows
    select * from Win32_ComputerSystem where Model like "HP Probook 6570b%." 
    Incidentally, I did a wmi query on the target PC to verify the model.  I deployed the TS to the unknown computers collection and PXE booted the target PC.  I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
    the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found."  I checked the smsts.log log and found the following:
    Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
    After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
    for deployment.  After more research I have done the following:
    Deleted the Driver Package and recreated it and updated the TS step to point to this package.
    Deleted and recreated the TS along with the driver package.
    Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
    When distributing content I verified it was successfully completed each time as per the console.
    Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error.  If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
    and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
    I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
    Thanks in advance,
    Mike G.

    Thanks for responding.
    Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points.  I checked now (about 12 hours later) and the package is showing it has not finished updating.  I checked the content status and
    it is "waiting for content."  I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1".  This error would occur every 30 min after each time the DP retried to process
    the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
    it retried, the error cleared, however the package status is still waiting for content.  I tried doing a validation on the package but so far there has been no change.

  • Does 2012 OSD get around requirements to get to the MP during the task sequence?

    Currently right now I am working in an environment where we are on SCCM 2007, but will be going to 2012 next year. We are in the process of trying to make it so we can build on a secure network that cannot route to any other network. I am prepared to put
    a DP out on this same network, but the problem I am running into is that during the task sequence starting, it downloads the task sequence from the MP, not the DP as it is not associated with the package. The MP is not on the same un-routable network. We will
    need to have about 6 or so of these, so we do not want to setup 6 MP because now you are looking at not only 6 primary site licenses, but 6 SQL installs (Our environment will not let me get away with doing SQL express for support reasons) which adds up quickly.
    Below is a link to exactly what I am speaking about:
    http://blogs.technet.com/b/configurationmgr/archive/2009/04/16/configmgr-2007-primary-site-mp-is-used-for-the-task-sequence-even-when-deploying-osd-images-to-secondary-sites.aspx
    What I am wondering is if SCCM 2012 OSD was structured differently in a way that access to the MP is no longer necessary during the task sequence process (say for example the task sequence xml is replicated to DPs too)?
    Thanks. 

    My apologizes. I was meaning to say Primary, Secondary Sites. Not MPs. I brought this up to give reference to idea about the boundaries that I am going to have to use to prevent these clients from contacting DPs they they can't route to.
    The idea behind getting off the build network and onto a prod is that security requirements from my companies Infosec require that we limit the amount of traffic on production networks. The idea is that the server be built on the build network, disconnected
    and brought into prod. The whole time the MP would be the same, but the DP would switch based on the prod network they were brought into as DP will reside in these prod networks which will get flipped over by the boundary for the prod subnets. Once on the
    prod network they would be able to contact the MP. 
    I would love to do stand-alone media, this is one of the first roads I started looking down as I have done them in the past for offline builds, but I need the machine to auto assign its hostname from a external servers that will script the build. The build
    process we are trying to put into place will be started from an external website. My first thought was to have it add the machines to a collection and add a variable that would be turned into a task sequence variable during the TS and use it for the hostname
    when it attempt to apply the Windows settings. The only way I think I could get this to work would be to write a script that is executed during the task sequence that would match the MAC address of the machine and assign the hostname by calling on another
    share that is written to by the external website with the MAC and hostnames. The only problem that I cannot get around is that this build process needs to be fully automated and this is for both virtual and physical. I have no problems mounting a stand-alone
    build ISO using a script for VMWare, but the problem starts when I look at the physical and limitations of scripting for both iLo and iDRAC for performing this step. iLo can be done, but iDRAC is limited. 
    As for a reverse-proxy I will not be able to look at that. They have specific requirements against using reverse-proxies in only specific situations and this it not allowed. I got turned down on this one. This requirement is created by a federal regulation
    my company has to follow. 

  • BDD 2007 -- ZTI -- OSD error "The Operating System Installation Failed Unspecified Error (80004005)

    Hi there
    Wonder if anyone can advise me on a BDD 2007 OS deployment issue? (Apologies if this is in the wrong forum, I couldn't see a forum for BDD 2007.)
    First of all, this BDD 2007 server and the OSD config was not done by me. For info, it is part of a SMS 2003 infrastructure.
    I am trying to get the XP Pro build process working. I am led to believe the config has been completed.
    Unfortunately, after booting the pc from the nic, I get an error. This is the order:
    - the 'Initializing Windows PE' splash appears for perhaps 15 seconds
    - very briefly, the text changes to 'Initializing Network'
    - for a second or two only 'Initializing Windows PE' appears again
    - then this error message appears:
    "SMS Operating System Deployment - The Operating System Installation failed. Please contact your system administrator for assistance. Unspecified Error (80004005)"
    I've spent some time looking into this error (80004005) and from what I can gather it possibly means 'access denied'.
    I'm assuming after Windows PE loads the first Task Sequence begins, and if this possibly is where the issue lies?
    One thing I cannot understand - the first Task Sequence (Initialization) has this command line (as do most, with different .wsf file):
    cscript.exe "%SCRIPTROOT%\ZTIGather.wsf" /localonly
    However, I cannot access %SCRIPTROOT% at all, Windows says it can't find it. I can run other variables such as %USERPROFILE%, %SYSTEMROOT%, etc, but cannot open %SCRIPTROOT%.
    Is it simply the case that I should create a new system variable (that has not been created by whoever built the server)?
    Thanks
    John Henry

    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Dv8 and HDX Series OSD Pop Up Solution

     Here are two youtube videos of the grounding procedure to prevent the WiFi button from turning off and on and popping up of the volume, bass and treble OSD.
     There are parts one and two because youtube will not allow anything longer then 15 minutes.
    Before going ahead with this you must remove the battery and adapter and hold the power button down for 60 seconds to dissipate any static in the laptop.
     You must also ground your self out as well by touching a metal electrical appliance. You don't want to shuffle across a wool rug and zap your laptop with the static that you have built up in yourself.
     http://www.youtube.com/user/HaggisCat1#p/a/u/1/8GreyKnF3TM        Part 1
     http://www.youtube.com/user/HaggisCat1#p/a/u/0/X5PLW7ExMQM    Part  2
     Here is also the link to the HP Media Services Library where you can find more videos to remove the speaker cover and hot-key bezel. The Library refers to the hot-key bezel as the "keyboard cover"
     http://h20574.www2.hp.com/default.htm?lang=en&cc=US&hpappid=psml
     Here is the HP firmware update the may correct the problem and this should be tried first.
     ftp://ftp.hp.com/pub/softpaq/sp53501-54000/sp53677.exe      THE FIRMWARE UPDATE ONLY APPLIES TO THE DV8 SERIES.
     http://www.amazon.com/JVCC-CFL-5CA-Copper-Conductive-Adhesive/dp/B000WQ5SZY/ref=pd_bxgy_hi_text_b  Copper Tape
       http://www.amazon.com/Gold-Kapton-Tape-Polyamide-36yds/dp/B0049KTIAU/ref=sr_1_3?ie=UTF8&qid=13133344...  Kapton Tape.
     +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     Update :
       A poster used simple black tape to insulate the bare terminals on the LIF connector and this works well as the aluminum tape will hold it in place. He also used the aluminum tape to hold the folded over tabs in place rather then the kapton tape. This also works well and looks cleaner as it was reported.
     In the videos it shows the tabs are around 3/16 of an inch, it would be beneficial to make them 1/4 of an inch or even larger.
     Thanks to bjoebalance.
     +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     Another update :   it has been reported that placing small sections of fridge magnets have cured the problem. 
      See this post on page 255. The magnets with the paper backing are placed in the center just above the bezel on the speaker grill. Some have also placed them around the WiFi button itself or in both locations.
     http://h30434.www3.hp.com/t5/Notebook-Lockups-Freezes-Hangs/Problem-with-Pavilion-dv8-top-slider-bar...
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     So the bezels do fail _ mine did _ know matter what I did I could not get the WiFi to stop turning itself off and on.
    In may case the solution was to replace the bezel with a new one _ not a used one.
     Everything is fine now, but I will be applying my fix anyway.
     If it had to happen to someone better me then anyone else.
     ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
     If you want to disconnect the bezel, it's best to remove the cable entirely. You don't want this to happen _ see post 58.
     http://h30434.www3.hp.com/t5/Notebook-Hardware/dv8-and-HDX-Series-OSD-Pop-Up-Solution/td-p/816295/pa...

    As far as the actual slide action taking two or three slides, this is normal and on mine it takes two if I start just outside the bars.
     I like to hold my finger either on the plus or minus sign, I find it works better that way.
     You may also try and uninstalling your "quick launch" software, it may improve the OSD action. At present I am running a retail version of W7 and the volume, bass and treble OSD do not depend upon the quick launch software to make it work.
     The volume OSD is in the Media Smart Smart Menu, the mute light is in the IDT High Definition Audio Driver and the bass & treble has it's own program.
     I am glad you like the videos, my little camera's resolution is not that great even at the highest setting, but I think I get the procedure across despite that.

  • OSD fails during WinPE Install drivers - "The hash value is not correct"

    Hello everyone,
    We are facing a strange problem during OSD for one of the hardware models. We are on SCCM 2012 R2, and mainly build Windows 7
    x86 machines on various Lenovo models.
    I can see this problem I have encountered has been discussed elsewhere on this forum (especially SCCM 2007 threads) but not really sure what I have
    observed is the issue being discussed. Here is the problem....<o:p></o:p>
    We have a laptop (Lenovo x240) which has been building perfectly fine for as long as I can remember. However since last 2 days when I try to build
    the same model, we get the above error during the driver installation stage (in WinPE).<o:p></o:p>
    I referred to some of the other threads and MS blogs where they say file names with extended ASCII character may break the hash of the files (packages)
    being downloaded during OSD resulting in the error(http://blogs.technet.com/b/smsandmom/archive/2008/10/09/configmgr-2007-smsts-error-hash-could-not-be-matched-for-the-downloaded-content.aspx).
    The point is I have manually gone into the Command prompt (F8) during driver downloading stage (right after apply OS image) and checked that the drivers are getting downloaded fine (but there is not enough time for me to check individual sub folders for the
    extended ascii character problem). When it comes to installing the drivers, the TS fails and immediately the whole of the driver packages folder under D:\_SmsTaskSequence\Packages\PackageID folder becomes empty.
    There is nothing much logged in the ts log either.<o:p></o:p>
    Any thoughts? The only thing that has changed in our environment in the last 2 weeks is that we have upgraded from SCCM
    2012 SP1 to R2(CU3). All the other models have built ok since and only X240 is running into this issue.
    Would recreating the driver pack be an option here? I also understand that we also can configure the TS to refer to the package media directly from
    the DP share (instead of downloading) but we would rather not get into that at this stage as we have not tested the TS with that configuration (it might open another can of worms with package command lines etc.)
    One more point - This "The hash value is not correct" error message is only logged on the SCCM status messaging system (which can be viewed
    under the Monitoring wunderbar - Status Message Queries). I do not find it on the ts log file interestingly.
    Any help is much appreciated.<o:p></o:p>

    I've only seen this once before in a ConfigMgr 2012 RTM environment and after fighting it for a few days I ended up simply recreating the driver packages.
    -Nick O.

  • Proper method to install R2 CU1 client during OSD?

    As of right now I deploy the client using an MDT 2013 OSD Task Sequence with the built in task "Setup Windows and ConfigMgr" with the following installation properties:
    SMSMP=server.domain.local SMSCACHESIZE=12000
    However after imaging the client version remains at 5.00.7958.1000, but I thought with CU1 some components should display a more recent version number.
    Do I need to add a xcopy step for the latest client hotfix during the OSD, then use the PATCH property during the client install?  For example: PATCH="D:\Hotfix\configmgr2012ac-r2-kb2938441-x64.msp"

    That's one method yes.
    See Justin Chalfant's post here for some info http://blogs.technet.com/b/jchalfant/archive/2014/04/26/patchconfigmgr2012x86andx64clientsduringatasksequenceusingthepatchproperty.aspx
    Cheers
    Paul | sccmentor.wordpress.com

Maybe you are looking for

  • Add Registry in WebDeploy package

    I have read some articles stating that a web deploy package can contain registry information. Can someone let me know how to include registry information into this package?

  • Setting source with a MediaContainer

    I agree with Jesse Warden in another thread where he complained about the removal of MediaPlayerSprite. That being said I was able to easily change my player to work with Sprint 10. The HelloWorld example is helpful, but the video source needs to be

  • How to make color from greyscale images?

    I have got a few photos into greyscale. How can I make them back to any color I want? thanks,

  • Adobe Standard 9 - Typewriter in Browser

    We currently have adobe 9 standard, and the typewriter function works just fine if you open a PDF directly We are paperless and we open PDF's from our system and the typewriter is not available if we mark Display PDF in Browser If we unselect it then

  • Common Name on SSL certificate

    I was wondering if anyone can tell me whether the Common Name on the SSL certificate (which I plan to request from Verisign) MUST be the same as the name of the Sun One 6.0 SP6 web server instance. For example, if my server name in the Servers tab is