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. That is indeed nuts. A CAS will not help you with your security boundaries. You might want to think about scoping objects so they can only access anything related to desktops.
  2. Usually you should uninstall the old ADK and after that install the new ADK. Also, keep in mind that you can even move to the Windows 10 ADK if you need to think about Windows 10 deployments. For some more information about that see: http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx
  3. For an example that should help you out see this: https://asithadesilva.wordpress.com/2013/04/01/how-to-prompt-collection-to-a-report-in-sccm-2012/
  4. When you've update ConfigMgr and the Windows ADK, then this is expected behavior. To view the drivers and everything available in the boot image you can use DISM manually.
  5. Are you sure you've made the adjustments to the client settings? That should trigger the creation of the new views.
  6. Well, that explains what you're seeing... Also, did you check the mentioned log file for more information?
  7. That's normal behavior, the maintenance windows are to prevent the installation and the restart. If you don't want anything to happen yet, you should make it available later (deployment scheduling).
  8. Thanks! The best option also depends a bit on the scenario. For example, when a client is only installed during OS deployment, you can also look at the MP_ClientRegistration agent name and time. Another option could be to tattoo your devices with the deployment information. In that case you could do something like this: http://www.petervanderwoude.nl/post/reporting-about-the-all-the-different-os-deployment-versions-with-configmgr-2012/
  9. If I'm not mistaken this works still the same as it did in the old SMS days. The good thing is that there is an article of that period with more information. Before the SMS UUID will change there have to be three hardware changes as mentioned in the following article: https://support.microsoft.com/en-us/kb/837374
  10. That's a very good start! You can make it even prettier by looking into configuration items.
  11. At what point in the task sequence are you performing this action?
  12. Yes, that's possible, but it will require (a lot) custom scripting. You need to find out the location and you need to find out the number that it has to use.
  13. That will be a hell of a job, because the ConfigMgr client runs in the SYSTEM context. That means it would require custom scripting in which you find the current logged on user and go through it's hyve in the registry.
  14. Not sure if it's directly related, but keep in mind that the failure comes from the Active Directory Group Discovery and not from the Active Directory User Discovery.
  15. You could use something like the following tool to adjust the source location of packages: http://www.scconfigmgr.com/2015/08/26/configmgr-content-source-update-tool-1-0-0/
  16. Agree. For running something on a schedule the package-program is the easiest method.
  17. I'm sorry, I completely missed the part about a stand-alone media, I responded based on the failure you've got. Are you absolutely sure that you've created a stand-alone media? A stand-alone media doesn't need any interaction with the site server at all...
  18. What version of ConfigMgr are you running? Also, what exactly is the issue that you're running into that makes you look at that post. Doesn't your task sequence start? Does the task sequence fail at a specific point? What's in your SMSTS.log file? As you can see, a lot of information is required to say something usefull
  19. That's usually an indication that either the task sequence is not deployed, or that the device is not in the right collection.
  20. One not small note here, only edit the database when suggested by Microsoft Support.
  21. Those are variables created by the poster of that script and they are not ConfigMgr variables.
  22. The problem is within the scoping. When those users are scoped to collections containing those devices, there is not much you can do from preventing them from adding those devices to a collection.
  23. At least your first issue sounds like it's still busy loading within the console. Please check your SmsAdminUI.log and Smsprov.log 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.