To delete user
data from the
database for migrating users, you must have read/write access to the Microsoft
Microsoft server provides an administrative way to delete a user from the
Microsoft server database. However, if you delete a user from the database in
this way, the user is removed from other users’ contact lists. To prevent the
user being removed from the contact lists of other Microsoft Lync or
Communicator users, Cisco provides an alternative means of deleting
the user from the Microsoft server database.
alternative tool (DeleteAccount.exe) allows you to delete migrating
users so that availability requests for these users are later routed to
IM and Presence Service. This tool also ensures that
the deleted users are not removed from the contact list of any users that
remain on the Microsoft server. Running the Delete Account tool is the second
step in a two-step process to disable a migrating user on the Microsoft server.
The two-step process is as follows:
Microsoft server account for migrating user.
Microsoft server user data for migrating user.
After you disable the account for migrating user, wait
until the Microsoft server's LDAP changes are synchronized before proceeding
with the Delete utility. The LDAP synchronization can take up to 30 minutes.
- You can run this tool on all
supported Microsoft server platforms.
You can run
this tool on any Standard Edition server or Enterprise Edition pool.
tool has no affect on the capabilities of other Microsoft server users who are
signed into Microsoft Lync or
Communicator. However, Cisco recommends that you run this tool during
a scheduled maintenance window to reduce the load on the Microsoft server and
Active Directory system.
The Delete Account
tool reads the list of users to delete from an input file. Each line in the
input file represents a contact list owner. The contact list owner is
represented by the owner’s Microsoft server SIP URI, for example,
sip:email@example.com. The following is a sample input file:
You can create your
own input file based on the above format. however, Cisco recommends that you
use the UserList<Timestamp>.txt file as the input file for the Delete
Account tool. The
UserList<Timestamp>.txt file does not contain
any duplicate, disabled, or nonexistent users.
Running the Delete Account
Tool on Standard Edition Deployments
When deleting data
for a list of users, you must run this tool once on each Standard Edition
server. The database is coresident on the Standard Edition server.
Running the Delete Account
Tool on Enterprise Edition Deployments
deleting data for a list of users, you must run this tool once on each
Enterprise Edition pool. The Lync/OCS database instance name to which the
Microsoft server's front-end connects must be specified when running the tool.
Enterprise Edition, you must run this tool first on the back-end database
server and then on each front-end server. The Lync database instance name to
which the Lync front-end connects must be specified in both options. The name
of the database for the front-end servers is rtclocal. The default name of the
database for the back-end server is rtc, but that can be changed during system
OCS Enterprise Edition, the tool must be run on only the back-end database