Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Windows Microsoft Operating Systems

Second Technical Preview of Windows Server 2016 Arriving This Spring 34

jones_supa writes: The second technical preview of Windows Server 2016 will be launching in May as the first one nears its expiration date. The next Windows Server is being developed and targeted for an early 2016 release, however, the latest and greatest preview builds haven't been released to the public by Microsoft since October 2014. At the same time, Windows 10 builds have been released regularly to everybody who wants to try them out. It was revealed earlier that the Windows Server release won't take place along with that of Windows 10, so it makes sense that Microsoft is pushing more builds of the desktop OS out for testing first. There is no mention of an exact date of the upcoming Windows Server Technical Preview, but an announcement can be expected during the upcoming BUILD 2015 conference which starts on 29th April.
This discussion has been archived. No new comments can be posted.

Second Technical Preview of Windows Server 2016 Arriving This Spring

Comments Filter:
  • by Zombie Ryushu ( 803103 ) on Saturday April 04, 2015 @04:08PM (#49405985)

    I hope Samba can keep up. I am just now migrating from the whole OpenLDAP, Samba 3+Heimdal+OpenLDAP to Samba 4. Boy has it been ride. Samba 4 AD will start out as a Windows Server 2008 R2 AD. I'm hoping that Samba team will pull what they did with the NT Domain Architecture and greatly expand the scope and flexibility of AD before Windows Server 2016 comes along, and does something that breaks compatibility, and puts 2012 ADs into a "Mixed Mode Compatible" status.

    As where Samba 3 had issues with them changing how the NTLM hash was handled, introducing service packs that made minor protocol variations that broke Samba, and older Windows Clients, Microsoft's Game plan seems to be all about changing the schema just enough so Replication and inter-domain trusts stop working.

    Not to mention, often times, AD replication to Samba 4 servers includes the RFC2037 Schemas to be installed as well, to support Linux OpenLDAP and Heimdal Clients. Windows machines have that off by default.

    • Samba is bullshit anymore. I've had so many problems lately with Samba not knowing how to handle filenames with spaces. It makes the files appear as though the permissions are bad to the Windows clients. You have to manually map the characters in the config. Why? Daemons like ftpd do not have this problem.

      • by fulano ( 4069217 )
        That is absolutely not true. The default configuration of Samba 4 can handle filenames with spaces flawlessly both in our FreeBSD server and the Windows clients. Even the last versions of Samba 3 didn't have this problem anymore. Could you provide us more details?
  • not all open source code is bulletproof but microsoft has proven their code is swiss cheese. so why would anyone willingly use a MS product that for something that needs to be secure? when people are shooting at you, do you want to be wearing body armor or cheese?

    • by Voyager529 ( 1363959 ) <voyager529@ya[ ].com ['hoo' in gap]> on Saturday April 04, 2015 @04:42PM (#49406149)

      Depends where it lives with respect to the infrastructure. As a web server with a public IP and nothing in front of it, running IIS? Probably not (though, to be fair, IIS8.5 has come a long way from versions 5 and 6). Running an application for an industry specific vertical product that is built on the IIS/ASP/MSSQL stack? I don't have a problem with that. Doing internal DHCP/DNS/AD/Exchange? I'm fine with that, too.

      Microsoft's issue is that they made it very easy to configure in an insecure way. Similarly, they didn't give much help when it came to giving novice server admins enough guidance to fix their issues without disabling the security measures wholesale. Now, the natural Slashdot argument would be the very concept of a "novice server admin", but the alternative is that certain small businesses don't have a server, so they can't run their applications, so things get messy.

      Think of a nail salon with two locations in neighboring towns. Not a large enough business to warrant an IT staff, but big enough to need a client/server model scheduling system, and not the kind of place likely to have an employee technical enough to really do the job right. Cloud vendors are starting to crop up to fill this kind of niche, but even five years ago, that was much less common. Back then, we'd get a server and a point to point VPN system up and running, but if the application runs on IIS/ASP/MSSQL, having a Linux server isn't an option, and the people in charge of choosing the product are unlikely to pick it based on platform. Situations of this nature are incredibly common on Main Street.

      I love using Linux and BSD where appropriate, but sometimes Windows is the right tool for the job. Other times, it isn't. No sense in turning it into a religious debate.

      • Running an application for an industry specific vertical product that is built on the IIS/ASP/MSSQL stack? I don't have a problem with that.

        sure, put a gun to my head and i won't have a problem with a lot of things. on the other hand, i'm going to avoid jobs that say they need such things.

        Doing internal DHCP/DNS/AD/Exchange? I'm fine with that, too.

        now you are just being lazy because there is no such thing as an internal server if you connect it to a network.

      • Doing internal DHCP/DNS/AD/Exchange? I'm fine with that, too.

        AD was engineered by crazy people obsessed with self-mortification.

        Exchange like Gas Pumps in Oregon and New Jersey is a jobs program for Administrators.

        DNS beloved by DDOS mitigation services everywhere.

        DHCP Jet databases are protected by a mysterious force that defies rational explanation.

    • not all open source code is bulletproof but microsoft has proven their code is swiss cheese. so why would anyone willingly use a MS product that for something that needs to be secure? when people are shooting at you, do you want to be wearing body armor or cheese?

      http://www.zdnet.com/article/t... [zdnet.com]

      Microsoft has (discounting the time before the nimda and code red disasters and the security push) consistently beat the industry average on fewer vulnerabilities for comparable products.

      Specifically the later versions of internet information services (IIS) - the webserver that would be roughly comparable to Apache httpd with PHP, Ruby or Java - have fared extremely well in comparison: IIS 7 has had 8 vulns discovered in it's entire lifetime, while IIS 8 still has a clean s

  • by Anonymous Coward

    Will Windows Server 2016 still have the shitty, shitty, shitty Windows 8-style UI that's fucking unusable and totally unsuitable for a server OS?

    • If you drink enough MS koolaid, putting metro in Windows 8 sort of made sense, in a "everyone will love it and buy our phones!" way. But putting it on a server OS was just mind-numbingly stupid, I just can't see how anyone thought it was a good idea. I cringe every time I have to log in to our 2012 servers.
      • I do not see what the big deal is on a server?

        Desktop by default loads up with Server manager. As long as you do not hit the Windows key the start screen doesn't pop up. You can with powershell install Windows Server 2012 headless with no gui at all!

        90% of the work on servers is done from a system admins desk anyway with MMC and the associated server tools. Very rarely does one log in unless something is wrong. Powershell version 4 means you can do alot without walking into the server room and plugging in a

        • Because the UI (in 2012 R2) is spastic and inconsistent. The different UI elements involved with say... creating and connecting to a VPN is stupid. Starting at a normal desktop UI, you get the Start Screen, then you manually type "control panel" because it may or may not be visible, then go to Network and Whatever Else, then you click to add a network connection and go through the normal UI to add the VPN. Then you have to actually open network adapters to see the connection you just added. Then when yo
          • I am not a metro fan at all.

            I am typing this on Windows 7. But really people do not use servers as a desktop and your thing with VPN's is a non issue in a server.

            There are younger folks who have no problem with the start screen after they get used to it. It is just different and requires muscle memory. For a server I only use server manager which opens by default or the tools at my desk. I do not run it on a laptop where I will VPN from a hotel room.

            More than likely when the release comes next month it will

          • Starting from scratch:

            PS C:\Windows\system32> Get-Command -Noun *vpn*

            (list of commands with VPN in the name - which includes an "Add-VpnConnection" command. Lets see...)

            PS C:\Windows\system32> man Add-VpnConnection

            (syntax and "man" page. Yup, that is the command I was looking for. Wonder if there are any examples...)

            PS C:\Windows\system32> man Add-VpnConnection -Examples

            (several examples with explanation. Let' try it...)

            PS C:\Windows\system32> Add-VpnConnection -Name Doh! -ServerAddress 10.1.1.1

  • Did they bother fixing the fuckup they did in RDP8 when trying to access Machines using RemoteFX? Using RDP7 you could easily pull a 20K+ score in 3D benchmarks, getting near-native performance, same hardware and RDP8 dropped that by HALF.

    If they haven't fixed that, I'm not interested and I'll stick with Windows Server 2012 and Hyper-V combo using Win7 VMs.

Beware of Programmers who carry screwdrivers. -- Leonard Brandwein

Working...