Archive for March, 2011


After installing any of OCS 2007 R2 Cumulative updates the front end service does not start up throwing the below error

untitled

This happens if you don’t install the DB2009-update.msi before running the updates.

So what you need to do is grab the update from here 

Then install it by opening up CMD and type DB2009-update.msi poolname=”your ocs pool”

Your OCS poolname doesn’t need to be FQDN

After applying the DB update, your service will start again Smile

As some of you might know already that whenever you are asked to create a another Replica for your current file server in another location, DFS comes in mind

Now the very first step in implementing DFS is mirroring your shares on a new given server.. cool, so how do we do that.

Well, thinking about it .. this is achievable through various methods

1- FSMT – Microsoft File server migration tool

2- Combination of Xcopy or Robocopy and a REGISTRY mod Winking smile

Now here I am gonna talk about the second method which I personally used a lot

So in short here is what you need to do

1- Robocopy the folder structure from the old server to the new server using the below command

robocopy “c:\test” “\\newfileserver\c$” /MIR /E /F /XF *

 image

Where the S is your Source and D is the Destination

This will copy the whole structure to the new server without the files hence the /XF * –> Exclude all files

Now that we are done lets move on to the shares

2- Using article 125996, all you need to do is to actually copy a registry key from your old server to the new server

  1. On the existing Windows installation that contains the share names and permissions that you want to save, start Registry Editor (Regedt32.exe).
  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

    SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

  3. Save or export the registry key.
    • For Windows NT and Windows 2000, click Save Key on the Registry menu.
    • For Windows Server 2003, click Export on the File menu.
  4. Type a new file name (a file extension is not necessary), and then save the file to a floppy disk.
  5. Reinstall Windows.
  6. Run Registry Editor (Regedt32.exe).
  7. From the HKEY_LOCAL_MACHINE subtree, go to the following key:

    SYSTEM\CurrentControlSet\Services\LanmanServer\Shares

  8. Restore or import the registry key.
    • For Windows NT and Windows 2000, click Restore on the Registry menu.
    • For Windows Server 2003, click Import on the File menu.
  9. Type the path and file name of the file that you saved in steps 3 and 4.
    Caution This step overrides the shares that already exist on the Windows computer with the share names and permissions that exist in the file you are restoring. You are warned about this before you restore the key.
  10. Restart the server.

 

Doing the above, you are fully prepared to start configuring DFS to replicate the same files  between two or more servers.

Well I have been facing this issue, banging my head here and there.

When the call is made from a wireless phone registered on the SSIP server to either OCS or PSTN, the call goes through.

Now the issue was when you call the user on the wireless phone it would get User Busy always.

Strange enough I couldn’t find any logs anywhere on why this is happening, but on the NET SSIP Server looking at the logs I saw it trying to dial a +1555xxxxxxx number before the call and getting a 403 Forbidden.

martSIPServerManager> SmartSIP:Information(4):Handling OCS call for registered endpoint>>>>>>>
Message #324: <<<<<<Event received at: (3/10/2011 11:05:19 AM) <ECSmartSIPServerManager> SmartSIP:Information(4):User call 8a0a83fa00 received for sip:ocstest@xxx.com from sip:xxx@xxx.com  Toast is: >>>>>>>
Message #325: <<<<<<Event received at: (3/10/2011 11:05:19 AM) <ECSmartSIPServerManager> SmartSIP:Information(4):Initiating B2B call. Target-to-dial:
tel:+15551184178>>>>>>>
Message #326: <<<<<<Event received at: (3/10/2011 11:05:19 AM) <ECSmartSIPServerManager> SmartSIP:Error(2):Back to back call failure : 403 : Forbidden>>>>>>>

so mmmm, let’s match this against the Normalization rules … and it turns out its matching to International Dialing.

Hang on a sec, my user cant dial internationally.

The moment I gave the user international dialing privileges, BAM the phone starts ringing and happy days.

All I did after that was to create a specific rule to match +1555 and assigned it to all my policies

image

I hope this helps someone Open-mouthed smile

Lync 2010 IM Archive Report

A lot of people would like a neat and easy way to extract IM conversation archive. So I have modified the attached report file that you add to the SQL reporting to get the following view

You will need to run the following on the Reporting Server

Installation

  1. Download the latest version of the OCSArchivingReport.  (The latest version is attached as a download to this post.)
  2. Open Report Manager – http(s)://<SRS Server>/Reports
  3. Click on New Folder
  4. Give the folder a name – i.e. OCSArchivingReport
  5. Click OK
  6. Click on the folder you just created
  7. Click on Upload File
  8. Browse to the location where you downloaded OCSArchivingReport.rdl and select the file
  9. Click OK to upload the report
  10. Click on New Data Source
  11. Enter LcsLog for the Data Source name
  12. Enter Data Source=<SQL Servername>;Initial Catalog=LcsLogfor the Connection String
    1. Replace <SQL Servername> with your SQL server\instance
  13. Select the Windows integrated security radio button
  14. Click OK
  15. Click on OCSArchivingReport
    1. You will see the following error: The report server cannot process this report. The data source connection information has been deleted. (rsInvalidDataSourceReference).  This is normal, since we haven’t linked the report to the data source we just created.
  16. Click on the Properties tab
  17. Click on Data Sources in the left-hand column
  18. Make sure A shared data source radio button is selected
  19. Click the Browse button
  20. Expand OCSArchivingReport and click on LcsLog
  21. Click OK
  22. Click Apply

This is just a modded version of the original report here http://blogs.technet.com/b/dodeitte/archive/2010/02/19/ocs-archiving-report-released.aspx

Big thank to my Colleague AMR Khalil for helping me out modding and testing that.

Download the Report.. Please modify the extension to remove PDF

LyncArchivingReport.rdl

You can also now download it from my BOX on the right side