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

Similar Messages

Just moved from in house ocs 2007 R2 to office 365 lync 2013, I'm clear to "unprep" right?

We've just migrated from in house ocs 2007 r2 to office 365 w lync 2013. We are using dirsync to sync our AD with o365.
We'd like to decommission our OCS 2007 server since its no longer being used. Will running unprep impact our hosted lync 2013 setup given that we are using dirsync? I don't think it should, but just want to confirm.
Any advice appreciated.

Hi MC625,
In my opinion, unprep is not necessary and I suggest you should not perform this action.
I haven't seen an unprep referenced in the migration from OCS to Lync 2013 articles.
https://technet.microsoft.com/en-us/library/jj205375%28v=ocs.15%29.aspx
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]

Can't open email items from search after installing Lync 2013 client

Hello,
We're deploying Lync 2013 in our environment.
At the moment we're using Office 2010 on the clients.
For testing the deployment I've installed the Lync 2013 client.
After installing, when I perform a search on my pc and outlook items are found, they suddenly appear with an Outlook 2013 icon.
When doubleclicking, nothing happens, neither when I rightclick.
I've checked the "associate a file type or protocol with a prgram", and "set your default programs" in the control panel.
In neither of them I can find the Outlook 2013 icon, and for email, every file type is configured to open with Outlook 2010.
Does anyone know what might be the problem. We have this problem with every user for which we install the Lync 2013 client.

You can do the following to restore functionality:
If you have office 2010 use the keys below, the Lync install will change them to Office15:
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}]
@="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-110"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\DefaultIcon]
@="@C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL,-504"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\InprocServer32]
@="C:\\Program Files\\Microsoft Office\\Office14\\MAPISHELL.DLL"
"ThreadingModel"="Apartment"
[HKEY_CLASSES_ROOT\CLSID\{138508bc-1e03-49ea-9c8f-ea9e1d05d65d}\ShellFolder]
"Attributes"=dword:20140000

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

Deploy Lync 2013 in phases

Can someone shed some light in this ? I really appreciate.
We currently have OCS 2007 (non R2), and planning to upgrade to 2013. We understand the choices of path of migration. However we want to understand if we can deploy 2013 with the the same features t we have today (IM and presence), and then add on other
features at a later stage. So this would look like this:
Phase 1: IM and presence
Phase 2: conferencing
Phase 3: AV conferencing
Phase 4: Dial-in conferencing
I understand at some point with Dial-in conferencing we have to setup FEs, so do we have to setup all the servers when we deploy in phase 1? How scalable it is if we want to expand/shrink the feature sets?
Thanks.

Hi,
Agree with Thamara.
The FE Server (or Standard Edition Server if it is Standard Edition) is the core Server roles for Lync Server 2013, and runs many basic Lync Server functions. After you install FE Server and BE Server (Standard Edition Server) and enable the related
function such as conferencing, you can use the function. IM and presence function is enable by default. If you want to use dial-in conferencing function, you need to collocate FE Server with Mediation Server or deploy Mediation Server alongside.
More details:
http://technet.microsoft.com/en-us/library/gg398536.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Deploy Lync 2013 with XML?

Lync 2013 is part of Office 2013 Pro Plus.
When I first deployed Office I never bothered with Lync... we now need it.
Same with Access.... for Access I use the following XML:
<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" /> -->
<USERNAME Value="Authorised Used" /> -->
<COMPANYNAME Value="XXX XXX" /> -->
<OptionState Id="ACCESSFiles" State="local" Children="force" /> -->
<Setting Id="SETUP_REBOOT" Value="Never" /> -->
</Configuration>
Doesnt see to work for Lync though....
In OptionState Id I've tried LyncFiles, LyncCoreFiles... but no joy.
Any ideas?

Hi Peter,
I also haven't found the OptionID for Lync, could we use the OCT to change the installation state of features instead? The equivalent option in the OCT is
Set feature installation states. And we can deploy the update via a MSP file.
Max Meng
TechNet Community Support

Deploy Lync 2013 Via SCCM 2012

