Lync Audio/Video Disabled in batch

If you want to disable Audio/Video for batch and only want to allow basic Lync features then following will be the command for this;

Import-Csv C:\LyncBatch.csv| ForEach-Object{$varUserId=$_.userid;set-CsUser -Identity $varUserid -AudioVideoDisabled $True}

In order to run this command, there should be a CSV file present in C:\ drive named as lyncbatch.csv. This file should have aliases of all the users accounts needs to disable Audio/video in following format(List should always start with userid) ;

userid

JDoe

MTaylor

BLee

 

After running this command the user can do chat and web conferencing but there will be no Audio/Video/Enterprise voice service available for user.

Batch Command for enabling Lync Users

Following is a very useful command for enabling Lync users in batches;

Import-Csv C:\LyncBatch.csv | ForEach-Object{$varUserId=$_.userid; Enable-CsUser -Identity $varUserid -RegistrarPool lspool01.contoso.com –SipAddressType EmailAddress -SipDomain contoso.com}

In order to run this command, there should be a CSV file present in C:\ drive named as lyncbatch.csv. This file should have aliases of all the users accounts needs to migrate in following format(List should always start with userid) ;

userid

JDoe

MTaylor

BLee

Windows Live Audio/video Federation with Lync

was aware that we can federate with windows live for instant messaging integration but was not sure about Audio/Video. After some research i found following blog post which is confirming this type of federation;

http://www.confusedamused.com/notebook/lync-to-windows-live-av-federation/

Please be aware that in order to federate with windows live you have to change Lync encryption settings

Lync 2010 Mobility in Split-brain DNS setup

After reading Mobility guide from Microsoft, it is not very clear that how users will connect to Lync auto discover service externally and internally in split brain DNS Setup and it requires reading again and again and troubleshooting again and again to find out the correct setup, in summary following should be the DNS configuration in split-brain DNs setup (Note: Split-brain DNS refers to the DNS setup where your DNS zone is split between your Internal Network and your external network for example Contoso.com zone is also present in internal AD forest DNS servers and also published outside publish DNS servers);

1. Lync Auto discover URL should be in external and internal DNS servers pointing to Lync external web services URL.

2. Lync Auto discover internal URL should be present in your internal DNS server pointing to Lync internal web services URL.

3. There should be a entry for Lync external web services URL in your internal DNS servers pointing to lync external web services IP for “Hair-pining” Lync mobile traffic to Reverse proxy servers.

4. Reverse proxy Rule for lync auto discover service should have lync discover internal URL added for mobile clients connecting from internal network through lync external web service public IP.

Lync 2010 Blogging

I have recently implemented Lync services in our organization and came across lots of problems mainly due to the guides which Microsoft has published is not clear and have lots of questions unanswered. The only way to do a correct configuration is to to a trial and error and then check if the problem is solved or not or engage Microsoft professional services.

I will be blogging on some of the issues I have faced and resolved for the benefits of other implementers.

Exchange 2007 unable to mount database

Recently we had a power failure which caused an improper shutdown to our exchange servers. After recovered from power failure we restarted all servers and fixed some cluster issues but there is one database which is showing failed in cluster manager. I had tried to mount the database but it was not successful and showing that there are some log files missing due to which database cannot mount.

For checking what log files are missing I ran following commands against the database which was not mounting. For running this command we have to go to the log drive of the database first and then run this command.

eseutil /mh

The output of this command is showing that the database is in dirty shutdown state and also showing that what log files are missing. I have checked these log files and luckily I have all log files present in the log drives folder.

Now recovery is easy, I have just renamed the check point file to any other name and try to mount it again and this time it mounts successfully without any issues and new checkpoint file is created.

MOSS "trial period for this product has expired"

Recently I faced an strange issue related to MOSS. One of my content admin is complaining that he is unable to add any link or page in his site anymore. whenever he is trying to create any page he is getting this error

"trial period for this product has expired"

Our MOSS farm has correct license and we haven't upgraded MOSS from trial version. After thorough analysis and research, I found that there is a bug in MOSS SP2 which reinitializes the license file and turns MOSS normal license to 180 days trial  license.

