Archive for April, 2009

Why File Server Resource Management is a Winner in Windows Server 2008

One of the most basic (and essential) services I offer on my network is file sharing. It has been frustrating that I have very few tools on Windows Server to manage my files shares. I have had little say over what type of files network users place on my servers, and only a small idea of how those files are being accessed. Luckily this difficulty has come to an end with File Server Resource Management in Windows Server 2008! Installed as a Role using the Server Manager Console, FSRM allows me to have the kind of control I have always craved.

Digital pack rats beware! I can now limit the amount of space on a folder that is available to a user with a Folder Quota. Each folder can have a different folder quota and quota limits can be hard or soft. A hard quota limit prevents the user from exceeding his quota. A soft quota writes an entry in the event log when it is exceeded. FSRM can be configured to send me and the offending user an email notification. I favor hard quotas as a rule in my environment but sometimes you have to make exceptions (such as the boss). You can use quota templates in FSRM to quickly apply quota settings to new folders. Microsoft has provided a number of pre-configured quota templates, but custom templates each with its own warning limit and space limit settings can be created and saved in the FSRM console.

Another great feature of FSRM is the File Screening Management node which lets me decide what types of files can be saved to my file shares. No more will users be able to fill up server disks with mp3s and pictures from their vacation. With FSRM I can block by file type and by file name extension. Again, Microsoft has created some default file screen templates but I can create file screening templates that can prevent (or just monitor) the uploading of specified file types. Templates can be applied on a per folder basis. Events are written in the event log and email notifications can be sent when the file screen blocks a file type.

Trying to get detailed information on file usage can be a pain. What are the most and least accessed files on my server? Are there unneeded duplicate files on my server? The Storage Report Management node in FSRM can generate nicely formatted reports that can be automatically emailed to multiple recipients. Report options include files by owner, quota usage, large files, small files, duplicate files and least recently accessed files.

So, take back control of your files servers! It is easy with FSRM.

Author: Mark Menges

Related Courses:

Managing and Maintaining Server 2008

Designing a Windows Server 2008 Network Infrastructure

Migrating to Server 2008

Configuring and Troubleshooting a Windows Server 2008 Network Infrastructure


