Jump to content


Method to disable specific component


4 replies to this topic

#1 hlarsen

    Member

  • Members
  • PipPip
  • 10 posts
  • Gender:Male

Posted 25 May 2012 - 01:17 PM

Is there a method for disabling a specific component? Autopatcher is a God-send, but I don't want it to install Windows Search for XP, and haven't figured out how to tell the system to ignore that specifi component.

#2 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 735 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 25 May 2012 - 01:32 PM

Firsatly welcome to the forum
Answer to your question is an easy one- remove the tick from the checkbox(click on the tick to remove) and that update(or add-on) will not installed.Same goes for any update you do not wish to install,the opposite is true if you wish to add other updates to be installed.
If you want more information there is documentation in the general support forum.

Edited by Whatacrock, 25 May 2012 - 01:35 PM.


#3 hlarsen

    Member

  • Members
  • PipPip
  • 10 posts
  • Gender:Male

Posted 25 May 2012 - 02:27 PM

Thanks for that welcome, Whatacrock. I've been searching for an alternative to WSUS (I think it is a terrible piece of software) and really like Autopatcher. I've been downloading my patches manually and have written my own system to deploy them based on registry and/or version checking, but it's really clunky.

I see what you are saying, my bad for not being more specific.

I've setup an autoit script to run autopatcher as part of an automated deployment system. It's basically running autopatcher in unattended mode. I think my question should have been, when using the unattended mode, can I tell the Autopatcher what not to install?

An answer file might help, but part of my concern is going forward. I can't tell how the answer file works. I want to install approved patches, not install those not approved or already installed, and allow for varying conditions such as previously missed patches or new needs such as newly installed versions of dot net. I think the answer file just saves the current selection and doesn't make the allowances I want to make.

Edited by hlarsen, 25 May 2012 - 02:29 PM.


#4 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,160 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 25 May 2012 - 10:03 PM

As far as I know you are right... the answer file is just a rigid set of answer that will try to install patches that are already installed. I have not gotten to far into that code area yet just skimmed over it.

I have not gotten to that part of the code yet, but I will see about adding:
* an ignore "already installed" function
* adding an option to install new recommended files not in the list(the list will have a creation date so any updates made after that date can be autoselected)

#5 hlarsen

    Member

  • Members
  • PipPip
  • 10 posts
  • Gender:Male

Posted 29 May 2012 - 04:55 PM

Thanks, ViroMan. I've got around my issue by not installing recommended patches as critical, at least for the time being.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users