Microsoft Active Directory is at the heart of the company’s server systems. From Windows Server to Exchange Server and beyond, the power of configuring Active Directory policies and objects allows IT to manage a vast empire of resources, users, and workstations in the Enterprise computing environment. Unfortunately, all of that scalability and flexibility can quickly add up to a high amount of complexity.

Simply finding the right objects and then updating their properties or implementing changes can be a cumbersome process. Many Microsoft systems engineers have developed their own shortcuts and conventions over the years for dealing with the administration of complex Active Directory structures. One tool that has been lacking, however, is the ability to write powerful scripts to manage Active Directory.

The good news is that the arrival of Windows Server 2008 R2 with PowerShell 2.0 and the Active Directory Module changes all of that for the better.

Powershell 2.0 and Active Directory Module

Of the many new features in Windows Server 2008 R2, PowerShell 2.0 is one that may finally be coming into its own. One of the key new features in PowerShell 2.0 is the addition of modules. Modules differ from PowerShell 1.0 snap-ins in that they are self-contained and do not require registration or installation. Rather, modules are imported into the shell via the Import-Module command. Modules can also be offloaded when they are no longer needed.

Click to continue…

File Classification Infrastructure, or FCI, is a new tool included with Windows Server 2008 RS to help better manage all of the data stored on file servers throughout the enterprise. Using a system that tags files, keeps those tags attached to files as they are used, and then uses those tags to manage the files, FCI creates a powerful infrastructure for fine-grained file management and security. Best of all, it comes free with all editions of Windows Sever 2008 R2.

Installing FCI on Server 2008

Although FCI comes with all versions of Server 2008 R2, it is not installed by default in line with Microsoft’s strategy of installing only the necessary services and roles on each server based upon its functionality within the network. FCI is installed as a component of the File Services role, and implemented via the File Server Resource Manager console. Once installed, FCI is at once deceptively easy to use, and at the same time, infinitely complex in its possibilities.

Click to continue…

Windows Administrators have been responsible for keeping data safe and accessible on File Servers for years. Recently, however, that role has been expanded. Legislation requiring companies to inform customers whenever their personal data has been potentially compromised led to a flood of embarrassing situations for business.

Ironically, these data breaches were seldom the fault of corporate IT professionals who were properly performing their duties of keeping the company file servers up and running, and secure behind firewalls and security protocols. However, when a problem with computers or data arises, everyone turns to IT for answers. Fortunately, Microsoft Windows Server 2008 R2 comes with a free data management tool that can help IT be more proactive in managing data.

File Classification Infrastructure (FCI) in Server 2008 R2

File Classification Infrastructure, or FCI, was released with Server 2008 R2. Although FCI comes bundled for free with all editions of Server 2008 R2, it is not enabled by default. FCI is primarily a function of file servers.

To install FCI, the administrator must first install the File Server Resource Manager (FSRM) role service to the File Services role. All FCI functions, reporting, and configuration are handled from inside of the FSRM console.

Understanding FCI

Understanding the potential power of FCI is done best through example. Consider the following scenario.

Click to continue…

I just finished giving my presentation on my three favorite TechEd 2010 presentations at our local Chicago Windows User Group meeting. Below are the slides from the presentation which include most of what I talked about including the links to TechEd resources that I thought would be valuable.

What I focused on was my three favorite sessions from TechEd:

• Server 2008 R2 SP1 and Windows 7 SP1
• Turbo Charging Active Directory
• Windows 7 at Mach 5

If you missed TechEd then check out the quick slides and make sure to visit msteched.com for videos of the TechEd presentations that were recorded.

MCSE: Out With The Old

Having an MCSE next to your name can open doors that would otherwise be closed. My MCSE Certification has helped me get job interviews and writing gigs, plus it has helped with my street cred in the IT world.

Another nice thing about the MCSE is that it will never expire, not even when the exams are discontinued (let’s hope, that in the future, the MCSE will be a sign of experience and longevity and not a sign of age).

But the MCSE is getting old, the technology is starting to go out of fashion and companies are looking for candidates with updated skills and new sets of letters after their names.

MCTS & MCITP: In With The New

Just in case you haven’t been following along, Microsoft has introduced two new certifications:

• Microsoft Certified Technology Specialist (MCTS)
• Microsoft Certified IT Professional (MCITP)

The MCTS demonstrates knowledge on a particular technology so it is possible to get several MCTS designations, one for each technology you test on. The MCITP certification requires 3-5 MCTS exams, depending on which track you choose.

The MCTS expires when the technology it is based on is out of mainstream support. The MCITP will need to be renewed every three years. Because these new certifications expire, having one will be a sign of keeping current and being up to date with changing technologies.

Learn more about the Server 2008 MCITP Certifications.

Click to continue…