Error when you start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The requested HTTP URL was not available"

Issue: -

Administrator not able to access the Exchange Management Console and Exchange Management Shell in Exchange 2013.

Error Message: -

Error when you start Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The requested HTTP URL was not available"

Problem Statement: -

Due to the above error Administrators not able to do there administrative work, The issue with HTTP binding on the Default Web Site in Internet Information Services (IIS) is either missing or is invalid.

Resolution: -

1.  Open IIS Manager, and then navigate to Default Web Site.

2.  Right-click Default Web Site and then click Edit Bindings.

3.  If a binding exists for HTTP, clear the host name value.

4.  If no binding exists for HTTP, create a new binding that has no host name and a value of All Unassigned for the IP address.

5.  Restart IIS.

 

Thanks.

Installing Lync Server 2013 Persistent Chat Server on Windows Server 2012

Installing Lync Server 2013 Persistent Chat Server on Windows Server 2012

In Pervious Article we have installed Lync 2013 Standard Edition Server on Windows Server 2012 Install Lync 2013 

In this article we are going to see, how to install and configure Lync 2013 Persistent Chat server.

Introduction: -

Lync 2013 Persistent enables to use multi-topic, Multiparty Conversation in single window.

·        Improve communication between geographically dispersed and cross-functional teams

·        Broaden information awareness and participation

·        Improve communication with your extended organization

·        Reduce information overload

·        Improve information awareness

·        Increase dispersion of important knowledge and information

High-Level Architecture: -

 




 

Pre-Requisites:-

• Lync Server 2013 Standard Edition
• Full instance of SQL 2008 or SQL 2012 called CHAT

 

Steps 1:-

Open Topology Builder then Right Click Persistent Chat and Define Persistent Chat Pool server. In our serious we are going to see Single Computer Pool and you do not need load balancing or high availability.

 Steps 2:-

Define the Persistent Chat Display Name and Port Number 5041, Enable Compliance and Enable this pool as default for site.

 

Steps 3: -

Define the SQL Store

 

Steps 4: -

Define the Compliance SQL Store for storing conversation history for Security and Compliance.

 

Steps 5: -

Define the File Store

 

Steps 6: -

Select the Next hop pool

 

Step 7: - Publish the Topology.

 

Steps 8: -

Now you’ll want to open up the Lync Server Deployment Wizard and click Install or Update Lync Server System.

It will install Local Replica of CMS, Once it’s completed without any error move on next

 

Click Run in steps 2, it will install the Persistent Chat Server

 

Click Run in Steps 3, Request certificate for Persistent Chat and assign it.

 

Click Run in Step 4 for start the Lync Persistent Chat server services.

 

Steps 9: -

Now that we have built out the Persistent Chat function, it’s time to move into the Lync Server Control Panel and enable the functionality.

Open the Control Panel.  Click on Persistent Chat –> Persistent Chat Policy –> Check “Enable Persistent Chat”.

 

Now we need to add a category.  Click “Category” –> “New” –> and select your newly created Persistent Chat Server.

Fill in the settings and add your Allowed members.



 

Now we will add Persistent Chat Creators Members list which will allow the Members to Create/Modify the Persistent Chat Rooms.

 

Steps 10: -

Install Lync 2013 Client on users systems and login using above creators account for accessing the Persistent Chat room.

Now it is time to add a Chat Room to the category that was just created.  This can be accomplished through PowerShell, but I have found it easier to do it through the Lync 2013 Client when you are adding multiple users.

Inside your Lync 2013 Client, click the “Chat Rooms” icon and then the “+” symbol to the right and click on Create Chat Room

Enter User Name and Password who have access for creating Persistent Chat Room and Click on Create a New Room 

Enter the Room Name and followed information

 Once you created wait for 15 minutes for replication , Once it’s completed sign out and sign in back for access the Persistent Chat Room

 

Double Click the Chat Room for starting Conversation.

Enjoy..

Thanks

Keep your comments..

 

Unable to access Exchange 2013 EAC/ECP webpage

Unable to access Exchange 2013 EAC/ECP webpage
Hi Buddy’s,

Today I am faced very interesting thing in Exchange 2013; while I am working in ECP for Creating DLP Policy and configurations suddenly Exchange 2013 ECP stopped working, when I checked in Internet most of the experts told to reinstall the Exchange 2013. I have resolved the issue in my scenario, so I thought to share the same with you, might it will help some of them.  

Issue: -

Not able to access the Exchange 2013 Administrator Center (EAC) for doing our regular administrative work.

Error Message: -

