I plan on trying this out later and make more notes if need be.
Following the successful installation of System Center Essentials 2007 SP1 on Windows Server 2008 Standard x86, we typically install Remote Web Workplace on the server as part of our System Center Remote Operations Manager deployment.
Just as with installing SCE on Windows Server 2008, there are a few tricks to installing RWW.
Conventions
In this post I use the terms <server> to indicate the NETBIOS name of the server on which we are installing RWW and <domain> to indicate the FQDN of the domain that the server belongs to.
Install Remote Web Workplace
- Log on to your server as an administrator
- Run remoteww.msi from the Remote Operations Manager CD
- Click Next at the welcome screen
- Click Next after accepting the license agreement
- Click Install
- Click Finish after installation succeeds
Create an Application Pool to Support Remote Web Workplace
- Start > Run > Inetmgr
- Expand <server> and select Application Pools
- Click Add Application Pool… in the right pane
- Click OK after specifying the following settings:
- Name: Remote AppPool
- .NET Framework Version: .NET Framework v2.0.50727
- Managed pipeline mode: Classic
- Start application pool immediately: Checked
- Click Advanced Settings… in the right pane
- Change Idle Time-out (minutes) to 480 and click OK
It took me about a month to figure out why my Remote Web Workplace sessions were being dropped after 20 minutes. Setting the idle timeout for the application pool is critical when using Remote Web Workplace with IIS7 on Windows Server 2008. This value determines the maximum duration of a remote session. If left at the default of 20 minutes, your connection will be dropped after 20 minutes and you will receive an error VBScript: an internal error has occurred.
Secure Remote Web Workplace
- Expand Sites > Default Web Site in the left pane
- Select Remote and click Basic Settings… in the right pane
- Click the Select… button
- Select Remote AppPool in the Application pool dropdown and click OK
- Click OK
- Double click Authentication in the middle pane
- Select Anonymous Authentication and click Enable in the right pane
- Highlight Default Web Site in the left pane and click Bindings… in the right pane
- Click Add…
- Select https… in the Type dropdown
- Select <server>.<domain> in the SSL certification dropdown
- Click OK
- Click Close
Test Remote Web Workplace
- Open https://<server>/remote in a web browser
- Accept any certificate warnings that may be issued by your browser
- Log on to Remote Web Workplace using your network logon
- Verify that you can connect to a server or desktop on your network
Mal says
I was planning to install this on my server. I have Windows Server 2008 Enterprise.
Can this be done?
Kind Regards
Malcolm
Tom says
I have spent hours and hours on this but can’t find remoteww.msi. I can’t find any reference to a “Remote Operations Manager CD” as a product in its own right or as part of another product. Can you please clarify this part of your post?
It’s so frustrating to feel I am so close to a solution without being able to go any further!