The service is working, except for occasional outages to the Comcast WAN - the wireless and conected ethernet ports are working during these internet disconnections. We can ping the internal services - but can't ping One site states that the firmware is out of date and possibly the issue.
As noted on the NetGear site and various Comcast forums, the firmware is updated by Comcast. Your help desk states that this is an automatic process ,it will update automatically, and nothing can be done.
August 7, at am. Thanks for that. July 11, at am. Running the script using the config. The log should talk specifically about that error and tell you to try running it with FirstRun and UseCustomIndexes. May 24, at am. With the new config. April 30, at am. I use your script regularly. But recently noticed some superseded updates are not being marked as expired. Release date goes back until for these updates. I tried debugging your script to identify if the script is really flagging these updates properly.
IsSuperseded is populated as False when that particular update is actually superseded. April 30, at pm. May 1, at am. I really doubt if these ghost updates came through third party application updates. Anyway, this implies script is fine.
It may need slight change to consider this scenario as well if the whole thing turns out to be valid. I was going through few other updates as well, which are shown as superseded, but not flagged as expired by the script. There are many, which are superseded even in Microsoft Update Catalogue, but skipped by the script for some reason. Below is one example;. April 4, at pm. Bryan, Works great, with one exception so far. I spoke one of my coworkers you know him.
I was able to run it with the command-line and it works, just ends up being a BEAST of a command-line to construct. The one thing that tends to trip people up is that when ran manually the script will set the WhatIfPreference globally. Just restart your PoSH session and it should work. I will see if I can clean that up at some point. I have the same issue with using the config. When running the script it acts like WhatIfPreference is not commented out.
The commands work fine when running it manually. January 8, at am. March 18, at pm. If I had to guess, it has something to do with permissions or some change to support the settings files and relative directories. I know that I test with that feature enabled and it poops out a file every time.
March 13, at am. For me, this script is broken since I use SSL. You just need to comment that line out. February 26, at am. February 23, at pm. Great tool my friend!! One item I would like a bit of clarification on.
Look forward to your guidance. You are correct. February 22, at pm. February 23, at am. Hahah, yea the comments really help me when I get a piece of code and I wonder what the hell I was thinking.
February 22, at am. That being said, for WSUS the timing is less crucial than in ConfigMgr because in the later you need to orchestrate when they sync, when the script runs, and when your ADRs run to deploy your updates. What I would do is disable the internal sync WSUS schedule and then write a PoSH script to trigger the sync, wait for it to finish, then run maintenance.
January 17, at pm. That is s different way to look at it but I can see where your coming from… Could you possibly update the documentation above to make that clearer? The results are 0 superseded updates have been declined yet I know there are a few. To be sure I wrote a simple code to find all superseded updates and sort by CreationDate, The following 4 meet the decline criteria:.
In other words, the age of the superseded updates is irrelevant. January 9, at pm. Hi Brian, I was looking at the code for the delete date as noted earlier it was the same as the decline date.
The -1 there is simply to take the existing ExclusionPeriod parameter used for declining updates and use it for deleting declined updates. What value are you using for the ExclusionPeriod? It would seem to be 36 based on the dates you have there. I read the documentation as if I set the exclusion period to 12 months, then the logs should say declining updates older the 12 months and deleting updates older then 24 months.
How the decline date are tracked in the data file is really up to you. It honestly took me a bit to get my head around too but what the log says is correct and as it should be.
It will decline updates that were superseded more than ExlusionPeriod months ago. It will also delete updates that you declined ExlusionPeriod months ago. January 8, at pm. What are the Actions, if any, do you set in the status filter rule you create called Run Software Update Maintenance?
The action is to run the script using a cmdline along the lines of what I have posted above that. I have found out the hard way that downstream servers seem to replicate new stuff but not removal of old stuff? Like when you remove declined updates. Approvals, which is what declining an update is, should flow from the top down into your hierarchy. However, Microsoft recommends running the cleanup wizard from the bottom up. Super high level though: any autonomous server you should run the full script against.
Any replica should only get the cleanup wizard and DB maintenance stuff. Thanks for the quick answer! Unfortunately because we also use a third party tool equivalent to SCUP we had to setup a downstream server replica for load balancing. Because declines should absolutely sync down. December 11, at pm. I ran the script with the -FirstRun -Force switches. It went on to work on what appears to be updates — curiously NVidia updates.
November 13, at am. H Bryani. Fantastic script, however I have a question about your ADR updating. Thanks again for a fantastic blog. It tries to explain what the requirements are.
Sounds like a short blog post. October 31, at pm. So how should run now? Correct, you can simply call the script by itself without any parameter. The documentation above was changed to reflect that. However, to be clear, you can run it however you want.
October 31, at am. Hi Bryan, this looks great and I would love to use it. But I am getting an error when I run it. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. First, my condolences on using WID. Those can be ran a single time and then automate the rest. November 22, at am. Did something changed with the latest version of the script? Connected to WSUS server xxxx.
October 30, at am. I am trying to use:. NET Framework 3. Decline By Title mean decline anything that contain x. If I understand, you want to decline only those superseeded that contain a specific title? This is already done since all superseeded updates are declined based on your settings unless you removed this setting.
It means it decline anything that match the title. So what are you trying to achieve with the declinebytitle? If you run it without any plugins, per default, is the result missing something?
What Jean-Sebastien said is correct. The various Decline parameters work independently of one another. The DeclineSuperseded will decline all superseded updates regardless of title.
The DeclineByTitle will decline all updates that match those titles regardless of their supersedence status. If you want to only decline superseded updates with specific titles you will need to create your own plugin to do so. Thanks Bryan and Jean, and thank you Bryan for this wonderful script! Du hast. I love it when people actually read the code so I like to reward them with a bit of humor.
Glad you found it. You can use a template or, like me, instead of using the declinebytitle, I created a pluging for everything I want. Your plugin would look like this. Thanks for posting. October 27, at pm. I may have missed it, but what is up with this log format? What tool will open these in a readable format? I mean beyond just a text editor.
Is CMTrace supposed to be able to translate the date format? April 5, at am. October 25, at am. Hi Brayan, For some reason my plugins are not working. Can you please help to fix it? Enumerating and calling plugins. Plugin Info: Kept most of the plugins as it is and just changed Decline-Windows10Versions plugin and added supported versions. Just uploaded the correct plugins. Please test them out and let me know. October 17, at am. First, try the latest version I just uploaded.
Second, update PoSH. October 19, at am. I updated powershell to 5. But I still have this in updatemaint:. Is it? December 19, at pm.
Please let me know if I can provide any more details. Help would be appreciated! December 20, at pm. Well yes. Should work for you now. If not, it should fail for some other reason so let me know. Thank you very much for your efforts! October 13, at pm. That function has a progress bar so you can watch with joyful anticipation.
October 14, at pm. So i already have the firstrun parameter listed, i did have a progress bar during the first stage of the script when it went through declining a tonne of updates, but its moved part that part and is now reporting this in the log;. October 15, at am. October 12, at pm. In Powershell, the command GetUpdates return me about 14 objects. Once I filter the declined, I have updates. WSUS list me out of updates as declined.
I only deploy updates and WSUS have only 2 updates approved. Simply put, no. What you describe makes total sense to me. The WSUS console will not show obsolete or 3rd party updates. Eventually those get removed from ConfigMgr but remain in WSUS … which was the initial reason a script like this needed to exist in the first place.
Ah, that make sens. I tried to find a way using get-cmsoftwareupdate to match all deployed update with those on the wsus server and decline all other update, but I failed at finding a matching item. I tried using update. Any idead how this could be done? October 1, at am. Will try to delete obsolete updates by directly calling the database store procedures. The timeout period elapsed prior to completion of the operation or the server is not responding.
Have you seen this problem anywhere when the inital cleanup command line. Powershell -File. October 10, at am. Just yesterday I was working with a friend who had the same problem. CommandTimeout value in seconds to something higher. I plan on setting it to 24 hours seconds in the next release and do some better error handling on those calls.
Give that a shot and let me know. September 27, at pm. What the actual f——? Only 16 Comments.. SO Just posting.. O—M—G -This is the one. Script to run! So good… Shiiiinyyyyy…… Precious…………….. May 16, at am. Hi there Thanks for sharing this great script. There is a small error in two lines where the percentcomplete is calculated. Otherwise you get errors about the percent complete going over in the write-progress function. Late to the game here Peter but this should be resolved at this point.
April 18, at am. Hi Bryan, great post and script, even for a PS Newbie like me. I checked out the script and ran with the -whatif switch to see the number of obsolete updates that would be removed — returning updates. I do not find any reference between number and a specific update. May 2, at am. Sorry, I really gotta fix the comment notification.
April 11, at am. April 11, at pm. Could just be a disconnect between WMI and the console. Have you tried running another sync? Source: Microsoft. March 20, at am. One question though; How long should this run? The PS1 is still running though; Can that be the case? March 20, at pm. February 13, at am. Props …. February 14, at am. The key is to remember that the purpose of Deployment Packages is only … only … for content distribution of the update binaries or installers.
They are totally unrelated to Software Update Groups or deployments. Practically speaking though, your DPs need to handle the validation of that package and packages can and therefore will go sideways on you forcing you to recreate them. The chance of a deployment package corrupting itself and the impact of recreating it is tied directly to the number of updates or the size of the deployment package.
So most organizations, mine included, usually create a new deployment package yearly. The source is essentially updated and all the DPs are going to try to get it immediately. If your organization needs to stagger the content distribution you might consider creating monthly deployment packages and add DPs or DP Groups over a period of time either manually or some other automation. December 1, at pm. This script has work wonders.
Tested this in my homelab and in production. Everything from the customized plugins to dumping the logs into something readable. December 3, at pm. Thanks for the kinds word Brandon, I had a lot of fun presenting. November 30, at am. I am getting an error of: Key cannot be null. UpdateID Error: …. November 30, at pm. That was an failure in the error logging for the CleanSources routine. Honestly, in all my testing I never saw that section of code do much of anything.
Dam Good Admin. Search for:. Reddit Twitter Facebook LinkedIn. Andrew Hall October 21, at pm. Bryan Dam Post author October 21, at pm. Andrew A. Vern Bateman July 5, at pm.
See my original post June 8th, thanks Vern Reply. Bryan Dam Post author July 5, at pm. David Briese June 9, at am. Bryan Dam Post author June 9, at am. David June 9, at am. But that other thread is about upstream speed -- competely different issue as you yourself mentioned Why would this thread get locked when I didn't find a DSLR thread covering this specific topic? I know there is the one kind of like it on CC, but as I'm saying, I don't quite get it On my upstream thread you said "Your understanding is perfect.
The difference is only the chip used. The has an updated version. Since they are so close in all respects, config files are generic; however firmware versions are not. Or is the heart of the issue that my modem needs an update to the firmware that will let it accept a config? If that is the case, then isn't it up to CC to push a firmware update first because users can't update firmware on their own so that the config they are tyring to push will be acceptable?
And if that is the case, then why hasn't CC already pushed a firmware update ahead of the config? Oh my head So you are getting the config pushed on your modem? Must be because I've been getting it. My up speed has been fine.. Thanks for those threads Johkal. I read them and everything spoking from them.
I think now I get it. Thanks for your patience while I stumbled up the hill. Chronologically the log entries show 6-Notice E And presumably the "unspecified file" is a firmware update.
It makes sense now. The problem may have started when CC initially received the modem and entered it into the CMTS Database and inventory -- the wrong model number was entered easy to mistype for , or pick the first drop-down from a GUI.
I should come home with a correctly configed modem -- but no guarantees 3 If nothing helps, call the Executive Complaint Center at But that still may not help I have a ticket open, so perhaps I'll get through step 1 okay after all the pain you and others went through to get it clarified. Head doesn't hurt so much just now!
Just for yucks I reset my and lo and behold what came down the pike: 6-Notice E I may be able to help clarify here: Comcast's config files are nearly identical between modem models. This means that any modem could likely use ANY config file on comcasts systems mostly without issue. Comcast segregates config files by model because that is the method they choose to send firmware updates.
Part of the config file has your modem check to see if it has the most current firmware. There is a tftp address and file name to check and download if different than current firmware.
0コメント