What is the broken concept between OCS 2007 and lync 2013?

The span of recent projects is relatively large. This is when the ocs2007 upgraded lync 2013. The following is a record of some processes (such as the blog article "2003 to 2012.

The initial plan was to clean all ocs2007 (without R2) and start lync2013. Discuss and discuss, if the push is not clean, there will be problems with lync2013 deployment. So I thought about migrating ocs2007 to R2 and then to lync2013.

This is a very embarrassing problem!

The original ocs2007 is an enterprise edition with a back-end database. The customer is a bit embarrassed about the price of lync2013 Enterprise Edition, and the demand is not high... So... The Standard Edition cannot be added to the Enterprise Edition pool. Finally, the plan is back to the origin, and OCS is re-launched to lync.

1. OCs 2007: Search for online tutorials in the general order of deactive roles-uninstall the OCS component-unprep architecture (a ray is buried)

2. Deploying the lync2013 Standard Edition is very simple... The 51cto expert's tutorial is longer than an article. Here we only talk about a few mistakes:

Remember to add the shared folder

Rtccomponentuniversalservices

Rtchsuniversalservices

Rtcuniversalconfigreplicator

Rtcuniversalserveradmins

These four groups. (Write one for most tutorials. Add everyone full control)

The frontend pool of the Standard Edition is entered by lync2013.FQDN, YesFQDNRather than a single samaccountname (very important ).

If the media you are using is the version number shown in (as unfortunate as me, it takes most of the time to download it ), manually edit and replace the sqlexpress installation file in the setup folder (download another file )... Otherwise, sqlinstancertc installation fails and an error is reported.

650) This. width = 650; "src =" http://ww2.sinaimg.cn/large/5e164d27gw1ehxe38ztwoj20ls09r0vg.jpg "alt =" 5e164d27gw1ehxe38ztwoj20ls09r0vg.jpg "/>

3. After the installation is complete, the problem arises... I don't have it here, just describe it out of thin air:

All the SIP attributes of original OCs users are retained. Open the control panel of lync2013-user-LDAP search-search, and you can see that all OCs users are recognized as office communication server pool users, that is, legacyuser. If you want to move the selected users to the new lync2013 front-end pool by executing "Move the selected users to the pool", an error is certainly returned, the first error is that you have to install a backward compatible component ocswmibc. msi, this component is used for migration...

After the installation is complete, execute this operation to get a further error: "The valid value of the global meeting policy cannot be found". At this time, the OCS server has been deleted... There is no place to run the import configuration of import-cslegacyconfiguration.

Later, I chose an option... Then enable the user and click search ...... These users are no longer recognized as legacyuser. You can set and enable the SIP type through the normal process.

Of course, Domain Admins users must use enable-csuser and disable-csuser.

650) This. width = 650; "Title =" clip_image002 "style =" border-top: 0px; border-Right: 0px; Background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; padding-Right: 0px; "Border =" 0 "alt =" clip_image002 "src =" http://img1.51cto.com/attachment/201407/1/8850288_1404233292cE27.jpg "Height =" 326 "/>

4. Later I thought that the old sip attribute was still playing a strange role. Why didn't I delete it? I just went through Microsoft's documents...

Http://technet.microsoft.com/zh-cn/library/bb936625 (office.12). aspx

Of course, the ocs2007 document structure is so bad that I don't want to talk about it... (Lync2013 is also bad... Is it recommended to read the CHM version of microsoftlyncserver2013documentationhelpfile?

There is such a section in the middle:

Disable sip-enabled users:

You can obtain a list of SIP-enabled users, using the ldifde.exe to create the list. for more information about the ldifde.exe tool, see using ldifde to import and export directory objects to Active Directory at http://r.office.microsoft.com/r/rlidOCS? Clid = 1033 & p1 = kb237677.

To use the ldifde.exe to disable sip-enabled users, run the following command from the command prompt:

Ldifde-d "ou = users 'Ou, Dc = domain, Dc = dom"-l msrtcsip-userenabled: True-F sipenabledusers.txt

If sip-enabled users are in more than one organizational unit (OU), run the command for each ou.

Open Office Communications Server 2007.

In the console tree, delete users from the Standard Edition server or enterprise pool by expanding the forest, and then doing the following:

For an enterprise pool, expand enterprise pools, expand the pool name, Click Users, right-click users, and then click Delete users to start the delete Office Communications Server users wizard.

For a Standard Edition server, expand Standard Edition servers, expand the pool name of the Standard Edition server, right-click users, and then click Delete users to start the delete Office Communications Server users wizard.

Complete the Wizard to delete all users of the Standard Edition server, verifying on the delete operations status page that the deletions succeeded.

In the console tree, right-click users, click Refresh, and then verify that no users are listed in the details pane.

After reading it, I couldn't help but scold fxxk... The document even writes how to query all sipenabledusers (I ran to find the powershell export method before ), then, you need to manually delete all OCs users on the console before uninstalling all OCs components ...... In this way, lync2013 can be deployed in a completely clean environment. I read the domestic uninstall documentation I found on the Internet and thought it would take for granted that, since you have all unprep architectures, The msrtcsip architecture is definitely gone... Result ......

So it's impossible to take it for granted without detours... In the future, we will continue to repeat the document and perform more tests.

This article is from the "castelomei rainy season" blog, please be sure to keep this source http://sodaxu.blog.51cto.com/8850288/1433326