Jump to content


Peter van der Woude

Moderators
 View Profile  See their activity

  • Posts

    2925

  • Joined

  • Last visited

  • Days Won

    79

 Content Type 

Everything posted by Peter van der Woude

  1. Peter van der Woude
    Take a look at the log files. For an overview of software update related log files, see: http://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_SU_NAPLog
  2. Peter van der Woude
    Well.. to be honest, you won't be able to do that for a user. Only for the user running the command, which doesn;t help you. Another thing you could do is to run it as the SYSTEM, which would cause every user to get it. For an example, see: http://social.technet.microsoft.com/Forums/systemcenter/en-US/18f8f363-8d8d-4508-8a19-19ab739ae343/age-old-question-installing-printers-via-sccm
  3. Peter van der Woude
    It's very likely that it's a user vs system context issue. During testing your script, did you try running it via psexec (to test in system context)?
  4. Peter van der Woude
    You can't skip that step if you still need to install software. What you could do is use the SMSTSPostAction variable to uninstall the client after the task sequence is done. But still I think MDT would be a better choice in this situation.
  5. Peter van der Woude
    Ok, so you're using WSUS for the regular patches and you want to use a SUP for updating the image. So, to complete your last sentence, you installed WSUS and a SUP on the site server and configured the existing WSUS server as upstream. In that case, make sure that you are syncing the updates on the upstream server first and then synchronize them into your SUP/WSUS. Every category selected in your SUP/WSUS, also needs to exist on the upstream server.
  6. Peter van der Woude
    I guess it can't find the script, but check the log files (AppEnforce.log in case of an application deployment) for more information.
  7. Peter van der Woude
    This very little information about the exact problem. Also, to verify, I assume you''ve installed the SUP on the remote server with WSUS and installed the WSUS console also on the site server.
  8. Peter van der Woude
    I'm not completely sure if ConfigMgr would be the ideal solution, but it would make your life a lot easier. Maybe in this specific case it would be worth a try to look at a combination of MDT and WSUS.
  9. Peter van der Woude
    That specific update is already superceded by http://support.microsoft.com/kb/2910552 and are also included in CU1 and CU2.
  10. Peter van der Woude
    First of, if the detection rule is only checking for the existence of a folder, then I would not use a custom script, but a simple check for a folder. Please provide some more details about what your application and deployment types look like.
  11. Peter van der Woude
    See: http://www.windows-noob.com/forums/index.php?/topic/11144-is-it-best-practice-to-apply-a-gpo-to-disable-automatic-windows-updates-when-using-sccm-2012-for-windows-updating/
  12. Peter van der Woude
    I haven't seen that error before.. A quick search gave me SUS_E_DM_INCORRECTFILEHASH, which indicates an hash error. Did you try to delete the cache and download the update again?
  13. Peter van der Woude
    Not every error is a problem. This task sequence seems to end fine. Are you having any issues after the deployment is completed?
  14. Peter van der Woude
    I wouldn't try to do that with a global conditions, as it's not being checked that often. It would only be checked again during the re-evaluation of the application, which could potentially cause it to take months before an application is installation. Have a look at the PowerShell App Deployment toolkit as I think it can help you with something like this: https://psappdeploytoolkit.codeplex.com/
  15. Peter van der Woude
    Please check the log files (for an overview of all log files, see: http://technet.microsoft.com/en-us/library/hh427342.aspx).
  16. Peter van der Woude
    In that case, simply only deploy to known computers. Create a collection specific for OS deployment and add the machines that need to be re-deployed to that collection and make sure they get removed when the deployment is finished.
  17. Peter van der Woude
    Correct, sometimes an update is updated. That's why I always sort my console on Date Released or Revised.
  18. Peter van der Woude
    See: http://social.technet.microsoft.com/Forums/en-US/d5d8c9f7-0ab6-46cb-a2b3-97c9765a1be0/sccm-2012-r2-mdt-2013-install-features-after-os-install?forum=configmanagergeneral
  19. Peter van der Woude
    Funny thing is that there is no buildin functionality to uninstall certain patches. To uninstall an update, you need to create a custom package, with a command line to uninstall that specific update.
  20. Peter van der Woude
    Not sure what you're exactly looking for.. are you not just looking for WiFi Profiles (see: http://technet.microsoft.com/en-us/library/dn261224.aspx
  21. Peter van der Woude
    If it's simply about recreating something you already had in your 2007 environment, you can just migrate your operating system images (see also: http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_migrate_OSD). If you're not using the migration options, you can also just copy the WIM file and import it as a new operating system image in the 2012 environment.
  22. Peter van der Woude
    You're correct. Simply create a collection that only contains those ten clients and target the updates to that collection.
  23. Peter van der Woude
    I can't recall ever looking in the event log for information about Endpoint Protection. What information did it show and doesn't that information simply reflect in the console (or the reports)? Minor note: It's System Center Endpoint Protection
  24. Peter van der Woude
    The error is a bit more clear in the log file, as it states "The Service Broker endpoint cannot listen on port 4022 because it is in use by another process."
  25. Peter van der Woude
    It doesn't exist anymore, you can now work with the hardware inventory classes in the client settings.
×
×
  • 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.