CUMC 7.1.x Presence with OCS 2007 Federation

Hi - We have a customer who is looking to use CUCIMOC (CUCM 7.1.3) on the desktop, but utilise CUMC / CUMA 7.1.x on their Blackberry devices.
Is it possible to extend the MOC Presence / IM features out to the BB CUMC 7.1.x client (and vice-versa) through an OCS > CUPS federation with CUMA?
Any thoughts appreciated.
thks
Brian

Hi
Last time I looked at this (I know Michael will be typing a more accurate response as I do this one) it had just become possible (in v7 of CUMA and CUPS) to share presence info between CUMA and CUPS (effectively CUMA lost it's presence engine and used the CUPS one), and between CUPS and OCS via federation... but the docs suggested it wasn't possible to get the presence info from OCS>CUPS>CUMA.
The other thing to consider is that federation isn't the same as having two different clients from the same vendor on your phone and desktop - for example, if it did work you would have your OCS contacts list on your desktop, and a separately managed list of federated contacts on your CUMC client. Most users would find that sort of thing clunky I suspect...
Regards
Aaron
Please rate helpful posts...

Similar Messages

How to connect Lync 2013 client with OCS 2007 R2 Edge server

Hi,
We have OCS 2007 R2 Edge server for external & OCS 2007 R2 FE Server for internal access in our environment.
We able to access internally Lync2013 clients with OCS 2007R2 server, however from external we cannot access Lync2013 client with OCS2007 R2 server.
Is there any patch or registry key trick to access OCS from lync2013 client externally? We cannot immediately migrate to Lync2013 server from OCS.
Any help
MD

Hi,
I suggest you still use OCS 2007 R2 client to login OCS 2007 R2 Server untill finishing migration to Lync Server 2013, as using Lync client with OCS 2007 R2 Server will offer a pretty limited experience.
Here is a great blog about Lync 2010 Client unsupported with OCS, it is for Lync 2010 client but similar for Lync 2013 client:
http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Webex Presence in OCS 2007 R2

We are currently using OCS in a pilot group. We want to deploy but OCS is displaying "In a WebEx meeting" when users are not in a Webex meeting. We have uninstalled the Webex productivity tools and configured them to not use IM per Cisco.
We are still getting this presence. Any help would be great.

Hi, removing following files and registries could prevent MOC from caching old status, the profile are stored at C:\Users\test\AppData\Local\Microsoft\Communicator, and registries from here: HCU\Software\Microsoft\Communicator\[email protected]
If still no luck, would you please try that sip user account on other computers?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

CUPS 6.0.6 OCS 2007 R2 RCC continuous self dialing

I have a strange issue with our COS/CUPS integration. RCC and Presence integration work fine. The problem is RCC enabled users on OCS receive missed calls from themselves every 30 minutes. If you are at the desk you will see the phone light up and a call from 'User A' to 'User A'. If you answer the call it hangs up immediatley. If you don't answer the call It goes to VM and hangs up when Unity answers. The same behavior occurs when 'User A' signs into Office Communicator.
The Real Time Trace Logs from RTMT and the OCS Trace logs don't show anything unusal but I can see the SIP Conversation taking place on sign in that sends the SIP INVITE incoming from CUPS.
Is there a 'Presence Timer' that is genereating this call? We have almost the exact same setup in the lab but can not duplicate the behavior.
Any suggestions are appreciated I am stumped.

First of all, CUPS 6.0.x does not support OCS 2007 R2. Which means:
1) This combination was not tested by Cisco. Thus unexpected behavior might be observed.
2) If you run into this problem, Cisco (TAC) won't be able to troubleshoot the problem for you (because it's not supported).
You should use CUPS 7.0.x with OCS 2007 R2.
With that said, here are something under the hood:
For MOC RCC, CUPS has to know which phone device to control. CUPS depends on the "device name" in the TEL URI to detemine which device to control.
Before the "phone selector" plug-in was introduced on CUPS 7.0.x, CUPS use a "call-back" method to detect the device. Which is: CUPS will make test calls to the devices that match the DN in the TEL URI. Whoever answered first would be the one choosen. This might be the cause of the "ghost calls".
Michael
http://htluo.blogspot.com

Re-routing Edge servers from OCS 2007 R2 to LYNC 2010

We have LYNC 2010 Enterprise pool with merged topology with OCS 2007 R2 Pool, using OCS 2007 R2 Edge servers. We would like to move onto LYNC 2013 and here i have some questions on Edge servers.
1. Once I migrate all users, can i keep OCS 2007 R2 Edge servers and decommission OCS 2007 R2 pool to setup LYNC 2013 Pool? ( we have 3 Front end servers and 3 CWA servers in OCS 2007 R2 pool).
Can i use OCS 2007 R2 edge servers for LYNC 2010 and LYNC 2013 Pools for federation and remote access?
Thanks for your help.
Tek-Nerd