Unable to access Exchange 2013 EAC/ECP webpage.

Exchange 2013 ECP error

The page cannot be display

Problem statement: -

If we are not able to access the Exchange administrative center then we not able to do any our normal/ day-to-day work.

Resolution: -

Resolution will differ based on the environment and scenarios.

1.    Check the Event Viewer whether we are getting any related events

 

Process MSExchangeHWWorker.exe (ExHMWorker) (PID=1124).ServerComponent 'RwsProxy' set by Requester 'HealthApi' to Inactive

 

2.    Check whether Default Web site pointing to WWWRoot (c:\inetpub\wwwroot), if it’s wrong change it to default settings.

3.    Check the ECP Virtual Directory configured correct Authentication, it should enabled windows authentication and form based authentication should be disabled.

4.     Check ECP Virtual Directory configured correct physical location, in my case it was C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp.

5.    Check the OWA Virtual directory and authentication; it should be Windows authentication and Physical location C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa.

6.    Check the Binding configuration in Client Access Server for post 80 and 443

 

 

 

 

  7.    Recreate the ECP and OWA Virtual Directory.

For the "OWA" virtual directory

1.    Open Exchange Management Shell (EMS), and then run the following cmdlet to change the authentication method of the "owa" virtual directory to Windows authentication:

Set-Owavirtualdirectory -identity "Exch15hub\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false

2.    Run the following command on both the Client Access and Mailbox servers to restart Internet Information Services (IIS):

iisreset /noforce

For the "ECP" virtual directory

1.    Start Windows PowerShell.

2.    Type the following commands, and then press Enter after each line:

Add-PSSnapin *exchange*

Set-EcpVirtualDirectory -Identity "Exch15hub\ecp (Exchange Back End)" -WindowsAuthentication $true -FormsAuthentication $false

3.    Run the following command on both the Client Access and Mailbox servers to restart Internet Information Services (IIS):

iisreset /noforce

Thanks

 

Post your comments..

 

 

 

 

 

Install and configure Exchange Server 2013 on Windows Sever 2012

Install and configure Exchange Server 2013 on Windows Sever 2012

Deployment of Exchange 2013 has three main stages

1.  Prepare Active Directory ( If you installing Exchange 2013 for the first time)

2.  Install required Exchange 2013 prerequisites

3.  Install Exchange 2013 Setup

Prepare Active Directory

When you install Exchange 2013 for the first time in environment you need to prepare the active directory.

·        Active Directory domain functional level should be 2003 or higher.

·        Active Directory Forest functional level should be 2003 or higher.

·        Each Exchange site should have one Global Catalog server that is running Windows server 2003 SP2 or higher.

·        An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup.

·        Schema master running Windows Server 2003 with SP2, or a later version of Windows Server.

Although Active Directory preparation can occur as part of the installation of the first Exchange Server 2013 server, you can also run the Active Directory preparation as a separate task beforehand on a 64-bit server running Windows Server 2008R2 SP1 or higher.

Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.

If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory Schema:

Setup /PrepareSchema

 

If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:

Setup /PrepareAD /OrganizationName: "your organization name" /IAcceptExchangeServerLicenseTerms

 

Install the Exchange Server 2013 Pre-Requisites

Exchange 2013 can be install Windows server 2008R2 SP1 or 2012.

