SCCM 2007 R3 / Offline USB Media

Has anyone come across a issue where they are having problems installation msi applications from a usb media deployment (created using 'Create Task Sequence Media')?
The task sequence runs fine, without any issues, if run from SCCM server/DP
If I create a external usb media, I can boot into Windows PE, it applies the wim and starts to install the software. The task eventually fails with 1612 error, unknown media..
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Looking for sourcelist for product {AC76BA86-7AD7-1033-7B44-AB0000000001}
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Adding {AC76BA86-7AD7-1033-7B44-AB0000000001}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Now checking product {AC76BA86-7AD7-1033-7B44-AB0000000001}
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Media is enabled for product.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Attempting to use raw LastUsedSource value.
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Source with value name 'LastUsedSource' is blank
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing net source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing media source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\Media 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Processing URL source list.
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2: -2147483647 3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: Note: 1: 1706 2:  3: AcroRead.msi
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Failed to resolve source
MSI (s) (D4:B4) [13:51:20:999]: MainEngineThread is returning 1612
Anyone with any ideas?
This seems to happen to all the packages installed from the usb media

The boot order is already set to boot from HD first
Running a normal PXE OSD build using the same task sequence works.. i only have issues when i used use a standalone media of the task sequence (i've tried both USB and DVD)
For some reason once the Win7 image is applied, the next step in the task sequence is to install applications..
The first application installation task eventually fails with 1612 error, unknown media..
MSI (s) (D4:B4) [13:51:20:999]: SOURCEMGMT: Looking for sourcelist for product {AC76BA86-7AD7-1033-7B44-AB0000000001}

Similar Messages

  • SCCM 2007 - task sequence - prestaged media - self-signed certificates - error message 'Certificate has expired for this media'

    Hi there
    Quick scenario.
    We have created a task sequence prestaged media .wim file (SCCM 2007, client OS is Windows XP).
    Recently some of these swap-out machinses, on delivery and start up, have started showing this message:
    'Certificate has expired for this media'.
    This is because the self-signed certificate created during the prestaged media creation process has expired.
    My question is: is it possible to mount the image using dism or imagex and then inject an updated sertificate?
    Best regards
    John

    the disk that has the prestaged media applied must be the boot partition.
    create a task sequence to stage the prestaged media. In this task run a format and partition step which configures both the system disk and the os disk, though make the os disk the active boot partition. Then apply the prestage wim.
    On your deploy task, somewhere after the OS has applied create a group that runs only if the media is OEM (from memory  _SMSTSMedia =
    OEMMedia)
    in this group run the command bcdboot C:\Windows /s F: /f ALL where f: is the drive letter assigned to the system disk, then run another step that removes the drive letter and reboots. The deploy task will now continue and you will be booting to the system
    partition.
    So I wanted to get back to working on this issue.  I noticed that when I said it Worked that it was actually still booting from C drive instead of the reserved partition.  For the past few days I have been trying to get the prestaged to work like
    a network deploy but fail every time.  I cannot get the prestaged to boot from any other partition other then the partition where windows was imaged too.
    So where I am at today.  When I do as suggest above the D drive (The reserved Boot volume) return on reboot. it will not stay hidden.  also the OS is till booting from C and does not change to the D drive or no drive letter drive with the above
    commands.  I think there is some other command missing that tells it to boot from a new location that is not bcdboot.
    Has anyone seen any guides for how to use prestaged and bitlocker enabled task sequence?  I think that would help me figure out my current issues as with bitlocker you must have this other partition.

  • SCCM 2007 standalone USB is prompting for media

    Hello.  I have been creating standalone media on USB for a while.  This week I needed to create new standalone media with an updated image and 3 new packages. 
    I modified the same TSs in SCCM 2007 I always use to create the standalone media on USB.  The USB sticks are 16 gig and I diskpart like usual. 
    After creating the new standalone media on USB, I tested the sticks. 
    It deploys the image and drivers successfully but when it is attempting to install the packages (applications) I get a popup asking me to insert the media for the install. 
    I checked the USB stick and the packages are all there and I can launch the packages successfully. 
    I also advertised the TSs and can deploy via advertisement.
    Any ideas?  I have to get these done as soon as possible.  WIll appreciate the help.
    Charles

    Did you find the source of the problem? I am running into the same issue but it appears to only occur on certain brands or models of USB stick.
    Also, unplugging the stick, plugging it back in, and clicking OK on the media prompt allows the process to continue.
    BWitz

  • Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

    Hi,
    I am trying to deploy Office 2013, along with SP1, in the following order:
    1. Prompt to close all office apps and continue (vbs)
    2. Installation of Office 2013, using modified msp.
    3. Restart
    4. Installation of SP1 with command line /passive /norestart.
    I am doing this all through a package I created in SCCM 2007 R2.
    The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
    Manual installation, through command prompt, with the same switches works fine.
    The error is only when remotely deploying.
    The system is Windows 7 X86 with latest SP.
    Please help!

    Hi,
    Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
    By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
    http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
    (Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • ConfigMgr client no longer installing during task sequence SCCM 2007

    I've been trying to create an image and deploy an image of Dell Latitude E6430 laptops that while the deployment of the image works it does not install the SCCM client (configmgr client).  This used to work in my environment but no longer does. 
    I can deploy the client manually either through the SCCM console or from the client itself.  But during the task sequence deploying a captured image it does not install and thus and software I need installed as part of the TS does not get installed. 
    But the rest of the image works fine including driver deployment, sysprep, domain join, etc.  If I watch the job run I do see it start downloading the SCCM client during the TS job but then reboots and that's it.  Not sure where to look to see what
    could be going on.  I read somewhere about a possible driver issue but if the rest of the TS works and all drivers install then how could it be that?  If anyone has any suggestions I would greatly appreciate it!  Oh by the way I'm still using
    SCCM 2007, haven't upgraded yet.  Thanks!
    Brian Stein

    What's interesting is in the smsts.log file it shows that part of the TS completed successfully.  So I'm going to try importing the cab files just to make sure I'm all set with that and I will change my TS to NOT auto apply drivers but rather I'll point
    directly to the new driver package I created from the extracted cab and will follow up then.  If interested a copy of the smsts.log file found inside the _SMSTaskSequence folder on the client machine (2/3 of the way down I 'bolded' the line where it seems
    to say the configmgr client step succeeded:
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ara.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ara.exe ]LOG]!><time="13:49:12.259+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-chs.exe ]LOG]!><time="13:49:12.305+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-cht.exe ]LOG]!><time="13:49:12.337+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-csy.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-csy.exe ]LOG]!><time="13:49:12.352+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-dan.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-dan.exe ]LOG]!><time="13:49:12.368+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-deu.exe ]LOG]!><time="13:49:12.399+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ell.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ell.exe ]LOG]!><time="13:49:12.415+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-enu.exe ]LOG]!><time="13:49:12.446+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-esn.exe ]LOG]!><time="13:49:12.508+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fin.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fin.exe ]LOG]!><time="13:49:12.539+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fra.exe ]LOG]!><time="13:49:12.555+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-heb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-heb.exe ]LOG]!><time="13:49:12.586+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-hun.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-hun.exe ]LOG]!><time="13:49:12.602+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ita.exe ]LOG]!><time="13:49:12.633+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-jpn.exe ]LOG]!><time="13:49:12.649+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-kor.exe ]LOG]!><time="13:49:12.680+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nld.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nld.exe ]LOG]!><time="13:49:12.695+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nor.exe ]LOG]!><time="13:49:12.727+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-plk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-plk.exe ]LOG]!><time="13:49:12.758+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptb.exe ]LOG]!><time="13:49:12.773+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptg.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptg.exe ]LOG]!><time="13:49:12.805+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-rus.exe ]LOG]!><time="13:49:12.820+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-sve.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-sve.exe ]LOG]!><time="13:49:12.851+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-trk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-trk.exe ]LOG]!><time="13:49:12.867+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/client.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/client.msi ]LOG]!><time="13:49:13.756+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp to C:\_SMSTaskSequence\Packages\RPS00005\i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp ]LOG]!><time="13:49:13.787+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msrdcoob_x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/msrdcoob_x86.exe ]LOG]!><time="13:49:13.819+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
    thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msxml6.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/msxml6.msi ]LOG]!><time="13:49:13.881+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wimgapi.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wimgapi.msi ]LOG]!><time="13:49:13.897+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsinstaller-kb893803-v2-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsinstaller-kb893803-v2-x86.exe ]LOG]!><time="13:49:14.084+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsupdateagent30-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsupdateagent30-x86.exe ]LOG]!><time="13:49:14.302+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wmirdist.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wmirdist.msi ]LOG]!><time="13:49:14.318+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe ]LOG]!><time="13:49:14.427+300" date="02-26-2014"
    component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe ]LOG]!><time="13:49:14.505+300" date="02-26-2014"
    component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe ]LOG]!><time="13:49:14.583+300" date="02-26-2014"
    component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe ]LOG]!><time="13:49:14.661+300" date="02-26-2014"
    component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msrdcoob_ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msrdcoob_ia64.exe ]LOG]!><time="13:49:14.692+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
    thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msxml6_ia64.msi to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msxml6_ia64.msi ]LOG]!><time="13:49:14.911+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/windowsupdateagent30-ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/windowsupdateagent30-ia64.exe ]LOG]!><time="13:49:15.316+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/sccm_client.bat to C:\_SMSTaskSequence\Packages\RPS00005\sccm_client.bat ]LOG]!><time="13:49:15.332+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe ]LOG]!><time="13:49:15.363+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe ]LOG]!><time="13:49:15.394+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe ]LOG]!><time="13:49:15.410+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe ]LOG]!><time="13:49:15.535+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe ]LOG]!><time="13:49:15.566+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe ]LOG]!><time="13:49:15.597+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe ]LOG]!><time="13:49:15.613+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe ]LOG]!><time="13:49:15.675+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe ]LOG]!><time="13:49:15.706+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe ]LOG]!><time="13:49:15.737+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe ]LOG]!><time="13:49:15.769+300"
    date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msrdcoob_amd64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/msrdcoob_amd64.exe ]LOG]!><time="13:49:15.784+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
    thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msxml6_x64.msi to C:\_SMSTaskSequence\Packages\RPS00005\x64/msxml6_x64.msi ]LOG]!><time="13:49:16.112+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
    file="downloadcontent.cpp:1177">
    <![LOG[Downloaded file from
    http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/windowsupdateagent30-x64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/windowsupdateagent30-x64.exe ]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook"
    context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
    <![LOG[Download done setting progress bar to 100]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1182">
    <![LOG[c:\_smstasksequence\packages\rps00005\i386 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\ia64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\x64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\i386\bits20 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\i386\bits25 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix is a directory. Setting directory security]LOG]!><time="13:49:16.829+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix\kb977384 is a directory. Setting directory security]LOG]!><time="13:49:17.297+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\ia64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.407+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[c:\_smstasksequence\packages\rps00005\x64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.516+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
    <![LOG[Content successfully downloaded at C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3131">
    <![LOG[Copying SMS client package source from "C:\_SMSTaskSequence\Packages\RPS00005" to "C:\_SMSTaskSequence\OSD\RPS00005".]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:1504">
    <![LOG[Locating architecture-specific OSDGina.dll]LOG]!><time="13:49:17.687+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:428">
    <![LOG[Successfully copied file OSDSETUPHOOK.EXE to C:\WINDOWS\SYSTEM32]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
    <![LOG[Successfully copied file TSProgressUI.exe to C:\WINDOWS\SYSTEM32\_SMSOSDSetup]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
    <![LOG[Successfully copied file tsres.dll to C:\WINDOWS\SYSTEM32\_SMSOSDSetup\1033]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
    <![LOG[Saving desktop wallpaper information.]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1553">
    <![LOG[Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3431">
    <![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\RPS00005 before releasing]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3438">
    <![LOG[Delete source directory C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3461">
    <![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3471">
    <![LOG[Exiting ConfigureEx: 0x00000000]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1592">
    <![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
    <![LOG[Installing hook to 'C:\WINDOWS']LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="setupwindows.cpp:785">
    <![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:229">
    <![LOG[Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:707">
    <![LOG[Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:805">
    <![LOG[Installing OSD setup hook]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="osdsetuphook.cpp:276">
    <![LOG[Setup hook install completed successfully]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="vistasetuphook.cpp:111">
    <![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
    <![LOG[OfflineRegistry::Init("C:\WINDOWS")]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:168">
    <![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
    <![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2]LOG]!><time="13:49:18.545+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
    <![LOG[CurrentControlSet is mapped to ControlSet001]LOG]!><time="13:49:19.169+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:215">
    <![LOG[SMS Client is not installed]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1633">
    <![LOG[Unloading offline SOFTWARE registry hive]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:270">
    <![LOG[Unloading offline SYSTEM registry hive]LOG]!><time="13:49:19.263+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:284">
    <![LOG[Exiting with code 0x00000000]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1751">
    <![LOG[Process completed with exit code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3010">
    <![LOG[Successfully complete the action (Setup windows and ConfigMgr) with the exit win32 code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3036">
    <![LOG[Sending status message . . .]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:292">
    <![LOG[Send a task execution status message SMS_TSExecution_ActionCompleteInfo]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:314">
    <![LOG[MP server SCCM1.ROSNET.ROSLYNSCHOOLS.ORG and port 80. SSL=false. CRL=false.]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:458">
    <![LOG[Site code: RPS]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:489">
    <![LOG[Client machine name: new6430]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:494">
    <![LOG[Client Identity: GUID:EBA20587-9DCD-4F19-B999-F6FA0E56D6CD]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:496">
    <![LOG[Advertisement ID: RPS20136]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:505">
    <![LOG[Package ID: RPS000E1]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:507">
    <![LOG[Sending StatusMessage]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:3806">
    <![LOG[Formatted header:]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>727ba42b-9664-4eea-8690-e285a795b870</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-02-26T18:49:19Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="4220"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80  CCM_POST /ccm_system/request]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:7446">
    <![LOG[The request has succeeded. 200 OK]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="libsmsmessaging.cpp:7734">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
    <![LOG[Clear local default environment]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:807">
    <![LOG[The action (Setup windows and ConfigMgr) requested a retry]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:263">
    <![LOG[Reboot to local harddisk]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:458">
    <![LOG[_OSDGinaIsConfigured variable set to TRUE]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:537">
    <![LOG[_SMSTSServiceStartType variable set to ]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:549">
    <![LOG[Calling RebootSystem()]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:567">
    <![LOG[OSD type of task sequence. ignore the service window setting]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:669">
    <![LOG[Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
    <![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="13:49:19.419+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:386">
    <![LOG[Set a global environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:414">
    <![LOG[Save the current environment block]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:833">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.450+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
    Brian Stein

  • Photoshop Elements 8.0: deplovment with SCCM 2007

    Hello
    We are currently planning the transition to Windows 7 Enterprise.
    The deployment will take place with MS SCCM 2007 - we could not find any policies regarding this case.
    We need to know if Photoshop Elements 8.0 with the following client applications, SCCM and standard user-rights is running.
    Used software products / local application deployed on clients:
    • Microsoft Windows 7 Enterprise
    • Internet Explorer 8.0
    • Adobe Flash Player 10.0.32.18
    • Adobe Shockwave Player 11.5.2
    • Adobe Acrobat Reader 9.2
    • Windows Media Player 12.0
    • Microsoft Office 2007 Enterprise mit SP2
    • Sun Java Runtime Environment (JRE) 6.17
    • Microsoft .NET Framework 3.5
    • Ghostscript 8.7
    • Software-Deployment: Microsoft SCCM 2007 R2 SP2
    • Server-Plattform: Microsoft Windows Server 2008R2
    • Standard User-Rights
    We ask for verification of requirements, whether the necessary conditions are met by PSE 8.0.
    Best wishes,
    Simon

    Hi Simon,
    I would request you to contact the Adobe Tech Support/Customer Care team and they should able to provide a confirmation on these queries.
    As per my knowledge, we dont impose any explicit restrictions on PSE working with Ms SCCM 2007/Server 2008/ or with Standard User Rights.
    But for installing PSE and doing a certain operations, you need to have admin rights.
    Again, I would request you to get in touch with support team and get a confirmation.
    Regards,
    Ankush

  • WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

    I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
    Whilst doing this I came across the following issue:
    The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
    the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
    Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
    the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
    So, when I come to update the client from 2007 to 2012, the following occurs
    The Client uninstalls, and the GPO policy settings for Windows Update are removed.
    Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
    for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
    As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
    maintenance windows.
    I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
    new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
    What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
    Any help would be appreciated.

    First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
    to it. Approving updates in WSUS is unsupported for ConfigMgr.
    What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
    need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM 2012 client push to SCCM 2007 clients

    Hi,
    I'd like to upgrade SCCM 2007 clients to SCCM 2012. Their computers appear in SCCM 2012.
    I could select them and then select "install client" but there are about 400 to upgrade, some or online some not.
    Will the process of upgrade run when the offline clients get online?
    J.
    Jan Hoedt

    If your clients are member of an Active Directory, you could also use a startup script to update the client.
    Jason has a very popular script you can use:
    http://blog.configmgrftw.com/configmgr-client-startup-script/
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
    @ronnipedersen

  • Stand alone USB media

    I'm attempting to create some stand alone USB media to deploy a full image and TS apps offline.  The USB's create successfully, but all of the application package folders are empty and when a system is deployed, it only has what was captured in
    the WIM file and not the TS applications. The folders containing the drivers have all the driver files.  Am I missing something?
    Thanks

    So it seems that the USB's must be able to contact the DP to install the TS apps.  How do you create a USB that can deploy the complete TS offline?

  • SCCM 2007 Inventory of Printer, Scanner, E-Signature Pads, etc

    Okay, I cannot seem to find any info on this anywhere and if it does exist it is ridiculously ambiguous or vague.
    PLEASE tell me how can I go about inventorying printers, scanners and other devices such as e-signature pads via SCCM 2007?
    I work in a healthcare environment and I NEED to get this information to the Asset Management Office.
    I know that I can extend the SMS_DEF.mof file Win32_Printer class, which I will do, but how do I go about doing that for scanners and other devices like e-signature pads?
    Would I use a NOIDMIF file? If so, what is the best tool to create one (MIFGEN)? After the creation of the MIF do I need to then save the ismif32.dll and ismifcom.dll files in their proper places for the MIF to be inventoried or are these two files
    only used in conjunction with package deployments (software advertisements) for successful installs? Do I then create a script to keep creating the MIF?
    Why is this soooooooo ridiculously convoluted when it shouldnt be?
    I need help please
    Thank you

    The only classes I found that may be useful are win32_pnpentity, and\or win32_usbdevice. I'm leaning toward just using the RegKey to MOF tool and see if a unique location within the Registry can be identified for the devices and then add the data to SMS_DEF.mof
    and Configuration.mof. I guess what I am trying to find out from this forum is can devices be identified on a computer system by manufacturer, model, etc. even if a generic driver is installed? Isn't the identity of the hardware device dependent on the driver
    that's installed for the device, or can a device be identified just by being plugged in, somehow? Let's make this simple. If you were tasked by your employer to find out what computers in your organization had the following devices installed, how would you
    go about doing it? By the way, assume all devices are USB. Also, I know I can use the Win32_Printer class and I already have that enabled in SMS_DEF.mof, but I'm just throwing in the printer below for good measure. The hypothetical devices are: Printer, Scanner,
    and SigPad. As always, thanks for your help, I much appreciate it.

  • SCCM 2007 Added update to search result, but don't wont to install them

    Hello everybody,
    I have some problem with my sccm 2007. Sccm added updates on the client machine but don't wont to install them. Here is my windowsupdate.log. Any help would be appreciate!
    2014-02-03 12:04:06:825
    784 350
    AU AU received policy change subscription event
    2014-02-03 12:04:36:861
    2200 1980
    COMAPI -------------
    2014-02-03 12:04:36:861
    2200 1980
    COMAPI -- START --  COMAPI: Search [ClientId = CcmExec]
    2014-02-03 12:04:36:861
    2200 1980
    COMAPI ---------
    2014-02-03 12:04:36:907
    2200 1980
    COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]
    2014-02-03 12:04:36:907
    784 bb4
    Agent *************
    2014-02-03 12:04:36:907
    784 bb4
    Agent ** START **  Agent: Finding updates [CallerId = CcmExec]
    2014-02-03 12:04:36:907
    784 bb4
    Agent *********
    2014-02-03 12:04:36:907
    784 bb4
    Agent  * Include potentially superseded updates
    2014-02-03 12:04:36:907
    784 bb4
    Agent  * Online = Yes; Ignore download priority = Yes
    2014-02-03 12:04:36:907
    784 bb4
    Agent  * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"
    2014-02-03 12:04:36:907
    784 bb4
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-02-03 12:04:36:907
    784 bb4
    Agent  * Search Scope = {Machine}
    2014-02-03 12:04:38:954
    784 bb4
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-02-03 12:04:38:954
    784 bb4
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://sccmprod.domain.local:80/ClientWebService/client.asmx
    2014-02-03 12:04:47:891
    784 bb4
    Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    2014-02-03 12:04:50:506
    784 bb4
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-02-03 12:04:50:506
    784 bb4
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://sccmprod.domain.local:80/ClientWebService/client.asmx
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {4AE85C00-0EAA-4BE0-B81B-DBD7053D5FAE}.104 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {726B7201-862A-4FDE-9B12-F36B38323A6F}.104 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {C5306702-92EC-4E99-9C77-2B70FB60078B}.101 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {7647D502-6E6F-4B6F-8E17-030168FB344E}.202 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {26928006-BF0E-4806-B5AA-489F64CC863A}.201 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {C5171A07-B024-44B4-B74A-A2EC2EEC177C}.102 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {505FDA07-B4F3-45FB-83D9-8642554E2773}.200 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {E1C9C708-3EA9-411C-A7C1-AC8AAC284912}.200 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {1FE1AC0A-7B22-470B-A317-5DA507385409}.101 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {9DB82D0B-5611-4BC1-A4B8-432FE1A3CC43}.201 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {F2C4640C-7687-4250-83D0-62DE1570DD9B}.103 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {567D7A0D-7F11-4C75-BA80-E7DD1B88FBE3}.105 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {D5FD720E-0F2C-4363-AA87-6AD4A6D11B0E}.106 to search result
    2014-02-03 12:04:51:090
    784 bb4
    Agent  * Added update {BE1A890E-593C-4EB2-9ADE-A09B4E8AD0D5}.202 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {22091E0F-3395-4CF9-9F3D-4AC28BD868AD}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {AEF6280F-8C4D-4804-9913-407582227E75}.202 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {E923690F-B6CD-442D-8CBA-EA162C00FB18}.202 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {55F1750F-564A-4E7C-962C-289818F647DD}.202 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {48993210-7C75-4DC4-917C-0BF6CCA5C60D}.106 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {FB2F4410-5A9D-4D71-A766-A39C095ADD2A}.106 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {609AEF10-0A3C-4484-BD38-86BB38E3EFA3}.104 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {A1893712-C814-4AC9-AEB3-4292A63EF2B8}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {965F4712-FC2F-4AF6-A80A-909211E12B74}.101 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {FDA58512-32F3-4A5D-A5C4-05A193E037D4}.103 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {B4413613-7062-4F6B-A1E4-7A957409A51F}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {C8514613-8E11-41C0-919C-DB7ECC292402}.100 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {9334B915-72B1-4F60-8885-4C327D7CC433}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {3E606416-36F7-4CAC-86A1-C3839368767E}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {6CFB7D17-F556-423A-B052-0A1F0463572E}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {53F2CC17-4951-4D4C-920F-4E44445F1EE2}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {3A6D1E19-0A32-4128-A2EB-72FCAC4C058C}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {3F15001A-A051-4CEF-8642-FF241D063C9A}.101 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {6AA7561A-7EBF-4601-B040-D73804C38356}.101 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {B89EC71A-1103-4EA7-B123-1C4D2E23F97A}.101 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {6FF0041B-435E-42BA-87DA-9F021C655E41}.103 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {594A6A1B-58C4-4664-B5D1-4337F8633458}.105 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {86C0F41D-6B1D-43D1-97D6-023C5B7C3343}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {5A88841E-DE21-4595-A5E4-49AE13640D3C}.104 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {3F6E4422-97A1-4485-A586-104B65B36C76}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {07B23623-9428-438E-8867-7348BBB95AAF}.202 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {023BB023-490F-4DF3-BCAA-9521EE8B5847}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {A2CDBA23-37CF-48C6-8182-16305985A886}.102 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {9E280124-F061-4371-8DBE-0F960957277D}.103 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {FE133824-41AF-4F69-B146-B8EB6A6505C0}.201 to search result
    2014-02-03 12:04:51:091
    784 bb4
    Agent  * Added update {1BB3DE24-0D76-4D59-9B9E-556722BFE852}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {175E3625-729A-4B66-AA17-BF492524A1C5}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {E023B326-53E4-4DC1-AF6B-FE28290F7D9B}.104 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {6E03D226-B005-4BE7-8254-7C1760886BFD}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {3D250F27-F8DA-4616-82E8-B3EC16AF2DBC}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {AD43B627-B2C6-4B26-BEEF-02BDB1C4A5FE}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {C7DB1D28-9160-4E63-9EAE-2C7DF322DC00}.105 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {21ED7B2A-F1CA-4865-9FFE-AC527BFDBD8C}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {8D7C892A-0F79-406C-91ED-2A3B2CBE122D}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {1C82B52A-6679-4D70-BE61-BC3E1F6AD4F5}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {6547EC2A-8A7C-467B-9045-0DE89B6856B5}.104 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {202C2C2C-9BB6-453B-9A75-3E80F1AD981D}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {81A49D2C-314B-4A5A-BB6C-9D52A2707735}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {41346B2E-35C4-45C5-9F82-9B70FE9253CB}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {D0FBAC2F-D08F-4A7B-A826-92B1C5AE0BC5}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {AF347830-F2BA-44FB-9429-539921038509}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {A448DD32-C91B-414D-9EFE-465A92AC4642}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {E31F6B34-7F48-4226-A566-04ECC2CBDE48}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {7725B934-3206-441D-90A6-824BAFC0F4EF}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {E0840035-6B21-4554-A6E9-2FFEBC99D9AA}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {70F4F236-0248-4E84-B472-292913576FA1}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {EAA48E38-404A-479B-8957-D7D50AF86918}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {0989F038-54B4-4085-81EA-AA078B633748}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {546CD439-B7C8-45E9-BE72-71493E296807}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {3B82CD3B-0163-4185-8FF5-7D18C05D2267}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {66EE0B3C-1093-401B-8F21-70CD31FD46BA}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {84A1813C-A410-42C4-B875-7CA1C4A5ACC6}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {C499223D-2F22-4626-BBE5-F5A35E7A5854}.204 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {EC1C253D-A3C5-49FB-A56A-9F2EEB223A1D}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {D5B0233E-30E5-4C79-844C-8D07FCADF5CE}.103 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {2655493E-0518-4FB7-9AE6-221D3FAF2C9D}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {3739A53E-845D-4945-9A5F-F5CE38AFCB56}.102 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {2908BF3E-E6D4-4789-9908-E03A0A29AE8E}.201 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {50E1A53F-E351-47A0-BAD4-1B0D223AE629}.200 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {0C737C40-B687-45BC-8DEB-83DB8209B258}.101 to search result
    2014-02-03 12:04:51:092
    784 bb4
    Agent  * Added update {62498940-D04D-4769-AF9A-F4CEC3A927D4}.104 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {48BEEF41-9D2D-4E72-9A61-59F98B12C07A}.204 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {CE09B442-0473-400A-82AE-9CD91C8D76EA}.200 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {0EEBE242-F0AD-4A1A-8796-4BFB54642198}.202 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {F3C64D43-89FB-452F-A7D5-60C1DC0ECF96}.102 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {41987343-1244-4F4E-8585-B1CCA27E48BE}.104 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {B9866145-A3EC-4B3C-A3D2-7203F04DF9FD}.101 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {CC74BC46-3001-4DB6-A714-B26660C0DFDB}.102 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {6D435D48-E94B-4C1F-AF51-E57CF310271E}.202 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {5CC5D348-10B2-4EB6-B446-B0F814D5B80E}.101 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {ED981249-8D8F-42A1-87DB-0AB5C07430B2}.201 to search result
    2014-02-03 12:04:51:093
    784 bb4
    Agent  * Added update {F939194A-E1AE-44D7-A6CA-33FE0891CE46}.102 to 
    2014-02-03 12:04:51:108
    784 bb4
    Agent  * Found 276 updates and 71 categories in search; evaluated appl. rules of 1302 out of 2025 deployed entities
    2014-02-03 12:04:51:149
    784 bb4
    Agent *********
    2014-02-03 12:04:51:149
    784 bb4
    Agent **  END  **  Agent: Finding updates [CallerId = CcmExec]
    2014-02-03 12:04:51:149
    784 bb4
    Agent *************
    2014-02-03 12:04:51:170
    784 bb4
    Report REPORT EVENT: {1E4B028B-0DFE-436E-AF9F-3F42A300EEC6}
    2014-02-03 12:04:51:127+0100 1
    147 101
    {00000000-0000-0000-0000-000000000000}
    0 0 CcmExec
    Success Software Synchronization
    Windows Update Client successfully detected 276 updates.
    2014-02-03 12:04:51:170
    784 bb4
    Report REPORT EVENT: {46820305-3D31-42E7-9827-D538BDF0BA2D}
    2014-02-03 12:04:51:127+0100 1
    156 101
    {00000000-0000-0000-0000-000000000000}
    0 0 CcmExec
    Success Pre-Deployment Check
    Reporting client status.
    2014-02-03 12:04:51:172
    784 bb4
    Report CWERReporter finishing event handling. (00000000)
    2014-02-03 12:04:51:172
    2200 1980
    COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = CcmExec]
    2014-02-03 12:04:51:350
    2200 1980
    COMAPI  - Updates found = 276
    2014-02-03 12:04:51:350
    2200 1980
    COMAPI ---------
    2014-02-03 12:04:51:350
    2200 1980
    COMAPI --  END  --  COMAPI: Search [ClientId = CcmExec]
    2014-02-03 12:04:51:350
    2200 1980
    COMAPI -------------
    2014-02-03 12:04:56:149
    784 bb4
    Report CWERReporter finishing event handling. (00000000)

    Hi friend,
    I like to answer on postings like yours, its a good exercise for my work and its really cool to have some topics where all people here will contribute.
    JohnnyS is a friend of mine which is working with me at our office and we talked a little bit about your problem.
    So his opinion was to use the UBCD4Win and work with that option.
    The advice of him was:
    Grab a USB-HDD case and put one drive in it and boot with UBCD4Win. Then copy all important data to a folder on the external HDD and remove the uneeded data on it. Just the important data!
    Make a backup of your data on the external drive from both HDDs. I hope you will have enough free space.
    Format the drive in your machine and recover it. Install the system as usually on your first HDD.
    Then put the data to where you want.
    So I am not sure if I understanded your question right, a little bit more explanation would be useful. I think that will be a long thread. ;)
    Greets

  • SCCM 2007 Drivers not importing

    I am having an issue with SCCM 2007 and some Lenovo T440-T540 Drivers
    The first issue I have is that the Win PE image doesnt recognize that I have a valid network driver on it. (USB OSD comes back with "not a valid network adapter found") even though I have verified that the Intel driver is there. 
    2) When I went to re-import the drivers I get an error stating the drivers are already imported. I have removed the drivers from the admin console and you cannot see them anywhere. Thinking I might have to go somewhere in the DB to nuke them out. 
    I have removed the drivers from sccm by just selecting and deleting the package is also gone from the DP. Not sure how i can re-import them into sccm for them to show up under OSD/Drivers/T44-T540. I have verified the boot image has the correct drivers on
    it for network. 

    The first issue I have is that the Win PE image doesnt recognize that I have a valid network driver on it. (USB OSD comes back with "not a valid network adapter found") even though I have verified that the Intel driver is there. 
    I have removed the drivers from sccm by just selecting and deleting the package is also gone from the DP. Not sure how i can re-import them into sccm for them to show up under OSD/Drivers/T44-T540. I have verified the boot image has the correct drivers on
    it for network. 
    If WinPE (your boot image) is returning "no valid network adaptor found", you need to diagnose that. Enabling F8 support can help with that. The driver store in the db, and driver packages, are not directly relevant to which drivers are (or are not) injected
    into your boot image. (The driver store in the db, and driver packages, are relevant to the post-image-apply steps, when FullOS is running)
    Have you followed the steps here?:
    http://technet.microsoft.com/en-us/library/bb680705.aspx
    Your site server is CM2007SP2 ?
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Lenovo X1 Carbon PXe boot errors with SCCM 2007

    I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1.  I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
    Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
    Now, I have the the following drivers in the boot.wim file:
    x86 -
    1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
    2. PCI bus
    3. Intel ICHR/DO/DH SATA AHCI Controller
    4. Intel USB 3.0 Root Hub
    5. Intel USB 3.0 eXtensible Host Controller
    x64 -
    1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
    2. PCI Bus
    3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
    4. Intel USB 3.0 Root Hub
    5. Intel USB 3.0 eXtensible Host Controller
    I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
    All other hardware works fine. Any suggestions greatly welcomed.
    Cheers - Mark.

    Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
    Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
    W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
    Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

  • For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

    While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
    Background:
    I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
    After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
    1.  Uninstall the OCS 2007 R2 client
    2.  Install all prerequisites for the Lync client
    3.  Install Lync on all user workstations silently.
    While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx".  Well, my response is, I
    tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
    start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them.  I was unable to find any switch or option to prevent the automatic launch.  I suppose the simple solution to that would
    be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
    The next simplest answer I saw was, "extract the MSI and use that with the right switches".  Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
    the MSI to be used or a hacked MSI that bypasses the registry key check.  I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly.  The other problem I ran into
    was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations.  It was this problem that ultimately led me to the solution that I'm about to detail and that has
    worked marvellously for us.
    Solution:
    As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install.  My first attempt was
    just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped.  So, my next attempt was to extract all the prerequisite
    files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
    In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique.  That's where you have, for example, 3 or more programs that run in a package
    in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order.  So, I created programs to 1) kill Communicator.exe 2) uninstall
    Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client.  That final step was always the point of failure because
    I couldn't get the hacked MSI for the Lync Client install to work.  I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error.  That's one of the downsides
    of program-chaining, if one step fails, SCCM completely bails on the deployment.  This is what also led me to the key to my solution:  TASK SEQUENCES.
    I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments. 
    One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running.  Another advantage is that task sequences have some very good built-in conditionals that
    you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine.  Both of those advantages factor highly into my solution.
    OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
    First, you need to extract all the files from the LyncSetup.exe for your needed architectures.  We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account.  To extract the files, just start up
    the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location.  The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
    both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
    or rename them to reflect the architecture).
    For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
    Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server.  Go to the SCCM console into Computer Management -> Software Distribution
    -> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
    Now you need to create 3 to 5 programs inside the package:
    1.  Name: Silverlight
       Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer. 
    The fact is the Silverlight installer is the same in both, so you only need one of them.)
       On the Environment tab:  Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
       On the Advanced tab:  Suppress program notifications
       All other options leave default.
    2.  Name:  Visual C++ x86
        Command Line:  x86\vcredist_x86.exe /q
       On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
       Environment and Advanced tabs:  same as Silverlight
       (If you have only x64 clients in your environment, change all x86 references to x64.  If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
    3.  Name:  Lync x86
        Command Line:  msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync"  (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
        Requirements, Environment, and Advanced tabs:  Same as with Visual C++ and Silverlight
        (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
    Now you need to make the Task Sequence.  Go to Computer Management -> Operating System Deployment -> Task Sequences.  Under the Actions pane, click New -> Task Sequence.  In the Create a New Task Sequence dialog, choose "create a
    new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
    The task sequence will have up to 12 steps in it.  I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
    Prereqs Phase:
    These are the easiest of the steps to do.  Highlight the task sequence and then in the Actions pane, click Edit.
    1.  Click Add -> General -> Install Software.  Name: "Install Microsoft Silverlight".  Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
    2.  Add -> General -> Install Software.  Name: "Install Microsoft Visual C++ 2008 x86".  Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
    As before, if you're an all-x64 environment, replace the x86 references with x64.  If you have a mixed environment, repeat step 2, replacing x86 with x64.
    3.  Add -> General -> Run Command Line.  Name: "Enable Lync Installation".  This step gets around the UseMSIForLyncInstallation registry requirement.  The Lync client MSI simply looks for the presence of this key when it runs, so
    we'll inject it into the registry now and it doesn't require a reboot or anything.  It just has to be there before the client MSI starts.
    Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
    Uninstall OCS Phase:
    This part consists of up to 6 Run Command Line steps.  (Add -> General -> Run Command Line)
    4.  Name: "Terminate Communicator".  Command Line: "taskkill /f /im communicator.exe".  On the Options page, check the box next to "Continue on error".  This will terminate the Communicator process if it's running, and if it's not, it'll
    ignore the error.
    5.  Name: "Terminate Outlook".  Command Line: "taskkill /f /im OUTLOOK.exe".  Check the "Continue on error" on the Options page here too.  Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
    because components are in use.
    (NOTE:  If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps.  I didn't run into
    this in my environment, though.  Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
    6.  Name: "Uninstall Microsoft Office Communicator 2007".  Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page:  Add Condition ->  Installed Software -> Browse to the
    Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
    7.  Name:  "Uninstall Microsoft Office Communicator 2007 R2".  Command Line:  "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart".  On the Options page:  Add Condition -> Installed Software ->
    Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
    SIDEBAR
    OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence.  I found out after I'd been deploying for a while that a tech in one of our remote
    offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there.  So, at first I just had our Help
    Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence.  Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
    and 7.  All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions.  This is part of how Windows knows that
    Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
    The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code.  This means that if I didn't have step
    6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong.  Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
    of the R2 client.  So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine.  If it was present, it uninstalled it and then skipped over the R2 step.  If non-R2 was not present,
    it skipped that step and instead uninstalled any version of the R2 client.  It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there.  What if neither is on the
    machine?  Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem.  It was assumed that the machines had some version of Communicator on them.
    8.  Name:  "Uninstall Conferencing Add-In for Outlook".  Command Line:  "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition ->
    Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    9.  Name:  "Uninstall Live Meeting 2007".  Command Line:  "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart".  Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
    -> Browse to the MSI for this optional component and set it to match any version of the product.  If you don't use this in your environment, you can omit this step.
    Install Lync phase:
    Now, finally the main event, and it's pretty simple:
    10.  Click Add -> General -> Install Software.  Name: "Install Microsoft Lync 2010 x86".  Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program.  As before, if you
    only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
    And the task sequence is done!  The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement.  Go get a beer!
    Some final notes to keep in mind:
    1.  You can't make a task sequence totally silent...easily.  Users will get balloon notifications that an application is available to install.  The notifications cannot be suppressed through the GUI.  I've found scripts that supposedly
    hack the advertisement to make it be silent, but neither of them worked for me.  It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade.  The task sequence will appear
    in the "Add/Remove Programs" or "Programs and Features" Control Panel.  You can still do mandatory assignments to force the install to happen, you just can't make it totally silent.  On the plus side, the user shouldn't have to reboot at any point
    during or after the install!
    2.  In the advertisement setup, you can optionally show the task sequence progress.  I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress.  This means instead of seeing
    5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
    3.  One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete.  The user either had to start the client manually or just let it start on its own at the next logon.  However,
    while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
    tab, set it to "Run with user's rights" "only when a user is logged on".
    4.  My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
    and it would fail.  Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first.  It ran much more reliably this way.
    5.  For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
    then fail.  I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
    doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
    I hope this helps some of you SCCM and Lync admins out there!

    On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook.  Here's a list of the ones I found in the machines on my network:
    {987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
    {2BB9B2F5-79E7-4220-B903-22E849100547}
    {13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
    {C5586971-E3A9-432A-93B7-D1D0EF076764}
    I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

  • How can I remove the SCCM 2012 client and reinstall SCCM 2007 client on all of our computers

    Hello All
    We have  bit of a problem. Our virtual SCCM 2012 r2 server was deleted and the back solution we had in place keeps failing.
    We do have our sccm 2007 server still in place but its only role was imaging as we transferred roles from one to another.
    My question is now our support needs to remote into pcs but cant because the CM12 server is gone. How can I remove the 2012 client from all of our companies computers and reinstall the CM07 client so we can remote into computers again.
    Thanks in advance!
    Phil
    Phil Balderos

    Run a ccmsetup /uninstall on the clients. You may need to run via PSExec. Then push out the SCCM 2007 client via the 2k7 console.
    Cheers
    Paul | sccmentor.wordpress.com
    Thanks Paul!
    I have to do this on over 350 computers and 110 servers. How can I do it on a more massive scale?
    Phil Balderos
    I would check Torsten's approach first and see if the ccmsetup will uninstall the 2012 version. I'm not sure. Obviously the other way round is fine.
    Using PSexec you can script this to call up a txt file of all your servers/computers and run the uninstall.
    e.g. 
    for /f "tokens=*" %a in (computers.txt) do psexec \\%a %WINDIR%\ccmsetup\ccmsetup.exe /uninstall 
    If your account has privileges on all devices you won't need to add in any username/password credentials. Obviously only devices that are switched on and you have access to will run this.
    Cheers
    Paul | sccmentor.wordpress.com

Maybe you are looking for

  • How to clear Spool ?

    Hi, I hve a report to download an PDF(1 pg doc)  invoice. It also generates a spool request. When the invoice is printed through this program, it creates a pdf file with multiple (same) pages. The number of duplicate pages is proportional with the no

  • Can't figure out why Music on Hold isn't working

    This is my first time trying to set up MoH.  I am using CUCM 8.6.  Here is what I have done so far. Uploaded a file and it converted into 4 files called MoH_female Configure MoH Audio Source Config,  MoH_female, Play continously and All Multi--castin

  • Killed Toad session does not disappear

    Status is KILLED, there is no SPID associated with the process, but if the user tries to compile the procedure he hung in it hangs again until the session completely disappears. The session has no locked objects according to v%locked_object. It is no

  • Help please, I can't get select list behavior correct

    I have a demo application at apex.oracle.com http://apex.oracle.com/pls/apex/f?p=71968:1 username is demo, password is demo I have a form with multiple fields field1 (Text Field) field2 (Text Field) field3 (Text Field) field4 (Text Field) Status (Sel

  • OBIEE Dashboard prompt space Increase

    Hello, I have requirement, where management doesn't like the crowded prompts in dashboard (Oracle Business Intelligence 10.1.3.4.1), is there any way i can increase the space between two prompts ? Seems like something to do with js pages but not exac