Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Auxon FuncOfT
  • Leap Motion

    Sorry, it just ended.  You'll have to wait until the video is available on YouTube, but it shouldn't take too long.

  • Leap Motion

    Live session on Leap Motion at http://live.dotnetconf.net right now ... or http://www.youtube.com/watch?feature=player_embedded&v=YixzSUxyGKU

  • Windows 8 flops, and Microsoft are to blame

    , elmer wrote

    *snip*

    What are you getting so aggro about? If it works for you, that's great, but it doesn't work for me, and I really don't need your attitude, thanks very much.

    Because you're all a bunch of winey babies, and you have all the power to disable what you want on the server anyways, but still complain.  Again - http://blogs.technet.com/b/server_core/archive/2012/05/09/configuring-the-minimal-server-interface.aspx - and that's not even Server Core, that's any Server 2012, and you just remove the GUI.  Done.

  • Windows 8 flops, and Microsoft are to blame

    If you really want no GUI in Windows Server 2012, then it's simple.  http://blogs.technet.com/b/server_core/archive/2012/05/09/configuring-the-minimal-server-interface.aspx

  • Windows 8 flops, and Microsoft are to blame

    , elmer wrote

    *snip*

    Yes, I've tried it, and it's useful in an emergency, but as a way to manage a bunch of servers on a daily basis, it sucks.

    Like many admins, I have a multiple-monitor management desktop, and I expect to be able to manage all of my servers in the lights-out room from there, using the same basic paradigm, regardless if they are running Server-2012, Server-2008, Server-2003, Linux, BSD or whatever.

    Having to think - "oh, server-x is running Windows-2012, so I'll need to grab a tablet to manage that machine" - is just not going to cut it.

    You don't have to think  "oh, server-x is running Windows-2012, so I'll need to grab a tablet to manage that machine", come on, get real, this is all about a bloody start button and a bloody start screen, which you can easily use with a bloody mouse and keyboard, in fact more easily because searching for applications is fast and you want the same paradigm for all servers, including Linux and BSD?  Then use Server Core and get over it.

  • Windows 8 flops, and Microsoft are to blame

    , elmer wrote

    *snip*

    because the GUI is optimized for consumer devices.

    And I would hardly say the "GUI is optimized for consumer devices", touch is a user interface mode, and it's not going away, ever, and it's not just for consumer devices.  That's just the same as saying the GUI is not required on a server *ever* (sometimes you don't need it, ok, but most of the time, you do), and a mouse and keyboard were only ever for "consumer" devices - nonsense - it's a user input device, like a mouse and keyboard, and you need to interact with a Server as well.

  • Windows 8 flops, and Microsoft are to blame

    , elmer wrote

    *snip*

    What a nonsense argument. You need to use a touch device to manage servers, because the GUI is optimized for consumer devices.

    And I never said, "need to use a touch device", you can just as easily use a keyboard and mouse and use the start key on the keyboard, or the RDP window context menu, or CTRL-ESC, or use your bloody mouse in the corner or swipe down the side to get the charms, oh it's SO HARD.

    The point was that those without a keyboard and mouse and only a touch screen need it.

  • Windows 8 flops, and Microsoft are to blame

    , elmer wrote

    *snip*

    What a nonsense argument. You need to use a touch device to manage servers, because the GUI is optimized for consumer devices.

    As has been stated by many (ad nauseum) the desktop should have remained 'classic' and the 'modern' GUI should provide for touch devices.

    It's not difficult to fix, and Stardock have demonstrated this fact, but MS seem totally intransigent in this regard. The message they are sending is that they would rather burn their business customer base than provide them with what they want.

    It's certainly not a "nonsense argument", have *you* tried RDP with a touch device?  Try it with Server 2008 R2 and Server 2012 then come tell me what you think. 

  • Windows 8 flops, and Microsoft are to blame

    , DeathBy​VisualStudio wrote

    *snip*

    People don't forget; Microsoft does. It's a server and not a tablet. It's hard to believe that Microsoft tested this over RDP and said, "Meh, that'll work" but I guess the proof is in the pudding. All hail the Windows Store 8 App environment! Perplexed

    Have you tested RDP to Windows Server 2012 with a tablet? It works great! If they didn't then everyone with a tablet or touch screen would complain. The only thing I wish is that I could zoom in and out the entire desktop at will to deal with the legacy UI because it is often too small, the same problem applies to picking files in details view with Explorer on the Windows 8 client OS.

  • Windows 8 flops, and Microsoft are to blame

    , Retro​Recursion wrote

    *snip*

    Don't get me wrong: I think Windows Server 2012 is awesome technically under the hood.

    BUT, you should have heard the fellow admins in the data center laugh when they saw Windows Server 2012 on the console. Between the laughing they kept asking where the touchscreen was. Why the metro start screen is on a server operating system, I cannot understand. Totally useless and cumbersome in a server environment, not to mention via Remote Desktop.

    What a lack of imagination ... when you RDP in with a touchscreen, believe me, you use the Start Screen with touch!