Jump to content


dunkel

Established Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dunkel

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Canada
  1. Yes. I was under the impression that SCCM injected extra files for Command support during the image build process. I will double-check by following the steps on your webpage and report back.
  2. I saw that solution but it doesn't seem to apply. I connected wbemtest and I see that the value described is already set to TRUE.
  3. I was wondering if there is any way to replicate what SCCM does when checking the "Enable command support (testing only)" checkbox for a Boot Image in SCCM 2012. I have a rather particular boot image that I must configure outside of SCCM. Everything is working as it should but I cannot find any info on enabling command line support for WinPE. Thanks.
  4. Here's a quick resume of the current setup I am using. I've been using AD groups to deploy applications from SCCM with query-based collection membership for devices. In short, this means that in AD a computer is added to a group and whenever SCCM runs AD Group discovery and sees a change, the collection which queries that group also updates that group and the application is deployed on the target computer. This was done in order to preserve the historical AD structure and method of deploying applications (previously done with GPOs). This works flawlessly and is relatively quick. Since we do not have a way to remove applications as of now, I am trying to trigger an uninstall deployment whenever a computer is removed from an AD group. I cannot push an uninstall deployment method on a collection that would include all systems except those that are members of the deployment group since this would break systems with the target application installed before SCCM implementation. There is however something that I have tested with a single application which consists of deploying a configuration baseline to all systems that detects if that particular application is installed. I then create a collection that excludes the "Install target software" collection and queries for compliant computers. I then deploy an uninstall application on the resulting collection therefore uninstall the application from the member systems. It seems to work properly for now. I am using configuration baselines because of their ability to run powershell scripts as part of the compliance process. My question is, is it against best practice to have a lot of configuration baselines? I have around 40+ applications that are deployed through SCCM and it would require the same amount of configuration baselines to ensure application are uninstalled in sync with AD group membership. Thanks.
  5. Thanks Peter. I set up your second option in my lab environment and it seems to work as advertised. Only downside is that if a workstation misses the reboot window then it skips its turn until next time but I'm willing to live with that.
  6. Thanks for that info Peter. What I'm trying to achieve is to have my workstations patch themselves on the second Wednesday of every month and give users a week to reboot their computers. Is this something that can be done with SCCM and maintenance windows? I can't seem to dissociate installation from reboot in software update deployment.
  7. Hi, I have my software updates setup to install on Wednesday right after MS Patch Tuesday. As far as I can tell all the patches are deployed succesfully but clients keep receiving updates for days after the installation deadline which causes multiple reboots. Is there any way to prevent this or maybe setup a maintenance window on a specific day of the month and outside of that no updates are pushed to clients?
×
×
  • Create New...