Skip to main content

Questions: What products are included in Windows Server 2008

Windows Server 2008 has a lot of extras that you can add on to enhance the server…..for free. We call them Roles and Features. Roles being major components and Features being enhancements to the roles. Here are a few.

AD RMS (Active Directory Rights Management Service)
AD RMS allows users, as opposed to Network Administrators, the ability to assign permissions to content. In the past, we as Net Admins, had to manage this. Now, with RMS aware applications like Office 2007, users can do this as well. Think about the PDF file that would not allow you to print it. Users can do the same to help protect their shared content. They can even determine who can read and modify their content, regardless of NTFS or file share permissions.

AD FS (Active Directory Federated Services)
AD FS allows you to securely share your networks resources with other organizations. The nice thing about AD FS is that you give access permissions to an organization and the other organization manages the user accounts. This give you the control off the access, the other organization the control of who gets the access, and SSO (Single Sign On) for the users.

Hyper-V
Hyper-V allows you to run servers (or clients) in a virtual environment. This allows you to save money in hardware and electricity. It alsow has some unique options to recovery quickly from a down physical server.

NAP (Network Access Protection)
NAP helps to protect your network. Let’s say that some who a users laptop mysterious lost its antivirus software while away from the office for a month. NAP can be set to not allow this client access to your secured network. Instead, it sends it to another network that will allow it to download and install the antivirus product, clean itself, and then admit it into the secure network.

Windows Server 2008 has many more features available at no additional cost to you. Visit the Windows Server Web Site for more details on what comes with Windows Server 2008.
http://www.microsoft.com/windowsserver2008/en/us/default.aspx

Comments

Unknown said…
This is really very helpful.Thanks a lot for sharing this information.I appreciate the efforts that you showed in your article.
webhosting

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...