@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 oh, had you thought that that was me linking a previously made video? Nope, just for this thread
Yeah, just because you've linked your videos in the past where appropriate.
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 that's how I roll.
Thanks Scott. You the MVP!
@scottalanmiller said in Are we still separating application roles out on different servers?:
Wow you made a video for/because of me! Nice!
And yeah, I see your points. That all makes sense. I guess I shouldn't have used to words "best practice". I just meant like, the thing that a lot of people commonly do because it's the current trend or whatever.. but yeah its good to question everything and use your brain. I just wanted good input/insight, which I got.
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
ok, can you provide some sort of info to support that? Not trying to be combative, I honestly want to evaluate it. I will watch your video next chance I get.
The big reason is performance and cost. Keeping the two together tends to cost less (especially if doing cloud) and makes it easy to maintain (one VM to backup and deal with.) Now if you do modern things like pure DevOps, automation of builds, backup only non-static DB data, then separate is often better. But if you are more normal and going to backup using Veeam or something, having a contained VM that has everything in one reliable package is a lot easier to protect and restore.
Local DB (inside the VM) means better performance under normal scaling. Lower latency.
Good points Scott, thanks
@scottalanmiller said in Are we still separating application roles out on different servers?:
@dave247 said in Are we still separating application roles out on different servers?:
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server.
That was never a best practice. Generally separating is good, but not always, it's a specific evaluation. And the one that you describe is actually where you rarely do it, both today and historically.
ok, can you provide some sort of info to support that? Not trying to be combative, I honestly want to evaluate it. I will watch your video next chance I get.
For example, if I have an application with a web front-end and an SQL database back-end - in the past, it used to be best practice to separate those two roles and have one server for the webserver and another server for the SQL database server. Is this still common practice?
@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:
@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 is free for download... the license is another story. The machines might have come with win 7 pre loaded but the built in license might have been win 10, or it could have gotten the free upgrades
Not the case here.
@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.
@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.
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?
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?
