My Blog

Windows File Server 2012 on cloud

1-click AWS Deployment    1-click Azure Deployment 1-click Google Deployment

Overview

Windows File Server, codenamed “Windows Server 8”,is the sixth release of Windows Server. It is the server version of Windows 8 and succeeds Windows Server 2008 R2. Two pre-release versions, a developer preview and a beta version, were released during development. The software was generally available to customers starting on September 4, 2012.
Unlike its predecessor, Windows Server 2012 has no support for Itanium-based computers, and has four editions. Various features were added or improved over Windows Server 2008 R2 (with many placing an emphasis on cloud computing), such as an updated version of Hyper-V, an IP address management role, a new version of Windows Task Manager, and ReFS, a new file system. Windows Server 2012 received generally good reviews in spite of having included the same controversial Metro-based user interface seen in Windows 8.

Cognosys Provides Hardened images of Windows File Server on the cloud ( AWS marketplace, Azure and Google Cloud Platform).

Deploy Windows File Server securely on cloud i.e. AWS marketplace, Azure and Google Cloud Platform (GCP)

Windows File Server On Windows Server 2012 R2_01

The successor to Windows Server 2012, called Windows Server 2012 R2, was released along with Windows 8.1 in October 2013. A service pack, formally designated Windows Server 2012 R2 Update, was released in April 2014.

 

Features

Major Features of  Windows File Server 2012

1. New Server Manager: Create, Manage Server Groups

One of the benefits of the newServer Manager interface is the capability to create server groups, which are collections of servers that already exist on your network and can be managed through the new user experience. Creating new server groups lets you manage tasks among each server with common attributes—a server group containing all machines running IIS, for example, a group of all database servers, and so on—and provide specific information on any of them as you wish. This is a big boon for organizations without dedicated monitoring software in place.

2. Better Edition, SKU Selection

Kudos to Microsoft for cleaning up what was a muddy value proposition. The core OS is now the same, and the edition you buy—Standard or Datacenter—depends on whether you want to run up to two virtual machines as guests or if you’d like unlimited guest virtualization. There’s no Enterprise edition gumming up the works. This is a big win for everyone.

3. A Command-Line First, GUI-Second Mentality

The emphasis for Windows Server has changed from a GUI-first philosophy to a GUI-optional mindset. Indeed, when you first install the OS, youre asked to choose between a core and a full installation. Core is the preferred, and encouraged, option. Once you install a core version of Windows Server 2012, you can flip on a GUI simply by installing the GUI role, and you can then opt to take it off without a full reinstall.

This is a great feature when you first deploy a server. You can use the GUI to take care of all of the mundane configuration tasks, but when the machine is ready for production, you can flip the GUI off and deploy. This offers a number of benefits, including reducing the attack surface, resource load and energy requirements.

4. Hyper-V Replication

The Hyper-V Replica feature allows you to replicate a virtual machine from one location to another with Hyper-V and a network connection—and without any shared storage required. This is a big deal in the Microsoft world for disaster recovery, high availability and more. VMware does this, too, but the vendor charges new licensees extra for the capability.

5. Expanded PowerShell Capabilities

There are hundreds more cmdlets in the latest version of Windows Server. This will make your life easier, since PowerShell is essentially the preferred method of managing all of the workloads you can run on the operating system.

6. Storage Spaces: Flipping Complexity on Its Head

Storage Spaces is an innovative features that basically takes commodity storage hardware—inexpensive drives and their controllers, like a JBOD (informal parlance for Just a Bunch of Disks—and turns it into a pool of storage that is divided into spaces that are in turn used just like regular disks.

7. DirectAccess: A VPN Without the Pain of a VPN

DirectAccess allows VPN-like secure tunneling from any endpoint back to the corporate network without the overhead and performance hit of a true VPN. There is also no management agent on the client. When the technology is configured correctly, it just works—users have seamless connectivity to file shares, on-premises equipment and other resources just as if they were on the corporate campus. In addition, group policy objects get applied and administrators can manage machines wherever they are, not just when they come to headquarters or when they connect up to the VPN. This technology had previously been difficult to set up, but in Windows Server 2012, it very much just works.

8. Dynamic Access Control: New Way of Thinking

Dynamic Access Control (DAC) is a suite of facilities that really enhances the way you can control access to information. It’s no longer about taking files or folders and making decisions about “Yes, these people can” and “No, these people can’t.”

9. Resilient File System: An Evolution of NTFS

The Resilient File System (ReFS) was designed as an evolution of the New Technology File System (NTFS) with a focus on availability and integrity. ReFS writes to different locations on disk in an atomic fashion, which improves data resiliency in the event of a power failure during a write, and includes the new “integrity streams” feature that uses checksums and real-time allocations to protect the sequencing and access of both system and user data.

10. Out-of-the-Box IP Address Management

In the box with Windows Server 2012, youll find a complete IPAM suite. This is something many medium-sized businesses simply don’t have access to. With the IPAM suite, you can allocate, group, issue, lease and renew IP addresses in an organized fashion, as well as integrate with the in-box DHCP and DNS servers to discover and manage devices already on your network.

AWS

Installation Instructions for Windows

Note: How to find PublicDNS in AWS

Step 1) RDP  Connection: To connect to the deployed instance, Please follow Instructions to Connect to Windows  instance on AWS Cloud

1) Connect to the virtual machine using following RDP credentials:

  • Hostname: PublicDNS  / IP of machine
  • Port : 3389

Username: To connect to the operating system, use RDP and the username is Administrator.
Password: Please Click here to know how to get password .

Step 2) Choose Start, expand All Programs, and then expand Windows File Server 2012

Step 3) Other Information:

Default ports:

  • Windows Machines:  RDP Port – 3389
  • Http: 80
  • Https: 443

Configure custom inbound and outbound rules using this link

 

Azure

Installation Instructions for Windows

Note: How to find PublicDNS in Azure

Step 1) RDP Connection: To connect to the deployed instance, Please follow Instructions to Connect to Windows instance on Azure Cloud

Connect to virtual machine using following RDP credentials:

  • Hostname: PublicDNS  / IP of machine
  • Port : 3389

Username: Your chosen username when you created the machine ( For example:  Azureuser)
Password : Your Chosen Password when you created the machine ( How to reset the password if you do not remember)

Step 2) Click the Windows “Start” button and select “All Programs” and then point to Windows File Server 2012

Step 3) Other Information:

Default ports:

  • Windows Machines:  RDP Port – 3389
  • Http: 80
  • Https: 443

Configure custom inbound and outbound rules using this link

Azure Step By Step Screenshots

 

Google

Installation Instructions For Windows

Step 1) VM Creation:

1.Click the Launch on Compute Engine button to choose the hardware and network settings.

 

2.You can see at this page, an overview of Cognosys Image as well as some estimated costs of VM.

3.In the settings page, you can choose the number of CPUs and amount of RAM, the disk size and type etc.

Step 2) RDP Connection: To initialize the DB Server connect to the deployed instance, Please follow Instructions to Connect to Windows instance on Google Cloud

Step 3) Choose Start, expand All Programs, and then expand Windows File Server 2012

Step 4) Other Information:

Default ports:

  • Windows Machines:  RDP Port – 3389
  • Http: 80
  • Https: 443

 

Videos

Windows Server 2012 R2, Installation, Migration, and Getting Started, Module 3

How to Install Windows Server 2008 R2

 

Windows File Server 2012 on cloud

Related Posts