I' m starting to look at Exchange 2010 in my spare time and noticed the following, concerning the required features. Note: yes, I am using the Exchange 2010 SP1 media. ---------------------------------------------------------------------------------------------------- I've installed .NET 3.5 SP1 - one of the pre-requisites. I used the file downloaded from MS (off-line install, 200+ MB) On the point of installing other required features, I see, among the features already installed (RSAT-ADDS for example): ".NET Framework 3" Apparently version 3.5 is not displayed as such? Is anything between 3.0 and 4.0 simply displayed as 3? What if I run an install scripts from the DVD media? Will it try to install 3.0 over 3.5? ------------------------------------------------------------------- I downloaded and installed the WinRM / PS 2 package but PS is shown as not installed: [ ] Windows PowerShell [PowerShell] Even though I run this command from... PS! PS C:\> ServerManagerCMD -q Same result in the GUI (as one would expect). Is this a bug?

What version of Windows 2008 are you installing on (2008 or 2008 R2)? This link will show all OS requirements and needed hotfixes required before installing Exch 2010 SP1. http://technet.microsoft.com/en-us/library/bb691354.aspx This should answer any questions that you have.Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

This topic provides steps for installing the necessary Windows Server 2008 Service Pack 2 (SP2) or later or Windows Server 2008 R2 operating system prerequisites for all Microsoft Exchange Server 2010 server roles. It also includes the steps for installing the Windows Vista and Windows 7 operating system prerequisites for the Exchange Management Tools. http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

Thanks Tim. That's precisely the link that I've been using - notably to gather all the pre-requisites. I have just installed Exchange 2010 on a Windows 2008 SP2 virtual machine (this is just for practice - I'm using VMWare Workstation 7.1) and everything went OK. But I installed all the pre-requisites (roles, role services, features and then patches) manually. I'm going to revert to the snapshot I took and then let the wizard attempt to install those pre-requisites itself. We'll see what happens. I'll then try this on W2K8 R2. Otherwise, unless there's some small print I'm missing, I still don't see: 1) Why the .NET Framework version is shown as 3.0 when I manually installed the 3.5 SP1 version. 2) Why Powershell is not shown as installed after I installed it as part of the downloadable WinRM/PS 2.0 package mentioned precisely in the link you provided (under the SP2 requirements).

m.salah: One of the scripts provided in that link (here): Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart is precisely what leads me to wonder what would happen if I installed the .NET 3.5 SP1 Framework package manually and THEN ran the above script? Of course, I can try this myself and we'll see. Maybe... You see, my concern is that if I install the .NET 3.5 SP1 package first and then run the script (which, I believe, corresponds with the version 3.0), this order of proceeding might cause problems. But in a worst case scenario, the problems might not be obvious at first. I don't know if it would cause problems or not. If it did, then perhaps the best course of action would be to run the script first, and then install 3.5 SP later. Ultimately, I want to know if the order of installation matters or not, so if I'm doing this for someone (or myself) or troubleshooting an installation, I do it right (or know why there are problems).

This is the kind of problem I am talking about. This is the kind of confusion I would like to avoid: http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/0382d99d-53e0-456a-ab45-c0c5c82ea787 I would say that PS not registering itself as installed, if not installed via the Server Manager Console (or cmd line) is a bug.

I'm going to revert to the snapshot I took and then let the wizard attempt to install those pre-requisites itself. We'll see what happens. This is what happens: The Exchange setup wizard detects that (at least) .NET 3 is installed and does not attempt to install over. This is from the Exchange setup log: Start Installation... Skipping [.NET Framework 3.0 Features] .NET Framework 3.0 Features because it is already installed on this computer. [Installation] Succeeded: [.NET Framework 3.0 Features] WCF Activation. [Installation] Succeeded: [Web Server (IIS)] Management Tools. [Installation] Succeeded: [Web Server (IIS)] Web Server. [Installation] Succeeded: [Web Server (IIS)] Application Development. [Installation] Succeeded: [Web Server (IIS)] Security. [Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Compatibility. [Installation] Succeeded: [Windows Process Activation Service] Process Model. [Installation] Succeeded: [Windows Process Activation Service] .NET Environment. [Installation] Succeeded: [Windows Process Activation Service] Configuration APIs. [Installation] Succeeded: [Web Server (IIS)] IIS 6 Metabase Compatibility. [Installation] Succeeded: [Web Server (IIS)] IIS Management Console. [Installation] Succeeded: [Web Server (IIS)] Request Filtering. [Installation] Succeeded: [Web Server (IIS)] IIS 6 Management Console. [Installation] Succeeded: [.NET Framework 3.0 Features] Non-HTTP Activation. [Installation] Succeeded: [Web Server (IIS)] .NET Extensibility. [Installation] Succeeded: [.NET Framework 3.0 Features] HTTP Activation. Success: Installation succeeded. So that's one question answered. I still don't know why Powershell is shown as uninstalled though.

Hi Le, "I still don't know why Powershell is shown as uninstalled though." If you installed the WinRM / PS 2 package (Windows6.0-KB968930-x64.msu), you can check it in the Programs and Features. And there is a link the the Start->All Programs->Accessories->Windows Powershell. By the way, if you didn't install the package, the Exchange setup will not let you choose to Install Step 3 or Step 4. "One of the scripts provided in that link (here): Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart is precisely what leads me to wonder what would happen if I installed the .NET 3.5 SP1 Framework package manually and THEN ran the above script?" The script if for Server 2008 R2, not for SP2. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Le, "I still don't know why Powershell is shown as uninstalled though." If you installed the WinRM / PS 2 package (Windows6.0-KB968930-x64.msu), you can check it in the Programs and Features. And there is a link the the Start->All Programs->Accessories->Windows Powershell. By the way, if you didn't the package, the Exchange setup will not let you choose to Install Step 3 or Step 4. "One of the scripts provided in that link (here): Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart is precisely what leads me to wonder what would happen if I installed the .NET 3.5 SP1 Framework package manually and THEN ran the above script?" The script if for Server 2008 R2, not for SP2.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Le, Any updates on your issue?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'm fine. I see how that works now. Thanks!