Just change this: if ($Coll.RefreshType -eq 6)
to this: if ($Coll.RefreshType -ne 2) Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: Thursday, July 25, 2013 11:34 AM To: [email protected] Subject: RE: [mssms] Script to Edit Collection Properties I think I figured it out… Mine are set to refresh type = 4 and I need them changed to refresh type = 2. It looks like the script checks for a value of 6 and changes it to 4. http://gregramsey.net/2012/02/15/how-to-enable-incremental-collection-updates-with-powershell/ ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of [email protected]<mailto:[email protected]> Sent: Thursday, July 25, 2013 9:51 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Script to Edit Collection Properties Hey John – this works fine for me on user collections: $a = [wmi] "\\mylab\root\sms\site_LAB:SMS_Collection.CollectionID='LAB00191'<file:///\\mylab\root\sms\site_LAB:SMS_Collection.CollectionID='LAB00191'>" $a.RefreshType = 6 $a.put() Do you receive any errors when you run this? And you’re running it using the same admin rights that you can make that change in the console, right? All of this would be limited to the rights you have in ConfigMgr. Also, to get a quick export of collection setting for this value, run this: $a = gwmi sms_collection -ComputerName mylab -namespace root\sms\site_LAB $a | export-csv c:\temp\collections.csv -notypeinformation Then in Collections.csv, take a look at RefreshType. 2 = normal update interval – no incremental 4 = incremental 6 = incremental AND normal update interval http://msdn.microsoft.com/en-us/library/hh948939.aspx Greg Greg Ramsey | DELL | 512.750.5205 ConfigMgr MVP<https://mvp.support.microsoft.com/profile=4226BAAF-E6DD-4911-9583-F0D876B53126> | Blog<http://gregramsey.wordpress.com/> | DellTechCenter<http://www.dell.com/configmgr> | @ramseyg<http://twitter.com/ramseyg> | in<http://www.linkedin.com/in/ramseyg> | [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Marcum, John Sent: Wednesday, July 24, 2013 3:17 PM To: '[email protected]' Subject: RE: [mssms] Script to Edit Collection Properties in what respect? ________________________________ John Marcum Sr. Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Brandon Linton Sent: Wednesday, July 24, 2013 9:00 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Script to Edit Collection Properties What's your smsprov.log look like? Sent from my Windows Phone ________________________________ From: Marcum, John<mailto:[email protected]> Sent: 7/24/2013 5:38 AM To: '[email protected]'<mailto:[email protected]> Subject: RE: [mssms] Script to Edit Collection Properties 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]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Brandon Linton Sent: Tuesday, July 23, 2013 4:10 PM To: [email protected]<mailto:[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]<mailto:[email protected]> | Work 484.323.7205 From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[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]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, July 23, 2013 3:27 PM To: [email protected]<mailto:[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]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Brandon Linton Sent: Tuesday, July 23, 2013 2:42 PM To: [email protected]<mailto:[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<mailto:[email protected]> Sent: 7/23/2013 12:36 PM To: SMS List ([email protected])<mailto:[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. ________________________________ 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. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
