Office Communications Server
27 March 2009, 02:05 PM
#1
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Perth, Western Australia
Posts: 1,866
Likes: 0
Received 0 Likes
on
0 Posts
Office Communications Server
I've been asked to set up this up as a POC but don't have the time to wade through a small forest's worth of documentation. This POC only needs IM, presence and federation setting up so I have an OCS standard edition and an edge server installed. I can IM within the local network OK but I'm starting to struggle with using communicator from the internet. Has anyone done this? Looks like I've got to get an SSL cert registered as well as a domain name (our lab setup thus far has needed neither). How many static IPs do I need to get this to work? I think a minimum of 2, one for edge server and one for the reverse proxy. Have I missed anything?
Thanks in advance.
Mark
Thanks in advance.
Mark
27 March 2009, 02:16 PM
#2
Scooby Regular
you can create your own self signed cert in IIS for testing purposes
it an MS command line tool SelfSSL.exe
also not sure whether you have had a look at the OCS planning tool
it an MS command line tool SelfSSL.exe
also not sure whether you have had a look at the OCS planning tool
28 March 2009, 05:34 AM
#3
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Perth, Western Australia
Posts: 1,866
Likes: 0
Received 0 Likes
on
0 Posts
Yeah, had a run through with the edge planning tool for OCS since I posted. Recommendations include SSL certs from Verisign or similar (thanks for the tip for testing though) and static IP addresses for at least the edge server and reverse proxy. More needed if using A/V etc.
My next immediate hurdle is sorting the domain name and certs. Easy you'd think but I see a ball of red tape and bullcrap trying to get approval from those above. Might just sort it myself and expense and sod the consequences...
My next immediate hurdle is sorting the domain name and certs. Easy you'd think but I see a ball of red tape and bullcrap trying to get approval from those above. Might just sort it myself and expense and sod the consequences...
28 March 2009, 09:40 AM
#4
Scooby Regular
the two functions that ssl certs provide are
1. to encrypt traffic
2. ensure the identity of the remote computer
in your scenario, you know the identity of the remote computer i.e. its your OCS edge server and presumably you "trust" it
the only reason for using commercial SSL certs is that the the root certs (i,.e. trusting certs) are pre loaded on the client OS
it's perfectly OK to use self signed certs for modest deployments, both POC and production
1. to encrypt traffic
2. ensure the identity of the remote computer
in your scenario, you know the identity of the remote computer i.e. its your OCS edge server and presumably you "trust" it
the only reason for using commercial SSL certs is that the the root certs (i,.e. trusting certs) are pre loaded on the client OS
it's perfectly OK to use self signed certs for modest deployments, both POC and production
31 March 2009, 11:22 AM
#6
Scooby Regular
Thread Starter
Join Date: Jun 2002
Location: Perth, Western Australia
Posts: 1,866
Likes: 0
Received 0 Likes
on
0 Posts
Thread
Thread Starter
Forum
Replies
Last Post
BlueBlobZA
Member's Gallery
30
25 July 2016 09:14 AM