SCCM 2007 Dead DP cleanup?

Hi,
We have some orphan DPs in SCCM 2007 that are dead that no longer exist.
However in hirarchy the system is still trying to send packages to the child DP's.
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone XXX 9/12/2013 6:38:05 PM SERVER1 SMS_DISTRIBUTION_MANAGER 2332 SMS Distribution Manager failed to remove package "XXX001CE" from distribution path "MSWNET:["SMS_SITE=XXX"]\\SERVER1\PACKAGE$\SMSPKG\XXX001CE\".   
Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server.  Solution: If users are currently accessing the package files on the distribution point, disconnect the users first.
I have read if you delete the package from the DP it will try for 100 times before giving up.
which supports what i seem to see in the distmgr.log:
Failed to process package XXX001CE after 4 retries, will retry 96 more times SMS_DISTRIBUTION_MANAGER 2332 (0x091C)
My question is will it clean up the orphan data at that time in the tables like:
pkgservers, pkgstatus and DPInfo tables.
I would rather not modify the tables directly as MS does not recommend playing
with the DB :)
Thanks,
Ward.

The best supported method to achieve your objective is to open a support case and have CSS work with you through the process of cleanup.

Similar Messages

  • How manually remove a DP in SCCM 2007 ?

    Hello,
    we had a disaster and our old SCCM 2007 site server is dead.
    We already have a SCCM 2012 site server up and running and a old SCCM 2007 distribution point still up.
    we need to convert the old DP to a 2012 DP.
    How can i manually remove the DP from SCCM 2007 without an access to the console, site server, bd, etc...?
    On the DP, Can I just remove all the share and permission?
    thanks

    If you don't use the 2007 environment any more you can delete the old shares and folders.

  • 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.

  • 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.

  • 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

  • How to perform a query to read an xml file in SCCM 2007

    Good,
    I need read knows how to read an csv file for a specific column after collecting the results, then put the PC's in a collection in particular.
    A greeting and thanks

    Good,
    What I want to do is create a query that examine a csv that is on a server. And after consideration and select the column that I am interested
    in(Name pc) be able to engage these data to a collection, clear is if it can be done in SCCM 2007
    A greeting and thanks

  • 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

  • Windows 8.1 Pro OS Deployment Using SCCM 2007 SP2 R3 - Possible? Supported?

    I have been able to successfully capture and deploy a Windows 8.1 Pro image to a desktop, however the Apply Device Drivers action consistently fails with the following error in the smsts.log:
    Driver-signing policy cannot be configured on this operating system
    After that point no suitable drivers are able to be found and the task sequence is unable to proceed due to the lack of drivers. I'm using the same task sequence I used for Windows 8 OS deployment within SCCM 2007 SP2 R3. I'm just looking for confirmation
    on whether or not driver deployment is now broken in Windows 8.1.

    The toolset has been updated significantly to support Win 8.1. Exact technical details of the changes aren't published anywhere beyond the fact that it simply isn't supported.  It's insufficient simply because it is known not to work -- beyond that,
    does it really matter?
    Note that even Win8 deployment within ConfigMgr is unsupported so basically you're off into uncharted territory and assuming a lot of risk in doing so.
    Jason | http://blog.configmgrftw.com

  • Help needed -- Considerations to be taken while migrating 2 different SCCM 2007 hierarchies into a single SCCM 2012 Hierarchy.

    Hi, I need your help on consolidating two different SCCM 2007 infrastructures into a single SCCM 2012.
    We have two different SCCM 2007 Hierarchies, Lets say 123 and ABC
    About 123 SCCM 2007 -- On 123 Hierarchy, we have already started migrating clients from SCCM 2007 to SCCM 2012.
    About ABC SCCM 2007 -- On ABC Hierarchy, This is still running on SCCM 2007 (This hierarchy only be started migrating once                                      we
    are completed migration on 123)
    Out of which, we have few co located offices across the globe for both 123 and ABC. Now we are decided to replace the hardware on all these locations by removing the existing two servers (one for 123 and other for ABC,with two different Forest and domains),
    and consolidate them into a single server.how can we plan/design to ensure that we covering both hierarchies SCCM clients for the operations.
    ===================Below are some possibilities we are discussing on================================
    1.Is there any way on "System management" in AD to enable access either in 123's domain or ABC's domain.
    2.Since we are planning to replace the hardware with Server 2012 R2 with Hyper-V, Create two instances and migrate 123 hierarchy to SCCM 2012 and other instance will serve ABC until we start the migration on this.
    ========================================================================================
    correct me, If i am in wrong direction. Please suggest me the best of doing it. Thanks in advance.
    srkr

    1) In CM 2012 you can publish data to System Management in other forest but you have to configure the permissions manually and create the forest object in the ConfigMgr console.
    2) CM07 and CM2012 instances can co-exist as long as you don't create boundary groups in CM12 for site assignment (that will cause overlapping boundaries if you still have boundaries in Cm07)
    Kent Agerlund | My blogs: blog.coretech.dk and
    SCUG.DK | Twitter: @Agerlund | Linkedin:
    Kent Agerlund

  • SCCM 2007 and 2012 coexistence and Cross Forest support

    Hi All
    I have a question
    My company has recently acquired another company
    That company exist of 2 forests (forest A has one domain namely domain A : and forest B has one domain namely domain B) with a two way forest trusts between them
    Domain A has a SCCM 2007 primary Site
    Domain B has a SCCM 2007 primary site and 2 secondary Sites
    The active directory schema is extended in both domains
    We cannot migrate the SCCM 2007 environment because it is a mess , so we want to build a new SCCM 2012 R2 environment into Domain B and from that environment manage both domains  (OSD, software deployment client management ...)
    We want to install a SCCM 2012 R2 (CU3) primary server into domain B and add two distribution points instead of the two secondary sites and manage both forests (domain A and B) from that primary site server
    Now my questions are
    1 )
    Can an SCCM 2007 environment coexist with a SCCM 2012 environment?
    I believe it can If I make sure that in the new SCCM 2012 environment we only use boundary groups for content locations and not for site assignment and in the SCCM 2007 environment (domain A and domain B) I need to disable the client push account.
    2)
    Discovery , How do we make sure that systems and users are discovered from both domains?
    Do we need to do some additional configuration to make that happen or will this be no problem because of the Two way trust and active directory schema extension.
    3 )
    Can we do all the management from the new SCCM 2012 R2 site , also OSD deployments for both domains ?
    I hope someone can help me with these questions
    Thanks in advance
    Regards
    Johan

    Hi All
    After talk with management and local support the decision is made not to deploy only distribution points but instead deploy secondary sites (of course with management point and distribution point) because the bandwidth to these sites is a
    problem.
    So the situation will be Domain A Primary site (SCCM 2012 R2) and for both remote locations a secondary site , domain B a secondary site (of course all the related ports need to be opened for both domains as explained here https://technet.microsoft.com/en-us/library/hh427328.aspx
    Question 
    Can we do all the management from the new primary SCCM 2012 R2 site (domain A) , also OSD deployments for both domains A and B ?
    I hope someone can review this
    Thx in advance
    Regards Johan

  • Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

    Hi,
    The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
    Below are the patches.
    MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
    MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
    MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
    MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
    MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
    MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
    MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
    MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
    MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
    I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
    all the 2008 server updates are set and marked to download.
    Please help me out on fixing this.

    So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • 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

  • SCCM 2012 Client delpoyment in SCCM 2007 Native world

    Hi Team,
    In my account I have SCCM 2007 running in Native mode.... we do not support internet based clients there..but work on HTTPS only. Now I have implemented SCCM 2012 R2 there and now testing the client migration so that I can upgrade the SCCM client agent from
    2007 to 2012. In SCCM 2012 we have to support internet based clients and so the SCCM 2012 client which we need to install should be compatible on internet and intranet both
    The plan is to use the existing SCCM 2007 infra to do that. Send the ccmsetup.exe ( of SCCM 2012 ) in a package to all the clients via SCCM 2007 Software Distribution and trigger SCCM 2012 installation.
    Just to do a small test I did this :
    1. Created a folder in C drive of a client machine and copied the ccmsetup.exe ( of SCCM 2012 ) in it.
    2. Tried to trigger the installation with below mentioned commandlines..... but getting error as mentioned below.... Please help.
    Command line used : 
    Here ABCD.contoso.org is the intranet MP and PQRS.dmzone.org is internet MP
    CCMSetup.exe /UsePKICert /NoCRLCheck smsmp=ABCD.contoso.org ccmhostname=PQRS.dmzone.org smssitecode=ABC
    CCMSetup.exe /UsePKICert /NoCRLCheck smsmp=ABCD.contoso.org smssitecode=ABC
    CCMSetup.exe smsmp=ABCD.contoso.org smssitecode=ABC
    Error in ccmsetup.log
    <![LOG[==========[ ccmsetup started in process 3068 ]==========]LOG]!><time="12:49:12.547+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="5076" file="ccmsetup.cpp:9441">
    <![LOG[Running on platform X64]LOG]!><time="12:49:12.548+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="5076" file="util.cpp:1892">
    <![LOG[Updated security on object C:\Windows\ccmsetup\cache\.]LOG]!><time="12:49:12.548+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="5076" file="ccmsetup.cpp:9285">
    <![LOG[Launch from folder C:\Windows\ccmsetup\]LOG]!><time="12:49:12.548+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="5076" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1401]LOG]!><time="12:49:12.549+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="5076" file="ccmsetup.cpp:727">
    <![LOG[Successfully started the ccmsetup service]LOG]!><time="12:49:12.550+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="4744" file="ccmsetup.cpp:3271">
    <![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.exe.download]LOG]!><time="12:49:12.551+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="4744" file="ccmsetup.cpp:9497">
    <![LOG[In ServiceMain]LOG]!><time="12:49:12.552+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmsetup.cpp:3365">
    <![LOG[Folder 'MicABCoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="12:49:12.556+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="4744"
    file="wintask.cpp:622">
    <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="12:49:12.556+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="4744" file="ccmsetup.cpp:10879">
    <![LOG[Running on 'MicABCoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18]LOG]!><time="12:49:12.618+300" date="11-11-2014" component="ccmsetup" context="" type="1"
    thread="3284" file="util.cpp:1974">
    <![LOG[Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice "/UsePKICert" "/NoCRLCheck" "smssitecode=ABC"]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup"
    context="" type="1" thread="3284" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context=""
    type="1" thread="3284" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice "/UsePKICert" "/NoCRLCheck" "smssitecode=ABC"]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup"
    context="" type="1" thread="3284" file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 448]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8621">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8636">
    <![LOG[CCMHTTPSSTATE:    448]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8654">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8672">
    <![LOG[FSP:    ]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8724">
    <![LOG[CCMFIRSTCERT:    1]LOG]!><time="12:49:12.619+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:8782">
    <![LOG[HTTPS is enforced for Client. The current state is 31.]LOG]!><time="12:49:12.621+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmutillib.cpp:403">
    <![LOG[Begin searching client certificates based on Certificate Issuers]LOG]!><time="12:49:12.623+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmcert.cpp:4393">
    <![LOG[Completed searching client certificates based on Certificate Issuers]LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmcert.cpp:4550">
    <![LOG[Begin to select client certificate]LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmcert.cpp:4706">
    <![LOG[The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'.]LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context=""
    type="0" thread="3284" file="ccmcert.cpp:4742">
    <![LOG[1 certificate(s) found in the 'MY' certificate store.]LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmcert.cpp:4770">
    <![LOG[Only one certificate present in the certificate store.]LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmcert.cpp:4774">
    <![LOG[Begin validation of Certificate [Thumbprint 50051EB74624621341900739D65706D8089A0941] issued to 'D-LJACKNVM7X64.ABClan.org']LOG]!><time="12:49:12.624+300" date="11-11-2014" component="ccmsetup" context=""
    type="1" thread="3284" file="ccmcert.cpp:1662">
    <![LOG[Failed to get certificate key provider information. Error 0x80092004]LOG]!><time="12:49:12.626+300" date="11-11-2014" component="ccmsetup" context="" type="3" thread="3284" file="ccmcert.cpp:1199">
    <![LOG[The Certificate [Thumbprint 50051EB74624621341900739D65706D8089A0941] issued to 'D-LJACKNVM7X64.ABClan.org' has 'Client Authentication' capability.]LOG]!><time="12:49:12.633+300" date="11-11-2014" component="ccmsetup"
    context="" type="0" thread="3284" file="ccmcert.cpp:582">
    <![LOG[Completed validation of Certificate [Thumbprint 50051EB74624621341900739D65706D8089A0941] issued to 'D-LJACKNVM7X64.ABClan.org']LOG]!><time="12:49:12.633+300" date="11-11-2014" component="ccmsetup" context=""
    type="1" thread="3284" file="ccmcert.cpp:1803">
    <![LOG[>>> Client selected the PKI Certificate [Thumbprint 50051EB74624621341900739D65706D8089A0941] issued to 'D-LJACKNVM7X64.ABClan.org']LOG]!><time="12:49:12.633+300" date="11-11-2014" component="ccmsetup"
    context="" type="1" thread="3284" file="ccmcert.cpp:4850">
    <![LOG[Raising event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    ClientID = "GUID:A5879665-7A1B-4529-827E-52FA34ABD384";
    DateTime = "20141111174912.640000+000";
    HRESULT = "0x00000000";
    ProcessID = 3068;
    ThreadID = 3284;
    ]LOG]!><time="12:49:12.640+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="event.cpp:715">
    <![LOG[Failed to submit event to the Status Agent. Attempting to create pending event.]LOG]!><time="12:49:12.643+300" date="11-11-2014" component="ccmsetup" context="" type="2" thread="3284"
    file="event.cpp:737">
    <![LOG[Raising pending event:
    instance of CCM_ServiceHost_CertRetrieval_Status
    ClientID = "GUID:A5879665-7A1B-4529-827E-52FA34ABD384";
    DateTime = "20141111174912.640000+000";
    HRESULT = "0x00000000";
    ProcessID = 3068;
    ThreadID = 3284;
    ]LOG]!><time="12:49:12.643+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="event.cpp:770">
    <![LOG[Successfully submitted pending event to WMI.]LOG]!><time="12:49:12.648+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="event.cpp:813">
    <![LOG[CCMCERTID:    MY;50051EB74624621341900739D65706D8089A0941]LOG]!><time="12:49:12.649+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmsetup.cpp:8803">
    <![LOG[No MP or source location has been explicitly specified.  Trying to discover a valid content location...]LOG]!><time="12:49:12.649+300" date="11-11-2014" component="ccmsetup" context="" type="1"
    thread="3284" file="ccmsetup.cpp:4729">
    <![LOG[Looking for MPs from AD...]LOG]!><time="12:49:12.649+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="ccmsetup.cpp:4737">
    <![LOG[Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ABC))']LOG]!><time="12:49:13.226+300" date="11-11-2014" component="ccmsetup" context="" type="0"
    thread="3284" file="lsad.cpp:657">
    <![LOG[OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F0308201D8A003020102021012B6F63E56359BB9493496A444140A76300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303931383135313330355A180F32313134303832363135313330355A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100D2F099DE475F5360729CBD0CEB1F9DC291383C9787E19DEA9CBE8988799E60CA26CB3FEBF2E4115FE6D8A6B42E063E72B2B035BEFA0BA9D8FB9E892366699A25FB9F10956770DAC5DD650CBAFB1BC46DACE2F2A777C42D269366361B6207318D5ED52D32078EA0D59CDBE13892B1A7BD7E21CD748B6BF636D9901610BE6D8D363646651ACB10440EE31F9F36FA48227631D9989E8349B888C3C4959E79AC0C4B579F10F41D30285B478FCED289AA23066D407D73AF73408D7609442EC7AC32F96EABB176E42159BEFDF6537864FEFC9F8491DA7C6BB9BCB99C5FF7E31ADC294FFD49088899C1698F44FE9F1C18046AF8255A521C6910AC113845997960ECA8070203010001A3383036301E0603551D11041730158213524F534E543232312E6574736C616E2E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101002061E3AC32E4EAF2BEA7CF3004372C1FA61B5114B3CB838FA92A2037D1A26FB2926F2D3FB000B1249099E513BBD76DCB01D74BD6A273CCEAE84CD87F77D8BBB256F4FA58030B8DADC3F6C8B84967D8F7DFA81FE2C57426AB918CC61E42D5838C4A40D84F39E1B3288415609F2C3B0E52988EAB6E155A68725828B09D7475D9ED764DFD976F1D40CCEFAAD5E0F3B21E4DE7EA0BFEF617D4C8459C8E37B49EFBCF0C3921B2FD74BFDBEFFEF1B0CB1A1C85C5F3A16AE974DF3AB0E28EED844C43AB0E3F564C82FCD986CC429057702680B3869765A2A5128EC1EC378F90A9E4BA27572E64F500E645CFA5CBC300EAC980D68E6B96A1E1C7D95B2041CC807F7C74FF</SiteSigningCert></SecurityConfiguration><RootSiteCode>ABC</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=ABC</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain
    Value="ABClan.org" /><Forest Value="ABCroot.org" /></ClientOperationalSettings>']LOG]!><time="12:49:13.378+300" date="11-11-2014" component="ccmsetup" context="" type="0"
    thread="3284" file="lsadcache.cpp:236">
    <![LOG[The MP name retrieved is 'ABCD.contoso.org' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="12:49:13.381+300"
    date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="lsadcache.cpp:334">
    <![LOG[MP 'ABCD.contoso.org' is not compatible]LOG]!><time="12:49:13.382+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="lsadcache.cpp:345">
    <![LOG[Retrieved 0 MP records from AD for site 'ABC']LOG]!><time="12:49:13.382+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="lsadcache.cpp:287">
    <![LOG[FromAD: command line = SMSSITECODE=ABC]LOG]!><time="12:49:13.383+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="ccmsetup.cpp:288">
    <![LOG[Local Machine is joined to an AD domain]LOG]!><time="12:49:13.383+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="lsad.cpp:715">
    <![LOG[Current AD forest name is ABCroot.org, domain name is ABClan.org]LOG]!><time="12:49:13.386+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="lsad.cpp:843">
    <![LOG[Domain joined client is in Intranet]LOG]!><time="12:49:13.386+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="lsad.cpp:1048">
    <![LOG[CMPInfoFromADCache requests are throttled for 01:07:08]LOG]!><time="12:49:13.386+300" date="11-11-2014" component="ccmsetup" context="" type="0" thread="3284" file="lsadcache.cpp:173">
    <![LOG[No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue.]LOG]!><time="12:49:13.386+300" date="11-11-2014" component="ccmsetup" context="" type="3"
    thread="3284" file="ccmsetup.cpp:4806">
    <![LOG[Failed to parse '"C:\Windows\ccmsetup\ccmsetup.exe" /runservice "/UsePKICert" "/NoCRLCheck" "smssitecode=ABC"' with error 0x80004005]LOG]!><time="12:49:13.386+300" date="11-11-2014"
    component="ccmsetup" context="" type="3" thread="3284" file="ccmsetup.cpp:4611">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="12:49:13.386+300" date="11-11-2014" component="ccmsetup" context="" type="1"
    thread="3284" file="ccmsetup.cpp:9767">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='307' will not be sent.]LOG]!><time="12:49:13.387+300" date="11-11-2014" component="ccmsetup" context="" type="1"
    thread="3284" file="ccmsetup.cpp:9767">
    <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="12:49:13.388+300" date="11-11-2014" component="ccmsetup" context="" type="1" thread="5076" file="ccmsetup.cpp:10883">

    Hi Jason,
    Thanks for your reply..... I tried with /mp switch.... but same error.... if you look at the logs it says 
    <![LOG[MP 'ABCD.contoso.org' is not compatible]LOG]!><time="12:49:13.382+300"
    date="11-11-2014" component="ccmsetup" context="" type="1" thread="3284" file="lsadcache.cpp:345">
    <![LOG[Retrieved 0 MP records from AD for site 'ABC']LOG]!>
    Not sure why it is saying " not compatible " ... its a valid MP..... from the same client machine below links are working fine..
    http://ABCD.contoso.org/sms_mp/.sms_aut?mpcert
    http://ABCD.contoso.org/sms_mp/.sms_aut?mplist
    Thanks,
    Sam

  • How to create a deletion of Adobe Acrobat through SCCM 2007

    Can anyone give me assistance with creating a deletion package through SCCM 2007 that will remove Adobe Acrobat 8? I've tried the delete switch and msiexec, but doesn't seem to do the trick. Any assistance would be helpful.

    Create A batch file
    Content:
    ==============================================================================
    @echo off
    cls
    echo
    =================================================
    echo Please wait while  ....PRODUCT NAME ....  is uninstalling
    =================================================
    Msiexec.exe /x {QUID} /q
    ::::Replace QUID with quid number ie  AC76BA86-1033-ffff-7760-000000000006
    ==============================================================================
    SAVE BATCH FILE IE UNINSTALL.BAT
    THEN CREATE PACKAGE IN sccm

  • Can I use SCCM 2007 to deploy SCCM 2012 Agent

    I was reading the scenarios for deploying the SCCM 2012 agent here
    http://technet.microsoft.com/en-us/library/gg682132.aspx
    I have been planning to deploy the 2012 agent using an SCCM 2007 deployment package. I am not migrating any data/packages/collections/anything from SCCM 2007. 
    I am looking for a sane way to deploy 2000ish clients a day for 2 weeks and be done. 
    I figure they are all SCCM 2007 clients so lets deploy 2012 agent using SCCM 2007.
    I read the following in the link above and it sounds like the way I want to go – use SCCM 2007 software distribution…
    Upgrade installation by using application management
    Upgrades clients to a newer version by using Configuration   Manager application management. You can also use Configuration Manager 2007 software  
    distribution to upgrade clients to System Center 2012 Configuration Manager.
    Then later in the same document there is this…
    How to Upgrade Configuration Manager Clients by Using a Package and Program
    You can use Configuration Manager to create and deploy a package and program that upgrades the client software for selected computers in your hierarchy. A package definition file
    is supplied with Configuration Manager that populates the package properties with typically used values. You can customize the behavior of the client installation by specifying additional command line properties.
    You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
    In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client.
    What???!??  There is no Automatic client upgrade feature in 2007 – so how does that even make sense?  In one section, it says I can deploy the 2012 Agent using SCCM 2007 software distribution, and then later in the same document, it
    says I can't.  I am probably misunderstanding somthing.
    Is it possible to make a package/program in SCCM 2007 that will make targeted clients upgrade to Agent 2012 and join the new SCCM 2012 Site?

    I tested this (deploying 2012 agent using existing 2007 SCCM infrastructure) with a few test systems at my desk and it seems to work pretty smoothly.  I made a package to deploy SCCM 2012 SP1 and added it to my SCCM 2007 Site.  Then I deployed
    the 2012 agent from 2007 and it worked great.  If it works this well in production, I will be able to migrate all of my clients in less than a weeks time. 
    I have not published the 2012 site information in AD - and I don't plan to.  We would have some overlapping site boundaries - and in 2012 it seems its unnecessary in a single site hierarchy.  I AM planning to use boundaries to assign
    DPs, but thankfully site and DP boundaries have been separated.  It works great to just specify the site in everything and not worry about auto discovery.  My clients don't move among sites since I only have one large site.
    Sorry that I somehow posted this same question twice, and thanks for cleaning that up.
     In my installation, I just called ccmsetup.exe with the following command line...
     /mp:myMP.mydomain.com CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=1000000 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=myMP.mydomain.com SMSSITECODE=CCM
    I am not sure that I need to specify the MP twice, but it is working to do so.  I'm also not sure whether the log and cache flags will be honored since there are existing settings from SCCM2007 agent.  I think that the 2012 install will not change
    these settings upon installation, but it does not appear to hurt the process to include them just in case it does work.

Maybe you are looking for

  • T CODE FOR OPEN PERIOD.

    Dear all Guru's                                 I know that for closing period the T.CODE is MMPV , Pl tell me that wat is the code for opening period . & also suggest wat is to enter when using MMPV & ( T CODE for opening period. rewarded if helps.

  • How to restrict simultaneous log in of a user

    Hi Experts,   I am facing one problem to implement the following scenario, The requirement is at a time one user can log in to the portal only once.Means after login if he tries to logging from another system it  will not allow him to do that and giv

  • Time Machine over a network

    I've been researching this issue for a couple of weeks now and every time I think I get close, I hit a speed bump. I have a direct connected Lacie 1 TB drive that I'm using for my iMac which has worked fine for 3.5 years.  It's now 90% full, and with

  • Issue with file download from BLOB type data

    i have been using this for a while, with no problems, including on hosted machines. the upload to the database works fine.. not the issue, and the download script also works fine, on the local WAMP machine. but once moved to the server it fails.. the

  • Subcontracting Process with Customer owned stock

    We are looking for SAP supported process where the customer sends us components along with a sales order for a finished good. The components have to be received into customer owned stock and will be used (for instance as part of the BOM) to produce t