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
    A GPO will only introduce more problems in this case, as there will be a difference between the GPO and the local policy. You could look at prevent access to the other SUPs to trigger the switch.
  2. Peter van der Woude
    The clients won't switch automatically to a different SUP, not even with a secondary site. Only during the initial configuration of the client, the client will pick the local SUP. After that moment the client will only switch after, I thought, 4 scan failures.
  3. Peter van der Woude
    Nickolaj made something nice to do that job, see: http://www.scconfigmgr.com/2015/03/21/get-lenovo-warranty-information-with-powershell/
  4. Peter van der Woude
    To my knowledge there is no integration on that level. Either use the Application Catalog for available software or use the BMC Remedy. Also, keep in mind that ConfigMgr CB introduced available apps in Software Center, which might be beneficial in your scenario.
  5. Peter van der Woude
    It can be that it's not displayed as a direct error. Simply look for a matching time stamp and look at the activity that was performed at that time.
  6. Peter van der Woude
    It sounds like you're not deploying the SCEP client updates. These can be deployed in multiple ways. For example as a software update, or during the automatic ConfigMgr client update.
  7. Peter van der Woude
    At which point does it fail, during the push (ccm.log on the site server), or during the installation (ccmsetup.log on the client)?
  8. Peter van der Woude
    Yes, that's possible and yes, you can install applications during the task sequence. Also, to uninstall the client you can use the SMSTSPostAction task sequence variable. That allows you to trigger the action after the task sequence and by that allow the task sequence to finish successfully.
  9. Peter van der Woude
    Regarding the network driver, keep in mind that you need to use the driver that matches the boot image version. Also, once you find the correct driver you can add the driver to the boot image through the ConfigMgr console (which uses DISM to complete the task).
  10. Peter van der Woude
    Something like this: https://gallery.technet.microsoft.com/Add-a-Requirement-to-an-ce60681f ?
  11. Peter van der Woude
    Minor correct, you cannot enroll your device and install the ConfigMgr or Intune agent. It's or MDM, or ConfigMgr agent, or Intune agent.
  12. Peter van der Woude
    A quick scan through your log file showed: There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Did you add the device to a collection to which a task sequence is deployed?
  13. Peter van der Woude
    Create a collection based on that OU and use that collection as an exclude collection for your other collections.
  14. Peter van der Woude
    Looks OK. Also good to know, Microsoft has a checklist for every upgrade, which you can find here: https://technet.microsoft.com/en-us/library/jj822981.aspx
  15. Peter van der Woude
    In that case you've created different membership rules. The device is member of the direct membership and not part of the query membership rule. That combination will add the device to the collection. Those rules act sepparately from each other.
  16. Peter van der Woude
    You can use the same web server certificate; The software update point requires the internal FQDN and the Internet FQDN, they can both be in the alternative name. They are both required, internal FQDN for configuration and the Internet FQDN for the clients; To my knowledge, the Internet FQDN.
  17. Peter van der Woude
    The main problem in that scenario is that the Outlook app is not supported for conditional access with Exchange on-premises.
  18. Peter van der Woude
    Keep in mind that ConfigMgr will perform the installation with the SYSTEM account.
  19. Peter van der Woude
    No, not really. Enabling the software update agent will make the ConfigMgr client set a local policy to configure the WSUS settings on the client. That will break your standalone WSUS configuration.
  20. Peter van der Woude
    Could it be that you're running into this issue: http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx
  21. Peter van der Woude
    Yes, you still need to create a new MDT package. The reason for that is pretty simple, creating the new package will make sure that your package includes the latest changes to the scripts of MDT.
  22. Peter van der Woude
    If you'e importing the devices in ConfigMgr, instead of using Unknown Computer support, this is a very stable method to deploy applications based on the department.
  23. Peter van der Woude
    Not sure what you're looking for exactly, but the integration with VPP is available within (at least) build 1602.
  24. Peter van der Woude
    The Windows 10 Updates are available like any other updates in the All Software Updates node. Also, keep in mind that most of it is put in a cumulative update.
  25. Peter van der Woude
    You mean something like this: https://www.petervanderwoude.nl/post/publish-cumulative-updates-of-configmgr-via-system-center-updates-publisher/
×
×
  • 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.