Jump to content


Peter van der Woude

Moderators
  • Posts

    2,925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. I think in a scenario like that the granular deployment would be the obvious solution and if not possible I would look at global conditions to simply verify if the app is installed.
  2. Create a custom policy for those machines and set Prompt user for Remote Control permission to No.
  3. You could have a look and see if the Set Dynamic Variables step might be of any use in this case. If not, then it would require custom scripting.
  4. What about using the default option for specifying an ip address in the task sequence wizard?
  5. When you only used Run command line steps then all the available logging should be in the SMSTS.log.
  6. Are you looking for something like this documentation script by David: http://www.david-obrien.net/2014/01/update-inventory-script-makes-configmgr-life-easier/
  7. Did you check the log files? In case of a PXE boot I would start with the SMSPXE.log.
  8. Are you by any change running Windows 7 x86? If so, please have a look at this: http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx
  9. Overlay is related to write filters. That settings is only applicable to Windows Embedded devices.
  10. That error can mean a lot of things. You need to provide more information about the messages in the installation log file itself and about what you're actually installing.
  11. Yes, you can. Also, schema extensions are not specific to a site.
  12. Two things to check. 1) Check if you're not deploying an update of the client. 2) Check the client evaluation (ccmsetup-ccmeval.log).
  13. Jason mentions the guidelines here: https://social.technet.microsoft.com/Forums/en-US/91910b73-2d47-424c-9f21-a4e4b06f0a82/best-method-to-apply-cu-to-default-client-package-for-use-in-console-pushes-osd?forum=configmanagergeneral
  14. To add-on to Garth, when nothing specific has been provided in the command line, the MSI often writes the log file in C:\WINDOWS\Temp.
  15. You're on the right path. You should use the required install. If it's not working please check the deployment status and the client log files for more information.
  16. Yes, I've heard that issue more often. The workaround is to set the deployment date back for at least a day.
  17. Please don't use a physical device to build an image, but use a VM instead. That will save you a lot of driver issues during the deployment of the image.
  18. No it doesn't has to be domain joined. It only needs to be able to communicate with ConfigMgr (MP/DP) and a network access account has to be configured in ConfigMgr to access the DP.
  19. Deploying to users gives you more flexibility. It does however not automatically remove the software after the user logs off.
  20. Yes, that's possible, but you have to clean it up afterwards. This should help you out: http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx
  21. It sounds like your PXE of the site server is responding to the client in the remote site. If so, than that's the reason why it's downloading the boot files from that location.
×
×
  • 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.