Five Things About Exchange Server 2007 You Might Not Know (#2)

What? You didn’t get a chance to read the previous post about black wells and Unified Messaging for only $35 per person? Well, if you did read all that, just continue on here for the ongoing story about “five things you probably don’t know about Exchange Server 2007.” Don’t forget to keep score.

2. Redundancy takes you from 1 server to 4 servers. Minimally.

Servers cost money – well, unless you know something about clouds and blue sky that I haven’t figured out yet… There’s hardware, licenses for installing and running the operating system (Windows), licenses for the extra server software (Exchange), client licenses to be able to access the software, electricity, more electricity for air conditioning (in Phoenix at least), real estate for the rack(s) of equipment, and perhaps some money for the people who set up and run that software and equipment.

But sometimes people don’t correctly assess the cost of redundancy. Yeah, obviously there are costs of not having redundancy. Once upon a time I had the great joy of working on a team developing a fault-tolerant UNIX operating system environment we affectionately called the perpetual operating system, but that’s another story. Nowadays we can do fault-tolerance in a couple of ways in Windows Server for supporting redundancy in Exchange Server 2007 services.

Clustering of the message storage in Exchange Server 2007 can be accomplished by deploying a pair of Windows Server 2008 Enterprise Edition nodes (or W2K3 EE) with Exchange Server 2007 Enterprise Edition. E2K7 can be configured with Cluster Continuous Replication (CCR) to replicate between the nodes in the failover cluster. Each of these two E2K7 EE servers can store each database and storage group (transaction logs plus system (e.g. checkpoint, temporary) files) locally on direct attached storage.

So we have two servers, we have redundancy, and we’re done, right? For the storage of messages in mailbox databases, yes. But there’s a catch. In order to use the Clustered Mailbox Server deployment, only the clustered mailbox role can be performed on these servers. The Client Access (CA) and Hub Transport (HT) roles must be performed elsewhere. Yes, that means on other servers.

Let’s ignore Unified Messaging (UM) and Edge Transport (ET) roles for the moment, because they both really lead to other stories.

Assuming you don’t want a single point of failure for the CA and HT functionality, such as (but by no means limited to) Outlook Web Access and Simple Mail Transfer Protocol (SMTP) respectively, we could use a Network Load Balancing (NLB) “cluster” for those roles. Let’s assume that both CA and HT roles will be deployed on each of the two Exchange Server 2007 Standard Edition servers we’ll set up on Windows Server 2008 Standard Edition (to potentially save licensing costs compared with the Enterprise Editions of E2K7 and W2K8).

Two servers as nodes in a failover cluster for storage for the clustered mailbox functionality, and two more servers for the NLB “cluster” for the CA+HT aspects of Exchange. So to recapitulate, if we had a smallish deployment which would have fit in one E2K7 server, and we want some decent redundancy, this redundancy takes us from 1 server to 4 servers. Minimally. Well, your mileage may vary, because I didn’t mention the word virtualization, but hopefully you get the picture.

Tune in next time for the continuing saga of 5 things about E2K7 you just might not have thought about yet.

Author: Brad Werner

Related Courses

MCTS: Microsoft Exchange Server 2007, Configuration Boot Camp

Microsoft Exchange Server 2007

Ultimate Exchange Server 2007

Five Things About Exchange Server 2007 You Might Not Know

If you’ve ever visited an old style well, you could look down the well and only see blackness. If you cast down a bucket on a rope, you’ll pull up only one bucket of water at a time. Unless you have a strong understanding of geology, from whence the water comes is at least a bit of a mystery for many wells. 

Similarly, there is a well-spring of features and capabilities of Microsoft’s Exchange Server 2007 messaging platform. The longer you use Exchange Server 2007, the more treasures you can pull up from the deep. We’ll avoid some of the more obvious or often stated aspects such as that only 64-bit (x64) servers (hardware, plus Windows Server operating system) can be used on production Exchange Server 2007 servers. Instead, let’s look at five things you probably don’t know about Exchange Server 2007. Keep score at home (work) and let us know how many of these you already knew!

1. Unified Messaging costs $35 US per person, but with it you get other features and support for free!

Well, just to be clear, here’s what I’m really trying to say. First, the Exchange Server 2007 licenses for the server itself do not include client access. As shown at http://www.microsoft.com/exchange/2007/howtobuy/default.mspx, a $699 US or $3,999 US server license is separate from the CLIENT access licenses (CALs).  Second, an Outlook 2007 license is separate from these too. Third, a standard E2K7 CAL, which retails for a list price of $67 US, could be used for access to the core features of E2K7 which are hosted by any number of E2K7 Standard and/or E2K7 Enterprise licensed servers. These are independent variables.

What core features of E2K7 does the Standard CAL allow us to use? Access to a mailbox via smartphone (OWA, EAS, etc.), or Netbook, Notebook, or workstation via OWA, POP, IMAP, MAPI/RPC, or Outlook Anywhere (MAPI/RPC/HTTP) are supported (the computer could potentially be running Windows, Mac OS X, Linux, etc.). Basic mailbox management of default folders is include.

Unified Messaging is not include in the Standard CAL. Four, an add-on “Enterprise” CAL in addition to the Standard CAL could be added per user to include Unified Messaging functionality. Although the estimated price is $35 US for the Enterprise CAL, as Microsoft’s site states, it’s not available as a simple retail ticket item. The Unified Messaging features allow inbound voicemail, inbound FAX, and Outlook Voice Access. Of course, one or more of your licensed servers need to host the Unified Messaging (UM) role for such clients and much configuration and integration with voice networks needs to be done as well. The details of all that are certainly another topic.

But with the Enterprise CAL comes more than just Unified Messaging features. Most importantly, the pricing is for Licensing and Software Assurance (L&SA) until you explicitly choose a license-only deal. Also, many other features are included in the Enterprise CAL, such as ForeFront Security for Exchange Server for anti-virus handling, Exchange hosted filtering, and support for more advanced mailbox policies than the Standard CAL gives, including custom managed folders.

 In the next post, I’ll continue with 4 more things you might not have known about Exchange Server 2007. Until then, take care!

Related Courses

MCTS: Microsoft Exchange Server 2007, Configuration Boot Camp

Microsoft Exchange Server 2007

Ultimate Exchange Server 2007

What’s so great about Windows Server 2008? (Part 2)

Not convinced yet?  Here’s part 2 of my earlier post

System optimization and troubleshooting

The new Reliability and Performance console is packed with new capabilities.  Data Collector Sets –DCS – can be custom designed to track key performance objects. DCSs can be saved and used multiple times. Reports can be created from the data and emailed by the Server to multiple recipients.

Improved Networking

Server 2008 has a new TCP/IP  protocol stack that includes support for both IP v.4 and IP v.6 using one set of system files. IP v.6 is always installed with v.4 and can only be disabled but not removed.  Network performance is enhanced compared to Server 2003 in many ways including Receive Window Auto-Tuning which maximizes the amount of packets received on a per-connection basis. The Windows Advanced Firewall can control inbound and outbound traffic by port, protocol, IP address range and Application.  IPSEC support is integrated into the Advanced Firewall. 

Powerful Virtualization Platform

64 bit installs of Server can run Hyper-V, a thin hypervisor layer that manages virtualized guest operating systems.  Hyper-V can run 32 and 64 bit guests and can create a “snapshot” of a running guest that can be reverted to in necessary.  Microsoft is generous with virtual licenses; a purchase of one copy of Windows Server 2008 Enterprise Edition includes the rights to one physical install, and four virtual installs of the OS.

Server Core Option

The Standard, Enterprise and Datacenter versions of Server include the Core option.  Core is Windows Server without the windows.  This gui-less version requires as little as 2 GB of disk space to install and needs far fewer security updates than graphical installs of Server.

Numerous Active Directory Enhancements

Upgrading your Active Directory to Server 2008 Domain Functional Level gives you access to many new and improved features including Read Only Domain Controllers, Starter GPOs, more efficient replication mechanisms and multiple password policies in  single domain.

This list of reasons why I think Server 2008 is so great is far from complete.  I did not even mention Bitlocker Drive Encryption, Global Name Zones, IP v.6 routing capabilities, Federation Services, digital rights management Services etc, etc…

Well, are you persuaded, yet?  Do I have to resort to mentioning the R2 release that is coming soon?  Before you render your verdict, I hope you will install Server and see for yourself.

Author: Mark Menges

Related Courses:

Managing and Maintaining Server 2008

Configuring Windows Server 2008 Active Directory Domain Services 

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

What’s so great about Windows Server 2008?

When I teach a Windows Server 2008 class, I am outspoken with my students about how much I like this latest version of Microsoft’s server operating system. How about you? Can you be convinced that Server 2008 is the greatest thing since the floppy disk?  I will now list some of the reasons why I think Server 2008 is a terrific OS. You be the judge.

Versatility

Server 2008 is a study in opposites; it is powerful, yet easy to install and configure, it can perform many roles on your network or it can be specialized to perform only one job.

Server is scalable too; it can run on one processor or on five hundred and twelve. It can be load-balanced, clustered or virtualized.  It comes in a budget Standard version and in the very expensive Datacenter version and all versions are available in 32 or 64 bit variants.

Easy Setup

If you are doing a manual installation you need only to enter information in a few screens at the beginning and setup completes with no further input required.  The ICT –Initial Configuration Tasks – window loads at the end of setup and allows you to specify computer name, networking and security settings. This single window can also be used to select services –Microsoft calls them Roles and Features – that will be enabled on the server. Windows Server setup finishes in a locked down mode by default with almost no ports open and hardly any services running; you can enable only needed functionality keeping your “attack surface” small.

Powerful Management Consoles

Many ongoing administrative tasks including configuring Roles and Features, monitoring system events and managing infrastructure services such and DHCP and DNS can be handled in the new Server Manager console.  Server Manager is a one-stop shop that has links directly to online help. Concentrating so many management tools in one place makes Server 2008 management easier to control.

Improved Logging Capabilities 

Event Viewer has been vastly expanded with dozens of new logs, saved filtered views and the ability to create event subscriptions that forward selected events automatically from many machines to a single server.  Plus you can click on any event in event viewer and specify a task that must run anytime that event recurs. The task can range from sending the Admin an email to running a script. Auditing has been improved with additional audit settings for Active Directory.

Check back for Part 2 of “What’s so great about Windows Server 2008?” later in the week!

Author: Mark Menges

Related Courses:

Managing and Maintaining Server 2008

Configuring Windows Server 2008 Active Directory Domain Services

Extra Extra! Windows Server 2008 Foundation

I was in the middle of writing a post about “Five Things About Exchange Server 2007…” when I decided to shift gears and write about something I didn’t think you could wait to hear about. Well, no, not the GM/Segway PUMA. That would be a bit too off-topic for this blog.

It’s an oh-so-recently released operating system which original equipment manufacturers (OEMs) bundle with server hardware and there are no client access licenses (CALs) for regular file & print functionality. Another strain of Linux? Um, no. The Snow Leopard version of Mac OS X Server? Not just yet.

Welcome: Yet Another Flavor of Windows Server 2008.

So you’ll just have to wait a bit longer for what I was going to post about Exchange Server 2007.

So just who is this new kid on the block?

Windows Server 2008 Foundation. The moniker “Foundation” actually includes much of the regular tried and true Windows Server 2008 Standard edition, but the licensing is different. That’s the big news.

1. You get the W2K8 Server FOUNDATION bundled with low-end server hardware from your computer vendor. Some people have likened it to “the NetBook of the server market” – low-end capacity, low-budget price point.

2. You can only have up to 15 user accounts on the server, but those could be in Active Directory Domain Services (AD DS) either as a stand-alone AD DS domain hosted by this Foundation server only, or with this Foundation server as an additional domain controller in a larger environment. The various possibilities of where these up to fifteen user accounts are is quite significant to understanding where W2K8 Server Foundation could be utilized in not just tiny businesses but branch offices too.

3. You can host services (think W2K8 Roles and Features) such as file & print, AD DS, Terminal Services, and other local applications which would normally run on a full-blown Windows Server 2008 system.

4. You don’t get any other applications such as Exchange Server or SQL Server bundled in the Foundation license deal like with W2K8 Small Business Server (SBS) or Essential Business Server (EBS).

5. Although Terminal Services CALs (TSCALs) are still needed for licensing access to terminal services, most other services, including file and print, do not require CALs. Remember the 15 user limit however.

6. The hardware + operating system total sale price is expected to be between US $500 and $1000. One of the W2K8 Server Foundation restrictions is a maximum of 8 GB RAM, however on a $500 server which can only host 15 users this shouldn’t really be considered as a hugely abnormal constraint.

Would you buy a server like this? For small business, it may be a question of cloud versus Linux versus Windows Server 2K8 Foundation in that price bracket (unless you’re thinking of Solaris or Mac OS X, et al). What you mid-size size business and enterprise people shouldn’t neglect is the question “Is there any benefit in having a tiny local server in a small office for file and print and applications for up to 15 users while having messaging and database applications accessed over the WAN to headquarters (or regional) offices?”

In other news, Windows Server 2008 R2 (Windows 7 Server by any other name) is expected to (really) be released this calendar year. That would be in 2009 along with Windows 7 (the client OS). Is it time to say “Hasta la vista Vista?” More on that later (well actually I’ve been blogging about that elsewhere already).

Author: Brad Werner

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

Let’s get back to basics shall we? Windows Server Core 2008.

Back in the days of my youth, long, long ago, you could buy a car with no options—no fancy gee-qaws like leather upholstery, chrome wheels or even a radio.  It rolled down the highway on bicycle skinny bias-ply tires with narrow white-wall stripes on the side.  Those cars were basic transportation, pure and simple.

Microsoft has embraced the concept of the no-frills model with the introduction of Windows Server Core 2008, an oxymoron of an operating system—Windows without windows—a gui-less, wizard-less, command  prompt driven contradiction of everything a Windows administrator, such as myself, was raised to believe in.

But Server Core makes perfect sense when you consider that the graphical version of Windows Server 2008 Enterprise Edition requires 20 GB of disk space for the 32 bit version, and 32 GB for the 64 bit installation. All of the cool management consoles, diagnostic tools, and enhanced displays requires additional services, and uses more memory and processor power.

Sometimes you don’t need all that.  Sometimes Server Core will get the job done for you with less fuss, muss and excitement.  It requires as little as 2GB of disk space, and needs far fewer hotfixes, patches and updates to stay secure, because well, there’s less operating system to secure.

Core shines as an infrastructure server functioning as a Domain Controller, Global Catalog, DNS, DHCP, or running the Hyper-V virtualization platform. It is an excellent choice as an RODC in branch office site, and can even be Bitlocked for additional security.

Installation and setup of Core can be a bit of a challenge. Unattended answer files are helpful for initial configuration of Core after setup, and are required when running DCPROMO if you want to create a domain controller.  An excellent guide to setup and management for Server Core is found at:

 http://technet.microsoft.com/en-us/library/cc753802.aspx

Server Core requires that you get familiar with command line tools such as Ocsetup, Netsh, Netdom and others.  Those tools can be very useful on graphical installs of Windows and are worth learning. Powershell is not available in the present version of Server Core, but that will be remedied with the R2 incarnation which is coming soon.

Maybe it is a sign of the times — do more with less – with Server Core.

Author: Mark Menges

Related Courses:

Managing, Maintaining, and Securing Your Networks Through Group Policy

Updating Your Network Infrastructure and Active Directory Technology Skills to Windows Server 2008

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

What’s new at Global Knowledge?

There are A LOT of new things going on at Global Knowledge these days. Here’s a summary of the latest news.  I’m pleased to say that many of these programs will really help maximize your training dollar in 2009…check it out!

 

More courses eligible for SATV Redemption

Some of our most popular Global Knowledge courses are now eligible for Software Assurance Training Voucher (SATV) redemption.  Visit www.globalknowledge.com/satv for a complete list of eligible courses.

 

New Microsoft .NET & Visual Studio now available virtually

All of the courses below are now available in Virtual Classroom e-Learning, offering you more flexibility in how and when you take these classes without travel.

Developing Microsoft ASP.NET Web Applications Using Visual Studio .NET

Introduction to Programming Microsoft .NET Applications with Microsoft Visual Studio 2005

Core Data Access with Microsoft Visual Studio 2005

Core Web Application Technologies with Microsoft Visual Studio 2005

Advanced Data Access with Microsoft Visual Studio 2005

Advanced Web Application Technologies with Microsoft Visual Studio 2005

View all our Virtual Classroom e-Learning courses here.


Save 40% on Microsoft Training with Hot Seats! Guaranteed to run sessions – order with confidence!

Take advantage of our Hot Seats program to get the best training available for the lowest price.  Register for any of the Hot Seat sessions listed below and save 40% off the list price.  Visit www.globalknowledge.com/hotseats.

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

Five Things About Windows Server 2008 You Probably Don’t Know (Part 3)

This is the 3rd and final part of the article on 5 things you probably don’t know about Windows Server 2008. Previously, I wrote about NPS and then 2 aspects of PowerShell (portability and remoting). Now let’s wrap up with 2 more things.

 4. Branch office support has reached “significant” status with Windows Server 2008.

Well, it’s true that many organizations have used Windows Server in small satellite offices for years. But often times the tradeoffs of what services should/must be run in the headquarters versus a field office weren’t all that effective for many organizations. But Windows Server 2003 R2 provided some truly useful “branch office” features and Windows Server 2008 extends support for such needs to encompass several additional services.

Windows Server 2003 R2 offered a Print Management Console (PMC) and massively upgraded (well completely redesigned is more apropos perhaps) Distributed File System (DFS) implementation which both helped to unify, policize, and centralize the management of file and print services hosted by Windows Server which are distributed across diverse and/or vast network topologies, geographies, or (organizational) political boundaries.

Windows Server 2008 includes all that and more. The most publicized branch office feature (which you may have heard of (but may not know enough about)) is support for Read-Only Domain Controllers (RODCs). While they don’t fully support local Exchange Server 2007 messaging servers, this sort of option for deploying additional domain controllers (DCs) is a boon for many management and security concerns. Compared with the staid “desktop” orientation of Terminal Services and Remote Desktop of the past, the new gatewaying and individual remote application extensions to the terminal services framework have substantial advantages not only for branch office scenarios, but even for single building deployments. There are many other features and roles in Windows Server 2008 which support this “branch office as a first class citizen” treatment that’s finally coming of age in Windows Server.

5. Windows Small Business Server (SBS) and Essential Business Server (EBS) licensing can potentially save small and medium businesses a lot of money and hassle.

For one price, Microsoft’s Windows Small Business Server (SBS) 2008 includes Windows Server roles and features plus more:

  • Windows Server 2008 Standard Edition
  • Exchange Server 2007 Standard Edition
  • Windows SharePoint Services 3.0
  • Microsoft Forefront Security for Exchange Server
  • Windows Server Update Services 3.0
  • Microsoft Office Live Small Business

And not just all that which we get in the Windows SBS 2008 Standard Edition, but the Windows SBS 2008 Premium Edition also licenses you to install Windows Server 2008 Standard on a second server which can host the include (again, this is just in SBS 2008 PREMIUM):

  • Microsoft SQL Server 2008 Standard for Small Business

Microsoft’s Windows Essential Business Server (EBS) 2008 goes much farther than Windows SBS 2008 with:

  • Windows Server 2008 Standard Edition on up to 3 servers (EBS 2008 Standard) or 4 servers (EBS 2008 Premium)
  • Microsoft System Center Essentials 2007
  • Windows SharePoint Services 3.0 (licensed for download (not on included media))
  • Exchange Server 2007 Standard Edition (E2K7)
  • Microsoft Forefront Security for Exchange Server
  • Microsoft Forefront Treat Management Gateway Medium Business Edition

For example, the three servers could be:

  • Management Server: W2K8 Server + SharePoint + System Center
  • Messaging Server: W2K8 Server + Exchange 2007 Server + Forefront
  • Security Server: W2K8 Server + Exchange 2007 Server + Threat Mgt.

And not just all that which we get in the Windows EBS 2008 Standard Edition, but the Windows EBS 2008 Premium Edition also licenses you to install Windows Server 2008 Standard on a fourth server which can host the include (again, this is just in EBS 2008 PREMIUM):

  • Microsoft SQL Server 2008 Standard Edition

(Note that on that 4th server (SQL), until the end of 2009, Microsoft allows Windows EBS 2008 Premium licensees to use Windows Server 2003 R2 and Microsoft SQL Server 2005 Standard as options.)

Consider adding all the licensing fees for these products separately. If you need several of these services, either the standard or premium editions of SBS or EBS 2008 versions could save quite a bit. Note that certain Enterprise edition features of Windows, Exchange, and SQL servers geared to big businesses – such as clustering – might be on the agenda of some small and medium sized businesses, and the Standard editions included in SBS and EBS 2008 wouldn’t be sufficient in those settings. Even so, it’s good to know the options.

Were all five of these things new to you? Did you know a few? Did you already know all five? Let us know if you’d like to know 5 more things…

Author: Brad Werner

Related Courses:

Managing and Maintaining Server 2008

MCITP: Server and Enterprise Administrator Combo Boot Camp

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

Five Things About Windows Server 2008 You Probably Don’t Know (Part 2)

Previously, I started writing about five things about Windows Server 2008 that you probably don’t know, noting that some Windows Server 2008 Network Policy Services features were available in Windows 2000 Server, Windows Server 2003, and Windows Server 2003 R2, but Windows Server 2008 has much much more! Now, here are two more things.

 2. Did you know that there’s an amazing new automation environment for administrations of Windows Server 2008 which can also be used on Windows Server 2003, Windows XP, and Windows Vista? And it looks like Windows 7 and Windows Server 2008 will get a newer snazzier version?

 Of course, you might have known I’m referring to Windows PowerShell. Some people think it’s just a new command line interface with different syntax than the classic Windows Command Prompt and old Disk Operating System (and virtual DOS machine of Windows ilk). And it is a hot little shell, but the automation and scripting capabilities are where it’s at. There is such an incredible wealth of tools and utilities available for download to extend the reach and capabilities of Windows PowerShell. Did you know that Windows PowerShell version 1.0 does indeed work with XP, Server 2003, and Vista as well? All of those versions of Windows could be managed with one shell. One shell to rule them all – just think about it. And yes, there are certainly graphical interfaces for PowerShell. When PowerShell version 2.0 comes out of Community Technology Preview (CTP) and hopefully gets bundled with Windows Server 2008 R2 and Windows 7, we get even more remote administration capabilities built in to Microsoft’s official shell.

3. Windows Server 2008-based servers which are installed with Server Core installation mode can still be managed in many ways across the network with Windows PowerShell.

 Assuming that the existence and exciting capabilities of Windows PowerShell, did you know that you don’t have to wait for Windows PowerShell version 2.0 to get many remote management capabilities? Good ol’ PowerShell version 1.0, which is included as an addable feature for Windows Server 2008 Full Installation has a lot of remoting built in.

Although there are ways around it, officially Windows Server 2008 which is installed with the much-recommended-because-it-helps-to-reduce-attack-surface-and-updates-and-a-whole-lot-more Server Core installation does not support the .NET framework which is a prerequisite to install and run Windows PowerShell. So does that mean that officially there is no way to manage a W2K8 Server Core server? Hardly.  Windows PowerShell comes with strong Windows Management Instrumentation (WMI) and some other remote administration features built in. For example, Windows PowerShell can be installed on a management workstation (or other server) and used to manage Server Core machines across the network. That’s just one way PowerShell can help you do remote management today.

How are you doing so far? Were any of these three things thus far new to you? That’s only 3 out of 5 things I’ll be writing about in this article, but I’ll post the other 2 soon so stay tuned.

 Author: Brad Werner 

Related Courses:

MCITP: Server and Enterprise Administrator Combo Boot Camp

Managing and Maintaining Server 2008

add to del.icio.us : add to furl : Digg it : Stumble It! : post to facebook

Next Page »