• Upgrading Your Skills to MCSA Server 2012 – Roles, Network & Remote Management (70-417)

    Posted on October 28, 2013 by in Certifications, Latest News

    In this blog we are going to look at a couple of items, (mainly server roles, network configuration and remote management)

    Before we start, let’s take a look at the supported server roles in 2012:

    •Active Directory Certificate Services
    •Active Directory Domain Services (AD DS)
    •Active Directory Federation Services
    •Active Directory Lightweight Directory Services
    •Active Directory Rights Management Services
    •Application Server
    •DHCP Server
    •DNS Server
    •Fax Server
    •File and Storage Services
    •Hyper-V
    •Network Policy and Access Services
    •Print and Document Services
    •Remote Access
    •Remote Desktop Services
    •Volume Activation Services
    •Web Server (IIS)
    •Windows Deployment Services
    •Windows Server Update Services

    As shown in previous blogs, installation of roles is easy (no different to any other version of Server) with exception to ADDS (dcpromo), so i’m not going to cover off installation of each and every one, it’s more to show you the roles available to you.

    Instead lets talk about something new to Server 2012……NIC TEAMING!

    Ok so maybe it’s not new to 99.9% of you, but we can now do this via Server Manager which may or may not be of use to you….
    Of course this can be done via powershell, and via the UI. To quickly access the UI from a run prompt type: lbfoadmin.exe

    From here simply select the two adapters on the right and select “tasks” > Add to New Team.

    Decide on a name to call the Team, and click OK

    Give it a few seconds……

    And hey presto, we have a new NIC team.

    To disable the Team (or dissolve the team I should say…), simply select the adapters and click “Tasks” > Delete Team.

    Yes I’m sure…

    We are now back to no NIC team.

    Now let’s configure NIC Teaming in Powershell now.

    The first thing you’ll need to do is see what network adapters you currently have setup.

    Type: “Get-NetAdapter” to get the list of network interfaces.

    Now with this information we can create the NIC team.

    Type: “New-NetlbfoTeam” to start the creation process.

    You will be asked for the “TeamMembers” that will be a part of the NIC team one by one. Enter the NIC names i.e. “Ethernet” then hit enter. When there are no more team members to add just hit enter while the current “TeamMember” prompt is empty.

    You will be asked to confirm the information and once you hit “Enter” or type “Y”

    Now let’s switch back to the GUI and make sure the team riccioniPSteam created correctly…

    You’ve got to admit it’s a pretty fast way to do some simple NIC teaming (with or without a GUI).

     

    So that’s NIC teaming out the way, next up let’s cover some remote management.

    In reality how often is it as an administrator you are actually sat in front of the physical server with a physical keyboard and mouse connected? (And your home lab does NOT count!).

    We are all familiar with MSTSC (RDP) and VNC and the likes, but Server 2012 takes it to one step further.

    As mentioned in previous blogs, Server Manager is the main hub for everything (or at least that’s how Microsoft have tried to make it).

    Before I show you how to access multiple server information from Server Manager, let’s get remote management enabled.

    So how do you enable remote management in Server 2012? Well there’s a few ways.

    • Server Manager console
    • WinRM qc
    • Sconfig.cmd (useful for server core)

    For enabling it via the console select “Local Server” then simply enable Remote Management. (Easy right!)

    Of course we can also disable it….

    Now let’s look at Winrm qc…

    Using winrm qc to enable Windows Remote Management will:

    • Configure the WinRM service for automatic start-up
    • Start the WinRM service
    • Configure a listener
    • Configure firewall rules

    Simply (from a powershell prompt) type winrm qc..

    Select Y to confirm, and job done.

    Quickly check the GUI to make sure it’s enabled again…

    I won’t cover configuring via sconfig.cmd but if you can follow the above you will have no problems configuring it.

    Now let’s move on to Server Groups.

    Server Groups are as they suggest “groups” of servers available to you via the Server Manager.

    For example you could have a management server which has all of your servers added in to the server manager console. This would allow you to quickly access any of the servers in your environment quickly and easily. (You can view eventlogs, perf mon etc…).

    The only problem here is it’s a very manual process (adding one at a time) and as of yet I’ve not found a way to copy a server group from one server to another (or even between profiles on the same server). Hopefully Microsoft fix this soon / allow this.

    Let’s get started….Fire up server manager, and select “Create a server group”

    I’m going to call this DC and Core – Meaning this will display my DC and my Core server.

    Select the computers you wish to add (select the AD tab) or you can manually enter the names via DNS

    Quick Tip – If after you’ve added another server in, you MAY find it doesn’t display any information (unable to connect – WMI error). Well it’s going to be most likely down to firewall rules and allowing that traffic to pass, so (as it’s just my home lab) I went ahead and disabled the firewall on my server core installation. After i’d done that and refreshed server manager all the info from my server core installation started to appear. (The command below disabled the windows firewall for all profiles).

    On the left you can see the new group we named “DC And Core” and on the right we can see basic information about the servers.

    If we scroll down you now see rather than just displaying one server we have both servers information in the one window….

    It also means you can right click on the server and remotely install roles, connect to a PS console, reboot, RDP etc… All the usual goodies.

    Hopefully this has shed a little insight in to the very basic admin functions of Server 2012.

    NIC Teaming is nothing new, but it’s new in that you don’t need a third party application to do so, likewise the “idea” of server groups is good in practice. But personally I wouldn’t fancy going through and adding all my servers to a group, only to find I can’t then copy that information to another server or even to another profile (for multiple admin’s who may use the same server).

    But hey, the above are nice little touches and it’s a step forward from what we’ve got at the moment….

     

     


Protected by WP Anti Spam