Jump to content


Jorgen Nilsson

Moderators
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    30

Posts posted by Jorgen Nilsson

  1. Hi,

    It is described here: http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

    Option 66 and configuring a boot file is not recommended and you should use IP Helpers instead which should already be inplace as your client will get IP addresses from tjhis computer. What are you trying to configure with option 66 and what error are you seeing?

     

    Regards,
    Jörgen

  2. Hi,

    That specific update can actually be deployed as an update using SCCM or WSUS http://blogs.technet.com/b/michaelgriswold/archive/2013/03/13/kb2775511-deployment-for-the-sccm-admin.aspx as it is availble in the Microsoft Update Catalog.

    I normally use a script which can be used as well. http://ccmexec.com/2012/02/installing-multiple-windows-7-hotfixes-msu-with-sccm/

     

    With the runtime execeeded what maximum runtime did you set? it takes a while to install that update as it contains 90+hotfixes.

    Regards,
    Jörgen

  3. Hi,

    The Configuration Manager Manager Client Upgrade is normally created when you create a MDT Task Sequence, it is the full client as well but as you normally would create a new package for OSD as the builin package/program is read-only.

    For the updates it the latest one you should deploy, "R2 CU3 - x64 client Updates" and the x86 and deploy them to the clients.

    Regards,
    Jörgen

    • Like 1
  4. Hi,

    Yes it works just fine to move a DP like that,done it many times. Make sure to remove it from all the boundaries / boundary groups when it is not used so that clients don't try to contact it when you have it in your office and update it. So when it is not used have it attached in the office so that it can be updated, then when you move it you assign it to a Boundary Group.

    Regards,

    Jörgen

  5. Hi,
    As you ar uninstalling three different softwares with a script you detection method should identify all three as detection methods and the command you want to run as uninstall, under the uninstall command, then you deploy it as intent: Uninstall and the detection method will detect that all three where removed.

    Regards,
    Jörgen

  6. Hi,

    As answered above,ccmsetup.exe is smart enough to choose the correct plattform for the client. Replicing your GPO is a good idea, Jason Sandys have written a great Startup Script that can be used instead, which is much miuch better. http://blog.configmgrftw.com/configmgr-client-startup-script/ It is also smart enough to install the correct CU update for the client and much more.

     

    I use it basically for all implementations.

    Regards,
    Jörgen

  7. Hi,

    No you must run that step as it does much more than just install the client, it sets it to provisoning mode as well..

    The best solution I can come up with is to build the image in MDT = no SCCM client and as you say to speed up things add Office in the image it takes a long time to install and even longer to upfate.

    You don't have any issues with updates that requires multiple reboots either, there are many benefits of using MDT to build the master image.

    Regards,

    Jörgen

  8. Hi,

    It is just the way SCCM 2012 works ;-) All content will be placed on the Primary site server and then sent from there to the DP's,

    So yes you will see all the content there, You could add a "cheaper" disk to your primary site server and move the SCCMContentLib to that disk using the tool: http://blogs.technet.com/b/neilp/archive/2013/01/08/configuration-manager-2012-sp1-content-library-transfer.aspx

     

    Regards,
    Jörgen

    • Like 2
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.