WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-2

<strong>SMB 3.0</strong><br/>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).<br/>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.<br/><strong>File Server Resource Manager</strong><br/>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.<br/>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.<br/><br/>You can read more about this topic starting in“Files, Folders, and Basic Shares.” Web-based Services<br/>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.<br/><strong>Web Server IIS</strong><br/>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.)<br/><br/>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.)<br/><br/>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.<br/>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:<br/><br/>[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]<br/><br/> <br/><br/> <br/><br/> <br/><br/>◆ Application initialization<br/>◆ Dynamic IP address restrictions<br/>◆ Centralized SSL Certifi cate Support<br/>◆ CPU throttling<br/>◆ FTP logon attempt restrictions<br/>◆ Server Name Indication (SNI) support<br/>◆ Improved SSL and confi guration scalability<br/>◆ Support for multicore scaling on NUMA hardware<br/>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.”<br/><br/><strong>FTP Server</strong><br/>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<br/>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.<br/><br/><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>

All Latest Post r2 server ser WHAT’S NEW IN WINDOWS SERVER 2012 R2 Windows Server 2012 WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-2

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 »

WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-1

<strong>Management Tools</strong><br/>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.<br/><strong>Server Manager</strong><br/>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.<br/>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.<br/><br/>[caption id="" align="alignnone" width="794"]<img alt="Management Tools" height="546" src="http://i61.tinypic.com/2j1al20.jpg" width="794" /> Management Tools[/caption]<br/><br/>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.<br/><br/>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.<br/><br/>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<br/><br/>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!<br/><strong>You can read more about Server Manager : </strong><br/><br/><strong>The Remote Tools: WinRM and WinRS </strong><br/><br/>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).<br/><br/>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<br/>computer from your desktop, you’ve used RPC.<br/><br/>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.<br/><br/>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:<br/>◆ It’s not proprietary but is standards-based and platform-independent—there are similar implementations popping up on Linux and Mac OS.<br/>◆ It’s a modifi ed form of HTTPS.<br/>◆ Its communications are encrypted.<br/>◆ It requires authentication to use.<br/>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<br/>remote-control tool, look to winrs. Read more about <strong>WinRM</strong> , “Remote Server Administration.”<br/><br/><strong>Remote Desktop Services</strong><br/>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<br/><br/>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<strong> Remote Desktop Services </strong><br/><br/><strong>Group Policy Object Improvements </strong><br/><br/>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.<br/>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.<br/><strong>Here are some additional changes to Group Policy in Windows Server 2012 R2:</strong><br/>◆ When dealing with monitoring replication issues at the domain level, you no longer need to download and run separate tools.<br/>◆ 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.<br/>◆ Group Policy has been upgraded to support Internet Explorer 10.<br/>You can read more about Group Policy, “Group Policy: AD’s Gauntlet and Active Directory Delegation.”<br/><strong>File and Print Sharing</strong><br/>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.<br/><strong>BranchCache</strong><br/>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.<br/><br/><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>

All Latest Post Part-1 Part-2 WHAT’S NEW IN WINDOWS SERVER 2012 R2 Windows Server 2012 WHAT’S NEW IN WINDOWS SERVER 2012 R2 | Part-1

Management Tools Any good networking operating system should offer ways to simplify the job of keeping one server or one thousand servers up...

Keep Reading This Post »

Deprecated Items in Windows Server 2012 R2 | Networking Changes inserver 2012 R2.