I've seen OCS 2007 R2 servers work for Lync 2013 internal users with some limitations. I'm not sure what would happen if you decommission the OCS front end. However, why not upgrade the edge as well?
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Decommissioning 1st OCS 2007 R2 FE after deploying Lync 2013

Hello,
We have done a successful deployment of Lync 2013 that interoperates with OCS 2007 R2. Now we want to start decommissioning OCS 2007 R2 step by step. We have four OCS pools on different sites and I want to decommission the first OCS. 2007
r2 FE. I´ve tried to follow the deactivation order suggested by different bloggers and MS site:
http://www.ucprofessional.com/2011/04/decommisioning-ocs-2007-r2-after.html
http://technet.microsoft.com/en-us/library/dd572548%28v=office.13%29.aspx
However when I want to deactivate any service like Application Host or A\V Conferencing Server I receive the next message,
even if I have domain\enterprise admin rights as well as RTCUniversalServerAdmins membership :
Remove Active Directory Object CN=UC AppServer Services
Failure
[0x80070005] Access is denied.
Remove Active Directory Object CN=LS AV MCU
Failure
[0x80070005] Access is denied.
We have a parent root domain, and this FE is joined to one of its child domains. I still have other three pools but I don´t want to touch these other three until I can decomm this first FE and its pool. I don´t have any users in this.
How could I deactivate these services on this first FE server and have my AD clean? what might be happening that the deactivation process doesn´t do its job?
Thank you for any feedback.
MC

Is the account you used to deactivate OCS 2007 R2 Servers in root domain or child domain?
Your problem is more of a permission issue.
Try to use an account created in root domain to deactivate OCS 2007 R2 servers.
Lisa Zheng
TechNet Community Support

OCS 2007 to OCS 2007 R2

Hello world.
Doing a side by side migration from OCS 2007 to OCS 2007 R2 (due to our goofy SA agreement cannot upgrade to 2010 or Lync yet) and I am following the step by step guide here:
https://technet.microsoft.com/en-us/library/dd572505(office.13).aspx
My question is this...can I have two disparate SRV records referencing TLS...one pointed to legacy and then a new one pointed to the new server? What will happen with my clients?
This is an internal only deployment...no edge servers...no director...etc.
I have the domain prepped and when I launch setupse.exe I get all the way to the end and it rolls back because it cannot create the pool as it does not exist and there is no SRV TLS record to reference the pool.
We use OCS 2007 extensively throughout the org day and evening so I need to be able to get the new SRV records and pool inline without impacting production.
Can anyone shed some light on how I move forward? Been over the documentation and Google/Bing quite a bit and have yet to find a sufficient answer.
Thank you in advance MS community!

Hi crashIO,
No, the DNS SRV record can point only to a single pool, and in a mixed environment the supported configuration is to use Office Communications Server 2007, Director, with both Office Communications
Server 2007 and Office Communications Server 2007 R2 pools. This means that during migration, you should configure DNS records to point to the Office Communications Server 2007 Director or FE.
Before installing the OCS 2007 R2 pool, did you move your OCS Global Settings from the System Container to the Configuration Container in Active Directory.
“With Office Communications Server 2007 R2, the default container for Office Communications Server global settings is the Configuration container. In previous versions, the default container
was System container of the root domain.”
If you did not perform this step, please follow the article below to do this.
https://technet.microsoft.com/en-us/library/dd572392%28v=office.13%29.aspx
In addition, in order to co-existence with OCS 2007 R2, please ensure your OCS 2007 Servers are up-to-date.
Best regards,
Eric
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

OCS 2007 compatibility with Windows Server 2008 R2 x64

Hi, we have OCS 2007 installed on our Windows 2003 R2 Standard X64 Production Server and are moving to Windows 2008 R2 X64.
I've been looking at a few support articles out there (e.g. http://support2.microsoft.com/kb/982021) and noticed that they're saying it (is) compatible.
I would appreciate a definite answer from you experts out there on this so I'll know definitely if we can proceed with our upgrade or not.

To be clear, if this is OCS 2007 R2, then yes it will run fine on Server 2008 R2. If it's OCS 2007 (not R2), that would not be supported.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 User Presence Unknown in OCS 2007 R2 Client

