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): ](/images/2012/04/ps2-2008r2core01.png" height=“480)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: ](/images/2012/11/sc-ps3-failure1.png” height=“503)PowerShell version 2 works fine on the server, but you’ve been tasked with loading PowerShell version 3 on it.
Windows Server 2008 R2
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.
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.
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).
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 .
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.
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.
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 Experience” feature using PowerShell: Import-Module ServerManager Add-WindowsFeature Desktop-Experience A restart is required once this feature is enabled. µ
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: Import-Module ServerManager Add-WindowsFeature PowerShell-ISE If you attempted to run this on the Core (no GUI) installation of Windows Server 2008 R2, you would receive the following error:
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 server:
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.
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.
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.
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 will be a few dialog boxes in this blog that you won’t see such as the HIT kit wanting to install the Multipath I/O feature.
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.
This blog article will guide you through the steps of setting up Remote Desktop Licensing or Terminal Services Licensing as it’s known in previous versions of Windows Server. You’ve decided to move from Windows 2003 R2 to 2008 R2 domain controllers and you want to run your terminal services licensing on the new domain controllers. You can run the licensing for all your terminal servers operating with Windows 2000 Server and newer Windows Server versions on Windows Server 2008 R2.
In an Active Directory environment the default time source is the domain controller in your forest root domain that is running the PDC emulator FSMO role. Keep in mind that the PDC emulator FSMO role is a domain level FSMO role so each domain will have one, but each domain’s PDC emulator will receive its time from the forest root’s PDC emulator. The following procedure will walk you through the steps of configuring the forest root’s PDC emulator to receive its time updates from an Internet time server.
Managed Service Accounts seem to be the end all and fix all for those services such as Exchange or SQL that we have all at some point either set to run as local system, an administrator account, or at best a domain user account that has been setup with the principal of least privilege. Using an account such as local system grants more rights than necessary and the service ends up running as a local administrator equivalent.
You have a Windows 2008 R2 server that is nearly out of disk space on its ‘D’ drive. The ‘D’ drive is a volume on an EqualLogic PS4000XV Storage Area Network. This is a production server and the change needs to be done immediately in the middle of the day without service interruption. Whenever possible, I prefer to make changes like this outside of production hours or as scheduled downtime if you operate in a 24/7 environment since there is a chance that something could go wrong.
Recently while assisting one of my customers who was transitioning from Windows 2003 to Windows 2008 terminal servers we experienced a problem with start menu redirection where there was nothing at all on a user’s start menu. The start menu was (empty) or blank. This problem ended up being due to applying the same group policy to the 2008 terminal servers that was previously applied to the 2003 terminal servers. To resolve this issue the “Remove user’s folders from the Start Menu” setting that was previously enabled in the group policy object (GPO) and worked without issue on Windows Server 2003 needs to be disabled on the new Windows Server 2008 terminal servers.
You’ve added hardware to a Windows Server 2008 R2 Core installation machine and you want to check the status of it through the GUI by using Device Manager on a remote computer. The following process allows you to access Device Manager remotely in “Read Only” mode and it assumes that you’ve already configured remote management on your core server through option 4 of sconfig. You’re already able to access the event logs and/or services using Computer Management on a remote computer.
So you’ve built a server and partitioned the RAID array into two logical partitions, one for the operating system and one for the data. For whatever reason, you need to reload the operating system on the server and you think you can format the OS partition and reload it without loosing the data that’s on your data partition. If you were booting directly to an operating system CD or DVD, that would be true, however if you boot to the Dell Systems Build DVD and attempt to reload the operating system with it, it will perform a step of “Clearing Existing Partitions” even if you choose to retain the existing RAID configuration.
To change the serial number on your Windows Server 2008 Core Installation, run “slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” where X is your new serial number. Wait for the popup confirmation message that the serial number has been changed: Run “cscript c:\windows\system32\slmgr.vbs -ato” to activate the operating system: µ
To determine if the Multipath I/O feature has been installed, login to your core server and run oclist.exe: If you already know the name of the feature or role your looking for, you can save yourself some time by piping the output of the oclist.exe command to the find.exe command. The /I parameter makes the search case insensitive. To install the MultipathI/O feature, run “start/w ocsetup.exe MultipathIo”. The name of the feature is case sensitive.
One of my customers contacted me today with an issue where the time on all of their servers was off by about 8 minutes or so. My first thought was “which Active Directory domain controller is their authoritative time server?” and “I’ll update the time on it manually and then set it up to synchronize from an Internet time server”. By default, the authoritative time server for your organization is the server that holds the PDC Emulator FSMO role in the forest root domain.
I recently built a test machine with Windows Server 2008 R2 and Microsoft Office SharePoint Server (MOSS) 2007. Before you get started with the MOSS installation, you need to add the .Net Framework 3.5.1 feature to your server and the Web Server (IIS) role. If you do not add the Web Server role manually, the MOSS installation will add it for you, but you’ll run into difficulties later. I’ve previously installed MOSS 2007 and WSS 3.
I will be diving into the dark side with this blog since I prefer working with Microsoft based technolgies such as SharePoint and ASP.NET. Each time I work with PHP and MySQL, it seems like it takes a little Voodoo to make them work. This blog is the bare minimum configuration to get Joomla working on a Windows 2008 R2 Server with Apache, PHP, and a remote MySQL server. First, download the latest version of Apache HTTP Server win32 binary without crypto MSI installer, PHP VC6 thread safe zip file, MySQL Community Server essential 64 bit MSI installer, and Joomla.
This blog will step you through the process of migrating your Active Directory domain controllers from Microsoft Windows Server 2003 R2 to Windows Server 2008 R2 Server Core. Server Core is an excellent choice for dedicated domain controllers since it requires less maintenance, has a reduced attack surface, requires less management, and will run on less hardware. Lots of people are scared off by Server Core because there’s no GUI. To be honest with you, it’s a blessing in disguise since you shouldn’t be managing your production Active Directory environment directly on your domain controllers anyway.
Problem: You receive the message: “The job failed with the following error: A failure occurred accessing the object list.” in your backup job notification email when attempting to backup the system state of a Windows 2008 Server with Symantec Backup Exec. The actual error from the backup server job is: “e000fedd - A failure occurred accessing the object list.” and the error code is: “V-79-57344-65245”. Solution: This error is fairly generic and can be caused by several different problems; the issue I encountered was specifically due to using the combination of Trend Micro Worry-Free Business Security Advanced (Antivirus), Symantec Backup Exec 12.
Problem: You receive an error Virtual Disk Manager “The RPC server is unavailable” when attempting to remotely manage Hyper-V Server 2008 or Windows Server 2008 Core Installation: Solution: Run the following command on the client and on the server: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes You have the option of using the Server Configuration menu on the server side if your using Hyper-V Server 2008. Select option 4, Configure Remote Management:
Problem: You’ve closed your command prompt window on Hyper-V Server 2008 or Windows Server 2008 Core Installation and need to re-open it: Solution: Start Windows Task Manager by pressing Ctrl & Shift & Esc. Click File>New Task: Type cmd.exe and click ok: You now have a new command prompt window: µ