Import-module servermanager

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Install Microsoft Office filter pack 2010 64 bit. (http://go.microsoft.com/fwlink/p/?linkID=191548)

Install Microsoft Office filter pack 2010 SP1 bit.

(http://go.microsoft.com/fwlink/p/?LinkId=254043)

Unified Communication Managed API 4.0 Runtime

(http://www.microsoft.com/en-us/download/details.aspx?id=34992)

Install Exchange 2013 Setup

After Installed all required Prerequisites restart the server before continue Exchange 2013 setup.

From the location where you have stored your Exchange 2013 files run Setup.exe.

The first dialog gives you the opportunity to check for updates to the setup files before you proceed.

If you have all required setup files and update you can select “Don’t check for the updates right now” and pass through Next step

 

This steps copy the Exchange Installation files to Temporary location before continue the process.

Click Next to continue pass through next steps

Next Process Initializing Setup

 

Accept the license agreement and click Next to continue.

Choose whether or not to enable Error Reporting and click Next to continue.

After a check that all the pre-requisites are installed the setup wizard will move on to the next step automatically.

Now we can choose the server roles to install. If this is the first server you’re installing Microsoft recommends you install the Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).

Verify that you have enough disk space for the installation, or choose a path that does have enough disk space, and click Next to continue.

Specify the name of this Exchange Organization and Click Next

 

When installing the Mailbox server role you are given the option to disable malware protection. If you disable it now you can enable it again later. Microsoft recommends living default option (Enabled).

Some readiness checks are performed. If this is the not the first server you’re installing and there is no Send Connector defined for outbound email then you may see a warning, but you can still proceed with the server installation.

If you received any error message during the readiness check, Please correct the issue before continues Next steps.

If everything goes smooth Click Next for continues Exchange setup, It will take some time to complete the full setup.

The install is a fairly lengthy process, so you may want to go and do something else while you wait. When setup has finished click Finish.

 

 Thanks.

Keep your comments..

 

How to Install Lync Server 2013 Std. Edition on Windows Server 2012

How to Install Lync Server 2013 Std. Edition on Windows Server 2012

In this post I am going to cover Basic installation of Lync 2013 in Windows server 2012.

Outline of the Lync 2013 installation:-

1. Prepare Servers
2. Install Lync Server 2013
3. Prepare Active Directory
4. Prepare First Server
5. Configure DNS
6. Build Topology
7. Install Lync Server System
8. Add & Enable AD Users
9. Login to Lync 2013

 Prepare Environment

Some prerequisites for you Lync system:

• You will need 1 AD Server O/S and 1 Lync Server O/S
• Lync requires 64bit O/S
• This guide is Using Windows Server 2012 64bit
• But Windows Server 2008 R2 SP1 should work fine as well.
• Make Sure you have the below role running on your AD Server
• AD-DS (Directory Services)
• DNS
• AD-CS (Certificate Authority)

Prepare Your Front End Server

Install using Windows Server 2012 “Add Roles and Features Wizard”

 

Server Requirements

Front End server must be joined to domain

FE must have UI installed

Install Silverlight (will save time later)

Front End must have these Features

Roles

Web Server (IIS)

Features

ü  Message Queuing | Message Queuing Services

ü  Remote Server Administration Tools | Role Administration Tools | AD DS and AD LDS Tools

ü  User Interfaces and Infrastructure | Desktop Experience  

ü  Windows Identity Foundation 3.5

ü  .NET Framework 3.5 Features

ü  .NET Framework 3.5

ü  HTTP Activation (Important!)

ü  Non-HTTP Activation

ü  .NET Framework 4.5 (all options)

ü  Roles

ü  Web Server (IIS)

ü  Role Services

ü  Common Http Features Installed

ü  Static

ü  Default doc

ü  Https errors

ü  Health and Diagnostics

ü  Http logging

ü  Logging Tools

ü  Tracing

ü  Performance

ü  Static Content Compression

ü  Dynamics Content Compression

ü  Security

ü  Request Filtering

ü  Client Cert Mapping Authentication

ü  Windows Authentication

ü  Management Tools

ü  IIS Mgt Console

ü  IIS mgt Scripts and Tools

ü  Application Development

ü  ASP.NET 3.5

ü  ASP.NET 4.5

ü  .NET extensibility 3.5

ü  .NET extensibility 4.5

ü  ISAPI extensions

ü  ISAPI Filters

Reboot Front End and login as Domain Administrator.

Install Lync Server 2013: -

Insert Lync 2013 Image file into CDROM and Run Setup.exe

You will be prompted to install Visual C++ 2012 x64. Click “Yes” (screenshot below).

Accept Terms and click “Ok” to install.

When install is complete (3minute wait time) you will have below apps on your server and the Lync Server Deployment Wizard (below) will appear.

Lync Server Management shell.

Lync Deployment Wizard.

Prepare Active Directory

Click “Prepare Active Directory”. (As noted in prerequisites, you will need AD DS and AD LDS Tools Feature installed on your Front End to complete this step.)

• Step 1: Prepare Schema. (takes 1minute, and you may need to wait a couple minutes before this and step 2)
• Step 2: Verify Replication of Schema is not necessary if this is a Lab and there is only one AD server—you can safely keep moving to step 3.
• Step 3: Prepare Forest | Next | select Local Domain | Next (5sec)
• Step 4: just keep moving
• Step 5: Prepare Domain | Next (5sec)
• Step 6: just keep moving
• Step 7 below

Add Lync Administrative User to Admin Group

Add the Administrator to CSAdministrator group (shownbelow)

CSAdministrator.

Prepare First Standard Edition Server

Now let’s go back to the Deployment Wizard and click “Prepare first Standard Edition server”.

 

You will see the below “Prepare single Standard Edition Server” wizard window and you can just click “Next”. During this process the below will be installed:

• SQL Server 2008 Express Edition will be installed
• RTC databases will be created and populated
• Lync Server installation files will be put in place
• Etc

 

 

 

 

 

Configure DNS Records


Let’s open DNS Manager on AD server. Right click on your domain (in our case Learnexchange.com) under Forward Lookup Zones, click “Other New Records…” and scroll down to “Service Location (SRV)” and click Create Record

We will add SRV to pointing our Front End server (Lync.learnexchange.com)

 We will also create 3 DNS A Records. Right click, “New Host (A or AAAA)…” Add a DNS A record for

• meet
• dialin
• admin

as shown below

Repeat this for meet and admin DNS A Records.

Now let’s go back to the Deployment Wizard and click “Install Administrative Tools”.

Build and Publish Topology

Next we will go to Start and run “Lync Server Topology Builder” (below).

Select New Topology (as shown below) and then give the topology some name.

Now we will be defining this topology.

Primary SIP domain: learnexchange.com | Next

Specify additional supported domains: {nothing/none} | Next

• Define the First site
• Name: Chennai Learning Center
• Description: Chennai Learning Center.

• Specify site details
• City
• State
• Country

Click “Finish”

Define Front End Pool

FQDN: Lync.learnexchange.com

Note: if this is a Standard Edition, this FQDN will be exactly the same FQDN as your FE server (Lync.Learnexchange.com in our case)

Standard Edition Server

Next we will select Features for this Front End Pool

Check these features:

• Conferencing
• Enterprise Voice
• Call admin control

• Select Collocated server roles
• collocate Mediation Server: check

Associate server roles with this front End pool

• Enable an Edge pool…: unchecked

Define SQL Store

Lync.learnexchange.com\rtc

Define the file store: default, next (NOTE: You will need to manually create this network share and give rights to everyone. This wizard will not automatically create it for you)

Let create the Lync file store share right now so we don’t forget. You can create this folder where ever you want it. (Preferred: other than OS Drive C) Next go into the properties of the folder and give full access permissions to these groups:

• RTCHS Universal Services
• RTC Component Universal Services
• RTC Universal Server Admins
• RTC Universal Config Replicator

Click on the “Sharing” tab, click on “Share

Specify the External URL ( In our case Lync.learnexchange.com)

Specify where your Office Web App server is (In our case OWA.learnexchange.com)

Now you are finished with the wizard.

Edit properties of topology

Right click on “Lync Server 2013 and then “Edit Properties” and update Central Management Server.

Publish Topology

Action | Publish | Next | Next

Install Lync Server System

Deployment Wizard | Install or Update Lync Server System

Now we will install some Lync Server System components, put Certs in place and Start Services:

1.  Step1 Install RtcLocal database

2.  Step2 Install Speechfiles, etc.

3.  Setup Certs

4.  Start Lync Services

• Step1 Install Local Configuration Store (will install RtcLocal)
• Run
• Retrieve Directly from the CMS…
• Next
• Step2 Setup Lync Server components (will install Speechfiles, etc)
• Run |
• Next
• Step3 Request Certs (Installed ADCA authoritative)

Run, select “Default Certificate” then click “Request”

Certificate Request: Next

Delayed or Immediate Request Send the request immediately to an online cert authority

Choose a Certificate Authority (CA): Select a CA from the list

Certification Authority Account: Next

Specify Alternative Certificate Template: Next

Name and Security Settings: some name

Organization Information: fill in Org and Org Unit

Geographical Information: fill in

Subject Name/Subject Alternative Names: Next

SIP Domain Setting on SAN: Select SIP Domain (example: Learnexchange.com) | Next | Next | Finish.

Configure Additional SAN: Next

Certificate Request Summary: Next

Executing Commands: Completed: Next

Online Certificate Request Status: Finish

Certificate Assignment: Next

Certificate Assignment Summary: Next

Executing Commands: Finish

Select “Default certificate” and click Assign certs

Now repeat the Certificate Wizard steps for the OAuthTokenIsuer.

Step 4: Start Services

After services are started you can open the Services to verify all the Lync Services are running.

 

Go to Start | Run Lync Control Panel before Install Silver Light.

 

Add and Enable AD Users

Next, we will move to our AD server and add several users to Active Directory (I suggest for your first test users to NOT use the Administrator, but 3 other users). In our case I added:

Gengaiyan

Administrator

Now back to Lync Server Control Panel. Click on User | Enable Users. Now click the “Add” button and Add the 3 users. 

Install Lync 2013 Client and Login Using SIP account.

Enjoy.
Thanks