Lync 2013 User Presence Unknown in OCS 2007 R2 Client
OCS users had reported that they can’t view the presence status of some Lync 2013 users in OCS client, presence unknown. I found one of FE01 server that registration for those Lync 2013 users have that effect on OCS client. I shut down FE01 server to force
Lync 2013 users to register to another FE02 server. After Lync 2013 users signed in again (Connected Lync Server has been changed to: FE02), OCS client can view their presence. However I still don't found the root cause, when I run Test-CsRegistration in both
FE server. The FE02 passed, but FE01 show the following error. I checked the same certificate was imported to FE01/FE02.
Target Fqdn   : ###########.com
Result        : Failure
Latency       : 00:00:00
Error Message : Unable to perform authentication of credentials.
                Inner Exception:NegotiateSecurityAssociation failed, error: -2146893053
Diagnosis     :
VERBOSE: Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow' started.
Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow' completed in '6.26E-05' seconds.
An exception 'Unable to perform authentication of credentials.' occurred during Workflow Microsoft.Rtc.SyntheticTransactions.Workflows.STRegisterWorkflow execution.
Exception Call Stack:    at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
   at Microsoft.Rtc.Collaboration.LocalEndpoint.EndEstablish(IAsyncResult result)
   at Microsoft.Rtc.SyntheticTransactions.Activities.RegisterActivity.InternalExecute(ActivityExecutionContext executionContext)
   at Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Execute(ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
   at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
   at System.Workflow.Runtime.Scheduler.Run()
   at Microsoft.Rtc.Internal.Sip.SipAuthenticationHelper.NegotiateSecurityAssociation(SecurityAssociationBase sa, String inputString, ContextFlags inContextAttributes, String& outputString)
   at Microsoft.Rtc.Internal.Sip.ProtocolAuth.DoProtocolOutgoingNegotiation(SecurityAssociation sa, SipMessage message, ChallengeData challengeData)
   at Microsoft.Rtc.Internal.Sip.AuthenticationControlModule.NegotiateSecurityAssociation(SecurityAssociation sa, SipMessage message, NegotiateArgs negotiateArguments)
'RegisterActivity2' sequence activity started.
'RegisterActivity2' sequence activity completed in '6.01E-05' seconds.
'Register' activity started.
Sending Registration request:
Target Fqdn      = #######.com
User Sip Address = sip:#####@####.com
Registrar Port = 0.
Authentication Type 'IWA' is selected.
'UnRegister' activity started.
'UnRegister' activity completed in '0.0004703' seconds.
VERBOSE: Workflow Instance ID '4fb4f7ee-de24-432b-b758-c4abd2010794' completed.
VERBOSE: Workflow run-time (sec): 0.2430276.
Does anyone know what does the error code 2146893053 means? Many Thanks.

Hi,
Please check if all services started on FE01.
It may cause by the issue of registrar authentication. Please also check if Registrar Setting click all authentication on FE01 Lync Server Control Panel.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Integration of Microsoft OCS 2007 with WebCenter Spaces 11G PS4

Hi All,
I want to know has anyone successfully integrate Microsoft OCS 2007 with WebCenter Spaces 11G PS4? If yes, pls share detail. Thank you.
Regards,

Hi,
I am also facing the same issue, not sure about what url to use. And also the login webservice doesn't work while I am testing using http://localhost:81/RTC/RTCService.asmx. It always throwing the following error
" Unable to cast COM object of type 'RTCLib.RTCClientClass' to interface type 'RTCLib.IRTCClient'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{07829E45-9A34-408E-A011-BDDF13487CD1}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))."
Is the current owc_lcs.zip support MS Office Communication Server 2007?
Please share the configuration step if anyone already integrated OCS 2007.
Thanks,
-Mukesh.
Edited by: user9127933 on Feb 19, 2010 4:05 AM

OCS 2007 R2 with SQL 2005 database mirroring failover?

We have OCS 2007 Enterprise Edition installed fine and with the databases mirrored to a backup server/location. I'm testing our environment for a potential disaster, including losing our primary SQL server (SQL 2005). I fail the databases over and update the backend pool to the backup SQL server name, but we cannot connect via Office Communicator and I see this error on the OCS server:
OCS User Services, error category 1006, event id 30962:
Connection to back-end database succeeded, but failed to execute registration stored procedure on the back-end. This error should not occur under normal operating conditions. Contact product support.
Back-end Server: databkp Database: rtc Sql native error: 515 Connection string of:
driver={SQL Native Client};Trusted_Connection=yes;AutoTranslate=no;server=databkp;database=rtc;
Cause: Possible issues with back-end database.
Resolution:
Ensure the back-end is functioning correctly.
Can anyone shed some light on this SQL 515 error? Thanks in advance!
-Erik

We're having a similar issue but with error number 601. I've tried a million different things aside from restoring the database, which may be next. I tried editing the procedure and I *think* I edited the right lines 77 and 105 for me. Changed:
delete dbo.DbConfigDateTime
from @DbTime as t
where dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtc'
and t.Value is null
to:
delete dbo.DbConfigDateTime
from @DbTime as t
where dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtc'
and t.Value is not null
and
delete rtcdyn.dbo.DbConfigDateTime
from @DbTime as t
where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtcdyn'
and t.Value is null
to:
delete rtcdyn.dbo.DbConfigDateTime
from @DbTime as t
where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtcdyn'
and t.Value is not null
Not sure if that's where the modification is supposed to go. Any clarity here? Anyone else get a 601 error?

OCS 2007 R2 to Lync 2013 migration – The new environment will be in a completely different forest with Lync 2013.

Hi All,
Need help - we are planning to migrate around 14000 ~ 16000 users from OCS 2007 R2 to Lync 2013 environment -
issues are - the new Lync 2013 environment will be in a new forest and sip address will not change.
Considering the same - I understand we don't have any option other than going for a cut-over.
please help me to understand how can I move the user's contact and other configurations from OCS 2007 R2 to Lync 2013.
Thanking you
Maz

Hi,
It is indeed a clean cut over. BIG BANG.
You export all users from your OCS environment. All scheduled live meetings will need to be rescheduled because Lync Server 2013 doesn't support Live Meetings anymore.
I would export, convert and import all users like this:
Dbimpexp.exe /hrxmlfile:"C:\Logs\Lync2010data.xml" /sqlserver:Sql.contoso.com\rtc
Convert-CsUserData -InputFile "C:\Logs\Lync2010data.xml" -OutputFile "C:\Logs\Lync2013Data.Zip" -TargetVersion Current
Import-CsUserData -PoolFqdn "atl-cs-001.litwareinc.com" -FileName "C:\Logs\Lync2013Data.Zip"
Don't use Import-CsUserData twice, but use Update-CsUserData the second time if needed.
Have fun!

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Migration to Lync 2013 from OCS 2007 R2 - queries

We are currently running OCS 2007 R2 across Citrix Presentation server 4.5 and Desktops using just IM functionality. We are looking to upgrade to LYNC 2013 for IM and to start using Group Chat. We currently have a Physical OCS front end server,
a physical server running SQL for the DB's and then a physical server running the Archive OCS component.
How easy is this to do? Would we keep the same Pool name?
Can the OCS client be used to connect to Lync 2013?
Can we move the physical servers into VM's? Do we need 3 or can we have all on one VM now?
The SQL DB part can this now be hosted on a stand alone SQL cluster in its own instance if required?
LYNC IM and Group Chat client - is it supported to run on Citrix Presentation server 6.5?
Is a Schema Update required?
Are there any good walk throughs on the internet just covering IM and Group chat migrations etc as from what I have been seeing there are some out there but have voice in them as well.
Thanks.

In addition, the presence and IM features in Office Communicator 2007 R2 are compatible with Lync Server 2013, but conferencing features are not. During migration from Office Communications Server 2007 R2, Office
Communicator 2007 R2 is suitable for presence and IM interoperability, but users should use Lync Web App 2013 to join Lync Server 2013 meetings.
Q: Is it supported to run on Citrix Presentation server 6.5?
A: check the official document at http://support.citrix.com/article/CTX138408
Is a Schema Update required?
Yes, schema update is required. See
http://technet.microsoft.com/en-us/library/jj205265.aspx
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Lisa Zheng
TechNet Community Support

Backing Up and Restoring Lync Server 2013/OCS 2007 R2 Co-existence Environment

Hello
I am seeking tips on how to build a replica of a Lync 2013/OCS 2007 R2 production pilot Co-existence environment in a test lab.
Lync 2013 is a standard Edition Pool
OCS 2007 R2 is an Enterprise Pool
Here is what I think...Is this feasible ? appreciate any other idea
1. Get Active Directory to Test Environment
For OCS 2007 R2 Servers
2. Use LCScmd on OCS 2007 R2 Servers to backup Global\Pool\Computer specific settings
3. Backup OCS 2007 R2 on Backend SQL Database
4. Restore data from steps 2 and 3 to equivalent servers created and prepared in test environment
For Lync 2013 SE Servers
5. Use the Lync 2013 Backup and Restore Process to bring up Lync Server 2013 into the test environment
http://technet.microsoft.com/en-us/library/hh202192.aspx
David

That should do it, as you said you'll need Active Directory as well so these accounts line up with something.
It may be easiest to restore into your virtual environment using virtual snapshots or Windows backups and fixing any corruption that may have occurred by restoring what you've backed up.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

CUMC 7.1.x Presence with OCS 2007 Federation

Similar Messages

Maybe you are looking for