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.
Windows Server 2008
This week while working with some PowerShell scripts that retrieve WMI information from remote servers, I ran into an issue where I was able to return results from Windows 2008 R2 servers without issue but was unable to return results from Windows 2008 (non-R2) servers even though they had PowerShell 2.0 installed and as far as I could tell they were configured exactly the same as the Windows 2008 R2 servers.
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. µ
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.
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.
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.
One of my customers that I provide level 3 support for recently contacted me with an issue where their system would hang on the message “Please wait for the System Event Notification Service…” when they attempted to logout of their Windows 2008 terminal server: We determined that their terminal server had recently received an update to Windows Live Messenger via Windows Update that was causing this issue. Removing Windows Live Messenger from their terminal server resolved their logout issues.
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: µ
I recently updated and migrated some HP MFP Digital Sending Software (DSS) from version 4.13 to 4.16 and from a Windows 2003 Server to a Windows 2008 Server. One thing to note is that even the newest version of the HP DSS Software (4.16) will not run on a 64bit operating system so the newest operating system that can be used is a 32bit version of Windows 2008 (non-R2 since R2 is 64bit only).
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: µ