Sync OWA public folders with freedocs on Exchange 2003

at my customer I installed SBS 2003 R2 SP2 with Exchange SP2. All is working fine, I just want to make some enhacements.
They like intranet SharePoint portal very much, and they also like Common Documents inside the portal. Some clients like to drag-n-drop documents in Shared Docs folder via Windows explorer, while others prefer SharePoint interface.
All fine for now.

But what I want to add is that some particular Shared Docs folder from SharePoint portal would be accessible also from outside, via OWA 2003 interface.
I found out Reg Key to enable FreeDocs feature in OWA 2003, so I set it to (3) "FreeDocs available from anywhere".
Now, my problem is how to add a share from server (actually, SharePoint Shared Documents share) to OWA to be accessible from Public Folders in OWA.

Any idea?
LVL 18
Andrej PirmanAsked:
Who is Participating?
Jeffrey Kane - TechSoEasyConnect With a Mentor Principal ConsultantCommented:
The problem is that FreeDocs won't sync with a SharePoint Document Library, it will show documents that are in a Public Folder, but by putting documents there you are reverting to older, legacy technology.  

Even if you hacked OWA to get a link to a SharePoint Doc Library, you wouldn't get passthrough authentication.  

Now, you technically could do it the other way around and just have them use SharePoint (with Exchange Web Parts or an I-Framed OWA).  But wouldn't it just make more sense to use SBS in the manner in which it was designed?  I've got tons of sites using RWW very successfully and you aren't "implementing too many options" to have them use it, only those items which you enable while running the CEICW will show up on the main menu, and even then you can edit it down to what you want.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Why don't they just use Remote Web Workplace instead?  It has links to both OWA and Companyweb right from the main menu with a single logon.

No need to start adding something that would do what is already there natively.

See for info.

Andrej PirmanAuthor Commented:
Hmmm...thanx, Jeff, interesting features. I almost forgot of RWW on SBS. I'll install it and ask for customer's oppinion. It might happent they will love it.

But on the other hand, I do not want to implement too many options, so I am still looking for some hint on my initial question.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Andrej PirmanAuthor Commented:
I am trying to get RWW to work, but have not suceed yet. All I got is 404 error.
Maybe the problem is, that "internet connection wizard" fails (and skips) Firewall Configuration, since I have only one single NIC adapter in server. So I opened ports 443, 444, 80 and 4125 manually on my router/firewall.
But still, no success, only 404 error, either via HTTP or HTTPS.

Only response I could get was localy via URL https// (which is server local IP) where IE asked if I trust SSL certificate, and then throwed out 404 error again.

