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.
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 this entire blog before beginning this process since there is an issue with SSD hard drives and Windows 7 in this particular netbook model. I will also warn you that this is one of the most difficult machines to replace the hard drive in that I’ve seen. First, remove the battery and hold down the power button for 30 seconds. Memory Upgrade Turn the computer upside down. Remove the single screw from the memory cover:
I recently loaded Windows 7 on my netbook computer and ran across a tool named Windows 7 USB/DVD Download Tool which makes creating a Windows 7 bootable USB flash drive much easier. Download and install this tool. Open the program and select the ISO you want to copy to your USB flash drive. Select “USB device”: Select the USB flash drive you want to copy the Windows 7 installation media to.
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:
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.
As most systems administrators know, you should log into your computer as a normal domain user who does not have elevated privileges in your Active Directory domain and only run administrative programs with elevated privileges when necessary. You could hold down shift, right click the shortcut, and select “Run as different user” to run a program as a user who has elevated privileges in your Active Directory domain, but there’s an easier, more efficient way to run programs that always require elevated privileges.
Problem: When attempting to open a pdf document by clicking on a hyperlink from within Windows 7, you receive a blank error message with Adobe Reader in the title and a question mark for the error message. Clicking on the OK button only displays a blank web page and does not open the pdf document. Solution: Installing all the available updates from the Adobe Reader 9 help menu > check for updates sub-menu option appears to resolve this issue.
Problem: You need to remotely manage your Hyper-V server from Windows 7. Solution: Download and install the “Remote Server Administration Tools for Windows 7” from Microsoft: https://www.microsoft.com/downloads/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en. Enable the Hyper-V Tools from “Control Panel>Programs>Turn Windows features on or off” menu: You should now have a “Hyper-V Manager” shortcut on your Administrative Tools menu. µ
Problem: I’m currently ruuning Windows 7 Ultimate Edition and Office 2007 Professional Plus. I receive “Microsoft Office Outlook has stopped working Windows is checking for a solution to the problem” just about everytime I use Outlook: " Application Event Log Error Message: Event ID: 1000 Task Category: (100) Level: Error Description: Faulting application name: OUTLOOK.EXE, version: 12.0.6504.5000, time stamp: 0x49e7f47e Faulting module name: olmapi32.dll, version: 12.0.6504.5000, time stamp: 0x49e7f423 Exception code: 0xc0000005 Fault offset: 0x00051a61 Faulting process id: 0xc1c Faulting application start time: 0x01ca340a023dfe6b Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.
Problem: An important audio codec is missing from 64bit versions of Windows Vista and Windows 7. Some media files generate an error when using Windows Media Player. Third party media players seem to be affected as well, since some will play the video portion with no audio, and others won’t play the media file at all. This problem even occurs with media files downloaded from Microsoft. The Windows Media Player specific error is: “Windows Media Player cannot play, burn, rip, or sync the file because a required audio codec is not installed on your computer.