Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. I agree with Peter. You also might want to have a look at this post, about how those settings connect: http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/
  2. It does use GUIDs. The only way you should add the SCCM client to an image is to either use the Build and Capture task sequence, or follow these guidelines: http://technet.microsoft.com/en-us/library/bb694095.aspx
  3. Did you check the execmgr.log to see if the advertisement arrived, or not?
  4. Discovering objects is no problem, as long as you're not auto configuring boundaries for the discovered Sites and/ or subnets.
  5. If you have a GPO configured for WSUS, your clients will keep on looking at the WSUS server for their updates. When you start managing your clients via SUP then you have to think about removing that GPO also, because SCCM uses local policies for configuring the WSUS/SUP location...
  6. Easiest way in this case, I think, is to create another Program with the new batch file and select Run another program first. This way it will only run when the installation of the software was/ is already done.
  7. Correct, because since SP1 you are able to configure an existing WSUS server as an upstream server.
  8. Make sure you've added a boundary for those clients and make sure the clients are communicating. Besides that, have a look here: http://blogs.technet.com/b/neilp/archive/2012/08/24/cross-forest-support-in-configmgr-2012-part-3-deploying-site-server-site-systems-in-an-untrusted-forest.aspx
  9. You need to install the complete WSUS on the server that you want to use as the SUP and install the WSUS console on the site server.
  10. Check out the Software Updates reports (\Monitoring\Overview\Reporting\Reports\Software Updates - A Compliance)
  11. Might be possible (haven't tried), but it's definitely not supported.
  12. By creating a new Application, selecting Manual specify the application information and following the wizard you can create an Application (and Deployment Type) for an executable.
  13. A Maintenance Window always applies to all the machines in the collection. It doesn't matter if the deployment is connected to a different collection, with the same machine, because the Maintenance Windows still count.
  14. Take a look at the distmgr.log for some details.
  15. When using ConfigMgr for patching, you shouldn't use GPO's at all. The reason for that is that the ConfigMgr client uses local policies to set the configuration (like the WSUS server).
  16. AFAIK, it's not possible to uninstall the Service Pack and it's only possible to completely uninstall ConfigMgr. It is possible to upgrade the SP1 Beta to SP1 Final/RTM, but the result of that is not supported.
  17. The task sequence idea is a good idea. Just keep in mind that when a package has Run another program first selected, it doesn't react the same in a task sequence. In a task sequence you have to add an extra step before it, that runs the other program.
  18. 7711 = CM2012 RTM 7782 = CM2012 SP1 BETA 7804 = CM2012 SP1 RTM SP1 RTM = SP1 Final
  19. Please give some more details about what you are doing and where you see the errors. Also see this: http://www.petervanderwoude.nl/post/using-client-push-installation-on-untrusted-forest-systems-with-configmgr-2012/
  20. There is no need to do that... Just set Should Configuration Manager enforce specific behavior regardless of the application's intended behavior to No specific action and that should do the trick.
  21. Lot's of options, see this post for some idea's: http://www.windows-noob.com/forums/index.php?/topic/5543-name-computer-to-serial-number-during-osd/
  22. This is way to little information to say something useful....
  23. Besides maybe TAP customers, it's not supported to upgrade SP1 BETA to SP1 RTM and that's with a reason...
  24. The SMSTS.log will give more detailed information about which package it can't find. Also something to check, in these cases, are your boundaries.
  25. Take a look at this post: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/84fb4914-21ca-4b9b-88ae-16a247551eb4
×
×
  • 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.