Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. You shouldn't use GPOs for configuring a WSUS/SUP server, ConfigMgr will use local policies itself to configure that.
  2. By deploying the server via ConfigMgr and during the deployment installing the updates.
  3. Well, KB2801987 is Microsoft solution from ConfigMgr perspective. When you want to solve it from a clients' perspective via WSUS/SUP/Offline servicing then you can use KB2756872. On a side-node: It says the update should be installed prior to installing the ConfigMgr 2012 SP1 client. Logically, on a site server it should be applied after installing SP1, as the issue doesn't exist before installing SP1.
  4. Nope, you do NOT need to create a new bootable media with every change in the task sequence.
  5. What action/steps did you exactly perform to add your change? Also on a side-note: When you are using a captured image via SCCM, then I would never manually edit the WIM afterwards. Just add your change to the task sequence and recapture the WIM.
  6. If you don't see any errors on the screen, start with looking at the SMSTS.log.
  7. Are you sure that your SUP is working correctly? Because the "Post-Installation Task" is something different then the running the configuration...
  8. 1. The easiest way is to discover the users in the AD. 2. 0x80072ee2 > To little information; 0x00000000 > Not an error... 3. To little information.
  9. Then you need to (re-)package the software with something like WISE Package Studio.
  10. The systems need to provide their hardware inventory and then the collection needs to run its update.
  11. I'm not sure what you are trying to do, but the it fails at a reboot to WinPE (which probably should be FullOS). This is the message: Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information.
  12. Not sure what your question is exactly, but your systems will first try to use the, via a boundary group, assigned dp(s).
  13. Yes there is. You can view the configured accounts at Administration \ Overview \ Security \ Accounts
  14. The functionality of the SLP is now merged into the MP itself.
  15. How are you restoring? From a task sequence (I hope)?
  16. The biggest difference is that you now also can control the traffic between a Site and a remote DP.
  17. Did you configure a Server Locator Point (SLP)? You need it to find your MP. See also: http://technet.microsoft.com/en-us/library/bb693467.aspx
  18. It doesn't use an Active Directory (AD) account when installing patches, packages, application, etc., it uses the SYSTEM account for things like that. For what usage did you configure the specific AD account?
  19. It's very good possible to query WMI, just not the chasistype (as it's an array).
  20. Correct, you can use one package in multiple deployments.
  21. Put all the files (batch, registry and dll) in the same package, change the location in the batch file to %~dp0 and advertise it.
  22. The Site server hosting the distribution manager needs access to the package source location (on both NTFS and Share level).
  23. Correct, but the full installer does give you the possibility to upgrade an existing installation.
×
×
  • 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.