B
bknfla
Has anyone installed the Web Portal on a SBS2003 (Microsoft Small Business Servers 2003) It has Sharepoint on it as well. Anything special to look out for? Does it work?
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
N
nixu
Hi there,
I tried it and it should work for you too..
Nixu
I tried it and it should work for you too..
Nixu
R
rjodwyer
How does this work?
SBS2003 is not a Terminal Server, it only allows 2 RDP sessions.
My question would be, how do you install it on SBS and get it to work with another 2003 Terminal server?
Regards,
Ryan
SBS2003 is not a Terminal Server, it only allows 2 RDP sessions.
My question would be, how do you install it on SBS and get it to work with another 2003 Terminal server?
Regards,
Ryan
N
nixu
Hi there...
For your scenario to work you need the following..
1) Install 2X ApplicationServer & Loadbalancer on the SBS2003
2) Set Up the 2X ApplicationServer & Loadbalancer to make use of another 2003 Terminal server.
3) Install the 2X Web Portal on the SBS2003 .
Using a web browser, clients connect to the 2X Webportal on the SBS2003 and when they click on the application they are connected with the 2003 Terminal server.
Nixu
For your scenario to work you need the following..
1) Install 2X ApplicationServer & Loadbalancer on the SBS2003
2) Set Up the 2X ApplicationServer & Loadbalancer to make use of another 2003 Terminal server.
3) Install the 2X Web Portal on the SBS2003 .
Using a web browser, clients connect to the 2X Webportal on the SBS2003 and when they click on the application they are connected with the 2003 Terminal server.
Nixu
B
bknfla
SBS2003 and W2K3 TS as recommended setup
Ok. If you have a SBS2003 server with IIS and Sharepoint, etc running and we all know SBS2003 does not run Applications in Terminal Services so the recommendation is of course to install Windows 2003 Server with Terminal Services and install 2x ApplicationServer and 2x TerminalServer. With that said I would imagine that you would install the 2x Windows Portal on the SBS2003 server..which works sort of however it messes up IIS and the Sharpoint services. Does anyone have any screen prints of how the 2x Windows Portal web services is supposed to be configured within IIS? Seems there some issues with duplicate versions of ASP.net 1.2 and 2.0 and etc.
Ok. If you have a SBS2003 server with IIS and Sharepoint, etc running and we all know SBS2003 does not run Applications in Terminal Services so the recommendation is of course to install Windows 2003 Server with Terminal Services and install 2x ApplicationServer and 2x TerminalServer. With that said I would imagine that you would install the 2x Windows Portal on the SBS2003 server..which works sort of however it messes up IIS and the Sharpoint services. Does anyone have any screen prints of how the 2x Windows Portal web services is supposed to be configured within IIS? Seems there some issues with duplicate versions of ASP.net 1.2 and 2.0 and etc.
R
rjodwyer
Hi,
The way I've done it is this is to not touch IIS ports, as i've found it breaks mobile activesync.
So i have the 2X application server installed on the SBS in this manner:
2X ApplicationServer listens on port 82 - forwards requests to port 80(done inside of 2X, ie. localhost:80 instead of 81)
IIS still listens on 80, it seems this is a must without major modifications.
External access is still port 80, but forwarded to port 82(2X listening)
I push the agent to the terminal server which means I dont need 2X installed on the TS.
This is an almost perfect setup, except for the need to leave IIS default.
Regards,
Ryan
The way I've done it is this is to not touch IIS ports, as i've found it breaks mobile activesync.
So i have the 2X application server installed on the SBS in this manner:
2X ApplicationServer listens on port 82 - forwards requests to port 80(done inside of 2X, ie. localhost:80 instead of 81)
IIS still listens on 80, it seems this is a must without major modifications.
External access is still port 80, but forwarded to port 82(2X listening)
I push the agent to the terminal server which means I dont need 2X installed on the TS.
This is an almost perfect setup, except for the need to leave IIS default.
Regards,
Ryan