<div style="text-align: justify;"> <u>VM Chimney</u>, also referred to as TCP offload, has been removed and will no longer be available to guest operating systems. The WMI root\virtualization namespace is changed to just <b>root\virtualization\ v2</b> and will eventually be taken out completely in future Server versions. <i>Authorization Manager</i> (AzMan) has also been deprecated in this version and will be phased out in future releases. Th e new management tools for virtual machines will be the new standard.</div> <table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody> <tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjd20gnPJR0Vht0q_-FGS20HJZ5z9hA_mGe4fNG5_aCP82qDG9z27HfeDyLmqqUeABCw7Zz1o9jBOz_OHpAAm_Tafjv-61hv6sFk_ZZVz9zqv9UqTTjEzNoYjQHpI_Rk4M8KyXs-v0olMg/s1600/Server-2012-logo.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img alt="Microsoft_Windows_Server_2012" border="0" height="102" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjd20gnPJR0Vht0q_-FGS20HJZ5z9hA_mGe4fNG5_aCP82qDG9z27HfeDyLmqqUeABCw7Zz1o9jBOz_OHpAAm_Tafjv-61hv6sFk_ZZVz9zqv9UqTTjEzNoYjQHpI_Rk4M8KyXs-v0olMg/s1600/Server-2012-logo.png" title="Microsoft_Windows_Server_2012" width="400" /></a></td></tr> <tr><td class="tr-caption" style="text-align: center;"><span style="font-size: small;">Microsoft_Windows_Server_2012</span></td></tr> </tbody></table> <div style="text-align: center;"> <br /></div> <h3> <strong>Virtual Desktop Infrastructure</strong></h3> In Windows Server 2012 R2, Microsoft has made vast improvements to the virtual desktop infrastructure (VDI), with simpler administration, increased value, and better overall user experience.<br /> Supporting mobile devices is a must in today’s market. Virtual desktop infrastructure helps bridge the compatibility gap between devices by virtualizing resources. VDI provides stronger security and higher effi ciency that improves productivity with a UI that the user is familiar<br /> with. Windows Server 2012 R2 and VDI make it a snap to deploy virtual resources across devices.<br /> <br /> Windows Server 2012 R2 VDI, if running in a datacenter, will allow access for mobile devices using Hyper-V and Remote Desktop Services. Microsoft offers three different deployment types in a single solution: pooled desktops, personal desktops, and remote desktop sessions.<br /> <br /> <strong>Networking Changes</strong><br /> Servers are no good without the ability to talk to one another, but—of course—the downside of being able to communicate with other systems means that infected systems can try to spread their malware joy. (“Want to secure your server? Easy...disconnect the Ethernet cable!”) Server 2012 R2 offers some networking changes to make Windows networking a bit faster and a bit more secure.<br /> <br /> <strong>EAP-TTLS</strong><br /> With Windows Server 2012 R2 an exclusive protocol is being introduced as an Extensible Authentication Protocol (EAP) type called Tunneled Transport Layer Security (TTLS). This protocol is used with 802.1X Authenticated Wired and Wireless access. This new standards based protocol provides a secure tunnel for client authentication. 802.1X provides a security shield that prevents unauthorized access to your intranet.<br /> <br /> <strong>DNS</strong><br /> Although DNS has been around forever, the process by which it translates names seems to get better with each version. Changes in Windows Server 2012 R2 affect both DNS Server and Client. Let’s take a look at the changes for Windows Server 2012 R2. In PowerShell, DNS management has received some improvements. The DNS Server role, for example, has had some improvements to installation and removal using PowerShell. Additional<br /> developments in PowerShell include user interface, client query, and server configuration on older operating systems. The LLMNR query time-out has been 300 msec, which was not enough time for computers in power save mode. With the new improvements to DNS Client, this timeout has been increased to 820 msec.<br /> <br /> <strong>IP Address Management</strong><br /> The IP Address Management (IPAM) framework is a new set of technologies for managing, monitoring, and auditing IP address space. By monitoring DHCP and DNS, IPAM can locate IP address servers within your network and allows you to manage them from a single central UI.<br /> <br /> <strong>NIC Teaming</strong><br /> NIC Teaming technology in Windows Server 2012 R2 can take multiple network interface cards and team them together to interface as one. Doing so helps with failover should one device become inoperative. Load balancing is also improved when NICs are teamed because the bandwidth is combined into a single larger bandwidth.<br /> <br /> You can read more about these topics and new features in upcoming post, <br /> <strong>Windows Server 2012 R2 Networking Enhancements</strong>, and <br /> <strong>IP Address Management and DHCP Failover</strong>.