Dear,
I wants to deploy Microsoft Lync 2013 via SCCM 2012, I have created a new deployment package based on MSI file to install Microsoft Lync 2013 for company machines, during the installation package will install for clients computer perfectly but instead of
install automatically to users, every time message coming user should do it manually for example user should accept the terms of the agreement, kindly I need a way to solve this issue, I need Lync 2013 automatically install without users doing anything, please
see attached snapshot.

Make sure that you are using the right command line using your newly created MSP
ex: setup.exe /adminfile "Lync_Updated.msp"
As proposed, update your DP so that your MSP gets distributed.
You can also follow this guide if you're still experiencing difficulties.
http://systemcentersynergy.com/lync-2013-silent-or-unattended-install/
Benoit Lecours | Blog: System Center Dudes

Deploying Lync 2013 client and SCCM Detection method

So I am deploying the stand alone Lync 2013 client via SCCM 2012 R2, I have used OCT to create a .MSP, and I am trying to import it into SCCM. However, I am curious as to what others are using for the Detection method? Normally I would just
use the MSI code, but since there is no single MSI, that is not possible with this particular version? I'm not sure what the best method would be, Option 1 is to find a registry key that is installed by Lync, or Option 2, use a file, maybe Lync.exe under
the Program Files?

From the testing I've done Lync creates this reg location...
HKLM>Software>Microsoft>Office>15.0>Lync
Try using one of the keys in there, or you could use the file version but not sure if this would change with updates.

No Numbers after March Lync 2013 Client update

Hi,
We have problems with the EWS sync after applying the March Lync 2013 client update. All contacts are synced from the users private contacts folder but no numbers are shown. After removing the update it is working fine again. We are not using UCS as
we are still on Exchange 2010.
Any ideas?
Kristian

I didn’t have this problem when I installed the update.
Did you download the update from
http://www.microsoft.com/en-us/download/details.aspx?id=42232 or
http://www.microsoft.com/en-us/download/details.aspx?id=42249?
Please check if this issue happens to other users.
Lisa Zheng
TechNet Community Support

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

Lync 2013 client is deployed but user accounts are not migrated from OCS to Lync 2013 Server - how to open Lync meetings automatically in the Lync Web Plug-in

We have in our enterprise the following scenario:
1 - Lync 2013 client is installed
2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
on the browser, using Lync Web Plug-in?

Thanks for the response,
First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue.

OCS to Lync 2013, move all users over before client deployed?

Hello, quick question hoping someone can answer...
We've deployed Lync 2013 and are migrating about 2000 users from OCS across many branch offices, going branch-by-branch.
Is there any downside to moving ALL 2000 users over to the Lync pool before they have the Lync client deployed to their site? They would still be using Communicator until their site receives the Lync install. I know Communicator works when connecting to
the Lync pool so I'm guessing this should be OK.
The problem we're seeing during this transition phase is when an employee travels to a site that's had Lync client deployed but the employee is still on the Communicator pool because their primary site hasn't been upgraded yet, and are thus unable to sign-in
to Lync.

I would agree with Anthony,
The basic features works with the Communicator clients but when it comes to conferencing users will face a lot of problems, also a problem as been identified during such scenario is when users homed on the lync pool and signing in using the OC client
experience a weird behavior when their contact lists disappear, then it appears again when logging using a lync client.
as a resume.
If you are obliged to use the OC client please make sure that it is patched with the latest updated released.
as a best practice move to Lync client as soon as possible.
Regards,
Charbel Hanna
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

Lync 2013 deployment via SCCM 2007

Hi All,
We are trying to deploy Lync 2013 to Windows 7 workstations that currently have Office 2013 professional installed on.
Unfortunately we arent have much luck at the moment..
It seems to push Office 2013 tools out but not Lync itself..
The package was created using the Office customisation tool
the sccm command is set to setup.exe /adminfile updates \name.msp and also tried msiexec command line but no joy
Please can someone advise me how to achieve this Lync rollout?
Kind Regards, Enjoy the weekend!
James
J R Vose