Any idea what am I missing?
OWA is working fine, also local SharePoint site via http:/*anything_IP_or_NetBIOSname/

Andrej PirmanAuthor Commented:
Maybe some additional info:
- in IIS, "Remote" web application's home folder is C:\inetpub\Remote
- "Remote" application uses .NET framework 1.1, not 2.0
- Default Web Site is configured to require 128-bit SSL
- from outside, WORKS, while /remote does NOT, as does NOT work  /*anything_but_exchange*
Andrej PirmanAuthor Commented:
Ahhhhh...sorry for bothering.
Internet Configuration wizard broke my IIS and OWA config... Nothing works anymore. Damn wizard...
Andrej PirmanAuthor Commented:
Ok, I fixed the issue with OWA, but still cannot access RWW. All docs I read, refer to go throuhg Internet connection Wizard to configure Firewall on SBS...
...but my SBS has only one single LAN adapter, so Wizard fails  on configuring firewall, and brokes my setting by the way, rendering even OWA unacessible from outside world.

Also, in MS documents I cannot find how to access RWW (Remote Web Workplace). Is the URL correct? Or is just my imagination, which claims that RWW is pretty bad documented feature?

Is there any other document on How to setup and access RWW, which would not require Internet connection Wizard?
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
" Damn wizard..."
The CEICW should NOT fail just because you have a single NIC.  That's a normal configuration.  If the wizard is breaking thing it's because you've mis-configured them.  Since there are so many things which operate inside an SBS box, they really can only be configured to work harmoniously when you use the wizard.

"SharePoint site via http:/*anything_IP_or_NetBIOSname/"
Are you sure that's SharePoint?  Are you seeing the Welcome to Small Business Server page? (screen shot:  That's not SharePoint, it's the default web page.  SharePoint is accessed via http://companyweb

"Default Web Site is configured to require 128-bit SSL"
This is not the default configuration, and it very well may be causing your problem.  Especially if you changed it to require 128-bit SSL and propagated that setting to virtual directories below.

So, here's what you need to do to get this configured correctly...

1.  If you did change the IIS settings to require SSL on the default site, you can check to see if there was an automated Metabase backup from before any changes were made.
If you don't have an earlier backup, just uncheck both the Require 128-bit encryption and Require SSL boxes and restart IIS.

2.  Find out what the exact error is when running the CEICW.  Easiest way is to rename the current log file so you can rerun the wizard and create a new, clean log.  Then look for the ERROR lines.
Log file is at:  C:\Program Files\Microsoft Windows Small Business Server\Support\icwlog.txt

3.  Make sure SharePoint is really running at http://companyweb

Andrej PirmanAuthor Commented:
Hi Jeff,
thank you very much for helping me even on out-of-the-scope of initial question issue.

I followed your instructions and found out the following:

1.) I really configured Default Web Site to require 128-bit SSL, and propagated this setting down to all virtual directories below. That's my paranoya, because our ISP allows listening on broadcast, so if I allow to use unencrypted communication, any hacker could listen.
I'll change that for the wizard to pass.

2.) http://companyweb automatically redirects to http://servername, which I really do not remember I ever changed. As I remember, just after initial setup it was automatically set so.
Actually, I uninstalled SharePoint 2.0 and installed SharePoint 3.0 on fresh SBS R2 SP2.
It is my first contact with SharePoint, so I thought that what I saw on local web site, that is SharePoint.

3.) One other anomaly which I notice is MSSQL$SHAREPOINT service is by default set to Manual and is stopped. I don't really understand why, and how is intranet web site working with this service stopped.

4.) In CEICW log I found some errors (see attached code)

5.) I think I'll manage from here on myself. thanx for help, I learned a lot on this subject.
Calling CCertCommit::ValidatePropertyBag
Nothing is published, will not touch SSL Settings
*** CCertCommit::ValidatePropertyBag returned ERROR 1
calling RegisterMSBOExchangeBP (0).
Error 0x1 returned from call to RegisterMSBOExchangeBP().
Call to Unpublishing the default web site () returned ok.
Error 0x80070003 returned from call to Fixing the inheritance for companyweb dir().
calling Set Web Publishing Rules (0x80070003).
Error 0x80070003 returned from call to CRFireCommit::Commit().
Calling CCertCommit::CommitEx
Calling CCertCommit::ValidatePropertyBag
Nothing is published, will not touch SSL Settings
*** CCertCommit::ValidatePropertyBag returned ERROR 1

Open in new window

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It doesn't matter that your ISP allows listening on broadcast... that's why you have a firewall.  You shouldn't have port 80 open anyhow... there's no need for it.  That's how you keep everything on SSL.

If you uninstalled SharePoint 2.0 and installed SharePoint 3.0 you broke SharePoint.  You can't do it that way.  If you want 3.0 you have to install it side-by-side following this documentation:

MSSQL$SHAREPOINT is set to manual and stopped because you uninstalled WSS 2.0.  WSS3.0 doesn't use that database.

My suggestion?  Start over.  

It's widely known that it takes at least 3 times to install your first SBS (it took me at least 4, and after over 100 SBS installs, I still do it with the documenation right in front of me).  See 

Starting over will give you the chance to do it right rather than trying to patch up what is now a very ill server, it'll take you less time and effort than chasing down little problems here and there for as long as you have the machine in service.  But this time... follow the documenation... ther's lots out there, and it really should be used.

Andrej PirmanAuthor Commented: starting over I hope you mean to start over only with Sharepoint, not the whole SBS. Because this SBS box is already in production and Exchange is in full deployment.

I uninstalled WSS 2.0 because of error in WSS 3.0 installer (it failed in step 3) and I found a suggestion on some forum, that I need to uninstall 2.0 to pass this step 3 sucesfully. Obviously it was wrong suggestion.

So, here is what I'll do:
- uninstall WSS
- reconfigure 2nd NIC adapter, which is curently service LAN, to be used as normal LAN adapter
- run CEICW
- install WSS 2, and upgrade to WSS 3
- and, of course, read all your docs prior to doing anything
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No, I mean start over completely.  Reformat.  Reinstall SBS.  Even though Exchange is in production, I'm telling you that you may find it easier to reformat/reinstall than to fight what you've got on your hands.

You can most likely do a reinstall in about 8 hours total.  It'll take you at least half that to do the above... and then consider it'll take you about 10 times that over the course of the next two years just messing with what's not working.  That doesn't even start to take into account employee's lost productivity due to the server not being deployed correctly.  Give the article a read and then decide.

Andrej PirmanAuthor Commented:
Jeff, thanx for great guidence.
I'll consider reinstalling SBS, since I know it would be beter for me and for customer, but unfortunatelly, I am bound to my employer's policy, who assigned 32 working hours for SBS installation, with all customizations, SQL, SharePoint, Exchange etc. And, guess what - my company thinks that paying for my education is bullshit, since I proved that somehow things work even without good knowledge.

So, what I have is just spend lots of time on net, reading, learning and, most of all, learning from my own mistakes.

I'll close this thread and go with SBS fresh install next weekend.
Thanx again.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.