@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.

@Dashrender 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:

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

I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.

I had a few Windows 10 machines that didn't upgrade either and I don't really know why. Some of them were the same Windows 10 images as the other ones that upgraded, so idk.

What are the chances (and I don't care what JB says - I don't agree) that those three had an image from VLSC media, and the rest are from the publicly available Windows 10 media?

When I build an install USB from the Public media - I only get the option to install Home or pro. When I build an install USB from the VLSC media - I get Enterprise/Pro/Pro for workstations/Education/Home. There is a difference.

Also WSUS sees a difference between consumer and business

I do not have any Windows 10 Home on my network, so when it's talking about consumer, I'm assuming it's talking about OEM or publicly available media used for install.

All of these systems were Dell OptiPlex systems (bundled with Windows 10) but then I used a VLSC Windows 10 image with MDT to image them all. Most of these were all upgraded automatically but there was 1 or 2 that did not.

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

@DustinB3403 said in Hyper-V Server 2016 - How should someone add 18.5 TB of storage:

HP Z600,

https://support.hp.com/us-en/document/c01720141

You're probably going to want to re-think your setup.

@DustinB3403 said in Hyper-V Server 2016 - How should someone add 18.5 TB of storage:

The system I am using is old. BIOS has no usable options for RAID and I don't know what a RAID controller is.

You don't know what a RAID controller is? Time to do some reading. Basically it's a logic card that manages the placement of data across multiple drives, depending on how you configure the RAID levels. Then it presents that to the OS as a single logical volume - the OS doesn't see the individual drives.

• https://en.wikipedia.org/wiki/Disk_array_controller
• https://en.wikipedia.org/wiki/Standard_RAID_levels

What server do you have? Do you have a service tag?

I'm not a storage expert but I would think you would want to start by creating a RAID volume first. You're not going to be able to just add to your existing storage volume and you would need additional hdd slots in your server in order to add more storage...

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

I don't have @Obsolesce settings in place, and none of my machines did this Dual Scan thing.

I had a few Windows 10 machines that didn't upgrade either and I don't really know why. Some of them were the same Windows 10 images as the other ones that upgraded, so idk.

@Obsolesce 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:

@Obsolesce 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:

not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.

We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.

Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.

My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.

Can you maybe provide me with your settings you applied to prevent that?

hmm.. I can give that a try but when I searched"GWX" it looks like it was meant to prevent Windows 7/8/8.1 systems from upgrading to Windows 10.

@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:

not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.

We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.

Can you explain how you disabled Dual Scan? Right now it seems like the only way is by adding those registry settings..

@Obsolesce 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:

not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.

We have WSUS with Windows 10 1803 professional and we do not have DUal Scan so they will not upgrade until approved.

Yeah, same here... however, I also have a group policy enabled company wide that strictly blocks OS upgrades. When I approve them in WSUS, then they upgrade. But never before.

My main point is that we have all versions of Win10 running, controlled by WSUS, and they only upgrade when approved in WSUS. There has never been a different result.

Can you maybe provide me with your settings you applied to prevent that?

oh wait, that's the quote from Anchor man, LMAO

This happened last week but I'm still fuming about it. I came into work and all but 6 or so of our Windows 10 Pro 1803 systems had upgraded to 1809. I had been planing to wait a while before upgrading so this was completely unexpected.

I have a WSUS server properly set up and the Feature update to 1809 was not approved at all. Googling around, I discovered that there's something called "Dual Scan" and running this check has shown me that I in fact have Dual Scan enabled. I can not disable it apparently since we are not on Windows 10 Enterprise. The registry settings may or may not technically work, so I'm holding off on that solution unless there is no other way.

Has anyone else dealt with this? Any suggestions?

@BRRABill said in delete:

I love lamp.

doesn't even make sense.

I recently started going to both Udemy and Pluralsight for training videos and things. Udemy is pay per course and Pluralsight is monthly/annual subscription with unlimited videos.

So far I've taken courses on Exchange 2016 and MDT and now I'm trying to learn powershell as much as possible.

@bnrstnr said in question about increasing MS volume licensing:

@dave247 As long as you're putting the same edition (probably Pro) that came on the computers you don't need a volume license for every one, because they're already licensed for that edition from Dell. You only need new licenses for computers you want to upgrade from 7, 8.1, etc.

You need a single volume license to get imaging rights.

Yes, I kind of forgot about this, but this is what I did. I purchased workstations with Windows 10 Pro on them and then a single VL for imaging rights. Then, I created a custom Windows 10 image and used this single MAK for activating the images (automatically in MDT task sequence). the Workstations haven't had any issues activating or anything.. but maybe I didn't need to do that part.

I guess this makes my original question pointless now since I realize I am talking about a whole different situation.

@scottalanmiller said in question about increasing MS volume licensing:

@JaredBusch said in question about increasing MS volume licensing:

@scottalanmiller said in question about increasing MS volume licensing:

You only need one VL license of Windows 10 to image everything in your environment. So I think you are fine. It is super rare that you buy more than one copy of Windows 10 through VL.

He's not talking about imaging. I mean he is in the end, but the first part is jsut about buying licenses.

I know, but I was worried that he was buying licenses for imaging (or install), neither of which they can be used for.

What? .. can you expand on this?

To clarify, I have purchased 30 Dell OptiPlex computers as well as 30 Windows 10 Pro licenses (one MAK) from my VAR. They've actually come with Windows 10 already installed but I'm using MDT to create and deploy a custom Windows 10 image - using the Windows 10 ISO from the MSVLC and the license I purchased added into the MDT task settings.

Now, I would like to install Windows 10 on a few slightly older Dell computers which had Windows 7 on them, hence the additional volume licenses needed.

@bnrstnr said in question about increasing MS volume licensing:

@dave247 said in question about increasing MS volume licensing:

Maybe I am just being anal, but if I have 25 computers that I'm imaging with the same single key, yet in reality I am using a key meant for 20 systems across 25, and not actually using the 5 new additional keys.... ah you all get what I'm saying...

It's my understanding that you can use whatever keys you want, so long as you own enough licenses to cover what you have installed. This was the case for us when we were audited a couple years ago anyway.

When you get a key from MS VLSC it doesn't ask which agreement you want the key applied to, it just gives you your key and tells you how many times you've activated with that key. For example, we only have 2 SA licenses, but our windows 10 key shows like 7/50 activations...

That is kind of how I though it worked. I guess it's probably the best way to keep one's sanity in IT..

Say I purchase 20 Windows 10 Pro Open Business Licenses from a VAR. I then get an MS license agreement added in my MSVLC and I am able to view the MAK licenses and download the software, etc.

Now, say I want to purchase 5 more Windows 10 Pro Open Business Licenses and I go through the same VAR again. Is it typical to receive a new MS license agreement along with new MAK license keys? Or should they just be increasing the number of existing Windows 10 MAKs?

I ask this because I am in that situation where I would like to simply bump up the number of Windows 10 licenses for the sake of having only the one Windows 10 MAK.

Maybe I am just being anal, but if I have 25 computers that I'm imaging with the same single key, yet in reality I am using a key meant for 20 systems across 25, and not actually using the 5 new additional keys.... ah you all get what I'm saying...

What is the "right way" to handle this?

@murpheous said in Question about server licensing affected by adding multiple networks in a domain?:

No. You wouldn't need anything more than you would when it is flat.

Ok good. I though I had heard something a while back about licensing being affected by multiple networks in a domain... Maybe I'm remembering something incorrectly though.