All Latest Post Deprecated Items in Windows Server 2012 R2 Networking Changes Networking Changes in server 2012 R2 server 2012 Windows Server 2012 Deprecated Items in Windows Server 2012 R2 | Networking Changes inserver 2012 R2.

VM Chimney , also referred to as TCP offload, has been removed and will no longer be available to guest operating systems. The WMI root\vir...

Keep Reading This Post »

Windows Server 2012 R2 Installation Requirements.

<div style="text-align: justify;"> Hello, How are you going to deploy <u>Windows Server 2012 R2</u>? There are some complications here.<b>Windows Server 2012 R2</b> is available with only 64-bit architectures. Microsoft is shifting all of its server products to be 64-bit only. This means you cannot upgrade from 32-bit installations of <a href="http://www.tutorial-blog.com/2012/09/windows-server-2008.html" target="_blank">Windows Server 2008</a>. You'll have to do a clean install on new hardware and move any services or data. If you have 64-bit server deployments, then you can do an in-place upgrade. This can be a time-saver, but it’s not usually recommended. Microsoft pretty much urges you to do a clean install every time. However, if your server is running just Microsoft features, roles, and applications (all being 64-bit), then an in-place upgrade is possible. We've done this and had reliable servers afterward.</div> <div class="separator" style="clear: both; text-align: center;"> <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjva_l2TS6jwII13HD3cQ6EtVag7Hm9YAQhE5B8OpYo7J3UJr8VVNtVd-xaWVEQwfuCI6vha9fhZYLRv0RJlr3H_zZfICW_mic2A1lm3Bsdq3KKcW4wky6PAa7DJT3iw5qVrPBb80On2cM/s1600/Server-2012-logo.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="102" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjva_l2TS6jwII13HD3cQ6EtVag7Hm9YAQhE5B8OpYo7J3UJr8VVNtVd-xaWVEQwfuCI6vha9fhZYLRv0RJlr3H_zZfICW_mic2A1lm3Bsdq3KKcW4wky6PAa7DJT3iw5qVrPBb80On2cM/s1600/Server-2012-logo.png" width="400" /></a></div> <div style="text-align: justify;"> <br /></div> <br /> <br /> <div style="text-align: center;"> <b> Microsoft_Windows_Server_2012</b></div> <br /> <strong>Installation Requirements.</strong><br /> <br /> In previous versions of Windows Server, there would be different requirements for each edition of Server you wanted to install, that is, Enterprise versus Standard edition. In <i>Windows Server 2012 R2</i>, Enterprise edition is no longer available and the requirements have been scaled down to just one set for all editions. As usual, you are given a set of minimum and recommended requirements with the operating system. Be aware that minimum means exactly that; the operating system will run, but it will not necessarily run very well. You should also take account of the applications that will be installed and the load that will be placed on your server.<br /> <br /> This can vary wildly depending on applications and organizations, so there are no hard and- fast rules on what your server specifications should be. The best thing to do to get accurate specifications is to develop a pilot environment and generate loads on your “proof-of-concept” servers while monitoring the performance and responsiveness of the servers and applications.<br /> <br /> However, if your server is going to have moderate loads in a small environment, then you’re probably going to be OK with the recommended specifications.<br /> <br /> <strong>Table 2.1 describes the requirements from Microsoft for Windows Server 2012 R2.</strong><br /> <br /> <div style="text-align: center;"> <img alt="Installation Requirements" height="449" src="http://i61.tinypic.com/2iasjyh.jpg" title="Installation Requirements" width="625" /> <span style="text-decoration: underline;">Installation Requirements</span></div> <br /> <strong>64-Bit Support : </strong><br /> <i>Windows Server 2012 R2</i> is available only as a 64-bit product. We’ll reinforce that: there are no x86 or 32-bit versions of <u>Windows Server 2012 R2.</u><br /> <br /> <strong>Here are some notes on deploying x64 servers:</strong><br /> <br /> <ul><br /> <li>Your hardware support for x64 is probably not a huge issue: The major vendors have been selling x64 processors for years for their mainstream products. You can do a quick audit of your server hardware and check for 64-bit support.</li> <br /> <li>A lot of 32-bit applications should be able to run on the x64-only Windows Server 2012 R2: This is thanks to 32-bit emulation provided by the Windows-on-Windows (WOW32) subsystem. Don’t count just on this; please check with application vendors, and test in a lab before making fi rm plans to upgrade servers from Windows Server 2008 to Windows Server 2012 R2.</li> <br /> <li>You cannot do an upgrade from x86 to x64: This precludes upgrading from an x86 installation of Windows Server 2003 or Windows Server 2008 to Windows Server 2012 R2. Getting your servers from x86 to x64 will require a migration plan from one physical server to another.</li> <br /> <li>64-bit builds of Windows require digitally signed kernel mode drivers: Sure, the operating system will allow you to install those drivers with a warning, but they will never actually load. Make sure your hardware vendor provides suitably signed x64 drivers for Windows Server 2012 R2. Very often we see people complaining about Microsoft for driver issues, but this is really something that your hardware vendor is responsible for. Printer drivers do appear to be something in particular to watch out for!</li> </ul> <br /> <br /> As with any project, preparation is the key to success. Review the hardware requirements, and check out application and service compatibility before moving forward with any deployment of Windows Server 2012 R2.<br /> <br /> <strong>Installing the Operating System: </strong><br /> Your first installations of Windows Server 2012 R2 in your live or laboratory environment will probably be either a clean installation or an upgrade installation. There are some other, more advanced ways to install Windows:<br /> <br /> <ol><br /> <li>An unattended installation: We'll talk about that a little later in this chapter.</li> <br /> <li>A cloned installation using ImageX from the Windows Automated Installation Kit.</li> <br /> <li>One of Microsoft’s deployment solutions such as <i>Windows Deployment Services</i> (WDS):This is an advanced installation performed over the network using functionality that is included in <b>Windows Server 2012 R2.</b></li> <br /> <li>Third-party solutions: Ghost is the classic example of a third-party cloning solution that works in conjunction with Microsoft’s sysprep tool.</li> </ol> <br /> <br /> We're going to look at the clean installation and the upgrade installation processes now. We've already mentioned that the installation process is pretty simple.<br /> The clean installation process is very simple in <u>Windows Server 2012 R2</u>. You’re pretty much only being asked to do the following:<br /> <br /> <ol><br /> <li>Select a language, time and currency format, and keyboard method.</li> <br /> <li>Choose an edition and build of Windows Server.</li> <br /> <li> Agree to the license agreement.</li> <br /> <li>Choose between a manual and upgrade installation.</li> <br /> <li>Confi gure the disk.</li> <br /> <li>Set the default administrator password.</li> <br /> <li>Log in.</li> </ol> <strong>There are some options during this flow:</strong><br /> <ul><br /> <li>Install a driver if needed.</li> <br /> <li>Repair an existing installation of the operating system on the computer.</li> </ul> <br /> <br /> In the next section, we’ll cover completing this fl ow for a clean installation and an upgrade installation. Then we’ll cover some of the options that are presented during the installation and follow that up with showing how to customize the installation of the operating system. <b>Windows Server 2012 R2</b> Installation Requirements.

