Category: Windows Server 2008 R2

PowerShell Version 3 Installation Failure on Windows Server 2008 R2 Server Core Installation (no-GUI)

You have a server which runs the Windows Server 2008 R2 with SP1 operating system that was installed using the "Server Core Installation" option (no-GUI): You've given this server a name, added it to the domain, configured the IP address settings, and configured options 1 -3 in the "Configure Remote Management" portion of sconfig as shown in the following image: PowerShell version 2 works fine on the server, but you've been tasked with loading PowerShell version 3 on it. You've downloaded and Read more [...]

When Trying to Install PowerShell Version 3.0 You Receive the Message: “The Update is Not Applicable to Your Computer”

You've decided to install PowerShell version 3.0 on your computer. Your computer meets the requirement of running Windows 7 with Service Pack 1, Windows Server 2008 with Service Pack 2, or Windows Server 2008 R2 with Service Pack 1. If you're running Windows 8 or Windows Server 2012, you already have PowerShell version 3.0 installed. There are several different ways to check the operating system version and service pack level. In the following screenshot, I've run "winver.exe" and I can see that Read more [...]

Use Data Stored in a SQL Server Database to Create Active Directory User Accounts with PowerShell

I need a few Active Directory users created in my mikefrobbins.com test environment so I thought why come up with fake information when I could use information that I already have in a SQL Server database? The Employees table in the Northwind database looks like an easy enough candidate since all the data I need is in one table. This is about the concept and not about seeing how complicated I can make this process. Here's the type of information I'll pull out of this database to use for the Active Read more [...]

Want VM Reliability and Uptime? Hyper-V on Server Core

While at TechEd last month I heard two things that I've been preaching for a while. Server Core installation (no-GUI) is the recommended installation type beginning with Windows Server 2012. I've been saying this for a while when it comes to Windows Server 2008 R2. Server Core: Reliability and Uptime In each of three datacenters that I support there are multiple Hyper-V servers that run Windows Server 2008 R2 w/SP1 with the Core Installation (Server Core). These production servers have unbelievable Read more [...]

ASP.NET v4.0 Application Pools Don’t Show Up in IIS

On a Windows Server 2008 R2 Machine, a default operating system installation was performed along with installing all of the Windows Updates to include the .NET Framework v4.0, then IIS was installed. On this particular server, the ASP.NET v4.0 Application Pools didn't show up automatically in IIS: My guess is this is because the .NET Framework 4.0 was installed before IIS. To resolve this issue open a command prompt as administrator (elevated privileges if UAC is enabled), change into the Read more [...]

Is PowerShell 2.0 Installed by Default on Windows Server 2008 R2?

As with most things in IT, the answer is that it depends. It depends on whether or not the server was installed with the Full Installation or with the Server Core Installation. It also depends on what your definition of installed is. If the server was installed with the Full Installation (GUI) then PowerShell is installed (enabled) by default, but if it was installed using the Server Core Installation (no GUI) then PowerShell is not installed (not enabled) by default. If you attempt to Read more [...]

Importing PowerShell Modules and Locating Added Cmdlets

Want to add a feature to a Windows Server 2008 R2 machine using PowerShell? That functionality is part of the ServerManager PowerShell Module that's install by default on 2008 R2. The module has to be imported for it's cmdlets to be made available since it's not loaded by default when you launch PowerShell. To view the Modules that are available to be imported, run Get-Module -ListAvailable The ServerManager module has to be imported so that it's commands are made available to PowerShell. Read more [...]

Open a SharePoint Document Library with Windows Explorer

When attempting to open a SharePoint document library from a machine running Windows Server 2008 or 2008 R2 by using the “Open with Explorer” button as shown in the image to the right, you receive:  “Message from webpage > Your client does not support opening this list with Windows Explorer.”: To resolve this problem, enable the “Desktop Experience” feature on the machine you are attempting to open the document library from (the client machine): You can also enable the "Desktop Read more [...]

Install the PowerShell ISE & Enable PowerShell Scripts

PowerShell 2.0 is installed by default on Windows 7 and Windows Server 2008 R2. The PowerShell ISE (Integrated Scripting Environment) is installed by default on Windows 7, but not Windows Server 2008 R2. You can use the following information to install the ISE on your 2008 R2 server (as long as it’s running the full GUI and not the Core installation). Launch PowerShell and execute the following: If you attempted to run this on the Core (no GUI) installation Read more [...]

Unable to Configure Email Server Settings in Trend WFBS 7.0

Problem: When attempting to configure email server specific settings in Trend Micro Worry Free Business Security – Advanced 7.0, you receive the error: “Internet Explorer cannot display the webpage”: When you hover over an option such as “Disable” in the Anti-spam section, you notice a URL that points to your email server. By default it points to port 16372 on the email server. This is the first clue that gives you an idea that this is potentially a problem with the firewall on the email Read more [...]

Configure the Page File Size on Windows 2008 Server Core

I recently ran into an issue where I couldn't start any additional virtual machines on a Hyper-V server that was running Windows Server 2008 R2 Enterprise Edition - Core Installation (no GUI). After a little research, I determined that the operating system had created a pagefile of over 100 gigabytes in size which was using up the majority of the DAS in the server. The server has 96GB of RAM which is the reason why the operating system automatically configured such a large pagefile. The VM's are Read more [...]

Running the Dell System E-Support Tool (DSET) on Server Core

There are multiple reasons why you might want to run the Dell System E-Support Tool (DSET) on your Dell PowerEdge server. It could be because Dell Support has requested it or you’re trying to diagnose a problem or you simply want to know what version of BIOS your server is running without having to reboot it. This tool is especially useful when it comes to Windows Server 2008 R2 core installation since many other utilities will not run on server core. The DSET utility can be installed on server Read more [...]

Enabling Jumbo Frames for iSCSI on Server Core

I recommend following the instructions in my “Rename a Network Interface from the Command Line” so you can easily distinguish the difference in the network interfaces. Once the network interfaces are renamed, they should look similar to the ones in this image: If you attempt to ping your SAN at this point with a 8972 byte ping (9000 bytes minus a 20 byte IP header and a 8 byte ICMP header), you’ll receive a message stating “Packet needs to be fragmented but DF set.”: In this example, Read more [...]

MultiPath I/O on Server Core with the EqualLogic HIT Kit

I’ve written a few other blogs about iSCSI and Multipath I/O on Windows Servers, but this one focuses on installing the EqualLogic Host Integration Tool (HIT) Kit on Windows Server 2008 R2 Core (no GUI). If you are using an EqualLogic SAN, I recommend installing the HIT kit before doing any of the iSCSI or Multipath I/O configuration. It will make your life a lot easier. It’s also not a problem to install the HIT kit after you’ve done some or all of the configuration, just keep in mind there Read more [...]

Rename a Network Interface from the Command Line

While building a Hyper-V server this week, I decided to rename the network interfaces to something that would make identifying the iSCSI connections a little easier. Since the server was installed with only the core (no GUI) installation of Windows Server 2008 R2, the process had to be performed from the command line. The network interface is also commonly referred to by other names such as network adapter or network connection. To show a list of the network interfaces, run the following command: To Read more [...]