The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
A few days ago I asked if anyone would be interested in an article/tip about setting up WSUS. The response was somewhat underwhelming (and focus quickly turned to the fact that I use a 10-year old version of OneNote) so I decided not to bother.
Anyway. I've been struggling with getting clients to connect to it ever since. Until this morning, when I changed the policy that names the WSUS server to include the port at the end of the string (:8530). After making that change, and then refreshing the policy on client endpoints, they started trickling in almost immediately.
This wasn't necessary before. The port hasn't changed. Why it's suddenly needed in this version, I don't know. Or when it became a requirement, I don't know (it could've been introduced in 2012, 2012 R2, 2016 or 2019...and I'm not about to review the documentation for each to try to find out).
The lesson, I guess, is don't take anything for granted...like assuming newer versions work the same as old versions (even though, based purely on the UI, you'd think MS hasn't done any change to WSUS).
Of course I know the difference between a URL and a name. I simply wrote that the server was "named" in that string because the URL happens to identify the server...by its name...
The change was made in version 6.2 from the default of 443 to 8530. The reason the URL did not need the :8530 before is because HTTPS defaults to 443.
I'm not following. The default (non-https) port was always 8530, and that's how I've always had it configured (by omission).
Are you claiming my older server, by not having any port specified, was therefore defaulting to an https connection, and not using port 8530, and now the newer version is enforcing https over port 8530 and effectively no longer using https over 443...? I'd love to see the page documenting that. Even that doesn't make sense, since the policy for my previous server had always been set to:
•On WSUS 3.2 and earlier, port 80 for HTTP and 443 for HTTPS
•On WSUS 6.2 and later (at least Windows Server 2012 ), port 8530 for HTTP and 8531 for HTTPS are used
So...even though WSUS has been widely known to be using port 8530 since day one, if you don't specify the port, it'll default to 80...
I've always made the assumption that if it "uses port 8530 by default", then if not specified, then that's the port it'll use. Meaning, even though I didn't specify one, the initial handshake might be done over port 80, but then switch over to port 8530. What the docs infer is that even though 8530 is the default, if not specified, then it'll implicitly use 80 and stick with that. That's a confusing definition of "default" if that's the case. And if it is, then I'm not sure how it would be technically wrong to instead say it's using port 80 by default. To me, "by default" has always meant "this is what will be used if omitted".
Anyway...again, the bottom line remains, don't take anything for granted.
When I win the new year lottery, I promise to treat myself on a trip with the Rocky Mountaineer[^]
Otherwise I will have to settle for a week in the Belgian Ardennes, which is the closest to mountainous terrain we have nearby.
Turkey white meat is unappealing; I eat (devour) the back half -- this goes for chickens as well.
White meat is good only for sandwiches.
When I were a lad my mother cooked a turkey once a month. (No, not the same turkey.)
Turkey was great for us; after my dad and I came back from our annual hunting trip(s) we would have moose (or caribou) in all the variations possible: steak, roast, sausage, ground, pot roast - my dad actually made corned moose a couple of years - even he couldn't stand it (800 lbs of moose takes a while to process and eat - we did our own butchering). Caribou was closer to elk, but still generally the same. One year I got a largish black bear on bow and arrow, that was pretty good.
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
I think the tradition goes back a few hundred years (see A Christmas Carol), when most people were poor and meat was a treat. That was much the case in my family in the 1950s and early 60s. Most days our meals could not exactly be termed 'hearty', but we generally had a cheap roast on Sundays. At Easter we had chicken, which was a treat in those days, and at Christmas we had turkey, two occasions for feasting. The traditional part has now been so devalued, by multiple Christmas meals in December, that there seems little point in choosing what is essentially a very average meat. However when catering for 12-14 adults it is a good choice.