All Latest Post Installation Requirements microsoft server 2012 server 2012 Windows Server 2012 Windows Server 2012 R2 Windows Server 2012 R2 Installation Requirements Windows Server 2012 R2 Installation Requirements.

Hello, How are you going to deploy Windows Server 2012 R2 ? There are some complications here. Windows Server 2012 R2 is available with on...

Keep Reading This Post »

MCITP Course Outline Complete

<h2>What is mcitp ?</h2><br/><br/><br />[caption id="attachment_1748" align="alignright" width="174"] mcitp logo[/caption]<br /><br />The World information IT field would most likely be able to shed light on what is MCITP (Microsoft Certified IT Professional) as it replaces the older MCSE of microsoft (Microsoft Certified Systems Engineer) that was geared towards the network structure of the older Windows 2000,2003 and 2008 systems. mcitp certification is a globally recognized way to validate and promote your professional level IT knowledge.<br /><br /> <br /><br /> <br /><br />[caption id="attachment_1747" align="alignnone" width="640"] mcitp-Certification[/caption]<br /><br /> <br/><br/><h1>MCITP Course Outline</h1><br/><br/><br /><strong>Microsoft Windows 7 (Exam Code: 70-680)</strong><br /><br />1. Introduction<br />2. Installation<br />3. Imaging<br />4. Configuring Devices<br />5. Managing Disks<br />6. Managing Applications<br />7. Application Restrictions<br />8. Internet Explorer<br />9. IPv4 Networking<br />10. IPv6 Networking<br />11. Wireless Networking<br />12. Windows Firewall<br />13. Remote Administration<br />14. Accessing Resources<br />15. Authentication and User Account Control<br />16. Remote Access<br />17. Monitoring Systems<br />18. Configuring Performance<br />19. Windows Updates<br />20. Backup and Recovery<br /><br /><strong> Microsoft Windows Server 2008 Network Infrastructure (Exam Code: 70-642)</strong><br /><br />1. Introduction<br />2. IP Addressing<br />3. IPv6<br />4. DHCP<br />5. Configure Routing<br />6. IPSec<br />7. Network Access Protection<br />8. Routing and Remote Access<br />9. Configure Wireless Access<br />10. Configure Firewall Settings<br />11. Configure Name Resolution (DNS)<br />12. Configure and Monitor Print Services<br />13. File Services<br />14. Windows Server Update Services<br />15. Monitor Event Logs<br />16. Performance Monitoring<br />17. Gathering Network Data<br/><br/><h3><strong>Microsoft Windows Server 2008 Active Directory (Exam Code: 70-640)</strong></h3><br/><br/><br />1. Introduction to Active Directory<br />2. Installing Active Directory<br />3. Server Core<br />4. Read Only Domain Controllers<br />5. Operations Masters<br />6. Domain Functional Level, Forest Functional Level<br />7. Automating Active Directory Accounts<br />8. Managing User Accounts<br />9. Groups and Computer Accounts<br />10. Replication and Sites<br />11. UPN and Trusts<br />12. Active Directory Lightweight Directory Services<br />13. Active Directory Rights Management Services<br />14. Active Directory Federation Services<br />15. DNS<br />16. Configuring Active Directory Certificate Services<br />17. Configuring Backup and Recovery<br />18. Backup and Active Directory Maintenance<br />19. Create and Apply Group Policy Objects<br />20. GPO Account and Audit Policy<br />21. GPO Software and Templates<br />22. Monitoring Active Directory<br/><br/><h3><strong>Microsoft Windows Server 2008 Administration (Exam Code: 70-640)</strong></h3><br/><br/><br />1. Introduction<br />2. Plan Server Installations and Upgrades<br />3. Plan for Automated Server Deployment<br />4. Windows Activation<br />5. IPv6<br />6. DHCP<br />7. DNS<br />8. Directory Services: Read-only Domain Controllers<br />9. Certificate Authority<br />10. RRAS and NAP<br />11. Application Servers and Services<br />12. Provision Applications<br />13. File Roles<br />14. Backup and Recovery<br />15. Storage and Print Servers<br />16. Server Management<br />17. Group Policy Objects<br />18. Monitoring Servers<br />19. Security<br />20. High Availability<br />21. Patch Management<br/><br/><h3><strong>Microsoft Server 2008 Enterprise Administration (Exam Code: 70-647)</strong></h3><br/><br/><br />1. Introduction<br />2. Design Active Directory Forests and Domains<br />3. Forest and Domain Functional Levels<br />4. UPN and ADPREP<br />5. Trust Relationships<br />6. Active Directory Physical Topology<br />7. Global Catalog, Universal Group Membership Caching, Printer Location Policy<br />8. Read Only Domain Controllers (RODC)<br />9. The Active Directory Administrative Model<br />10. Enterprise-Level Group Policy Strategy<br />11. Upgrade and Migrate Domains, Interoperability<br />12. IP Addressing<br />13. DNS<br />14. Network Access<br />15. Terminal Services<br />16. Application Delivery<br />17. Business Continuity<br />18. Software Updates<br />19. Compliance Management<br />20. Virtualization Strategy<br />21. Data Management and Access<br />22. Designing a PKI<br /><br /><a href="http://www.mediafire.com/view/?ttqdhc9bml3qvg0" rel="nofollow"></a><br/><br/><blockquote><br /><h3>MCITP Course Outline Tag: mcitp,mcitp exams, mcse, microsoft certified it professional, mcsa, microsoft exams, microsoft mcitp, mcts, mcitp server,mcitp 2008, mcitp 2012</h3><br /></blockquote><br/><br/><br /><br />src="http://pagead2.googlesyndication.com/pagead/show_ads.js"><br />

