Jump to content


NickolajA

Moderators
  • Content Count

    97
  • Joined

  • Last visited

  • Days Won

    6

NickolajA last won the day on July 11 2017

NickolajA had the most liked content!

Community Reputation

11 Good

About NickolajA

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    http://www.scconfigmgr.com

Profile Information

  • Gender
    Male
  • Location
    Stockholm, Sweden
  • Interests
    ConfigMgr, Intune, PowerShell

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. An active Deployment for a Software Update Group is a deployment that's not disabled, meaning it's enabled Use my Clean Software Update Groups extension: http://www.scconfigmgr.com/2015/03/15/clean-software-update-groups-console-extension-for-configmgr-2012/
  2. Check in the WSUS console to see if someone have used that to configure the language settings. If you for instance make a change through ConfigMgr on your SUP, it's propagated to WSUS. But if you make a change in the WSUS console, it's not visible in the ConfigMgr console.
  3. I've not heard anything against having "a lot" of Configuration Baselines. But I'd be cautious with how often you set them to evaluate, since it may put unnecessary load on the client. Cool trick!
  4. For example if you have several versions of the driver in your catalog but they are intended for various models, the PnP will select which one it thinks is the best in accordance with it's ruleset and it might break things, especially for TPM drivers this happened a lot a while ago. Driver Packages is the way to go, it's also really simple to maintain and update with a versioning fasion.
  5. You could set the BITS maximum transfer rate on your clients to a certain amount of KB/s during your business hours.
  6. I'd think that's because when you re-image the machine, the execution history on the client is not preserved and due to the fact that there's a TS deployed to it and it is allowed to run it again during the maintenance window, it will re-run.
  7. Like Peter is saying, that's the default behavior. It's rather better to have the clients at their "random" time (what I mean by that is that not all clients will refresh their machine policy at the same time) download the content, than after the deadline during a maintenance window all of them would download at the same time.
  8. I second Nial and Jakob, dedicated server for MBAM.
  9. I'd say that's "normal". It all comes down to what update classifications that you've selected to download in addition to the update languages. I'd start looking at deploying SP1 if you haven't done that already.
  10. Just a lousy answer, but have you attempted to create the E: volume to see what happens?
  11. In ConfigMgr 2012 R2 SP1, Operating System Installers was renamed to Operating System Upgrade Packages. They simply have the same purpose as before, just with a new name.
  12. Have you verified that you client is in fact within a defined boundary in ConfigMgr? Is it an IP-range boundary?
  13. I had a look around in the DB, but I was not able to find anything referencing the user name. You could simply just remove the subscription, and re-add it if you're unsure.
  14. Yes, I'd say that some of the official documentation. Although with ConfigMgr 2012 R2 SP1 the process is a bit more complicated since the task sequence engine including the new steps will first be released in the vNext version that's about to be released during Q4 this year. Why are your users not logged on in the first place? Are you In-Place upgrading newly imaged system that has not been given to a user yet?
×
×
  • Create New...