Category Archives: OCS & Lync

Moving Orphaned Users from OCS 2007 “2007 R2” to Lync 2010 Pool

Howdy ;


It might happen that you installed lync 2010 pool in enviroment that you still have the OCS 2007 server pool functioning.Suddenly you decided to decommission and totally remove the OCS pool, while you still have users that are not enabled for neither ocs 2007 nor lync 2010 pool. You open the lync 2010 control panel then you search for those users and try to enable them oooops you got the below error.


Screenshot (2)



ok that’s fine, then you decide to use the enablecs user command using the lync powershell command tool, and now you get the following error “Can not Move Legacy user in enable operation”.

ok here is what you have to do  open up adsiedit.msc, navigate to the user’s object, open the properties, and removing or setting the following attributes to “<not set>” and “0”:

    1. msRTCSIP-ArchivingEnabled
    2. msRTCSIP-FederationEnabled
    3. msRTCSIP-InternetAccessEnabled
    4. msRTCSIP-OptionFlags
    5. msRTCSIP-PrimaryHomeServer
    6. msRTCSIP-PrimaryUserAddress
    7. msRTCSIP-UserEnabled


see image below:


Screenshot (5)



after doing so go and run the following command:



Enable-CsUser -Identity "Pilar Ackerman" -RegistrarPool "" -SipAddress "" 






OCS 2007 The sign in address was not found

While searching for the above specified error i have come to many sites that describe the same problem and suggest many solutions.Here in this post i will try to publish what was the solution that works for me.


in my very specific situation the error was originating from user that his sip address was in a domain different than the domain we installed office communicator pool on it but in a domain that is trusted by the OCS server domain.

when i started the troubleshooting i took a look at the event viewer on the OCS server and discovered that there was alot of information with event ID “User Replicator connected to domain controller in domain to perform synchronization” and when i tried to enable a user for OCS communication in the domain it didn’t work. Further troubleshooting leads me to open the resource database table in the “RTC” database and query the users in the tables to see if the user gets created, here also the results was negative. After some researches i tried to re-prepare the domain for the OCS server by using the command “LCSCmd.exe / /Action:DomainPrep” and then recheck the status by using the command “LCSCmd.exe / /Action:CheckDomainPrepState” after initiating this command the users got created immediately in the OCS database and the problem was resolved.

Moving the OCS 2007 Databases to a new SQL 2005 Server

***Update – I’ve tested this process with OCS 2007 R2 as well and it works as expected.  The only difference is that you need to repeat the backup/restore processes on the acddyn and rtcab databases.***

In this post I’ll go over the relatively easy process of moving the OCS databases from one SQL 2005 server to another using only SQL Management Studio.  Of course there are many options for how you perform backups and restores, but given the small size of the core OCS databases I find that it’s usually fastest to use the built in tools.  The entire process usually takes under 15 minutes.

Before you begin, stop all the OCS services on all servers in the pool.  Now you are ready to take a backup of your existing rtc, rtconfig, and rtcdyn databases.  To do so, open SQL Management Studio, right click on the database you wish to backup, and select Tasks/Backup:


 You will be presented with some backup options:


 All you need to do here is note the file location of the .bak file (or change it to a location of your choosing) then click OK.  This will start the backup and the circle in the bottom left will show the backup progress.  You will need to perform these steps on the rtc, rtcconfig, and rtcdyn databases.  When you are done you can either copy the .bak files to the new server or note the location and access them via \\servername\share\location from the new SQL server.

Next you must restore the databases to the new SQL server.  On the new SQL server right click Databases and select Restore Database:


Read more »