Re: RPCH Over HTTP config

Thanks answers inline

Where these machines added to the server using
http://servername/connectcomputer ?

Actually I don't know but what the computer needs to grant access to users
using the Remote Web Workplace (whithout running the
http://servername/connectcomputer)?

I am not sure exactly what you need here but the following might help.
http://www.microsoft.com/technet/prodtechnol/sbs/2003/support/e34b3539-6bd9-430f-8884-32435d5b4b90.mspx?mfr=true

Thanks for the link but doesn't answer my question, please let me
rephrase...
Assuming that "Web Workplace Users" is used to grant access to the Remote
Web Workplace from the Internet, where can I check how and were this is
configured. Let's say that I need to configure a security Group Named
"Partners Web Workplace Users", and I don't want to make that new security
group member of the default "Web Workplace Users", how do I setup
permissions to this new group to grant access to the Remote Web Workplace
from the Internet?

Thank you again for your time and patience
Regards...

"Michael Jenkin [SBS-MVP]" <michael.jenkin@xxxxxxxx> wrote in message
news:OVAIIi3AHHA.1224@xxxxxxxxxxxxxxxxxxxxxxx
I am not sure exactly what you need here but the following might help.

http://www.microsoft.com/technet/prodtechnol/sbs/2003/support/e34b3539-6bd9-430f-8884-32435d5b4b90.mspx?mfr=true

Gig wrote:

Hi Michael
Thanks for your fast response, if you don't mind I have another one:

Remote Web Workplace users security group, where its applied the
permissions
for this group?
I know that if you're member of this group you can connect remotly to the
website and access remotely to the machines, but for example if I wanted
to
create a nother group with the same permissions where should I configure
that?

Thanks again?

"Michael Jenkin [SBS-MVP]" <michael.jenkin@xxxxxxxx> wrote in message
news:%23tyP$ayAHHA.4592@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

Once you have run the ceicw, you have done all you should need to do
(As
long as you opted to create a certificate etc in the wizard).

The only other items to make sure is to allow port 443 etc through your
router.

Now, go to your servers default web page (http://serverip) or
https://mail.servername.com/remote (if you are remote) and you will see
a link telling you what to do at the remote end. As long as you have an
outlook profile on the remote Pc (Which can be done over a VPN) you
have
all you need to continue.

See the link called "Configure your computer to use Outlook via the
Internet" on the RWW page.

Curtesy of that link :

Using Outlook via the Internet
If you are using Microsoft® Office Outlook® 2003, you can connect to
the
computer running Windows® Small Business Server through the Internet
using the feature called RPC over HTTP. This means you can remotely
access your server e-mail account from the Internet when you are
working
outside your organization's firewall. You do not need security-related
hardware or software (such as smart cards or security tokens), and you
do not have to establish a virtual private network (VPN) connection to
the server.

Comparing RPC over HTTP and Outlook Web Access
When using RPC over HTTP to access your mailbox, you get the full
functionality of Outlook 2003. For example, you can work offline, use
Microsoft Office Word 2003 as your e-mail editor, and easily organize
your mailbox.

To use Outlook via the Internet

Ensure that the following requirements have been met on the client
computer:

Verify that the computer is running Microsoft Windows XP Service Pack 1
or later
Click Start, right-click My Computer, and then click Properties.
The version of the operating system and service pack is displayed under
System. If you do not see a service pack version, there is no service
pack installed.
Verify that Windows update Q331320 is installed on the computer (not
required if you are running Windows XP Service Pack 2 or later)
Click Start, click Control Panel, and then open Add or Remove Programs.
Under Currently installed programs, search for the item Windows XP
Hotfix (SP2) Q331320.
If the item is not present, go to the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=18651) and follow the
instructions to download and install it.
Verify that the computer is running Outlook 2003 or later
Open Outlook.
Click the Help menu, and then click About Microsoft Office Outlook. The
version number appears at the top of the box.
Verify that the computer trusts the certificate used by the server
Open Internet Explorer, and then in the address bar type:
https://mail.domain.com/remote


If the certificate is trusted, a certificate warning does not appear.
In
this case, continue with step 1 under Ensure that you have an Outlook
profile configured for the server.
If the certificate is not trusted, a warning appears. Click View
Certificate, click Install Certificate, and then follow the
instructions.
Ensure that you have an Outlook profile configured for the server
Click Start, and then click Control Panel.
If you are viewing Control Panel in the default Category view, switch
to
Classic view, and then double-click Mail.
If you are viewing Control Panel in Classic view, double-click Mail.
In the Mail Setup dialog box, click Show Profiles. If your profile
appears in the list, select your profile, click Properties, click
E-mail
Accounts, select View or change existing e-mail accounts, and then
click
Next. If your profile does not appear, open Outlook and follow the
instructions to create a profile before proceeding.
If Microsoft Exchange Server does not appear in the list, the existing
profile is not associated with a Microsoft Exchange Server e-mail
account. Click Cancel, and then click Close. Continue with step 3 to
add
a profile.
If there is an existing Microsoft Exchange Server profile, continue
with
step 3 under Configure the computer for RPC over HTTP.
Click Add. The New Profile dialog box appears.
In the Profile Name box, type a name for the new profile, and then
click
OK. The E-mail Accounts dialog box appears.
Under E-mail, select Add a new e-mail account, and then click Next. The
Server Type dialog box appears.
Click Microsoft Exchange Server, and then click Next.
Continue with step 4 under Configure the computer for RPC over HTTP.
Configure the computer for RPC over HTTP
Click Start, and then click Control Panel.
If you are viewing Control Panel in the default Category view, switch
to
Classic view, and then double-click Mail.
If you are viewing Control Panel in Classic view, double-click Mail.
In the Mail Setup dialog box, click E-mail accounts, click View or
change existing e-mail accounts, and then click Next.
In the E-mail accounts dialog box, click Microsoft Exchange Server, and
then click Change.
In the Microsoft Exchange Server box, type the local name of the
Exchange server:

servername.domain.local


In the User Name box, type the user name that you use to log on to the
Remote Web Workplace. Do not click Check Name.

In the Exchange Server settings page, click More Settings.
On the Connection tab, under Exchange over the Internet, select Connect
to my Exchange mailbox using HTTP, and then click Exchange Proxy
Settings. The Exchange Proxy Settings dialog box appears.
Under Use this URL to connect to my proxy server for Exchange, type the
following URL:
mail.domain.com

Select Connect using SSL only, and then select Mutually authenticate
the
session when connecting with SSL.
In the Principal name for proxy server box, type the following text:
msstd:mail.domain.com

Select On slow networks, connect using HTTP first, then connect using
TCP/IP.
Under Proxy authentication settings, select Basic Authentication.
Click OK, and then click OK again. Click Next, and then click Finish.
Click Close.
In the Mail dialog box, if Always use this profile is selected, choose
the newly configured profile.
Open Outlook and type your Windows Small Business Server user name (in
the format DOMAIN\user name) and password. You can now work with your
Outlook mailbox.

where domain is your internet domain


Gig wrote:

Hi
I was told to configure RPC over HTTP for SBS clients, we have Windows
2003
SBS with ISA 2000, and we also have a cisco as gateway router, my
question
what ports do I need to open (I think that's 80 and 443 or do I need
more
ports).

Is there any link that helps me with that?

I also have another problem, I'm thinking configuring with SSL but I
have
2
network users that don't belong to our internal domain is it possible
for
them to use their home laptops to connect to our RPC over HTTP using
SSL?

Thank you for your help



--
Michael J. Jenkin MVP - SBS, MCP, Small Business Specialist, Senior
Systems Engineer
Visit http://www.mickyj.com



--
Michael J. Jenkin MVP - SBS, MCP, Small Business Specialist, Senior
Systems Engineer
Visit http://www.mickyj.com


.

Relevant Pages

  • Re: Where does it get its content from?
    ... App server is installed into the WS2003 server the registry should reflect ... >>Web Workplace. ... >> Learn more about the Remote Web Workplace. ...
    (microsoft.public.windows.server.sbs)
  • RE: need to migrate a older win 2003 srvr sbs to newer one
    ... as I assume I should reading upon Windows Server 2003 inside out book. ... there are three method to move the SBS 2k3 to new ... Also check the path of the public folder database ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.migration)
  • RE: SBS2003 changed hardware
    ... For your situation, the old server hardware has failed, we only have to do ... the Disaster Recovery of SBS if you have full backup of your SBS. ... Another way is to create a local profile, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 - Move Profiles, Etc. from 2000 Server
    ... moving PST on old server. ... guide in SBS 2003, we have a white paper for this kinds of migration, ... Another way is to create a local profile, ... Click Personal Folders File, ...
    (microsoft.public.windows.server.sbs)
  • Re: RPCH Over HTTP config
    ... See the link called "Configure your computer to use Outlook via the ... Small Business Server through the Internet ... profile configured for the server. ... If Microsoft Exchange Server does not appear in the list, ...
    (microsoft.public.windows.server.sbs)
Loading