Monday, September 22, 2014

Lync Server 2010 to Lync Server 2013 installation steps

Lync Server 2010 to Lync Server 2013 installation steps

Recap: I have Lync Server 2010 installed in my environment and want to migrate Lync Server 2013.
You can find so many articles on Lync Server 2013 installation however I have recently deployed Lync Server 2013 for of my customer and want to share best practices with you.
Step: 1: Install Windows Server 2012 and update patches with latest one.
Now you need add your Windows Server to Domain Lync Server 2013 supported following Server Operating System
·         Windows Server 2008 R2 SP1 or latest service pack

·         Windows Server 2012

·         Windows Server 2012 R2

Step: 2: After Server Operating System installation, complete the following pre-requisite –
a.     Windows PowerShell 3.0
b.     Microsoft .NET Framework 4.5 on all internal server roles.
c.      After .NET Framework 4.5 is installed, use Server Manager to install HTTP Activation.
d.     Windows Identity Foundation 3.5 in order to support server to server authentication scenarios.
e.     Internet Information Services (IIS) with so many components. ( )
Use the following command let to install all components without fail.
Open PowerShell and Import-Module ServerManager and then run following command so that all required prerequisites gets install.
Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-WCF-HTTP-Activation45
Step: 3: Create DFS name space for Lync to store share information.
Best method is to create share folder on domain controller and then create folder on SQL server or somewhere else.
You can refer my previous article for, How to create DFS for Lync 2013.
Step: 4: This is time to Install Lync Server 2013, Core Components and start the Deployment wizard.
a.     Start Lync Server 2013 Media DVD. Refer Image 1.

b.     Time to Accept the License Agreement. Refer Image 3
c.      Now install Lync Server 2013, Core Components. Refer Image 2.

d.     Core Component installation progress.  Refer Image 4. 
e.     After core component installation open Lync Server deployment Wizard. Refer Image 5. 
a.     This is time to Prepare Active Directory.
Note: You must have Schema Admins and Enterprise Admin permission in order to prepare the Active Directory.
Step1: Prepare Schema. [Once per deployment]
Click on Run next to prepare Schema and it will start the Schema preparation for Lync Server 2013. This step will extend the schema and add the new classes and attributes.
Step2: Prepare Current Forest. [Once per deployment]
Click on Run next to Prepare Current Forest and it will start.
It will create global settings and Universal group for Lync server component.
Step3: Prepare Current Domain. [Once per Lync Server user or server domain]
It will set Access Control entries for Lync Server universal group.
Refer image 6 
b.     Again open Lync Server 2013 – Deployment Wizard and install Administrative Tools. Refer Image 7. 
Note- Best practices: Run the latest Lync Server 2013 Cumulative Updates.

c.      After Administrative tools installation, you will get Lync topology builder to build the topology.
1.     Download the existing topology and open the same. Refer Image8 
2.     Under Lync Server 2013 define the Lync front end pool name. refer Image9 
3.     Define Lync FE pool name. Refer Image10. 
4.     Add the Front End server FQDN. Refer Image11 
5.     Now time to define required role. We are defining all except EV (Enterprise Voice). Refer Image12 
6.     Check the "Enable an Edge pool to be used by the media component of this Front End pool" Option. Refer Image13 
7.     Next page define the SQL server FQDN and port number and use default instance. Refer Image14 
8.     Now time to add Mirror SQL server FQDN and select default instance. Refer Image15 
9.     Now time to ‘enable SQL Server Store mirroring’ it will show both SQL servers FQDN with default instance. Refer Image16. 
10.                        Next screen you have define the file store. Type the domain FQDN where you created file store and folder name. Refer Image17 
11.                        Next screen define the Web services URL. (Internal and external URL). Refer Image18 
12.                        Next screen define the Office Web App Server name and URLs. Refer Image19 
13.                        Next screen select Office Web App Server with Associate pool with an Office Web Apps server in central site. Refer image20 
14.                        Next screen define the Archiving SQL server store and Archiving SQL server store mirror. Refer image21. 
15.                        Next screen define the Monitoring SQL server store and Monitoring SQL server store mirror. Refer image22. 
16.                        Next screen select the Edge Server. We are migrating Lync Server 2010 to Lync Server 2013, here we are initially using legacy Edge server so select legacy edge server FQDN. Refer image23. 
17.                        Now Publish the Topology. Refer image24 
18.                        Now create database, select SQL server. Use SQL Server instance defaults. Refer image25. 
19.                        Now create mirror database and select the same. Refer image26. 
20.                        Now published the Topology. See the screenshot Image27. 
21.                        Topology Published. Refer Image28. 
22.                        After Lync topology published, Time to install Lync component on Front End Server. Open Lync Server 2013- Deployment Wizard and deploy the Lync Component. On Deployment Wizard, click on “Run” next to ‘Install Local Configuration Store’.
23.                        Next screen select option 'Retrieve directly from the Central Management store (requires read access to the Central Management store). Refer Image30. 
24.                        See the progress of Local configuration Store installation. Refer Image31. 
25.                        Lync Server components installation complete. Refer Image32. 
Note: It will install SQL express edition on FE server locally and ask for reboot.

