Re: Free / Busy between two companies

Tech-Archive recommends: Fix windows errors by optimizing your registry

If you go with this as part of the solution, I for one would like to hear
about your experinces implementing it. I have not used it since Exchange
2000 and never with SBS200x.

--
/kj
"Steven Banks [SBS MVP]" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Otq8FY9EHHA.3616@xxxxxxxxxxxxxxxxxxxxxxx
Thanks kj!

That's a lot closer to a useable solution than what I've been dealing with
up to this point. Will see if both companies are game to give it a go on
their respective servers.

Thanks again,
Steve

Steven Banks, MCP, CSSA [SBS MVP]
Microsoft Small Business Specialist
Banks Consulting Northwest Inc.
http://www.banksnw.com
http://msmvps.com/blogs/steveb/

Co-Author, Advanced Windows Small Business Server 2003 Best Practices


"kj" <kj@xxxxxxxxxxx> wrote in message
news:eUeJTS9EHHA.140@xxxxxxxxxxxxxxxxxxxxxxx
The closest I know of is the Interorg Repication connector;

http://support.microsoft.com/kb/238573/en-us

Hope it helps.

--
/kj
"Steven Banks [SBS MVP]" <steve@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23%23jIhl8EHHA.4080@xxxxxxxxxxxxxxxxxxxxxxx
Hi!

West coast company (Company A) has a group within it's LAN that is
supporting East coast company (Company B). The subgroup in A is on its
own workgroup with a single file server and users have retained their
domain accounts on A to allow access to shares on A's network while the
workgroup's file server has local accounts created for this small group
to secure B's data from others on A's LAN. Lost you yet? ;-)

A is running Exchange 2000 Enterprise and B is running SBS 2003. The
workgroup users needs to be accessible in Outlook for calendaring with A
and not B. When I created a free/busy share on the workgroup server and
attempted to set the path for it in Outlook I was expecting to be able
to have two folders, one for each FQDN, and have each company A and the
workgroup's free/busy map to their respective folder. Instead what I
got was the A Exchange accounts attempting to place it in an LDAP/X.509
path within the directory structure (O=, OU=, CN= ...) and the workgroup
users' (who are using RPC over HTTP with the SBS box back east)
computers attempting to publish to share\WORKGROUP instead of their FQDN
folder. So that is leading me to guess that the free/busy server
solution has been intended for non-Exchange Outlook 2003 clients and not
Exchange based.

Cross forest trust will not work due to SBS in the mix and the two
companies really don't want the cross forest trust in the first place,
so anyone have any ideas/solutions they have used to accomplish this?

Thanks for any help!
Steve

Steven Banks, MCP, CSSA [SBS MVP]
Microsoft Small Business Specialist
Banks Consulting Northwest Inc.
http://www.banksnw.com
http://msmvps.com/blogs/steveb/

Co-Author, Advanced Windows Small Business Server 2003 Best Practices








.

Relevant Pages

  • Re: Network Neighborhood not working and Error 6118.
    ... You met the error 6118 while trying to access workgroup in other subnet ... Enable WINS log on SBS server. ... Right click the server name then choose Properties. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Shutdown Automatically?
    ... I am by no means a domain/server whizz but I have set up SBS 2003 for 5 of my clients and they all think I'm a genius! ... workgroup network to an SBS domain network. ... If you wanted workgroup then perhaps plain Windows 2003 Server would have been a better choice. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating "up" from XP Pro
    ... My challenge is that I'm not very familiar with the Windows Server ... Workgroups are not generally suitable for businesses as there's no central management, security, administration, whatnot. ... Doing so will provide you the upgrade to SBS 2008 at no additional charge for the server software component. ... What I'm trying to suggest is that managing a workgroup is a HUGE pain and completely lacks security. ...
    (microsoft.public.windows.server.general)
  • Re: Removing a workstaion from SBS Domain
    ... Simply right click on My Computer> Properties> Computer name and then click the radio button on workgroup and enter workgroup name. ... Before I removed SBS ... reformatted the server and redid the partitions. ... related stuff from the one workstation before I try a third time to ...
    (microsoft.public.windows.server.sbs)
  • POP3 connector problem
    ... I am new to running a server. ... Previously just a workgroup. ... We have 5 PC's (upgrading to XP Pro as needed) and have ... The upgrade and connection to SBS 2003 worked fine but I ...
    (microsoft.public.windows.server.sbs)