Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. It is possible to create two deployments of one application. Just wondering how it will exactly behave when a user is a member of both groups...
  2. Here is a thread with the same subject: http://social.technet.microsoft.com/Forums/en-US/265d3460-cf62-404e-8d0b-77065eb956bc/schedule-reevaluation-for-deployments-question?forum=configmanagerapps
  3. The problem is that AFAIK it's not possible to do a select from SMS_R_System in a User Collection....
  4. The link between an ADR and a deployment package is only visible via PowerShell. This will be 'fixed' in R2. For an example of how to change it now, see: http://gallery.technet.microsoft.com/Change-the-Package-linked-65662298
  5. The default application deployment re-evaluation cycle is 7days... it can be manually triggered via the actions tab of the client.
  6. What exactly are you trying to achieve? Your current query contains all selections from devices, while you're talking about a user collection.. those two things don't match.
  7. You can indeed try in case the GPO is not applying. Keep in mind that ConfigMgr does basically the same, but then via a local policy. So make sure they are at least equal, when using both methods, as the GPO will always win/overwrite.
  8. Did you take a look at the installation log files of the MP?
  9. On the server-side the SUP uses WSUS only for it's metadata. At the moment that it will really download the update it will use the content location (which is specified in the metadata) to download the update itself. So ConfigMGr/SUP downloads the real content and not WSUS.
  10. It displays the disk space of the disk where it's installed.
  11. Really?!?!? This is a community forum, with all people answering questions in their own time! Please respect that and don't expect answers directly. If you want a direct answer just call Microsoft or a consultancy company.... Back to the question... I've got no clue what you mean with your Managment Point displays 0 bytes... Can you give some more information?
  12. It's a known issue with a few updates, see this kb-article: http://support.microsoft.com/kb/2894518/en-us
  13. This is very little information.... It sounds like the UDI is still a step in the task sequence, which means that you have to check the logics of the steps (what's configured in the options tab?).
  14. Did you add a reference to the Content Location (DP) in the Distribution Point Group?
  15. CU3 only adds support for Software Distribution, Software Update Management and Compliance Settings for Windows 8.1.
  16. Start by looking at the ccmsetup.log in the ccmsetup directory.
  17. What about duplicate GUIDs?
  18. A device is affected by every maintenance window that is targeted to it via any collection. The different maintenance windows are cumulative.
  19. Ehmm... keep in mind that the only reason for a client to stay in provisioning mode is because a task sequence didn't end successful. In other words, if that's the case, try finding the root cause as there might be a different/bigger problem...
  20. AFAIK not in a supported way. The only supported way is to make a backup, do a clean install and restore the backup.
  21. You can use the PATCH= property in the Installation properties to specify the specific update(s).
  22. You could also use a Configuration Item (which is actually build of PowerShell scripts), see: http://powersheller.wordpress.com/2012/11/20/sccm-2012-setting-software-center-business-hours-with-a-compliance-configuration-item/
  23. That's default behavior, when using the standard install.wim. The good thing is that there is a solution, see: http://www.petervanderwoude.nl/post/how-to-apply-the-default-install-wim-of-windows-7-to-c-with-configmgr-2012/
  24. It looks like the client isn't assigned to a site yet and/or can't communicate with the MP. Look at log files, like ClientIDManagerStartup.log, LocationServices.log, ClientLocation.log.
  25. Can be a lot of things, like problems with joining the domain, problems with the client installation, etc.. Try looking for more information..
×
×
  • 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.