Download E-Books Networking Windows 7 Windows Server 2008 Windows Server 2012 MCITP Course Outline Complete

What is mcitp ? [caption id="attachment_1748" align="alignright" width="174"] mcitp logo[/caption] The World i...

Keep Reading This Post »

Windows Server 2012 | Microsoft Windows Server

<p style="text-align: left">Windows Server 2012 Part of the Microsoft Windows family, Windows Server currently under development by Microsoft. It is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 will be the first version of Windows Server to have no support for Titanium-based computers since Windows NT 4.0. A developer preview was released on 9 September 2011 to MSDN subscribers. Windows Server 2012 has been released to manufacturing on August 1, 2012.</p><br/><br/>[caption id="attachment_539" align="alignleft" width="640"]<a href="http://www.gopcclinic.com/windows-server-2012/" rel="attachment wp-att-539"></a> windows server 2012[/caption]<br/><br/><h1><span style="text-decoration: underline">Features Windows Server 2012</span><span style="text-decoration: underline">:</span></h1><br/><br/><p style="padding-left: 30px">Windows Server 2012 includes a number of new features or feature changes.</p><br/><br/><h4><span style="color: #0000ff"><span style="text-decoration: underline">IP address management</span><span style="text-decoration: underline">:</span></span></h4><br/><br/><p style="text-align: left">Windows Server 2012 has an IPAM role for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. IPAM provides for administration and monitoring of servers running Dynamic Host Configuration Protocol (DHCP) and Domain Name Service (DNS). IPAM includes components for.Both IPv4 and IPv6 are fully supported.</p><br/><br/><h2><span style="text-decoration: underline">Windows Server 2012 Active Directory</span><span style="text-decoration: underline">:</span></h2><br/><br/><p style="text-align: left">WindowsServer 2012 has a number of changes to Active Directory from the version shipped with Windows Server 2008 R2. The ADDS installation wizard has been replaced by a new section in Server Manager, and the Active Directory Administrative Center has been enhanced. A GUI has been added to the Active Directory Recycle Bin. Password policies can differ more easily within the same domain. Active Directory in Windows Server 2012 is now  aware of any changes resulting from visualization, and ritualized domain controllers can be safely cloned. Active Directory Federation Services is no longer required to be downloaded when installed as a role, and claims which can be used by the Active Directory Federation Services have been introduced into the Kerberos token. Windows Power shell commands used by Active Directory Administrative Center can be viewed in a Power shell History  Viewer.</p><br/><br/><p class="none"><span style="color: #0000ff"><span style="text-decoration: underline">ReFS F</span><span style="text-decoration: underline">ile System</span><span style="text-decoration: underline">:</span></span></p><br/><br/><p class="none">ReFS <strong>F</strong>ile <strong>S</strong>ystem, originally codenamed "Protogon" is a new file system in WindowsServer 2012 .</p><br/><br/><p class="none"><h3><span style="text-decoration: underline">Windows Server 2012 Editions</span><span style="text-decoration: underline">:</span></h3></p><br/><br/><p style="text-align: left">Windows Server 2012, unlike Windows Server 2008 R2, will have only four editions - the Enterprise, Small Business Server, Web, and HPC editions do not exist.</p>

