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
    See: https://social.technet.microsoft.com/Forums/en-US/65142308-4b35-4ebf-b01b-1a8f5c8f5694/how-to-remove-a-computer-from-sccm-during-a-task-sequence?forum=configmanagergeneral
  2. Peter van der Woude
    Probably the device is not in ConfigMgr and you've got nothing deployed to the unknown computers.
  3. Peter van der Woude
    Did you look at a task sequence?
  4. Peter van der Woude
    Check the client log files (locationservices.log).
  5. Peter van der Woude
    That's only possible with a required deployment of the task sequence.
  6. Peter van der Woude
    Check the SMSPXE.log for more information.
  7. Peter van der Woude
    No, that should not affect your network performance.
  8. Peter van der Woude
    If you're using a direct membership rule you don't need to update the membership as there is no query to process. A direct membership rule only needs a collections refresh. Do keep in mind that the device needs to be member of the limited collection first.
  9. Peter van der Woude
    Nope, you can always use IP helpers. Especially when you've got UEFI and legacy BIOS devices, you need to use IP helpers, because they need different boot files and with DHCP options you can only specify one file.
  10. Peter van der Woude
    It can't find a deployment for your device. See the following message from your log: [LOG[00:50:56:32:7F:96, 9FDA4D56-4232-2AC8-EDC1-208C2D0BAF20: no advertisements found]LOG] [LOG[00:50:56:32:7F:96, 9FDA4D56-4232-2AC8-EDC1-208C2D0BAF20: No boot action. Rejected.]LOG] [LOG[00:50:56:32:7F:96, 9FDA4D56-4232-2AC8-EDC1-208C2D0BAF20: Not serviced.]LOG]
  11. Peter van der Woude
    The PATCH parameter is not really an option for client push, as you can't differentiate between x86 and x64. The easiest is to use the packages.
  12. Peter van der Woude
    Yes, the updates should reschedule for the next maintenance window. Could it be that the user triggered the installation themselves?
  13. Peter van der Woude
    Are other devices able to do a PXE boot? Also, is the boot image available for PXE (checkbox on the Data Source tab)?
  14. Peter van der Woude
    Is this log snippet from the timeframe of the failure?
  15. Peter van der Woude
    Did you check the SMSProv.log for more information?
  16. Peter van der Woude
    A software update point is only used by clients to scan for compliance. The content will come from the distribution point.
  17. Peter van der Woude
    There might still be information in WMI of the SMS Provider, but it's probably easier to just recreate everything.
  18. Peter van der Woude
    Could make sense, but I haven't seen how they're created, so I can't say for sure.
  19. Peter van der Woude
    If nothing fancy is required, just use the ConfigMgr console to add drivers to the boot image. Only drivers added via the console, to a boot image, will show in the console in the properties of the boot image.
  20. Peter van der Woude
    You can slightly configure the restart notifications via the client settings (Computer Restart section). Personally I think the real solution would be to educate the users with the importance of restarting and/or shutting down their devices.
  21. Peter van der Woude
    Small note, the SMSSLP parameter is not used anymore in ConfigMgr 2012. The state locator point functionality is now part of the management point. That also means that you can and should use the SMSMP parameter for that.
  22. Peter van der Woude
    Did you verify if the task sequence variables are set?
  23. Peter van der Woude
    The one thing it does need before it can retry is a new deployment schedule. The "rerun on failed previous" is only applicable on the next time the deployment is scheduled to run.
  24. Peter van der Woude
    No you either exclude everything below an OU, or nothing...
  25. Peter van der Woude
    My mistake, as you didn't mention ConfigMgr 2007 and you did mention application, I assumed you were using ConfigMgr 2012. In ConfigMgr 2007 you can't configure detection methods. The only method to prevent the installation on system that already have that software is to create a custom script or filter them out of your collections.
×
×
  • 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.