For fixing this issue, you can go to MOSS central admin->operations->Convert license type->Enter product key and add the key again or apply the hotfix mentioned in the below KB article.

http://support.microsoft.com/kb/971620

Renewing Edge Synchronization

If you have added any domain on HUB server and you are not able to see this domain on Edge server then might be your synchronization between your hub and edge servers are not working. To test this you can run following command;

Test-EdgeSynchronization

If the connection result is showing failed then you need to do edge subscription again for this edge server. Following are the steps for this

1. On the edge server which is not synchronizing run following command;

New-EdgeSubscription -filename "C:\temp\edgesub.xml"

now copy this .xml file to hub server and run following command

New-EdgeSubscription -filename "C:\temp\edgesub.xml" –site London

Please note the site parameter is required to bind this edge server to a specific AD site.

Now run following command

Start-EdgeSynchronization

You will notice that now the edge server is synchronizing data with HUB server.

For verification you can run test command again and this time it should show you the success message

Test-EdgeSynchronization

Enabling SCR on WAN

SCR is an Exchange 2007 DR solution available from Exchange 2007 SP1 onwards.  You can enable SCR on LAN and also on high latency networks. SCR also gives you benefit to recover from a Datacenter failover scenario. Since last month i was working to enable SCR between our DCs connected via MPLS. After a thorough analysis and lots of try and error i have compiled following results;

SCR Enabling Steps:

1. Seeding of .Edb File.

2. Enable Replication.

3. Monitor Replication

 

Step 1: Seeding:

Seeding is a prerequisite for enabling SCR, we can enable seeding by automatic way and manual way, because i have to seed .edb file on MPLS which is a high latency network i have to go for manual procedure. Following steps i have followed for manual seeding.

1. Take a snapshot of storage group on which i want to enable SCR (we are using snapshot based backup solution) you can also take the normal backup of the storage group. This will also truncate all the committed logs and we have less log files to copy from source to destination after enabling replication.

2. Run  below Command

Enable-StorageGroupCopy -Identity StorageGroup1 -StandbyMachine London1 -ReplayLagTime 0.1:0:0 –SeedingPostponed

The above command will enable SCR on storage group “StorageGroup1”. Standby machine (destination server) used is London and the replay lag time i have mentioned is 1 minute. seeding postponed is used because i don't want to enable seeding automatically i want to copy .edb file manually to destination server.

After running the above command, log files for this storage group will not truncate unless until we enable replication. This means that the drive space of log files folder should also be carefully planned because if the latency is high and the .edb file is taking days to copy then the log file drive space might going to be fill which will affect the production environment.

3. Take a snapshot on the storage group again or take a normal storage group backup again.

4. Ask the backup team to provide the .edb file from the last snapshot.

5. Use TeraCopy to copy .edb file from source to destination server. make sure the drive letters for log and data drive are same on standby server because it is one of the prerequisites of SCR.

2. Enabling Replication:

Replication will copy all logs files from source to destination. Replication is an ongoing process and whenever a log file is created on source it has to be shipped to destination for making both source and destination mailbox databases in same state.

Following is the command for enabling replication

Resume-StorageGroupCopy -Identity StorageGroup1 -StandbyMachine London1

after running the above command you will see that the log files started to copy from source to destination server. Standby server will replay these log files after 50 logs files has been copied. The first log file after you enable SCR should be present on destination otherwise replication will fail.

3. Monitoring Replication:

It is very important to check the status of storage group copy. The below command will show us the health of SCR and how many files in copy queue and replay queue.

get-storagegroupcopystatus StorageGroup1 -standbymachine London1

If you are seeing failed  in the summarycopystatus field then there is a possibility that the database you have seeded and the logs files copied are not at the same state (LSN number mismatch) or might be you don't have the first log file available to replay on the destination.

If you are seeing large number of files in copy queue length then bandwidth might be the possible cause.

You can also run following command on standby server for checking replication status;

Test-ReplicationHealth

Moving LCS databases to Different SQL server

LCS use 2 databases for its configuration and user data

1. RTC
2. RTCConfig

If you want to move these databases to different SQL server then you need to follow below sequence

