@obsolesce said in Wsus for remote vpn and on-premise users:

@scottalanmiller said in Wsus for remote vpn and on-premise users:

There is little different between an MSP and internal IT.

They are basically the same thing. In many cases the internal IT is a separate entity that basically bills the company and/or child companies, but is on the payroll of the company.

Yup, the key difference isn't their relationship to the rest of the org, effectively MSP, ITSP, Internal IT, etc. are all external in how they are approached. Only how they are paid really differs and the staff don't always see that.

What makes the two different is that an Internal IT department (even one treated as a consulting group) has only a single top level customer and MSPs have multiple. That's really it.

And that doesn't always make a real difference. If the top level internal IT customer doesn't force all underlying groups to unify under a single IT strategy you get an effective situation of multiple customers, sometimes as you said, even with separate billing.

@wrx7m said in Server 2016 - Force Default Update Server to WSUS Server Via GPO:

@dbeato said in Server 2016 - Force Default Update Server to WSUS Server Via GPO:

This would have happened on Server 2012 R2 as well, dual scan has been around and causes a lot of problems as you noted.

It is strange that I didn't have these issues in 2012 R2. I essentially copied the same GPO for 2012 R2 and made some minor changes to it to convert it for 2016. My 2012 R2 show the correct default service.

Weird, I have various Server 2016and now 2019 with WSUS and while dual scan was an issue for me on Server 2012/ 2012 R2 not anymore.

@jt1001001 Thanks. If you are running from PDQ deploy, you won't see anything. But, if you are doing it from PS/ISE or similar, that would be a great help.

@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:

@scottalanmiller said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:

@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:

@dbeato said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:

@dave247 said in Most of my Windows 10 1803 computers upgraded to 1809 despite it not being approved in WSUS / Dual Scan is a thing:

e systems was a consumer version of Windows 10 which the previous tech installed - no idea where he got it.

Probably came pre-installed on the Dell Computer and not imaged.

Actually it had Windows 7 installed on it but then the co-worker put his version of Windows 10 that I think he got from college on it, and a few other systems. So idk.

Windows 10 will activate on a Windows 7 license. So should be all set from that perspective.

I don't think so.. and it was a fresh install, or at least I know he used the Windows 10 key that he had been provided. That key was also used on about 5 other systems at the time.

You can work around it, but should accept the Win 7 key, too.

I finally got this to work if anyone is interested. The sql file is fine, but I had to change my batch file. The correct one looks like this:

"C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\sqlcmd" -I -S \.\pipe\MICROSOFT##WID\tsql\query -i C:\Scripts\WSUSDBMaintenance.sql

It must be run from an Administrator command prompt. This took me several days to figure out so I hope it can benefit someone else. Everything I found about reindexing the WSUS database was on Server 2008 or 2012. This works on Server 2016.

I've had this happen on multiple occasions. The system was configured to use the internal windows database instead of sql, and there were too many records so the refreshes and etc. would take forever, or you'd get the reset server node issue. After I migrated the database to sql, the problem mostly went away. It still occurs on slow connections.

@momurda said in WSUS preparation for Windows 10 Feature Upgrades:

Wow. Definitely not doing that if I have the same problems as you.
Ill just go around and install the upgrade manually.
Not even sure why MS still has WSUS, it is nothing but problems unless you spend hours a week fixing and maintaining it.

I hear ya, this took me an hour to research, make sure to gather correct logs and then do the how-tos.

Just select Windows 10.

@dashrender Oh yeah, that is the most annoying part. We have SSDs and still it takes 2 minutes to get the OS backup 😕

https://www.theregister.co.uk/2017/04/13/microsoft_kills_support_old_windows_on_new_chips/

http://www.theregister.co.uk/2016/12/14/microsoft_windows_10_dhcp/

I guess up config release and renew didn't work for a lot of people.

Someone pointed out that they put an update out online for people who can't get online.

WSUS still controls updates to Windows 10 1607 installs.

There you go, that's how VSS is supposed to work. Get one taken right before patching and another right after. Then you have lots of options.

@wrx7m said in WSUS 2012 (r2) support for Windows 10:

I see mention of SCCM in the article. Does this only apply to SCCM-related installs of WSUS?

No, this whole problem is related to WSUS only. I'm guessing the author mentioned SCCM because that's how he became aware of the problem.

@aaronstuder said in Moving to a New WSUS server:

@BBigford No Problem. Once I realized that the port numbers change, I realized the issue right away.

Clients are being seen by the WSUS server now 🙂

Sweet!

@Dashrender said in What would you use to replace WSUS from SBS:

@Shuey said in What would you use to replace WSUS from SBS:

@JaredBusch said in What would you use to replace WSUS from SBS:

@DustinB3403 said:

Ah....

Sorry for the confusion then. Do they have the resources to run another WSUS server and proper licensing? It really is quite a simple solution.

PDQ Deply has options for 3rd party app updates etc, but requires annual renewal.

Oh, I can easily setup WSUS on one of their existing VMs. Just not really sure I want to with the size overhead for this many users.

Hey Jared, sorry if I sound a little lost, but what is the overhead you're referring to? You pretty much only have two options: Deploy a WSUS server and use a GPO (or regedit) to make the workstations talk to it, or you can manually install updates once per month (or per quarter). I would think you could easily deploy a very small WSUS server (either on 2008 or 2012) using WID and about a 60-80gb hard drive. You could even make it one of the guest VMs.

When I was supporting Office 2010 and Office 2013, Windows 7 and 8.1 I needed more like 120 GB to hold all of the updates, and monthly had to do the cleanup or I would run out of disk space.

Obviously there will be some variables to consider. I was basing my recommendation off our current WSUS setup (over 200 workstations, and 30 servers) vs his environment (8 desktop, 2 laptops and some unnumbered servers). Up until recently when MS changed the way the update cycle works, I cleaned our db every month and we've been doing completely fine with an 80GB hard drive on the server.

I had to disable IE10 installs for similar reasons.
Craptastic legacy applications that are pushed upon us 😞

@PSX_Defector I can't believe how many IT people in this era aren't aware of what architectures are and how many confuse IA64 ( Itanium) and AMD64 (PC).

When I worked for a major Wall St firm they actually labeled many of their packages backwards. What a mess that was.