Happy Friday everyone.
I am in a quandary:
My client is splitting two division into separate companies. One will stay in it's original Forrest/Domain and utilize it's current services. The other will move to a newly created Forrest/Domain with newly minted services. As you may have surmised, Lync 2010 is one of these services. After the users are brought online in the new AD, we will be adding them to the new Lync 2010 system.
One a the Project Requirements is to provide certain VPN users the ability to use IM & Presence with having the Lync Client Application installed on their computers. This requirement was provided using the OCS Web Communicator.
As has become apparent to me, the "Web Communicator" was decommission with the release of Lync 2010 Server. Instead this functionality was made to integrate into Exchange OWA.
At this juncture, the email services will remain in the original AD until the final email service rollout is complete. So, at least for the time being, Exchange OWA with Lync integration is NOT an available option.
OCS has never been installed in this new Forrest/Domain. A functioning production Lync 2010 environment already resides in the domain. My understanding is that without a previous OCS Installation, or at least the AD Schema Extension for OCS, the "OCS Web Communicator" role cannot be introduced to service the new Lync Clients.
>>>-----> I am trying to determine if there is a third party solution out there that can be introduced in order to provide a similar environment as the Web Communicator offered?
Any assistance, ideas, or pointers would be greatly apprec
Other recent topics