1. Stop Live communication Server Service.
2. Take backup of the above mentioned databases.
3. Restore to them to new SQL server.
4. Make sure you have all 4 LCS domain groups (mentioned below) added to new SQL server and have all the required permissions given (Compare permission with the existing SQL server).
   LCS Domain Groups:
   RTCABSDomainServices
   RTCDomainServerAdmins
   RTCDomainUserAdmins
   RTCHSDomainServices
5. Run Following Command for setting new SQL server information;  
   LcsCmd.exe /forest /action:UpdatePoolBackend /poolname:[PoolName] /poolbe:[SQLSeverName]
6. Start LCS service again.
7. Open LCS MMC.
8. Make sure all services are running fine.

Exchange 2010 Unified Communication webcast

During some searching i found an excellent webcast on Exchange 2010 unified communication features. Following is the link;

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032442908&CountryCode=US

SharePoint website not opening on same server

I faced a strange issue recently, i have deployed SharePoint 2003 servers for one project and one of the requirements was to open SharePoint site from same server. when i was trying to open site from the same server i was getting authentication prompts and the site was not opening. I have even added the URL entry in the local host file but the issue remains same. After googling i found one Microsoft KB on the same issue which stated that  “This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.”

In order to fix this we need to disable loopback check on all web server which are facing this behavior. I have applied this fix on my both front-end servers and after restarting both front-end servers the issue solved and i can now open website on same server. Following is the fix i followed.

Click Start, click Run, type regedit, and then click OK.

In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Right-click Lsa, point to New, and then click DWORD Value.

Type DisableLoopbackCheck, and then press ENTER.

Right-click DisableLoopbackCheck, and then click Modify.

In the Value data box, type 1, and then click OK.

Quit Registry Editor, and then restart your computer

 

Following is the KB for this issue;

http://support.microsoft.com/kb/896861

Command for shrinking Log files

Below command will shrink SQL log files and also release unused physical space on drives.

Use DatabaseName

Backup log databasename with no_log

DBCC SHRINKFILE (logfilename)

WSS search and SQL 2005 indexing issue

Recently we have migrated our SharePoint 2003 from one AD forest to another forest, apart of this change we have also upgraded our backend DB from  SQL 2000 to SQL 2005.  Recently i faced a very critical issue, one of the heavily used site is not showing search result and the search is timing out. In order to investigate this issue i have identified the query in the SQL profiler and ran it directly on the SQL management studio. It took around 10 minutes to show results in new DB Server (SQL 2005)  but the same query is returning result in 1 sec in the old DB server (SQL 2000) i ran the query again with the Query execution plan against both servers and compared it, i have seen the cost for referencing Clustered index is very high in new DB server as compared to old DB server.  After some researching i have planned to update DB statistics by using following command;

update statistics tablename

SharePoint create its own indexes which we cannot alter and it uses the hard coded name for indexes such as ix_databasename. As per my analysis after moving DBs from SQL 2000 to SQL 2005 the databases statistics were not updated and indexes were not using optimal path for searching for data that why it is showing results after long delays.

Exchange 2007 unable to view deleted mailbox

In exchange 2007 if you delete any mailbox or any AD user, the mailbox will be there for 30 days in disconnected mailbox view and you can reconnect it again within 30 days if you want to restore the mailbox to its original state. After 30 days the mailbox will be permanently deleted and you can then only restore it from the backup.

Recently i faced a strange issue, one of the mailbox user was deleted by mistake and i am unable to see this user in disconnected mailbox view. The mailbox was deleted 2 days back which is under 30 days threshold but still the mailbox was not visible. After done some research and some help from one of my friend i figured out that i have to run following command in order to make this mailbox visible in disconnected mailbox view

Clean-mailboxdatabase –identity Databasename

As per Microsoft,

“use the Clean-MailboxDatabase cmdlet to scan the Active Directory directory service for disconnected mailboxes that are not yet marked as disconnected in the Microsoft Exchange store and update the status of those mailboxes in the Exchange store. This cmdlet is not able to update the Exchange store unless the Microsoft Exchange Information Store service is running and the database is mounted.