Are you using Office2013Professional (the Retail edition), or are you using Office2013ProfessionalPlus (the Volume Licensing edition)?
Or are you using Office365ProPlus (the Subscription edition of 2013, which comes in a Click-to-Run format)?
The steps may vary for you, depending upon the above.
Also, which Lync are you using for the install? (there are various ways to deploy Lync, depending upon what you have)
e.g. if you have previously deployed Office2013ProfessionalPlus, and at that time, you customised the installation such that Lync would not be enabled, and now, you wish to enable Lync, you would use the tip from Daniel, via something like this:
setup.exe /modify ProPlus /config AddLyncConfig.xml
[the AddLyncConfig.xml would be a file you create, containing the content like Daniel has suggested]
refer: https://technet.microsoft.com/en-us/library/cc178956.aspx
These steps are valid for Office2013ProfessionalPlus, but aren't valid for Office2013Professional nor for Office365ProPlus.
Ultimately, it depends whether your are "adding a new product" or are "modifying an existing product".
ConfigMgr is merely automating your instructions, it doesn't "know" if what you are telling it is "valid".
Have you tried to install/enable Lync using manual steps first as a test?
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Lync 2013 OCT deployment on machines with Office 2010. Installation Failure

Hi,
In our environment, we have Win7, Office 2010 x86. (no plans to upgrade all of Office to 2013 as yet)
I'm trying to deploy Lync 2013 x86, and have packaged an MSP using "setup /admin" for later deployment via SCCM.
Now I know there are no problems running Lync 2013 with Office 2010 as it works fine if you manually install.
Strange thing is, when I try running the setup with MSP for silent install, it runs silent and all looks well although all the Office Tools shortcuts are created and there are files under the Program Files folders for Office\15.0 as expected
but not Lync itself. ie: no lync.exe file or shortcuts.
Reviewing the setup log doesn't show any obvious errors that I can tell.
Also after this, if I go through the "Add/Remove Components" under Uninstall Programs\Lync 2013, and I can see in there that it DOES already show Lync as being installed, if I just click continue, it runs through the setup process and
then Lync will be installed
I've also tried this same process using the Full "Office Pro Plus 2013" and only select Lync to install and the same thing happens.
Has anyone else come across this issue or could point me in the right direction.
For the OCT (setup.exe /admin) the only settings I've changed from defaults are:
- Filled in the Organisation name
- Set KMS licensing, display level to none and suppress modal
- some regkeys for some default settings for GalDownloadInitialDelay, ShownFirstRunOptin
- Force on Lync (Run from My Computer)
I'm running "setup.exe /adminfile Lync_x86.MSP" in my case to test this MSP.

I had the same issue. As soon as I updated to the latest Admin admx/opal files, it worked great.
Cheers,
JeffCSP
This issue was introduced when SP1 was released, and is detailed here:
http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx
(it remains uncorrected by MSFT :(
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Client Version Policy: Upgrading from OCS R2 Phone Edition to Lync 2013

Hey, everyone!
Looking at the settings in Lync Control Panel, the default OCPhone Client Version Policy is set to block anything older than 3.5.6907.*.
Now, I have two older Polycom CX700's that are running. In order for them to receive updates from Lync Server, do I need to temporarily remove that policy? I know I need to upgrade them to 3.5.6907.* first, so I guess my question is this: is the Client Version
Policy, just for signing in or does it also pertain to which devices are allowed to get update information?
Thanks so much.
-Eric

The client policy should only prevent your phones from signing in. Your phones should update fine being blocked.
I've updated CX700's out of the box (with ancient OCS 2007R2 firmware on them) using Lync 2013 and have not had to modify the Client Version policy.
Edit: I will add that I needed to install a specific couple interim versions of the firmware before I could upgrade to the latest (OCS 2007 R2 Phone Edition 3.5.6907.222 and then Lync 2010 Phone Edition Feb 2012 4.0.7577.4066) - I blogged about it here: http://www.lynced.com.au/2013/08/getting-that-out-of-box-cx700-from-ocs.html
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Decommissioning 1st OCS 2007 R2 FE after deploying Lync 2013

Similar Messages

Maybe you are looking for