Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. Yes, you can! Please have a look at the many other guides of Niall: http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/
  2. What if you check the scheduling tab of the true deployment (can be found on the configured software update group)?
  3. See: http://social.technet.microsoft.com/Forums/en-US/a1bf8020-f6f6-44c9-94bc-1977d8fd03a4/wcf-activation?forum=configmanagergeneral
  4. It seems to be struggling with the wireless network adapter. What if you disable it while still in WinPE?
  5. That would just be guessing. Please do as Peter suggested and supply the AppEnforce.log
  6. It almost can't be any different than that you configured the deadline to 7 days... Please provide a screenshot of the deployment schedule tab.
  7. The main problem with a flat design, is indeed the locating of management points and software update points, because these are selected "at random" within the same site. Do keep in mind that the traffic to a software update point or a management point is very little, the most traffic is to the distribution point and that you can control. So either accept it how it is, or use a secondary site to "control" the sotware update points and the management points. I would never use a GPO as a workaround as it will only bring you problem (local policies vs. GPOs).
  8. What does that specific package look like (settings, command line, etc)?
  9. Sorry, I didn't read the log file good enough... The port 8888 is of your application catalog and not of your WSUS. I also just read your initial post.. First get rid of the GPO pointing to your ConfigMgr, it will only cause problems. By enabling the ConfigMgr client for software update (via the client settings) the ConfigMgr client will set a local policy that will point to the Software Update Point. Make sure this is in place an that the updates are deployed to the clients (via a Software Update Group).
  10. Port 88 is not a standard port for WSUS... WSUS normally uses something like 8530 or 8531.
  11. It has a step for installing updates "offline", which just means that you have to create a package with updates and those will be applied during the task sequence.
  12. Did you manually check the machine and the version of the executable?
  13. Depends on the issues you're having. An often seen problem is a combination of SSD drives with application installations. A solution (workaround) for that is SMSTSMPListRequestTimeout, see also: http://technet.microsoft.com/en-us/library/hh273375.aspx
  14. It looks like you didn't configure ConfigMgr to write it the different forests. I would start by supplying an initial management point during the client installation. This should tell the client were to assign and the management point will help the client with locating polices, distribution points, etc. For more client installation properties, see: http://technet.microsoft.com/en-us/library/gg699356.aspx
  15. Did you check the answer you've got on Technet on the same question: http://social.technet.microsoft.com/Forums/en-US/699e84ad-8695-4833-ba17-aae79feab6f7/how-to-give-a-permission-for-another-user-in-sccm2012?forum=configmanagergeneral
  16. Do you also see information about the updates (package) in one of those log files?
  17. Did you also run the configuration of reporting services?
  18. Nope, that's what offline servicing is for.... The only other thing you can do, is to create a build and capture task sequence and create an image that you deploy with the normal task sequence.
  19. Then I think I would rather do something like deploying the client via a GPO
  20. It's a bit of a long sentense of things that you don't want... So no offline servicing from ConfigMgr (which uses DISM)? What exactly are you looking for, just the normal updates during a task sequence?
  21. Check the AppEnforce.log. If that log file does not exist then either it was a package or no application installations have been tried.
  22. Do you mean by removing SCCM, the client? If so, then the client record still exists in your database. Either manually remove it, or check the configuration of your site maintenance tasks.
  23. Don't really get the question.. are you still busy the SUP?
  24. If the installation was successful, this means that your discovery rule is not correct.
  25. The remote site system has to be domain joined, but I would indeed prefer a different domain. The biggest issue will probably be firewalls.
×
×
  • 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.