SCCM Software Center: Need some quick help
-
To be more specific... it is an operating system that, if installed, would certainly brick any laptop that it attempts installation on (it's an incomplete build I'm testing) unless it flat out wouldn't take (50/50 shot at that one...). Made the mistake of deploying it and not merely distributing it. Huge oversight on my part.
-
I'm afraid that SCCM is outside of my ken.
-
@scottalanmiller Ah, no worries. Thanks for popping in anyway. It's enough pressure that it's got some cold sweats going on. I'm pretty sure I have it to a point that all people have to do is simply reboot their machines, but I'm trying to make this as seamless as possible. I already put it right out in the open for everyone (more so for the higher ups) so it doesn't seem like I just made a mistake and have no idea what is going on. But would love to avoid anyone accidentally installing a test OS obviously. I thought I was distributing it, not deploying as available. Obviously I need to pay closer attention to what window I'm in. Thanks anyway Scott.
-
@scottalanmiller said:
I'm afraid that SCCM is outside of my ken.
Just out of curiosity, what do you use for deployment then? Something like WDS or FOG, or something entirely different?
-
Interesting note while learning more about SCCM... you do indeed choose the Deploy option. I know in 2007 there was (still is with 2012?) a configurable option of Run Selected Programs in the Control Panel on the client. Effectively being able to reimage a workstation from the GUI instead of PXE. Instead of choosing Distribute for the task, you still choose Deploy. I thought by choose All Systems > Configuration Clients, boot media, PXE that it would (for the clients) put it in the list. It essentially put it in the Software Center list instead (noooo... don't prompt for that!). I should have only chose boot media, PXE (you can't JUST choose PXE... though you can choose hidden), for it to only show upon a successful PXE boot. Anyway, once I stopped the deployment. There was no two ways around it. I have to wait for users to log off/reboot. But since it didn't drag down the entire file (users can only see 1MB for the file size) and cache the package, I break the connection and it just drops off. Case closed I guess. Long afternoon.
-
@BBigford said:
@scottalanmiller said:
I'm afraid that SCCM is outside of my ken.
Just out of curiosity, what do you use for deployment then? Something like WDS or FOG, or something entirely different?
We are a small environment that is very disparate and have very few software packages. Pretty much everything is just MS Office. We can deploy very easily via Chocolatey. Pushing out from a tool like SCCM would be wasteful for us since it would have to push over the WAN every time which is a pain.
-
We don't even use SCCM here (a fortune 100) We looked at it but for the cost doesn't give us a lot over using WDS, GPOs and Powershell. It really just leverages features already there for the most part.
-
@BBigford said:
Hey everyone,
I was doing a test in SCCM and made a piece of software available to all systems. I went into SCCM and removed it from the "deployments" portion of the task sequence, found in the bottom section. After removing it from "deployments", it still shows up in user's Software Center as available software. Any way to force it to remove from user's Software Center so they don't accidentally install it? I've already sent out a mass email saying we're doing some testing, disregard the notification, and don't try to install it. Any help is appreciated. Thanks
Righto, I think that you are supposed to 'Retire' the application --> remove (delete) the deployment, and then delete the application.
-
Also, you should make a Test-Bunny user collection (a handful of the IT Staff as members) that you can deploy these apps to. That way the general populace doesn't freak out when apps appear/disappear
-
@BBigford said:
To be more specific... it is an operating system that, if installed, would certainly brick any laptop that it attempts installation on (it's an incomplete build I'm testing) unless it flat out wouldn't take (50/50 shot at that one...). Made the mistake of deploying it and not merely distributing it. Huge oversight on my part.
Utilise the "Unknown Devices" collection for this. That way you actually have to Delete the device from SCCM to allow the image to be deployed to the machine. (for initial testing)
As with the Test-Bunny Users Collection, you should really create one for computers too and use a direct query to specify which PC's are a part of it.
-
@Jason said:
We don't even use SCCM here (a fortune 100) We looked at it but for the cost doesn't give us a lot over using WDS, GPOs and Powershell. It really just leverages features already there for the most part.
It's not for everyone.
I should also point out that I recently found out that if you purchase a System Center 2012 license, you now get access to ALL System Center products. No more purchasing individual System Center parts. One license to rule them all. -
@scottalanmiller said:
@BBigford said:
@scottalanmiller said:
I'm afraid that SCCM is outside of my ken.
Just out of curiosity, what do you use for deployment then? Something like WDS or FOG, or something entirely different?
We are a small environment that is very disparate and have very few software packages. Pretty much everything is just MS Office. We can deploy very easily via Chocolatey. Pushing out from a tool like SCCM would be wasteful for us since it would have to push over the WAN every time which is a pain.
Yeah, NTG are pretty spread out. SCCM would be a pain to configure and then to push out things from.
SCCM 10747D course was gloating (read: distributing propaganda) about linking into Azure and utilising Intune.
A lot of fluffing around for not much return (if any?) in your case.
-
@Jason said:
We don't even use SCCM here (a fortune 100) We looked at it but for the cost doesn't give us a lot over using WDS, GPOs and Powershell. It really just leverages features already there for the most part.
I've never worked in a large enterprise that used it myself. Most use something similar or toolsets that cover a lot of the same ground, but SCCM seems like one MS product that is more common in the mid market than in the enterprise, from my limited exposure to it.
-
@nadnerB said:
Yeah, NTG are pretty spread out. SCCM would be a pain to configure and then to push out things from.
Yeah, tons of work for negative gain. We are licensed for it, so we could use it if we wanted. Just do not see the value in running it.
-
@nadnerB said:
SCCM 10747D course was gloating (read: distributing propaganda) about linking into Azure and utilising Intune.
We had Intune, we gave it up. Was okay but not good enough.
-
@nadnerB said:
That way you actually have to Delete the device from SCCM to allow the image to be deployed to the machine.
I've been looking for the GUID entries in SCCM 2012 but have been unable to find them. When a machine is reimaged by SCCM, I was under the impression that it does indeed log the machines entry in SCCM. Google has evaded me... do you know where they get stored at in 2012?
-
@BBigford said:
I've been looking for the GUID entries in SCCM 2012 but have been unable to find them. When a machine is reimaged by SCCM, I was under the impression that it does indeed log the machines entry in SCCM. Google has evaded me... do you know where they get stored at in 2012?
2012 is different to 2007 in that you don't need to go hunting for the GUID unless you are digging through the database.
That being said...
If you go to Assets and Compliance --> Overview --> Devices, you can add the GUID column by right clicking any of the column titles and selecting ID. Deleting the device from here also deletes it from the database.
