Tutorial Blog | Blogger Tutorial Blogspot Templates, Cara Membuat Blog Networking Tutorials SEO.: WHAT’S NEW IN WINDOWS SERVER 2012 R2

SMB 3.0 Windows’ file server service bears the official name of SMB, which stands unhelpfully for Server Message Block. (Blame IBM, not Microsoft, because an IBM guy first designed it.) SMB  has changed little over its roughly 25 years of life, with its biggest changes being support of somewhat bigger block sizes so as to be able to make use of networks faster than 100 Mbps (appeared in 2000), the ability to handle multiple paths, and the addition of digital signatures so as to foil man-in-the-middle attacks (appeared in 2001). Windows Server 2012 R2 sports a somewhat reworked version of SMB that handles slow networks better, handles encryption more intelligently, cranks up throughput on file transfers, and supports PowerShell. File Server Resource Manager You can manage data stored on a file server using the tools in File Server Resource Manager. Some of the tools included help you to automate classification and reporting and manage files and quotas. With Dynamic Access Control’s File Classification Infrastructure you can control and audit access to files on the file server. You can now get more control on how your files are classified on your file servers. With the enhanced features, classifying files can be done manually or automatically. You can read more about this topic starting in“Files, Folders, and Basic Shares.” Web-based Services Finally, there’s the subset of the Internet that’s become more important than all the rest of the Net put together: the Web and related services. They’re important to Windows, and they saw some big changes in 2012 R2. Web Server IIS Windows’ file services may not have changed much over the years, but that’s not the case for Windows’ web server. One key to hardening any server product is to keep the amount of code exposed to the Internet to a bare minimum; if a web server can support, for example, something called FastCGI but your website doesn't need FastCGI, then why run FastCGI on an Internet-facing server and risk the possibility that someone discovers a way to use IIS’s FastCGI to hack the server? Clearly you wouldn't, so it’d be nice to just strip your web server software of the things that you aren't going to need. (Security folks call this “minimizing the attack surface.” Sometimes we think they play too much Halo.) The perfect web server, then, would be composed of dozens of small modules, each of which could be removed or added as needed to allow the web administrator to build a web server that did exactly what she needed it to do...but no more. That was the guiding light for Windows Server 2008’s IIS 7.0, a complete overhaul of IIS including some of the latest security technologies, including WinRM. (When you’re doing remote administration of an IIS 7 box, you're using that protocol rather than RPC.) Knowing how companies live and breathe on the Internet in today’s market, we would expect no less from Microsoft than for it to wave its technology wand across the web server. With the release of Windows Server 2012 R2 comes the newest version of the web server, IIS 8.0. IIS 8.0 has also received a wealth of new rich features to administer and secure your website. Here are a few important changes made in IIS 8.0: [caption id="" align="alignnone" width="639"]<img alt="WHAT’S NEW IN WINDOWS SERVER 2012 R2 " height="441" src="http://i57.tinypic.com/2vxnokh.jpg" width="639" /> WHAT’S NEW IN WINDOWS SERVER 2012 R2[/caption]       ◆ Application initialization ◆ Dynamic IP address restrictions ◆ Centralized SSL Certifi cate Support ◆ CPU throttling ◆ FTP logon attempt restrictions ◆ Server Name Indication (SNI) support ◆ Improved SSL and confi guration scalability ◆ Support for multicore scaling on NUMA hardware Even if you’re not a webslinger by trade, it’s never a bad idea to understand the current Windows web server—so don’t skip Chapter 19, “Web Server Management with IIS.” FTP Server Microsoft gets some things right and some things wrong. In a few cases, the company gets things terribly wrong, as was the case with the built-in File Transfer Protocol (FTP) server software that shipped with Windows for the past 15 years or so. It was so clunky, was so diffi cult to confi gure, and offered such minimally useful logs and an inability to confi gure things that should have been childishly easy to confi gure (such as user home directories) that just about everyone who needed a Windows FTP server ended up shelling out a few bucks for a third-party FTP server. Starting with Windows Server 2008 and R2, however, things changed considerably. As far as we can see, Microsoft tossed out all the FTP server code and rebuilt it from scratch. In Windows Server 2012 R2, they also added the ability to restrict the number of failed logon attempts that can be made to an FTP account in a certain period. So if you need a Windows-based FTP server, fl ip over to the IIS chapter  to learn about the new changes to the FTP server. <h1 class="title single-title" style="color: #2a2a2a;"><a href="http://tutorial-blog.com/whats-windows-server-2012-r2/" target="_blank" title="WHAT’S NEW IN WINDOWS SERVER 2012 R2 | PART-1">WHAT’S NEW IN WINDOWS SERVER 2012 R2 | PART-1</a></h1>