Active Directory All Latest Post Download latest ms server Networking Reviews Windows Server 2012 Windows Server 2012 | Microsoft Windows Server

Windows Server 2012 Part of the Microsoft Windows family, Windows Server currently under development by Microsoft. It is the server version ...

Keep Reading This Post »

How to Install Windows Server 2012 R2 Step by Step

<strong>Performing a Clean Installation: </strong> A clean installation refers to installing the operating system onto a computer that does not have an installation present or one that you want to keep. In our example, we are dealing with a computer that has no previous installation. We are assuming that you have not done any of this before, so we are going to get back to basics. More advanced readers might be tempted to skip ahead to another section, but we recommend that you at least skim this section to see what has changed.<br/><br/>[caption id="" align="alignnone" width="580"]<img alt="Windows Server 2012" height="347" src="http://i60.tinypic.com/2mo1304.jpg" width="580" /> Windows Server 2012[/caption]<br/><br/>Windows Server 2012 R2 comes on a DVD. It’s a pretty large installation. Ensure your server has a DVD-ROM drive, and then insert the DVD media. Alternatively, if you are using a virtual machine, you can redirect the virtual CD/DVD to the Windows Server DVD ISO image that you have downloaded from Microsoft or created from your original media. Once the media is loaded, you should power up your server and ensure that your server boots from the DVD drive. Normally, a computer with a blank hard disk will boot from the DVD drive by default. If the computer fails to boot from the DVD, then there may be one of a few things going on. There may be a valid operating system on the hard disk that is booting up by default. You might have a boot menu available in your computer that is briefly made available during or after the Power-On Self Test (POST). Alternatively, your server might not get the option to boot from DVD because of a boot configuration. You can alter this by entering the BIOS and making a change there. These two options will vary depending on your hardware, so you should consult your hardware vendor’s documentation or contact their support desk. In most cases it will show something like “Boot Order.” We have also seen situations where we have burned the DVD from an ISO file but we used a write-speed that was too fast to ensure a good burn. In the following examples, we'll cover how to install Windows Server 2012 R2. <a href="http://tutorial-blog.com/windows-server-2012-r2-installation-requirements/" target="_blank" title="Windows Server 2012 R2 installation Requirements."><strong>Figure 2.1</strong></a> is the fi rst screen you'll see. It allows you to customize the installation language, time and currency format, and the keyboard settings of the server. You'll need to change some settings here if the defaults do not match your language, region, and keyboard. For example, if you are in Ireland using an Irish-based keyboard, then these defaults won’t suit you at all! The time zone won't work correctly, currency symbols will be wrong, and the keyboard layout will be totally wrong. For example, you will struggle to find the backslash (\), which is kind of important in the Windows world. Topic: Install windows server 2012 (How to Install Windows Server 2012 R2 Step by Step) The “Language to install” option will vary depending on the languages supported by your DVD. Most people reading this book will probably deal with English-based media, even those in non–English speaking nations. But you may be choosing Spanish, French, German, Chinese, and so on, depending on where you are and what your company standards are. The “Time and currency format” setting affects how Windows presents and formats those regional-specific settings. You’ll probably always want to ensure that this matches the location where your server is located. The “Keyboard or input method” setting should match the keyboard that is physically attached to the computer. Keyboards can often vary from country to country, so make sure that this is correct. Don't worry; it won't affect your ability to manage a server using Remote Desktop. An RDP session will use the keyboard settings of the client computer that connects to the server. The screen shown in Figure 2.2 allows you to do a couple different things: <strong>You can troubleshoot and repair an existing installation of Windows Server 2012 R2. In this example, you’ll install Windows Server 2012 R2, so click the Install Now button.</strong> Figure 2.1 : Setup environment to install Windows<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows Server 2012 R2 installation" height="461" src=" http://i61.tinypic.com/2i3uqs.jpg " width="622" /> Windows Server 2012 R2 installation[/caption]<br/><br/>Figure 2.2: Install Windows now.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_02" height="461" src="http://i60.tinypic.com/2d7ev5z.jpg" width="622" /> Windows_Server_2012-install_Step_02[/caption]<br/><br/>Figure 2.3 : Choosing an edition and installation type.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_03" height="461" src="http://i57.tinypic.com/103j51s.jpg" width="622" /> Windows_Server_2012-install_Step_03[/caption]<br/><br/>Figure 2.4: Agreeing to the EULA.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_04" height="461" src="http://i57.tinypic.com/2412kvk.jpg" width="622" /> Windows_Server_2012-install_Step_04[/caption]<br/><br/>Figure 2.5: Upgrade or clean installation?.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_05" height="461" src="http://i59.tinypic.com/25so3ef.jpg" width="622" /> Windows_Server_2012-install_Step_05[/caption]<br/><br/>Figure 2.6: Setting up the drive to install Windows.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_06" height="461" src="http://i57.tinypic.com/b62gk4.jpg" width="622" /> Windows_Server_2012-install_Step_06[/caption]<br/><br/>Figure 2.7:Drive options.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_07" height="461" src="http://i57.tinypic.com/10z0cxs.jpg" width="622" /> Windows_Server_2012-install_Step_07[/caption]<br/><br/>Figure 2.8:Adding a mass storage controller driver.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_08" height="461" src="http://i59.tinypic.com/2eugxsi.jpg" width="622" /> Windows_Server_2012-install_Step_08[/caption]<br/><br/>Figure 2.9: Windows Server 2012 installation progress<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_09" height="461" src="http://i60.tinypic.com/2i2bu5h.jpg" width="622" /> Windows_Server_2012-install_Step_09[/caption]<br/><br/>Figure 2.10: Setting the administrator password.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_10" height="461" src="http://i59.tinypic.com/2w527t0.jpg" width="622" /> Windows_Server_2012-install_Step_10[/caption]<br/><br/>Figure 2.11: Logged in as administrator.<br/><br/>[caption id="" align="alignnone" width="622"]<img alt="Windows_Server_2012-install_Step_11" height="461" src="http://i58.tinypic.com/14ccjgh.jpg" width="622" /> Windows_Server_2012-install_Step_11[/caption]<br/><br/>So, that’s your fi rst Windows Server 2012 R2 machine up and running. Congratulations! It doesn’t do very much, but it is a minor victory. Grab a celebratory drink of something, and then we’ll take a look at upgrading an existing installation of Windows Server to Windows Server 2012 R2.

All Latest Post How to Install Windows Server 2012 R2 install Install Windows Server Install Windows Server 2012 R2 Install Windows Server 2012 R2 Step by Step Windows Server 2012 How to Install Windows Server 2012 R2 Step by Step

Performing a Clean Installation:  A clean installation refers to installing the operating system onto a computer that does not have an inst...

Keep Reading This Post »