I haven't looked at the script, but if it has this line:

  if ($Coll.RefreshType -eq 6 -And $Coll.CollectionID -notlike "SMS*") {****

It will skip all user collections. User collections start with SMS and
device collections start with CM. Remove any checks in the script for the
collection ID starting with SMS and it should work.


On Wed, Jul 24, 2013 at 7:36 AM, Marcum, John <[email protected]> wrote:

>  Did you test on 2007 or 2012? I tried the script on Greg Ramsey's blog
> that you link to as well. It only lists out the device collections not the
> user colletions. I am running this on 2012.
>
>
>
>
>
>
>  *
> ------------------------------
> *
>
> *John Marcum*
> *Sr. Desktop Architect*
>
> *Bradley Arant Boult Cummings LLP*
>  ------------------------------
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Brandon Linton
> *Sent:* Tuesday, July 23, 2013 4:10 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Script to Edit Collection Properties
>
>
>
> I validated that this works on user collections.  Did you verify this on
> the default collections?  I have them excluded by default.  Check one of
> your custom user collections and it should be disabled.
>
>
>
>   if ($Coll.RefreshType -eq 6 -And $Coll.CollectionID -notlike "SMS*") {
>
>
>
> *Thanks,*
>
> *Brandon A. Linton* | Sr. Consultant | [email protected] | Work
> 484.323.7205
>
>
>
> *From:* [email protected]
> [mailto:[email protected]] *On Behalf Of *Marcum, John
> *Sent:* Tuesday, July 23, 2013 1:43 PM
> *To:* '[email protected]'
> *Subject:* RE: [mssms] Script to Edit Collection Properties
>
>
>
> I spoke too soon…. This only did device collections. I need user
> collections. :-(
>
>
>
>
>
>
>   *
> ------------------------------
> *
>
> *John Marcum*
> *Sr. Desktop Architect*
>
> *Bradley Arant Boult Cummings LLP*
>   ------------------------------
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Marcum, John
> *Sent:* Tuesday, July 23, 2013 3:27 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Script to Edit Collection Properties
>
>
>
> thank you sir.
>
>
>    *
> ------------------------------
> *
>
> *John Marcum*
> *Sr. Desktop Architect*
>
> *Bradley Arant Boult Cummings LLP*
>    ------------------------------
>
>
>
> *From:* [email protected]
> [mailto:[email protected]] *On Behalf Of *Brandon Linton
> *Sent:* Tuesday, July 23, 2013 2:42 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Script to Edit Collection Properties
>
>
>
> Here yea go.
>
>
> http://blogs.technet.com/b/brandonlinton/archive/2013/04/23/powershell-how-to-disable-incremental-collection-updates-in-mass.aspx
>
> Thanks
> Brandon
>
> Sent from my Windows Phone
>   ------------------------------
>
> *From: *Marcum, John <[email protected]>
> *Sent: *7/23/2013 12:36 PM
> *To: *SMS List ([email protected]) <[email protected]>
> *Subject: *[mssms] Script to Edit Collection Properties
>
> Does anyone have a script to uncheck the box "use incremental updates for
> this collection" for all collections? Also I'd love to see a report of all
> the collections that have it checked before unchecking it if anyone happens
> to know how to get that out of SQL.
>
>
>
>
>
>
>    *
> ------------------------------
> *
>
> *John Marcum*
> *Sr. Desktop Architect*
>
> *Bradley Arant Boult Cummings LLP*
>    ------------------------------
>
>
>
>
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
>
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
>
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
>
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
>
>
>
>  ------------------------------
>
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
> ------------------------------
>
> Confidentiality Notice: This e-mail is from a law firm and may be
> protected by the attorney-client or work product privileges. If you have
> received this message in error, please notify the sender by replying to
> this e-mail and then delete it from your computer.
>
>



Reply via email to