SMB 3.0 Windows’ file server service bears the official name of SMB, which stands unhelpfully for Server Message Block. (Blame IBM, not Micr...

Keep Reading This Post »

Management Tools Any good networking operating system should offer ways to simplify the job of keeping one server or one thousand servers up and running. The server should also stay up and running with the smallest amount of effort possible on the part of the humans doing the server administration. No one operating system has the answer for server administration, but Windows Server has gotten a bit better in 2012 R2 with some useful new tools. Server Manager Prior to Windows Server 2008, when an administrator had to configure and maintain a server, the administrator would have to use many different tools. Windows Server 2008 changed all that by introducing Server Manager, a one-stop shop for all of your configuration and management tools. In Windows Server 2012 R2 Microsoft has expanded this functionality even further. Server Manager now lets administrators manage multiple servers (virtual or physical/local or remote) as long as they are no older than Windows Server 2003. [caption id="" align="alignnone" width="794"]<img alt="Management Tools" height="546" src="http://i61.tinypic.com/2j1al20.jpg" width="794" /> Management Tools[/caption] Adding roles and features in Server Manager has gotten even smarter. As you make your your selections the Add Roles and Features Wizard dynamically changes. The wizard assists you in deciding which subset of tools and features are needed for the requested role. Server Manager has a new dashboard that can show you if problems exist using color-coded boxes. If, for example, an error occurred from within the DNS event log, the DNS box on the dashboard would turn red. This is an excellent tool for troubleshooting your server, and since the dashboard is the fi rst thing you see when you log in, you can’t miss it. Speaking of troubleshooting your server, Server Manager has a host of new troubleshooting tools that we will show you more about in Chapter 2. These tools are all inside the role, inside Server Manager, so you do not have to open multiple applications like Event Viewer or Performance Analyzer to see the results—they’re all in one spot! You can read more about Server Manager :  The Remote Tools: WinRM and WinRS  It’s the case all too often that new operating systems include some really important and useful features that go largely unnoticed. Windows Server 2012 R2 contains one of those neat but largely unknown features in a new network protocol called Windows Remote Management (WinRM). To understand why WinRM is a great feature, let’s consider what WinRM is intended to replace: a protocol known as the Remote Procedure Call (RPC). Even if you've never heard of RPC, chances are that you've been using it for years. RPC’s job is to allow one program to talk to another program, even if those programs are running on different computers. For example, if you’ve ever started up Outlook to read your email on an Exchange Server instance, then you've used RPC: it’s how Outlook can tap Exchange on the shoulder and say, “Can I have my email, please?” Or if you’ve ever used an MMC snap-in like DNS, DHCP, or Computer Management to remotely control those functions on a remote computer from your desktop, you’ve used RPC. RPC is a protocol that has provided much service over the years, but it has one big problem: it’s hard to secure. Microsoft invented RPC back in the days when there was no Internet, and the vast majority of LANs extended no farther than the distance from the fi rst fl oor to the top floor in an office building, so security wasn't all that big a concern. Years later, when security became a big concern, Microsoft tried to retrofit security onto RPC with some optional changes wrought fi rst by XP SP2, but by that point the horse was out of the barn, and requiring RPC security would just end up breaking hundreds or perhaps thousands of RPC-dependent applications. Clearly, the time had come for a change in how Windows programs talk to each other, so Microsoft decided to adopt a protocol that did the same sort of thing that RPC did, with a few changes: ◆ It’s not proprietary but is standards-based and platform-independent—there are similar implementations popping up on Linux and Mac OS. ◆ It’s a modifi ed form of HTTPS. ◆ Its communications are encrypted. ◆ It requires authentication to use. Components of Windows 2012 R2 that use WinRM include event log collection; the ability to use the new Server Manager snap-in on remote servers; and my personal favorite, a secure remote command shell called Windows Remote Shell, or winrs. If you need a secure, low bandwidth remote-control tool, look to winrs. Read more about WinRM , “Remote Server Administration.” Remote Desktop Services In Windows Server 2012 R2 Microsoft has made large strides in improving the user and management experience. Microsoft intended to improve the user experience regardless of the kind of device being used to connect. They wanted to make sure connecting through a WAN or LAN (to virtual desktops, RemoteApp programs, or session-based desktops) provides a rich experience to the user. Microsoft also wanted to make the remote desktop management experience better. We agree that they did make it better by adding a centralized console so administrators can manage Remote Desktop Services from a single location. You can read more about Remote Desktop Services  Group Policy Object Improvements  What got better? Plenty. Managing Group Policy objects (GPOs) got easier with the built-in Group Policy Management Console. In previous Windows versions, one problem that administrators had was manually forcing a GPO to update. Even though GPOs automatically update every 90 minutes, there are times when you need a GPO to take effect immediately. Administrators had to remote in to the specific computer and run gpupdate.exe from the command line to manually update a GPO.Now if an administrator wants to manually force a GPO update, the administrator can use the context menu for an OU in the Group Policy Management Console and schedule gpupdate.exe to run on multiple computers at the same time. Administrators can also achieve this by using the PowerShell utility and the new Invoke-GPUpdate cmdlet. Here are some additional changes to Group Policy in Windows Server 2012 R2: ◆ When dealing with monitoring replication issues at the domain level, you no longer need to download and run separate tools. ◆ For devices running Windows RT, you can now confi gure local Group Policy. By default it is disabled, and the service must be started and set to automatic. ◆ Group Policy has been upgraded to support Internet Explorer 10. You can read more about Group Policy, “Group Policy: AD’s Gauntlet and Active Directory Delegation.” File and Print Sharing Back before we ran web or email services on our Windows servers, we only used Server to share two things: big hard drives and expensive printers. File and print are the oldest services offered by Microsoft networks, but apparently they’re not too old to learn a few new tricks. BranchCache BranchCache is a technology that optimizes WAN bandwidth by copying content from either your main location or cloud server to your branch office. Once content is copied to the branch, users can access it locally rather than over the WAN. Having the ability to cache files will conserve bandwidth and improve security. BranchCache can support any size office and is not limited to how many it can service. BranchCache can be deployed with just a single Group Policy object (GPO). This technology uses the Windows fi le server to divide fi les into small encrypted pieces. The cool thing about dividing the files into smaller pieces is that client computers can download only the pieces that changed. BranchCache will also check for duplicate content and only download one instance of the content, saving disk space. <h1><a href="http://tutorial-blog.com/whats-new-in-windows-server-2012-r2-part-2" target="_blank" title="WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-2">WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-2</a></h1>