Calendar presence with CUPS and Exchange

[mannycho]

I am trying to get Calender Presence with CUPS and Exchange too work and have followed the steps carefully. The Microsoft Calender will not integrate with CUPS. I have gone through assigning the right permissions to the CUPSAdmin account for the user mail box and also CUPS has the CA Cert that issued a certificate to exchange. DNS is configured correctly for CUPS.

I get "The calender server may be down. Please make sure the server is up and running" message from the IP Phone, when logged into IPPM and select option 1 Todays Meeting.

I have attached the presence engine logs for viewing.

Cheers

[Jonathan Schulenberg · Accepted solution]

IIS is returning a 401 unauthorized message:

|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.959 EPE|system.pe.pa.owa.backend 130670 DEBUG <--CalendarSubscription::doSUBSCRIBE: cokojie@enet.com
|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.960 EPE|system.pe.pa.owa.backend 2192562 DEBUG -->QMS::SUBSCRIBE cokojie@enet.com
|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.960 EPE|system.pe.pa.owa.backend 2192562 DEBUG -->SessionManager::allocateSession cokojie@enet.com
|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.960 EPE|system.pe.pa.owa.backend 2192562 DEBUG <--SessionManager::allocateSession exchange.enet.com:443
|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.960 EPE|system.pe.pa.owa.backend 2192562 DEBUG ---->QMS::SUBSCRIBE cokojie@enet.com
|<:STANDALONECLUSTER><:CUPS><:DETAILED><:0800>
06/02/2010 21:56:13.960 EPE|system.pe.pa.owa.backend 2192562 INFO send SUBSCRIBE cokojie@enet.com 86400
|<:STANDALONECLUSTER><:CUPS><:ARBITRARY><:0800>
06/02/2010 21:56:13.966 EPE|system.pe.pa.owa.backend 2192562 INFO received SUBSCRIBE (initial) status: 401 Unauthorized
HTTP/1.1 401 Unauthorized
x-powered-by: ASP.NET
date: Thu, 03 Jun 2010 00:56:08 GMT
content-length: 1539
www-authenticate: Negotiate, NTLM, Basic realm="exchange.enet.com"
server: Microsoft-IIS/6.0
content-type: text/html

I'm not entirely clear why. If this is Exchange 2003 you should be able to test the WebDAV connection yourself. Open a browser and type https://exchange.enet.com/cakojie/calendar. Use the CUPAdmin account credentials when prompted by IIS and see what you get; presumably a 401 error. I suspect the ReceiveAs permission isn't applied properly.

[mannycho]

Hi,

I am running exchange 2007 and when i enter https://exchange.enet.com/cokojie/calender I get IIS 404 error page cannot be found. However I can access URL https://exchange.enet.com/exchnage/cokojie/calender and login with CUPSAdmin successfully

I have confirmed my permissions are set correctly for the CUPSAdmin account

[PS] C:\Documents and Settings\Administrator.ENET>([ADSI]"LDAP://CN=CUPS Admin,OU=Service Accounts,DC=ENET,DC=com").memberof
CN=Exchange View-Only Administrators,OU=Microsoft Exchange Security Groups,DC=ENET,DC=com

[PS] C:\Documents and Settings\Administrator.ENET>Get-ADPermission "First Storage Group" -user cupsadmin | Format-Table -AutoSize

Identity                     User           Deny  Inherited Rights
--------                     ----           ----  --------- ------
EXCHANGE\First Storage Group ENET\CUPSAdmin False False     Receive-As

[PS] C:\Documents and Settings\Administrator.ENET>Get-MailboxPermission cokojie -user cupsadmin | Format-Table -autosize

Identity                                         User           AccessRights IsInherited Deny
--------                                         ----           ------------ ----------- ----
ENET.com/ENET Employees/Managers/Chris E. Okojie ENET\CUPSAdmin {FullAccess} True        False

[PS] C:\Documents and Settings\Administrator.ENET>

[htluo · Accepted solution]

1) CUPS > Presence > Gateways > click on the Outlook gateway.  Make sure "Account Name" is in "domain\username" format.

2) Restart Presence Engine service.

Michael

http://htluo.blogspot.com

[mannycho]

Thanks Michael,

All working now...looking forward to reading your book that shipped this week. How did you know that not having domain/accountname was the issue, what was the clue in the presence engine logs

Cheers

cokojie

[htluo]

When you got a "401 Unauthorized" from Exchange, there are three possiblities:

1) The user does not have "Receive As" permission.

2) The user ID/password was incorrect

3) The user ID was not in the format Exchange expected.

#3 is the most popular one.  On Exchange, you may set the "default domain" for authentication.  If you didn't set it, Exchange would expect a "fully qualified username" in "domain\username" format.

Michael