Servers
Windows Server 2012: Smarter, stronger, frustrating
Microsoft has released Windows Server 2012, based on the same core code as Windows 8. Yes, it has the same Start screen in place of the Start menu, but that is of little importance, particularly since Microsoft is pushing the idea of installing the Server Core edition – which has no Graphical User Interface. If you do install a …
Re: pssssttttttttttt
Eadon, when are you going to realise that the best route is the one that takes the least administrative effort, whether thats GUI or CLI?
Or whatever is nearest to your hand, keyboard, mouse pointer, users face, cursor, tab ordered list.
Also, who now actually gives a flying shit what OS they are running as long as whatever services run on whatever it is they are designed to run on?
the important bit is that, if it breaks, you know how to fix it quickly before anyone notices.
What you have just told me, is that you're such a stuck up twonk that you are unwilling to learn new or different technologies, that you can't actually use or configure anything a "click monkey" could use or configure and you are so unbending that you probably couldn't bring yourself to help out if there was a problem with any of my Windows environment.
Nice work.
p.s just noticed, first para "difficult to configure" - how does this match with "click-monkey"? Are you suggesting windows admins achieve infinite clicks, or that they actually know what they are doing?
Re: pssssttttttttttt
@superhans Well said sir. There are some things Linux does well and other things Windows does well. For those of us who work in the trenches of the enterprise we know there is no nirvana OS. We have to maintain an objective view of tools .
Re: pssssttttttttttt @ Super Hans & Trevor 3
You guys should know by now that Eadon's views are as follows (with no exceptions):
1. If you aren't using Linux for everything YOU ARE WRONG
2. If you are using anything by or related to MS then YOU ARE DOUBLY WRONG
3. If you don't use Java or a relatively low-level language for some given task YOU ARE WRONG
Wading through repetitive, prejudiced crap like this to find genuinely interesting insights is getting tiring. El Reg, can we get a user preference to filter out certain commenters please?
I hate per core licences
despite their proliferation, i hate them.
I pay you for the right to use the code. what i run it on shouldn't affect the price. Why charge me more for running it on 4 cores? Thats like Shell charging me £1.50 a litre on an Astra but £6 a litre if i drive a DB9.
Re: I hate per core licences
Well more like if you were charged some kind of registration fee for being able to drive cars on the road, and if you had a more powerful/ bigger car, you paid more even though you don't particularly take up more space or go over the road more.
Yes, imagine if the government levied different levels of tax on more powerful cars! The tragedy....
Re: I hate per core licences
> Thats like Shell charging me £1.50 a litre on an Astra but £6 a litre if i drive a DB9.
Shell is happy enough with the extra liters that sweet DB9 will be guzzling. Heck, it might even give ya a volume discount.
Plus, your local garage will correct Shell's oversight and not forget to overcharge you.
Re: I hate per core licences
"Thats like Shell charging me £1.50 a litre on an Astra but £6 a litre if i drive a DB9."
Actually I quite like that idea... :-D
@Prof Denzil Dexter
If Shell could charge like that, believe me they would mate.
Why do they charge per core? Because then they make more money. Rather simple really. When people moan loud enough or move to Linux then they will change it. Until then, (shrug).
Re: @Prof Denzil Dexter
(MSFT - Windows Server PM)
A clarification on the point above - Windows Server is not a per core licensing model. Windows Server is a processor licensing model with both Windows Server STD and Windows Server Datacenter licenses covering 2 proc's.
Re: @Prof Denzil Dexter
So my dual processor box requires a single license (with extra licenses required if I want more than 2 VMs on it?), but a quad processor box requires 2 licenses? (with extra licenses required if I want more than 2 VMs on it?).
Re: @Prof Denzil Dexter
(MSFT - Windows Server PM)
Windows Server STD and DC are the same in terms of capabilities - what differentiates these two editions are the virtualization rights. High density virt = DC, Low density virt = STD.
A single STD license covers 2 procs and 2 VMs. You are able to stack multiple STD licenses if you want to build out small virtualized estates.
If you are building out high density virt environments then DC is the right edition as this gives rights for unlimited number of VMs.
In the case of a 4 proc box where you want to do high density virt then 2 DC licenses are required to cover each proc.
Some thoughts
2) Windows Server 2012 delivers simplicity in managing a server estate with large investment in Powershell, 2000+ new commandlets + Intellisense
That is not simple, simple is being able to join, mix and match tools that were already there, not having to learn a new 2000+ commands language.
Also in my opinion powershell is a strange mix of all that is bad about BASH/PERL/PHP and nothing that is good about windows. The old vbScript syntax was good, what was shitty IMHO was the backend.
Now Windows sysadmins have to ditch yet another technology and embrace another one, that will get ditched again in one or two releases.
Also what makes the Windows platform really good is the sheer vastness of 3rd party tools that you can use to deal with the many shortcomings of Windows. Take away the GUI and you are taking away half of the reason of why people run Windows.
SMB's that can not afford a SAN have been building them on the cheap using a regular RAID server and any, yes I repeat ANY Linux distro via ISCSI for peanuts.
Hyper-V is at best a mediocre product, I will give them the benefit of the doubt though thanks to the improvement of the integration components in Linux, which IMHO is the best improvement yet, albeit any other vendor had perfect Linux support for how long now? 2001!!!!
I will admit (The MS PM can be proud of this one) that the huge clock in the login screen of Winserver 2012 is very handy.
Haters gonna hate
Kudos to MSFT for this release - their server OSes were always so much nicer than their client ones. To all those who say, "yah boo sucks UNIX had this 30 years ago" I say: you are absolutely right. And you know what? No one gives a damn.
I prefer administering UNIX boxes myself too, but Microsoft deserve credit for offering GUI less, scriptable access, so please let's not throw the baby out with the bathwater.
Now all they have to do is implement bash and a decent SSH server and I will be one happy bunny. Yeah, it'll never be UNIX, it'll never give me the feeling I get when I log into a strange UNIX box and know that I'm home amongst friends ("Bourne shell? Check. GNU C compiler? Check. Perl? Check. <Happy sigh> Houston, the Eagle has landed"), but it's soooo much better than it was.
Microsoft new Windows release strategy:
1. Rename all the APIs and SDKs.
2. Rename all the control panels.
3. On the server end: everything that was a control panel is now a plugin: everything that was a plugin is now a control panel.
4. Make all the management windows fill a percentage of area of screen area in proportion to recieved bribes from the various LCD panel makers.
5. Submit a suite of minor changes to an unimportant network protocol to the IETF as a proposed standard.
6. Roll out Embrace-Extend-Extinguish response to the (5) from the last rondo.
7. Obsolete all the previous the MS certifications, raise price on new ones (gotta know where M$ moved all the buttons!)
@KingZongo ...
Yes M$ makes a decent app server OS. But it insists on re-obscuring & re-obfuscating reliable old stuff that Windows has done well for 20 years on every new release. Why? I can only conclude, after 20 years in the biz, that M$ believes it's bread is buttered by a constant stream of new sysadmins and old ones that must pay for the MS cert piece of paper.
Whereas once you know NFS or POSIX threads, well, you know NFS or POSIX threads. People who've been around a while know a snow job when they see it. MS does a snow job every release - it gets tired and obvious after a while and that pisses people off. That's not hate, brother, that's anger. There's a difference.
Also @ King Zongo
My Windows sysadmin friends tell me that with every new release of Windows, of Exchange, of SQL Server their Powershell scripts break because the new release exports new & different COM/COM+/DCOM interfaces.
If UNIX (Linux, *BSD, what have you) broke BASH scripts with every major kernel release, well, I suppose you would see a lot of hate leveled at *NIX. But such breakage in *NIX-land has not happened...
Unix vs Windows
Simple really.
So simple I may have been misled by the 5 servers I've tried this on.. If I have I apologise to Microsoft.
1... Write 8000 1 MB files on a DVD (like a backup)
2... Put it into a Unix Box and read every file name
3... Put it into a Windows box and wait 15 minutes (at least) to regain control of the box.
As far as I am concerned a fatal Windows flaw which still exists on Windows 8...
But If I have done something wrong please correct me.
Re: Unix vs Windows
At an educated guess you are running AV software which is the problem....It is near instant to do this on a standard system.
If these are archive files, thne that will add to the problem with some AV clients as they will want to unpack them....
Either exclude the file type from scannig or install a better AV product....
Re: Unix vs Windows
So you're recommending we ditch the AV software?
What could possibly go wrong!
Desktop OS
I wonder if it would be a viable alternative to Windows 8 on the desktop
Re: Desktop OS
If you have deep enough pockets, almost certainly. But "booting straight into the desktop" isn't the same as "has a proper start menu once you are on that desktop", so why not just install Classic Shell and save yourself several hundred smackers?
Parity-based RAID schemes...
...are horrendous.
"parity striping, which is more efficient"
They are more efficient in terms of raw space utilisation, yes.
However, their write performance is terrible as calculation is required for every write. This would have been worth a mention.
You should look up the read-modify-write cycle and block alignment if you're not clued up on such things.
Please don't recommend the use of parity-based RAID. Disk space is cheap enough to use RAID 10 where performance or resilience is important, and it is far superior.
Re: Parity-based RAID schemes...
There's evidently someone who disagrees with my views on parity RAID.
Would you care to tell me your opinion? What issue do you have with my advice?
I am asking because I am genuinely interested in an intelligent discussion.
Re: Parity-based RAID schemes...
You have not a clue. RAID6 is used for the majority of bulk storage these days. RAID 10 is only usually for premium storage or local boot disks.
Re: Parity-based RAID schemes...
I was going to write a nice reasoned reply, despite your 'discussion' skills leaving a lot to be desired.
I might even have offered references to back up my arguments or some credentials that would help to support my position.
Then I realised you are just a low-level troll and are talking rubbish so I won't waste my time.
DHCP resilience
Difficult to configure?
No, it wasn't.
Also, should people really not be using hardware RAID for servers?
Re: DHCP resilience
Indeed, but storage spaces is designed to supply a solution for JBOD disks too....