A connected mailbox has two parts: the mailbox object in the Exchange store, and the user object with Exchange properties in Active Directory. A disconnected mailbox is the mailbox object in the Exchange store, but it is not connected to a user object in Active Directory

Under normal circumstances, it is not necessary to run Clean-MailboxDatabase because a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. If you used the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Exchange Information Store service was stopped, or if a mailbox was disabled by an external means other than the Disable-Mailbox cmdlet or Remove-Mailbox cmdlet, you may want to use the Clean-MailboxDatabase cmdlet to scan for disconnected mailboxes.”

SQL 2005 services not starting

When you have SQL server running in clustering and you changed any startup parameters, it is possible that SQL services will not run due to any incorrect parameter  settings. As per Microsoft this is because the cluster service obtains an incorrect protocol setting from a cluster checkpoint when you start the SQL Server service.

In order to fix this issue you have to first remove the last check point by running this command (after making SQL server resource offline)

cluster res "SQL Server (Instancename)" /removecheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER

and then fix the startup parameters for all nodes and then run following commands

cluster res "SQL Server (Instancename)" /addcheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER"

Following is the Microsoft KB for more details.

http://support.microsoft.com/kb/912397

Exchange 2007- Mapi session exceeded the maximum of 32 objects of type "session"

Two days back i faced a strange issue from one of the user that he is not able to open his outlook. Although he can open his OWA but whenever he open his outlook he is getting following error

“Unable to open your default e-mail folders. You must connect to your Microsoft Exchange Server computer with the current profile before you can synchronize your folders with the offline folder file”

After further investigation i found that there is an event logged in the application events of the mailbox server for the same user

Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      9646
Date:            XXXXX
Time:           XXXXX
User:            N/A
Computer:      XXXXX
Description:
Mapi session "/o=firstorganisation=XXXX/cn=Recipients/cn=username" exceeded the maximum of 32 objects of type "session".

After researching i found following KB on the same issue

http://support.microsoft.com/kb/842022

As per this KB this issue may occur if the following conditions are true:

• You have installed Microsoft Exchange Server 2003 Service Pack 1 (SP1) on the Exchange Server computer.
• A program that is running on a client computer opens many MAPI sessions to the Exchange Server computer. The number of MAPI sessions is larger than the permitted limit.
• You are using Microsoft Office Outlook 2007, and you add a large additional mailbox to your profile. For example, this issue may occur if the additional mailbox contains more than one thousand folders.

I am unable to found any of the above condition in my case. Also fixes mentioned in this article is not relevant to my case except the last registry change which i don't want to apply for one user.

Then i decided to view the connections on the mailbox server. I downloaded TCP view utility from sysinternals (one of the best sites for troubleshooting tools). After running TCP view i have seen lots of connections coming to mailbox server but the user name which i was searching was not visible in the list of connections, then i ran following command on exchange management shell for finding out the source IP of the user having problem

Get-logonstatistics username | FT ClientIPAddress

After viewing the IP Address i searched the IP address in the TCP View and was able to found lots of connections coming from the same IP, i killed these sessions by using Kill option in TCP view and then again tried to open the outlook and the issue gone !!!!  I have also informed the user to have a look on his PC for checking if there is any third party software or any other MAPI program which is causing this issue for having a permanent fix for this.

Storage in Exchange 2010: Webcast

Join the new webcast on exchange 2010 storage technology planned to be delivered on July 13 2009. Following is the registration link

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032418920&EventCategory=4&culture=en-US&CountryCode=US

Exchange 2010 updates for Windows Mobile

During some researching i found an interesting video on Exchange 2010 mobile features and thought worth to blog. As per this video introduction

 

Adam Glick shows us the newest Exchange 2010 features for Windows Mobile 6.1/6.5 and explains the goals the team had for the client mobile experience. On his WM 6.5 device, he walks us through conversation view, ignore/move conversation, voice mail preview, voice to text, and get free/busy. Additionally, he tells us about the new allow/block/quarantine phone list and reporting built in to Exchange 2010.

 

Check out this video on following link

http://edge.technet.com/Media/Exchange-2010-updates-for-Windows-Mobile/

