How to install Power. Shell 2. 0 on Windows 2. R2 SP2 3. 2 bit. This is a post to explain how you can install Power. Shell 2. 0 on Windows 2. R2 SP2 3. 2bit which, by default, has no Power. Shell at all. As you might have noticed, yesterday I published a blog post explaining the steps to install Power. Shell 3. 0 on Windows 2. Uninstall Sharepoint 2010 Sbs 2011 Open' title='Uninstall Sharepoint 2010 Sbs 2011 Open' />R2 box. Unfortunately you cannot install the last version of this package on operating systems older than Windows 2. MSU installer Windows. KB2. 50. 61. 43 x. Windows 2. 00. 3 simply cant read it. So, due to the lack of anything better, lets focus on Power. Shell 2. 0. Heres what I did. Downloaded and installed Dot. Net 4 dot. Net. Fx. Fullx. 86x. 64. MB. Easy install, no reboot. Now download and install the Windows Management Framework 2. Windows. Server. 20. KB9. 68. 93. 0 x. ENG. exe, approximately 6 MB from here. This package contains Win. RM 2. 0 and Windows Power. Shell 2. 0. Go through the installation and there you are just click Start, Run and type Power. Shell then press Enter. Check the value of the host variable by simply entering it and pressing Enter and you should get the expected output telling you that Power. Shell 2. 0 is up and running host. Name Console. Host. Version 2. Instance. Id ddb. UI System. Management. Automation. Internal. Host. Internal. Host. User. Interface. Current. Culture en US. Current. UICulture en US. Private. Data Microsoft. Power. Shell. Console. HostConsole. Color. Proxy. Is. Runspace. Pushed False. Runspace System. Management. Automation. Runspaces. Local. Runspace. The next step is to enable Remoting, with the help of the Enable PSRemoting cmdlet. Execute this cmdlet and press A to confirm. With netstat we can now check that Win. RM is effectively listening to remote requests netstat abn find 5. TCP 0. 0. 0. 0 5. LISTENING 4. For your information, TCP port 5. Power. Shell 2. 0 uses for incoming unencrypted connections. Older versions of Win. RM use TCP port 8. Uninstall Sharepoint 2010 Sbs 2011 Open' title='Uninstall Sharepoint 2010 Sbs 2011 Open' />Wow, 412 years later and this post is still saving butts We encountered the issue after removing Exchange 2010 from and SBS 2011 box as part of an Office 365. The last step is to bind Power. Shell 2. 0 to Dot. Net 4. By default Power. Shell relies on Dot. Net 2, which you can verify with this command environment Version. The output is Major Minor Build Revision. To change this, move to C WINDOWSsystem. Windows. Power. Shellv. Legacy. V2. Runtime. Activation. Policytrue. Runtime versionv. Runtime versionv. Run again environment Version and this time you will that Power. Shell is using Dot. Net 4 Major Minor Build Revision. Get fast, free assistance preview our new Virtual Agent today. Ask the Virtual Agent. STATUS ON 12132011. HOTFIX HAS BEEN RELEASED Assume that you create a document in Word 2010. When you type an email address inside the. Recently a Windows 2008 server is displaying the following message when users admins try to log off from RDP sessions. So, heres my conclusions easy installationno need to restartunfortunately no Power. Shell 3. 0 support on Windows 2. Dot. Net 4 runs fine on Windows 2. For mire details about the topics covered here you can check. Hope this posts will help you. Do not hesitate to share you experience with Power. Shell on older systems. Problem starting Server and Workstation services after installing Great Plains. Edit August 2. 01. This post is over 6 years old and its the most popular post Ive ever made. Still going strongIts one of the top Google results for this type of error. Still getting dozens of hits per day. Nearly 1. 00 commentsIm glad I could give something back to my fellow IT pros. I know I spend most of MY day researching errors on Google as well. PS why not throw me a bone and click an ad on my site, like one of the banners up top I might earn a penny or two. Thanks. Ive stumbled across a rather odd issue the past few weeks. Best Software For Mpc 2500 Transfer. At first I just thought it was a typical Windows problem but when it started turning up on more than one machine, i figured there had to be a common thread. Here is the problem. Your XP machine cant browse the network. You can get the internet just fine but cant connect to any servers. As you are troubleshooting the problem, you discover that several Windows services are not running Server, Workstation, Computer Browser, Net Logon, among others. These services not running will definitely prevent you from browsing your network and connecting to other machines. So you try to start Computer Browser manually it tells you it cant start the service because it has a dependency on another service which turns out to be Server andor Workstation service. So now you try to start Server or Workstation service and you get the same error message on both of them The system cannot find the file specified. It also registers an Event 7. The system cannot find the file specified. This was happening on my laptop for a few days and i wasnt having much luck finding a solution. In fact, i was getting ready to re install Windows XP. But then i ran into the exact same problem on a few workstations at a clients site that i was just working on. They were going thru an upgrade to Great Plains 8. So i decided to look a little bit on Partner. Source, which i hadnt checked before since i didnt think it was a GP related issue. I did find an article that talks about this problem. Here is the link for Customer. Source or Parter. Source users. The title is Error 1. The specified file cannot be found and the Workstation Service Does Not Start After Installing or Updating Great Plains 8. What seems to be happening is the installation, update or maybe uninstall of Great Plains is wiping out some registry entries that point to the location of the. Server and Workstation services. So you need to edit the registry and put these keys back in place. Here are the steps from the TK article WARNING If a mistake is made on any of the instructions listed below, you may not be able to restart your system. If you are not familiar with the Registry, please seek assistance from Microsoft or your local Microsoft support representative. Microsoft can be reached at 1 8. IMPORTANT Back up your system before making these changes. It is also important to create a new Emergency Repair Disk. Verify that Service. Dll is stored in the registry at HKEYLOCALMACHINE SYSTEM Current. Control. Set Services lanmanworkstation Parameters. You should see an entry with the Name of Service. Dll, Type REGEXPANDSZ and Data value of systemrootsystem. If this entry does not exist, you can add it with the following steps a. Choose Edit New Expandable String Value. Name the new value Service. Dll it is case sensitive. Double click on this new value and specify Value data systemrootsystem. You could also copy the reg key from a working workstation. After the entry is added to the registry you should be able to start the Workstation Service. NOTE The uninstallinstall of Great Plains does not remove this registry entry. Ok, so those steps tell you how to get the location of the Workstation service dll back into the registry. You may find that the last key Parameters is missing all together. If that is the case, then right click on Lan. Man. Workstation and select New Key and name this Parameters. Then continue with step 3. But in my experience, i was missing both Workstation and Server dlls and all of the machines that had the problem. So here are my additional notes on how to get the Server service running again. The Registry location is HKEYLOCALMACHINE SYSTEM Current. Control. Set Services Lan. Man. Server Parameters. Again, i was missing Parameters key all together so right click on Lan. Man. Server and select New Key and name it Parameters. Then in this folder, create a new entry named Service. Dll, of type RegExpandSZ Expandable String Value and a data value of systemrootsystem. This is the dll for Server service. With this new entry in place, you should now be able to start the Service service as well. With Server and Workstation service both running, you should now be able to start Computer Browser and any other services that were dependent on them. This should get you properly connected back to the network. So ive seen this happen on 3 4 different machines now. The one thing in common would be that they previously had Great Plains Dynamics 6. Great Plains 8. 0 installed. Must be something to do with the Great Plains 8. Dynamics 6. 0 a million times and have never seen this problem. Ill definitely be keeping an eye on this situation with my other upcoming Great Plains upgrades. I hope this can help someone else and save you from re installing Windows like I was about to do. Update I seem to be getting lots of hits from Google searches concerning this problem. If youve run into this situation and my article helped you, please click down below on the comments link and leave a note, or shoot me an email Tech. Roundupjasonhartman. If this looks like a wide spread issue, i can pass the info along to my contacts at Microsoft and see how we can get this taken care of or at least publish some better Tech. Knowledge articles about it.