NickolajA
-
Posts
97 -
Joined
-
Last visited
-
Days Won
6
Posts posted by NickolajA
-
-
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.
-
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!
-
If you've got lots of different models of computers, auto-apply can break stuff for some of them. It'll sometimes pick the wrong "best" driver for a component.
I'd say that if if works for you, then hey, great. We ran with it for a long time. Then we got in some Lenovo T440s that required a newer version of a driver used by our existing Dell Optiplex 7010s. When auto-apply picked that "better" driver for the 7010s... BSOD.
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.
-
You could set the BITS maximum transfer rate on your clients to a certain amount of KB/s during your business hours.
-
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.
-
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.
-
I second Nial and Jakob, dedicated server for MBAM.
-
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.
-
You're welcome. Glad we could help!
-
Just a lousy answer, but have you attempted to create the E: volume to see what happens?
-
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.
-
Have you verified that you client is in fact within a defined boundary in ConfigMgr? Is it an IP-range boundary?
-
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.
-
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?
-
Like Garth said, this is the default and non-modifiable configuration for Software Center.
-
Are you're using ConfigMgr with MDT integration, you could create a new Client UDI task sequence (User Driven Installation task sequence), where you have the option for the "Applications" screen to appear. That way your help desk team could select what applications they want to install. Here's an excellent guide for your scenario:
-
2
-
-
Then build a new site and slow migrate clients from one to the other.
I agree with Garth on this one.
-
A side-by-side migration is really what you do when you migrate from ConfigMgr 2007 to ConfigMgr 2012. You setup and configure a new environment and connect from the new environment to the old. When the source hierarchy configuration is working, you're able to migrate almost all of your objects and configuration from the old environment.
-
Yes there is, but you'll most likely not find any script that does exactly what you're looking for (or perhaps you will). I'm just saying that you could look at my scripts to perhaps get an understanding of what classes you'd have to work with when you create your own
-
It's all about the deployment and how you'd configure its setting to adhere to the configured maintenance window. The deployment deadline also plays a huge role in a successful configuration.
-
You can't have both ADK 8.1 and ADK 10 installed. You'd have to go with either one, and just to be clear, both are supported for ConfigMgr 2012 R2 SP1.
-
That's not gonna work, since there can be several Primary Devices for a single user, and you're only able to have one of them per line. You'd have to have duplicate lines for the users.
I've created a couple of scripts related to Primary Users/Devices, maybe they can be an inspiration for you:
https://github.com/NickolajA/PowerShell/tree/master/ConfigMgr/Users
-
Just to clarify, what that means is that he installed https://support.microsoft.com/en-us/kb/3084586
-
Since you're not prestaging (or importing it, whatever
) and using Unknown Computer support, ConfigMgr only knows that this system during the provisioning phase is in the All Unknown Computers collection. Therefor you'd have to deploy SUG's to that collection if you'd want to deploy Software Updates during OSD.I'm glad I was able to help!
Removing Expired Updates from SUPs and DPs
in Configuration Manager 2012
Posted
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/