Publishing Exchange 2007 OWA via ISA 2006 Reverse Proxy

The best way to publish OWA is to publish via ISA reverse proxy deployment. In this blog i will discuss the process for publishing OWA via ISA reverse proxy. The process will be like this;

1. Generate CSR for Exchange 2007 CAS server(s).

I have discussed CSR generation in my previous blogs (http://khurramullah.wordpress.com/2009/07/01/exchange-2007-certificate-request-generator/ and http://khurramullah.wordpress.com/2009/07/01/command-for-generating-csr-for-exchange-servers/) if you have more than one CAS servers then you have to repeat the steps for all of them.

Make sure you have included all Subject Alternative  Names (SANs) in your certificate requests such as for webmail, auto discover services etc.

2. Submit this request to online Certificate Authorities such as VeriSign, Thwate or Entrust for purchasing UCC (Unified communication certificate). (Exchange 2007 only supports UCC type certificates, UCC=multiple SANs).

3. Now we have to import these certificates to Exchange CAS servers.( I have discussed these steps in my previous blog http://khurramullah.wordpress.com/2009/07/01/importing-certificates-to-exchange-servers/)

4. Now we have to deploy this certificate to ISA servers. In order to do this you have to first Export certificate from CAS server in .PFX format and then imports it to the ISA servers. Following is the process for doing this;

1. Open Certificate MMC Snap in on the CAS server for local computer.
2. Go to personal container and locate the certificate which you want to Deploy on ISA Server.
3. Export this certificate with private key in .PFX format.
4. Copy this certificate on ISA Server.
5. Open Certificate MMC Snap in on the ISA server for local computer.
6. Import the copied certificate.
7. Repeat steps 4 to 7 if you have more than one ISA Servers.

5. Forms-based authentication can be configured on the Client Access server when not using ISA Server to publish Exchange Web client access. When ISA Server is being used to publish Exchange Web client access, forms-based authentication should only be configured on the ISA Server computer following are the steps for validating this;

1. Start the Exchange Management Console.
2. In the Exchange Management Console, expand Server Configuration, and then click Client Access.
3. Select a Client Access server and then select owa (Default Web Site) on the Outlook Web Access page.
4. In the action pane, click Properties under owa (Default Web Site).
5. Select the Authentication page, and confirm that the following are selected: Use one or more of the following standard authentication methods and Integrated + Basic authentication (password is sent in clear text).
6. Click OK.
7. Review the Microsoft Exchange Warning dialog box and click OK.
8. Restart IIS by running following command: "iisreset /noforce".
9. Perform this procedure for every Exchange Client Access server.

6. On the CAS server please make sure that “Forms based authentication” is not configured on the Exchange Client Access Activesync folder. By default it is configured for basic authentication.This folder is configured to Basic authentication by default.

7. On the enabling page for Outlook Anywhere, we will use Basic authentication (default).

Note: The external host name used here should match the common name or FQDN used in the server certificate installed on the ISA Server computer

8. Now we need to publish a Rule for OWA on ISA but before doing this we need to configure web Listener for OWA which will be responsible for  listening OWA requests, following are the steps for configuring web listener for OWA

1. In the console tree of ISA Server Management, click Firewall Policy:
2. For ISA Server 2006 Standard Edition, expand Microsoft Internet Security and Acceleration Server 2006, expand Server_Name, and then click Firewall Policy.
3. For ISA Server 2006 Enterprise Edition, expand Microsoft Internet Security and Acceleration Server 2006, expand Arrays, expand Array_Name, and then click Firewall Policy.
4. On the Toolbox tab, click Network Objects, click New, and then select Web Listener. Use the wizard to create the Web listener as outlined in the following table

Page	Field or property	Setting
Welcome	Web listener name	Type a name for the Web listener. For example, type Exchange Web Listener.
Client Connection Security	Select what type of connections this Web listener will establish with clients	Select Require SSL secured connections with clients.
Web Listener IP Addresses	Listen for incoming Web requests on these networks ISA Server will compress content	Select the External and Internal networks. Check box should be selected (default). Click Select IP Addresses
External Network Listener IP Selection	Listen for requests on Available IP Addresses	Select Specified IP addresses on the ISA Server computer in the selected network. Select the correct IP address and click Add.   Notes For ISA Server Enterprise Edition with an NLB-enabled array, you should select a virtual IP address.
Listener SSL Certificates	Select a certificate for each IP address, or specify a single certificate for this Web listener	Select Assign a certificate for each IP address. Select the IP address you just selected and click Select Certificate. Choose the certificate corresponding to the url mapped to this IP in the public DNS/NAT configuration Example: External 192.168.1.101 for abcmail; .102 for xyzmail and .103 for autodiscover Internal: 192.168.12.101 for abcmail; .102 for xyzmail (autodiscover is resolved differently in intranet)
Authentication Settings	Select how clients will provide credentials to ISA Server Select how ISA Server will validate client credentials	Select HTML Form Authentication for forms-based authentication and select the appropriate method that ISA Server will use to validate the client's credentials.
Single Sign On Settings	Enable SSO for Web sites published with this Web listener SSO domain name	Leave the default setting to enable SSO. To enable SSO between two published sites, such as abcmail.Contoso.com and autodiscover.Constoso.com, type .Contoso.com (with the dot)
Completing the New Web Listener Wizard	Completing the New Web Listener Wizard	Review the selected settings and click Back to make changes or Finish to complete the wizard.

 

9.  Now after creating web Listener we need to publish a rule for OWA, following are the steps for this process;

1. In the console tree of ISA Server Management, click Firewall Policy:
2. For ISA Server 2006 Enterprise Edition, expand Microsoft Internet Security and Acceleration Server 2006, expand Arrays, expand Array_Name, and then click Firewall Policy.
3. On the Tasks tab, click Exchange Web Client Access Publishing rule.
4. Use the wizard to create the rule as outlined in the following tables. For a single Web server, use the table in New Exchange Publishing Rule wizard for a single Web site. If you are using a server farm, use the table in New Exchange Publishing Rule wizard for a server farm.

   Page	Field or property	Setting
   Welcome	Exchange Publishing rule name	Type a name for the rule. For example Constoso OWA Publishing Rule
   Select Services	Exchange version Web client mail services	Select Exchange Server 2007. Select the desired access method – begin with OWA, then Outlook Anywhere (Select to publish additional folders) and finally choose ActiveSync
   Publishing Type	Select if this rule will publish a single Web site or external load balancer, a Web server farm, or multiple Web sites	Select Publish a single Web site or load balancer.
   Server Connection Security	Choose the type of connections ISA Server will establish with the published Web server or server farm	Select Use SSL to connect to the published Web server or server farm.   Note A server certificate must be installed on the published Exchange Client Access server, and the root CA certificate of the CA that issued the server certificate on the Exchange Client Access server must be installed on the ISA Server computer.
   Internal Publishing Details	Internal site name	Type abc.contoso.com or whatever you like   Important The internal site name must match the name of the server certificate that is installed on the internal Exchange Client Access server.
   Public Name Details	Accept requests for Public name	This domain name (type below) Type the domain name that you want ISA Server to accept the connection for. For example, type abc.contoso.com. This must match the FQDN of the certificate selected when creating the Web listener.
   Select Web Listener	Web listener	Select the Web listener you created previously, Exchange Web Listener
   Authentication Delegation	Select the method used by ISA Server to authenticate to the published Web server	For Outlook Web Access, select Basic Authentication. For Exchange ActiveSync, select Basic Authentication For Outlook Anywhere, select Basic Authentication
   User Sets	This rule applies to requests from the following user sets	Select the user set approved to access this rule. Replace the default All Authenticated users with All Users Pass the warning
   Completing the New Exchange Publishing Rule Wizard	Completing the New Exchange Publishing Wizard.	Review the selected settings, click Back to make changes or Finish to complete the wizard.

   Note: When publishing Outlook Web Access, after you click Finish, review the Remaining Exchange Publishing Tasks dialog box, and then click OK.

5. In the path tab (properties of the OWA rule), add the path “/” in order to be able to access OWA without typing /owa at the end of the url