What Are You Doing Right Now
-
Reading about "How to set up
WSUS on server 2008
-
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
-
@Dashrender said:
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
It was just a test-set up.
-
Getting the car loaded up to go to our new storage unit.
-
@Joy said:
@Dashrender said:
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
It was just a test-set up.
Things have changed quite a bit... might be learning something for nothing if you do plan to deploy this on Server 2012R2.
-
@Dashrender said:
@Joy said:
@Dashrender said:
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
It was just a test-set up.
Things have changed quite a bit... might be learning something for nothing if you do plan to deploy this on Server 2012R2.
We will use windows server 2008.
I was following this guide.
https://technet.microsoft.com/en-us/library/dd939859(v=ws.10).aspx -
@Joy said:
@Dashrender said:
@Joy said:
@Dashrender said:
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
It was just a test-set up.
Things have changed quite a bit... might be learning something for nothing if you do plan to deploy this on Server 2012R2.
We will use windows server 2008.
I was following this guide.
https://technet.microsoft.com/en-us/library/dd939859(v=ws.10).aspxOK, Mind if I ask why you are using a 7+ year old OS? Will the company not buy a new license?
-
@Dashrender said:
@Joy said:
@Dashrender said:
@Joy said:
@Dashrender said:
@Joy said:
Reading about "How to set up
WSUS on server 2008are you limited to a 7 year old OS on purpose?
It was just a test-set up.
Things have changed quite a bit... might be learning something for nothing if you do plan to deploy this on Server 2012R2.
We will use windows server 2008.
I was following this guide.
https://technet.microsoft.com/en-us/library/dd939859(v=ws.10).aspxOK, Mind if I ask why you are using a 7+ year old OS? Will the company not buy a new license?
Well, Windows 7 is pretty good for production use.
As you know, users get to used to it. -
@Dashrender We're migrating this year from 8 to 12, it's not a small task. Only reason we're doing it is because we got a smoking deal on licensing from techsoup!
-
@Joy said:
Well, Windows 7 is pretty good for production use.
As you know, users get to used to it.But that has nothing to do with what severs you have in the Datacenter.
-
@MattSpeller said:
@Dashrender We're migrating this year from 8 to 12, it's not a small task. Only reason we're doing it is because we got a smoking deal on licensing from techsoup!
We're not talking about migrating, Joy is talking about deploying a new server to use for WSUS. Since this is a new server, I'm just wondering why she isn't doing it on Server 2012r2 instead of Server 2008.
-
@Dashrender I deployed an 8 this week because of licensing. Unless you're 12 on the hypervisor the licencing gets really screwball (which is why we bought datacenter(and the cause of our issues) )
-
@Dashrender said:
@MattSpeller said:
@Dashrender We're migrating this year from 8 to 12, it's not a small task. Only reason we're doing it is because we got a smoking deal on licensing from techsoup!
We're not talking about migrating, Joy is talking about deploying a new server to use for WSUS. Since this is a new server, I'm just wondering why she isn't doing it on Server 2012r2 instead of Server 2008.
Hmm, I checked our list of licenses and I found out we have a lot of Windows2012 license.
Forgive me but, may I ask what's the difference on Win Server 2008 and Win Server 2012 when deploying WSUS?
Since I will do this for the first time. -
@MattSpeller said:
@Dashrender I deployed an 8 this week because of licensing. Unless you're 12 on the hypervisor the licencing gets really screwball (which is why we bought datacenter(and the cause of our issues) )
I know it's wrong, but I put datacenter 12 as the hypervisor so I could just have at it. This is only a test environment, of course, but even on a T3500 desktop it runs pretty well. No license worries, though....
-
@RojoLoco said:
I know it's wrong, but I put datacenter 12 as the hypervisor so I could just have at it. This is only a test environment, of course, but even on a T3500 desktop it runs pretty well. No license worries, though....
Nothing really wrong with it in my opinion. Installing it as core+gui for initial setup and then backing it down to core only after the hyper-v setup is done is still a solid hyper-visor.
-
@JaredBusch said:
@RojoLoco said:
I know it's wrong, but I put datacenter 12 as the hypervisor so I could just have at it. This is only a test environment, of course, but even on a T3500 desktop it runs pretty well. No license worries, though....
Nothing really wrong with it in my opinion. Installing it as core+gui for initial setup and then backing it down to core only after the hyper-v setup is done is still a solid hyper-visor.
Ya know, I never thought to put it back to just core... but I use the host machine for stuff too. Q4 is when we get new hardware... dammit.
-
@RojoLoco said:
but I use the host machine for stuff too.
That part is the wrong part. You are using DC, just spin up another Windows VM.
-
Just got back from our first load to the storage unit. Managed to get away with a little 5x5 unit for just $22/mo. Not too bad.
-
@MattSpeller said:
@Dashrender I deployed an 8 this week because of licensing. Unless you're 12 on the hypervisor the licencing gets really screwball (which is why we bought datacenter(and the cause of our issues) )
The hypervisor has nothing to do with what you can use on top of it. Licensing from the hypervisor comes down purely to "virtualization: yes or now". What the hypervisor is never changes the licensing of Windows on top of it.
-
@RojoLoco said:
Ya know, I never thought to put it back to just core... but I use the host machine for stuff too. Q4 is when we get new hardware... dammit.
That's not a good design. It's "legal" because it is DC licensing but it would be very bad with standard licensing. But it is an anti-best practice in general. Remember the "host" machine is not the host, it's a control environment designed to only be used to manage HyperV, never should anything else happen there.
