Lync Server 2013 Now Supported on Windows Server 2012 R2
With the release of the Updates for Lync Server 2013: October 2013, Lync Server 2013 is now supported on Windows Server 2012 R2.
More Information Here:
http://blogs.technet.com/b/dodeitte/archive/2013/10/25/lync-server-2013-now-supported-on-windows-server-2012-r2.aspx
Background
The Lync client integrates with Exchange Server to enable many features in the Lync Client. Having both Lync Server and Exchange server really enables Unified Communications. Based on the Exchange version you have different integration options. Here are some examples of those integrations that only work when Exchange Webservices are discoverable and configured in Exchange: Contact Information, Calendar Information, Conversation History, Missed Conversations, Missed Calls, Voice Mail Playback, Unified Contact Store, High Resolution Photo’s, …
While this is great there is a difference in how Lync connects to Exchange compared to Outlook.
Problem
When customers want to add Lync to their application stack we have to make sure that the Exchange Autodiscover process works as expected. Unfortunately Outlook and Lync do not use the same process to discover the Exchange Web Services when connecting from the Local Area Network (LAN). Most customers don’t implement the Exchange Autodiscover process correctly.
Outlook checks the Service Connection Point (SCP) in Active Directory first and uses this information to connect to the Exchange CAS Server, using this method there is a side effect that because it is an Authoritative Source for Exchange connectivity and the client will not prompt for any Certificates issues (by default Exchange uses a Self Signed certificate for the Web Services which you should change as soon as possible)
Now adding Lync at the Customer puts some other requirements for the Exchange Autodiscover process. The Lync client does not query the Service Connection Point (SCP) in Active Directory as outlined in the drawing below.
Autodiscover Process for Exchange Web Services by Lync (in specified order)
1. https://<smtpdomain>/autodiscover/autodiscover.xml
2. https://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml
3. http://AutoDiscover.<smtpdomain> /Autodiscover/Autodiscover.xml
4. _autodiscover._tcp.<smtpdomain> (Autodiscover DNS SRV Record)
Impact
Because the Lync client only uses DNS to discover the Exchange Web Services and Outlook does not (internally) most customers have to change their Exchange configuration. While most Admins do not configure Exchange Web Services correctly because not required by Outlook they have to reconfigure the environment for Lync.
Solution
Have the Exchange Admins configure the Exchange Autodiscover process correctly, not only for Outlook but also for the Lync client
Reconfiguring Exchange involves a lot of steps; Changing Certificates, Changing DNS entries, Changing Exchange Configuration … This is not something the Exchange Admin wants to do often and must be planned thoroughly.
Workaround
A workaround exists to configure both Outlook & Lync client to dismiss Certificate Warnings if DNS entries are added for Exchange Autodiscover and Certificates/Configuration cannot be changed on Exchange.
The workaround is configuring both clients by GPO with specific registry entries to disable the Certificate Popups.
While this is not an ideal solution it does work.
Personal Thought
Microsoft should make the Exchange Autodiscovery process transparent for both Outlook & Lync.
Either make the DNS Entries mandatory or have Lync query the Service Connection Point in AD
More Information: Understanding and Troubleshooting Microsoft Exchange Server Integration
This document introduces you to some of the new client features that are available whenever Microsoft Lync Server 2010 communications software is integrated with Microsoft Exchange Server 2010.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=15668
Do you really, really want to learn Lync in-depth?
Then get your popcorn and cafeïne drinks ready for more than 80 hours of free, great-quality video training materials on Lync 2013!
Most them are available for some time but thought it was interesting to bundle them all in an overview.
Lync 2013 Ignite Training on Channel 9 (11hrs)
The Lync 2013 Ignite series gives you the critical information you need to successfully deploy and support Lync 2013 in your business.
Core Solutions of Microsoft Lync Server (11+hrs)
This is a two-day, demo-rich Jump Start aimed at helping IT Pros plan and design a Lync Server 2013 implementation that meets organizational and user needs. Brian Ricks, Unified Communications Architect from BriComp and by Microsoft Senior Consultant Aaron Steele provide a fast-paced and engaging learning experience packed with a variety of scenario-based demos focused on Lync Server 2013. Additionally, this course follows the criteria for exam 70-336 and provides accelerated preparation for this important exam in the MCSE: Communication track.
Enterprise Voice and Online Services with Lync Server 2013 (10hrs)
View this two-day, demo-rich Jump Start aimed at helping IT Pros design and configure Enterprise Voice and Online Services in Microsoft Lync Server 2013. Brian Ricks, Unified Communications Architect from BriComp and Microsoft Principal Writer Rui Maximo provide a fast-paced and engaging learning experience packed with a variety of scenario-based demos focused on configuring and managing a Lync Server 2013 on premises, in the cloud or in a mixed deployment. Additionally, this course follows the criteria for exam 70-337 and provides accelerated preparation for this important exam in the MCSE: Communication track.
Lync Developer Roundtable SDK Trainings (10hrs)
Various Video Training on developing for Lync
TechEd 2013 Europe Lync Sessions (17+hrs)
All Lync related sessions on TechEd Europe 2013
TechEd 2013 North America Lync Sessions (22+hrs)
All Lync related sessions on TechEd North America 2013
Have fun (and just a very little bit of sleep!!)
Microsoft released an out-of-band Security Advisory (2896666) today for an exploit that could allow remote code Execution. It is currently actively used in the wild but mostly in Asia (based on reports).
Due to a vulnerability in the GDI library, which is used by Office and all Lync versions, a hacker could use a specially crafted Word Document to gain Remote Code Execution access to a machine running the affected software.
A patch does not yet exist, but a workaround is available by disabling the TIFF codec in registry:
To disable the TIFF codec:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Gdiplus
DisableTIFFCodec
More information: Security Advisory (2896666)
In general Lync is a very secure communication platform and this vulnerability requires uses interaction to be exploited. The exploit is not found in core Lync application code but in a library that is used by Lync. It is not the first time that vulnerabilites are found in the GDI library, as you can see here: MS07-046MS08-021
Update: Microsoft provided more information in this blog post and stated that so far Lync has not been targeted for exploit .
OfficeMaster Gate (Virtual Edition) from Ferrari electronic AG is now qualified as a Session Border Controller for Microsoft Lync Server 2013!
http://ucblog.deutinger.de/?p=321
What is a Session Border Controller (SBC) and Do I Need It?
http://blogs.technet.com/b/nexthop/archive/2013/07/08/what-is-a-session-border-controller-and-do-i-need-it.aspx
More information
Infrastructure qualified for Microsoft Lync (Session Border Controllers)
http://technet.microsoft.com/en-us/lync/gg131938.aspx
Ferrari electronic AG OfficeMaster Gate (Virtual Edition) SBC v4.0-5
Don't cry victory too soon as this is a very limited troubleshooting tool...
If you need to do real troubleshooting then the Client Logs and Snooper & Fiddler are still your friend.
Tyring to log into an un existing account just to try out the new Log option for Sign-In issues
We get a default message box saying “Can’t sign in to Lync”
Right-Click the Lync Icon in the Taskbar and Select “Sign-in Logs”
You will find some more detailed information in here
While there is more information available then before, this could be much better, it would be nice to clean up to have a more user friendly Sign-In log
The Lync client would not load the Powerpoint presentation before the Office Web Apps Update
After the update has been installed on the Office Web Apps server it works like a charm.
Screenshot with Windows version
Description of the Office Web Apps Server 2013 update 2837634: November 12, 2013
http://support.microsoft.com/kb/2837634/en-us
This update provides the latest fixes for Office Web Apps Server 2013. It also includes stability and performance improvements.
Note: It does not really say too much but it does fix the issue for Lync Powerpoint Sharing on Windows 8.1
Important: Don't forget to update according to this Microsoft article
Apply software updates to Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj966220.aspx
Take control of shared screens or apps During a Lync Meeting with app sharing or screen sharing, take control of the sharing started by someone else in the meeting.
Take control of app and screen sharing
Run Lync side-by-side with another app at any window size Use apps side-by-side when you need to reference another app or website while using Lync. You aren’t limited to the old 320 pixel snapped size; you can make the Lync window any size you want.
Lync side-by-side with Excel
Answer audio and video calls on the lock screen Answer audio and video calls quickly when your device is locked, without having to unlock it.
Answer calls on lock screen
Mute and Control Call Volume from inside Lync Mute the speakers orcontrol the volume of your call from the conversation window without affecting your Windows speaker volume.
Mute or control the volume of your conversation
In-app contact search Find your contacts faster, with a simple, in-app contact search.
In-app search
Sign in reliably This update includes a number of improvements to the sign in experience so that you can more easily connect and stay connected.
More information at the Lync Team Blog
New Lync app for Windows 8.1 now available
http://blogs.technet.com/b/lync/archive/2013/12/03/new-lync-app-for-windows-8-1-now-available.aspx
Microsoft has updated the Update Resources landing page. It now has all downloads and updates nicely grouped together and even more you can select everything from OCS 2007 R2 to Lync 2013. Nicely done Microsoft 
Lync downloads and updates
http://technet.microsoft.com/en-us/lync/dn146015.aspx
Please join us in congratulating Ruben for being awarded earlier today his first time as a Lync MVP. Ruben's always been a valuable member of this crew and I'm glad to see that his commitment and efforts have been picked up and recognized! I'm sure that we’ll see plenty more of great content from him in the next year(s)!
In case you’re not following Ruben on twitter, here’s his handle: @rnauwelaers
Ruben, once more: congrats! Well deserved.
Your Pro-Exchange colleagues,
Johan, Tonino, Michael, Koen and Wim
Response Groups Service (RGS) is a built-in Lync Server application for automated call flows based on templates or custom designed PowerShell scripts.
Despite it's good integration and decent amount of features, I believe it has a wide margin for improvement. (Take a look at Lync Ideascale and you can see that with 95 votes it's currently the most requested improvement for Lync)
That being said, today I got the following error when adding an existing Agent to an existing Agent group:
After a restart of the RGS Windows Service I also found Event ID 31137 and 31138 from LS Response Group Service stating that it could not find an agent with SIP address XXXX:
Why does this happen? I knew that the SIP address of the Lync user has been changed after a SIP Domain change .
To explain what is happening here, we have to dig into some RGS internals and explain some basics:
A Lync user is considered a RGS Group Agent when he is added to at least one Agent Group, but he can also be a member of many. An administrator can assign a user to an Agent Group using PowerShell or Lync Control Panel.
Now let's have a look how RGS handles this internally.
The RGS application has two specific databases: rgsconfig and rgsdyn:
The rgsconfig database contains the RGS configuration while rgsdyn contains "dynamic" data like current signed in agents and instances.
Within the rgsconfig database we will find a table called Agents:
The Agents table has the following structure:
In troubleshooting this issue the following 3 fields are important:
Internally RGS works with the ID field when mapping Agent Groups to Agents as you can see in the table AgentGroupsToAgentsMap):
When adding a user to an Agent Group, the Response Group service will check if the user already exists. The key for our problem is how RGS performs this lookup: based on what information?
After studying it's behavior we can only conclude it does this based on the user SIP Address:
We now found the root cause for the error 
Before changing the SIP Address of a user, remove the user from all Agent Groups he's currently assigned to (as described in KB2393943).
Then, add the user with his new SIP Address back to the Agent Groups.
Sounds like great fun if you ever need to change SIP domain and have 50 agents, right?
Disclaimer: editing a Lync database table is unsupported. You'll do this at your own risk/responsibility
Use SQL Management studio to update the user SIP Address in the Agents table. To edit a few rows you can use the "Edit Top 200 Rows" menu item on the table property menu:
You can then look for the agent record and then change the SIP Address field to the new SIP Address. I would recommend restarting the RGS Windows Service afterwards.
Feel free to post any feedback, cheers
Lync Server 2013 Cumulative Update KB 2809243
http://www.microsoft.com/en-us/download/details.aspx?id=36820
2912334 Event ID 57006 is logged when you cannot restart the Lync Server 2013 front-end service
2912338 Can't call Enterprise Voice-enabled users when the users have the same main telephone number in a Lync Server 2013 environment
2912340 An external call is routed based on Location-Based Routing that is configured for internal AD sites in a Lync Server 2013 environment
2912342 Lync Server 2013 supports TDE in SQL Server 2008 or a later version on a back-end server
2912343 Event ID 1001 is logged when the RTCSrv.exe progress crashes on a Lync Server 2013 Edge server
Lync Server 2013 Debugging Tools
http://www.microsoft.com/en-us/download/details.aspx?id=35453
The cumulative update improves the reliability, stability, and performance of Lync Server 2013, Snooper
Lync Server 2013 Resource Kit Tools
http://www.microsoft.com/en-us/download/details.aspx?id=36821
The cumulative update improves the reliability, stability, and performance of Lync Server 2013, Resource Kit Tools
Lync Phone Edition (for Aastra 6721ip and Aastra 6725ip) | 4.0.7577.4420 | |
Lync Phone Edition (for HP 4110 and HP 4120) | 4.0.7577.4420 | |
Lync Phone Edition (for Polycom CX500, Polycom CX600, and Polycom CX3000) | 4.0.7577.4420 | |
Lync Phone Edition (for Polycom CX700 and LG-Nortel IP Phone 8540) | 4.0.7577.4420 |
This cumulative update resolves the following issues:
2918039 Voice is distorted when you resume a call from hold by using Lync Phone Edition for Aries telephone
2918044 Exchange integration fails in Lync Phone Edition when an Exchange mailbox is enabled for the Exchange Online service
Today I was working on a customer environment where external users had issues retrieving PowerPoint presentations during conferences.
When joining a conference with PowerPoint content, users get presented with an empty slide and a slide counter:
After around 2 minutes this was replaced by the famous error "Either the network connection has been lost or the server is busy. Please check your network connection":
In this case the Office Web Apps server was published by the still supported but already retired TMG 2010 Reverse Proxy. The same issue could also occur with a different brand/type of Reverse Proxy in case it applies some filtering techniques on HTTP traffic.
While capturing logs during a PowerPoint sharing session following Denied message was found "Blocked By HTTP Security Filter: URL Normalization was not complete after one pass"
This can be solved by changing some HTTP filtering options on the HTTP Publishing rule used for publishing Office Web Apps:
PowerPoint presentations for external users will now work.
Without any apparent reason the Lync hybrid deployment with Office 365 (aka Split Domain) stopped working correctly. The experience fluctuates and can be corrected by restarting the RTC Service on the EDGE Server but that does not last for long. (usually within the same day the issue returns) Obviously we want to have a stable environment and don’t want to restart services every day.
Issue:
Routing problem to Office 365 from On-Prem EDGE
ms-diagnostics: 1017;reason="Cannot route From and To domains in this combination";cause="Possible server configuration issue";summary="The domain of the message that corresponds to remote peer (external) is not shared between local and remote deployments";external-domain="domain.com";external-type="domain-type-local";internal-domain="domain.com";internal-type="domain-type-local";source="sip.domain.com"
Presence cannot be updated and no other communication is possible with the Lync Online user
Temporary solution:
Restart RTC Service on On-Prem EDGE Server and things work again for a while.
The difference is obvious when you look at the SUBSCRIBE messages when it works and when it is broken are very different:
Does not work then this is the SUBSCRIBE message :
Start-Line: SUBSCRIBE sip:lync.eight@domain.comSIP/2.0
When it works this is the SUBSCRIBE message :
Start-Line: SUBSCRIBE sip:sippooldb30e06.infra.lync.com:5061;transport=tls;ms-fe=DB30E06FES04.infra.lync.comSIP/2.0
Solution:
Updating the On-Prem EDGE Server to Lync Server 2013 Cumulative Update January 2014 does seem to make it better but only makes the time it works longer but eventually also fails with the same problems.
Updating both On-Prem EDGE Server and Front-End Pool with Cumulative Update January 2014 seems to fix the Split Domain Setup with Office 365 (at least for what we have been able to test and I will update when there is more news)
So Update all your Lync Server ASAP to the latest Lync Server 2013 Cumulative Update January 2014. (no information yet if Lync 2010 updates are required)
Get the Lync Server 2013 Cumulative Update January 2014 here
http://www.pro-lync.be/blogs/lync2013/archive/2014/01/09/lync-server-2013-client-amp-tools-cumulative-update-released-january-2014.aspx
Today Microsoft shipped an update to the Lync Connectivity Analyzer, adding welcome support for Office 365 accounts and fixing a crash I reported earlier regarding a .NET framework security update.
Complete list of changes:
• A fix to the bug that made it crash on Windows 8.1
• Support for Office 365 accounts
• Accessibility support
• Bug fixes
Announcement on official Lync blog
Download 32-bit Download 64-bit
http://www.windowsphone.com/en-us/store/app/lync-2013/d85d8a57-0f61-4ff3-a0f4-444e131d8491
Lync 2013 for Windows Phone extends the power of Lync to your mobile device – including voice & video over wireless, rich presence, instant messaging, conferencing, and calling features from a single, easy-to-use interface.
Key Features:
modalities
What’s new in version 5.3:
https://itunes.apple.com/us/app/microsoft-lync-2013-for-iphone/id605841731?mt=8
Lync 2013 for iPhone extends the power of Lync to your mobile device – including voice & video over wireless, rich presence, instant messaging, conferencing, and calling features from a single, easy-to-use interface.
Key Features:
Anyone can use the Lync Mobile app when invited to a Lync 2013 meeting. However, you must have a Lync account in order to use (and enjoy) the full capability of the Lync Mobile app. Also, some functionality might require an update to Lync Server or might not be available to all users. If you’re not sure about your account status, please contact your IT department.
What's New in Version 5.3
https://itunes.apple.com/us/app/microsoft-lync-2013-for-ipad/id605608899?mt=8
Lync 2013 for iPad extends the power of Lync to your mobile device – including voice & video over wireless, rich presence, instant messaging, conferencing, and calling features from a single, easy-to-use interface.
Key Features:
Anyone can use the Lync Mobile app when invited to a Lync 2013 meeting. However, you must have a Lync account in order to use (and enjoy) the full capability of the Lync Mobile app. Also, some functionality might require an update to Lync Server or might not be available to all users. If you’re not sure about your account status, please contact your IT department.
What's New in Version 5.3
-View shared PowerPoint presentation during a Lync Meeting
-Full support of the new iOS 7
This article is a followup for the following articles
Autodiscover for Exchange Webservices by Lync impacts Exchange Deployments
http://www.pro-lync.be/blogs/lync2013/archive/2013/10/30/autodiscover-for-exchange-webservices-by-lync-impacts-exchange-deployments.aspx
The mysterious case of the “Network Password” popup
http://www.pro-lync.be/blogs/lync2010/archive/2013/10/23/the-mysterious-case-of-the-network-password-popup.aspx
While trying to fix a customers enviroment I have been playing with the following Registry Cache information that you can potentially pre-populate into the Lync clients registry information so that it will find the Exchange Webservices without properly configured Exchange Autodiscover process. The following screenshot is information that is stored in the registry for the user and acts as a cache for the Exchange Autodiscover information.
Registry Key For Lync 2010 :
HKCU\Software\Microsoft\Communicator\<SIP Address>\Autodiscovery
Registry Key for Lync 2013:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync\<<SIP Address>\Autodiscovery
This is an example of Exchange 2010 Cache export from Registry:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync\<Replace with real SIP Address>\Autodiscovery]
"cacheVersion"=dword:00000002
"WasSoapBased"=dword:00000001
"WasWsSecurityBased"=dword:00000000
"InternalAvailabilityServerUrl"="https://<InternalURL>/EWS/Exchange.asmx"
"InternalOofServerUrl"="https://<InternalURL>/EWS/Exchange.asmx"
"InternalEwsUrl"="https://<InternalURL>/EWS/Exchange.asmx"
"InternalEcpUrl"="https://<InternalURL>/ecp/?p=customize/voicemail.aspx&exsvurl=1"
"InternalBasicEcpUrl"="https://<InternalURL>/ecp/"
"InternalPhotoUrl"=""
"InternalServerVersion"=dword:738081e2
"ExternalAvailabilityServerUrl"="https://<ExternalURL>/ews/exchange.asmx"
"ExternalOofServerUrl"="https://<ExternalURL>/ews/exchange.asmx"
"ExternalEwsUrl"="https://<ExternalURL>/ews/exchange.asmx"
"ExternalEcpUrl"="https://<ExternalURL>/ecp/?p=customize/voicemail.aspx&exsvurl=1"
"ExternalBasicEcpUrl"="https://<ExternalURL>/ecp/"
"ExternalPhotoUrl"=""
"ExternalEcpPhotoUrl"=""
"ExternalServerVersion"=dword:738081e2
"TimeStamp"=hex:90,e1,c7,15,79,da,ce,01
"InternalTimeToLive"=dword:00000018
"ExternalTimeToLive"=dword:00000018
This is an example of Exchange 2013 Cache export from Registry:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync\johan.delimon@ordina.be\Autodiscovery]
"cacheVersion"=dword:00000003
"WasSoapBased"=dword:00000001
"WasWsSecurityBased"=dword:00000000
"InternalAvailabilityServerUrl"="https://<InternalURL>EWS/Exchange.asmx"
"InternalOofServerUrl"="https://<InternalURL>/EWS/Exchange.asmx"
"InternalEwsUrl"="https://<InternalURL>/EWS/Exchange.asmx"
"InternalEcpUrl"="https://<InternalURL>ecp/?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=ordina.be"
"InternalBasicEcpUrl"="https://<InternalURL>/ecp/"
"InternalPhotoUrl"="https://<InternalURL>/EWS/Exchange.asmx/s"
"InternalServerVersion"=dword:73808888
"ExternalAvailabilityServerUrl"="https://<ExternalURL>/EWS/Exchange.asmx"
"ExternalOofServerUrl"="https://<ExternalURL>/EWS/Exchange.asmx"
"ExternalEwsUrl"="https://<ExternalURL>/EWS/Exchange.asmx"
"ExternalEcpUrl"="https://<ExternalURL>/ecp/?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=ordina.be"
"ExternalBasicEcpUrl"="https://<ExternalURL>/ecp/"
"ExternalPhotoUrl"="https://<ExternalURL>/EWS/Exchange.asmx/s"
"ExternalEcpPhotoUrl"="https://<ExternalURL>/ecp/PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=ordina.be"
"ExternalServerVersion"=dword:73808888
"AnchorMailbox"="Johan.Delimon@ordina.be"
"TimeStamp"=hex:e2,42,2c,9c,ce,1d,cf,01
"InternalTimeToLive"=dword:00000018
"ExternalTimeToLive"=dword:00000018
You can use this key to solve autodiscover.domain.com not being provisioned by the Exchange Team and work around the problem manually or by script. Based on my tests Lync uses this key as a last resort when it cannot find the Exchange Webservices.
Note: If you make a script that uploads the correct values to the registry you could override a faulty Exchange Autodiscover implementation. You have to pay attention to the complete registry key because it includes the SIP Address in het key structure so you will need to use a script to generate or lookup the correct SIP Address for every user or this will not work.
Lync Call Quality Methodology poster
http://www.microsoft.com/en-us/download/details.aspx?id=41698
Learn about CQM, the Call Quality Methodology for Lync 2013 and 2010 that helps you find and eliminate issues affecting call quality and user experience for Lync implementations that include enterprise voice features.
Call Quality Methodology is a new troubleshooting and service management framework that can better focus efforts to improve enterprise voice services in Lync. In this article, you can learn more about CQM, the kinds of servers and solutions that are monitored, and what to do with the collected telemetry data.
Lync 2013 for Android updated to Version 5.3
https://play.google.com/store/apps/details?id=com.microsoft.office.lync15
Description of the cumulative update package for Lync 2013 for Android: February 2014
http://support.microsoft.com/kb/2926050
This article describes the Microsoft Lync 2013 for Android issues that are fixed in the cumulative update that is dated February 2014. Additionally, the article also describes the improvements that are introduced in the cumulative update. The cumulative update includes the following improvements:
This cumulative update fixes the following issues:
More Info
Lync Mobile update for Android phones: Rejoin and Conversation Continuum
http://blogs.technet.com/b/lync/archive/2014/02/11/lync-mobile-update-for-android-phones-rejoin-and-conversation-continuum.aspx
