Why?
Actually, why not?
In the Windows Server 2003 era, quite a few of us used it as a quasi-primary workstation operating system.
With Windows Server 2008 allowing you to define roles for it, I guess it was just a matter of time before it became the IT pro's workstation operating system.
In this post here, Steven Parker at Neowin has some insight, and a link to detailed installation/conversion instructions.
Really though, shouldn't you try it?
I am managing partner and chief technology officer of Logikworx, an SMB solution provider based in California. I'm also editor-in-chief of SmallBizVista.com and The Interlocutor, an associated monthly e-mail newsletter. I am also a member of the Microsoft Featured Communities and The Hive.
The opinions expressed in this Weblog are those of the writer and may not represent the opinions of Network World.
|
|
Sounds great and looks
Sounds great and looks pretty - but if you ever get the blue screen that prevents you from entering the operating system after you've been working in it for days with a message telling you that no language packs have been installed, good luck fixing that issue. No one has a quick answer. I have so many programs that I use that are dependent upon a Microsoft operating system. Well, I will be re-evaluating my whole business. For the first time in my life, I'm about to become anti-Microsoft. The thing won't let me into the operating system to fix the issue - which wasn't an issue prior. Flippin' weird - I am so angry right now. Too bad Bill Gates isn't there - I'm sure he'd be ranting around, calling these dopes incompetent.
This is not a supported feature
"The thing won't let me into the operating system to fix the issue"
Two things:
1) Using the OS in this fashion is unsupported, and probably a violation of your license, and
2)What kind of access into the OS do you want?
Post new comment