26.                        Now time to 'Setup or Remove Lync Server Components'. Click on 'Run' button to start. Refer Image33. 
27.                        Next screen click on "Next" to install the components. Refer Image34. 
28.                        Next screen see the installation progress and see the components which are getting installed. Refer Image35. 
29.                        Next screen see the Installation get completed and "Finish" button shows to complete the installation. Refer Image36. 
30.                        Open Deployment Wizard and Step 2: is showing checked mark. Refer Image37. 
31.                        Again open Lync Deployment Wizard and Run the Step 3: to Order and assign Certificate for Lync Client-Server communication. Refer Image38.

Ordered the certificate: Installed both certificate Lyncauth and Lyncinternal certificate on server.
Once assign the certificate now certificate part shows green.

NOTE: As per Best practices-
                                                      o   To install Latest Cumulative Updates again to get all components updated.

o   Later Update the SQL database (Backend Server).

o   Now you can run Bootstraper.exe to make sure.

o   Later run the Start-CsWindowsServices to start all required services.

32.                        See the Image39 to show Lync Server 2013 services started.

Note: If your deployment has multiple Front End servers then install Lync components on all remaining front end server. In my deployment was two Front End Server.

Now Office Web Apps server Deployments

Web Office App server Installation:

Note: We are installing Office Web Apps server to Windows 2012 R2 Server.
1.     Install all prerequisite:
a.     .NET 4.5.2

2.     Download the Office Web Apps and unmounts the ISO image.
Before installation you must install all prerequisites.

3.     Open Windows PowerShell and run the following command to with Admin rights.
Import-Module ServerManager
Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-Core

4.     Open folder where you downloaded the Office Web Apps.

5.     Click on Setup executive files. Refer Image002 
6.     Next screen you must accept the license. Refer Image003. 
7.     Next screen you need to choose a file location. Refer Image004 
8.     You can see the Installation Progress. Refer Image005

9.     Next screen you see installation got completed. Refer Image006 
10.            Now it’s time to Install Service Pack 1 for Microsoft Office Web Apps Server (KB2880558) 64-Bit Edition and accept license. Refer Image007.

11.            Now you can see the installation progress. Refer Image008. 
12.            Next screen it shows installation completed. Refer Image009. 
13.            It’s time to configure internal and external farm URLs. Use below command to configure both Urls.

New-OfficeWebAppsFarm -InternalUrl "" -ExternalUrl "" -CertificateName "" -EditingEnabled

14.            Refer Image10 for better information. 
Thank you.

Monday, September 15, 2014

Consider below point before Office 365 rollout

Consider below point before Office 365 rollout:

Now most of planning for cloud solution because cloud solution is economically better than hosted services. Also no maintenance cost.
Office 365 is my got to solution and I am referring Office 365 to my current customer. It’s your choice…..
1.     Office 365 License plans and features.
Select the plan as per your requirement. Check the pricing before make decision.
a.     Office 365 Small Business      

b.     Office 365 Small Business Premium

c.      Office 365 Midsize Business 

2.     Internet Bandwidth :
Less bandwidth is always problem for synchronization.  Slow internet connection would make it impossible to upload Terabyte data per day to Microsoft’s data centers. Small organizations with lower bandwidth and a lot of data to move take longer to migrate from Exchange on-premises to O365. Without a high-speed connection, migration tools can help overcome this barrier by taking multiple passes over mailbox data before completing the actual cutover.
3.     Calming security fears:
Migration to O365 is a controlled process with safeguards in place to ensure data is secure both during and after the transition. Currently multiple big companies are using same solution. Microsoft improves security drastically.  E.g. MS is agreeable to signing liability paper related to specific compliance issues e.g. HIPPA. 

4.     Journaling will not work:
Issue that may come up is that journaling for compliance no longer works after migration to Office 365. 

5.     Existing Email Archiving doesn’t work:
Archive tool simply doesn't work (or work well) with Office 365. You move the mailbox to the cloud, which breaks the stubs, so users can't access those archived emails. Basically Microsoft providing good amount of data storage for Mailbox, SharePoint etc. may you not worried about archiving however what about old data.  

6.     The recipient rate limit per day 10000 (email send / receive limit).

Workaround: If you want to send email to over 10000 recipient then add recipient to distribution list and then send email. 

7.      There are no public folders in Office 365. Yes, it’s time to move to SharePoint. SharePoint is better choice than Public folder. 

8.     User get 10 GB of space plus 500 MB per user of shared storage.

9.     No choice for Spam filter- Because Microsoft using Microsoft Forefront Online Protection for Exchange for Office 365. 

10.  By default gets email addresses. Outbound and inbound email domain changes are possible.

11.  DNS setup is difficult if customer has other than Microsoft DNS server. Like Linux DNS server. 

12.   You may need to reset file server permission, if you are planning outsource Active Directory. Because some point you have decommission the Domain Controller. 

Thank you. 

Curtesy: MS O365 docs, 10 things you should know….