Pages

Monday, October 27, 2014

Enable Blog and Team site templates in publishing Site Collection

Enable Blog and Team site templates in publishing Site Collection

Follow below steps to enable the blogs and Team Site template:

1. Go to Site collection site settings ->Page Layout and Site Template Settings under Look and feel

      image

2. Under Sub site template, add Blogs and Team Site entries

      image

3. Click Save the settings once you added

Wednesday, February 26, 2014

Install and configure workflow Manager1.0 for SharePoint server 2013

Install and configure workflow Manager1.0 for SharePoint server 2013

Download the Workflow Manager 1.0 and Workflow Manager Client from the Microsoft Site. Once you downloaded run the Workflow Manager 1.0 on one of the Application SharePoint Server.

NOTE: install Workflow Manager Client all the SharePoint Web Front Servers.

1. Run the setup file and click continue to finish the installation.

clip_image002

clip_image004

clip_image006

clip_image008

2. Run the Workflow Manager configuration Wizard using Recommended setup once you installed and Provide the below information and click Next

2a. Provide SQL Instance

2b. Provide Workflow Service Account

2c. enable “Allow Workflow Management over HTTP on this computer”

2d. Provide “Certification key”

clip_image010

3. Click Apply to finish the workflow configuration.

clip_image012

4. Register Workflow with SharePoint using HTTP over communication.

Register-SPWorkflowService –SPSite http://yoursharepointsite –WorkflowHostUri http://workflowhosturl:12291 –AllowOAuthHttp

Or

5. Register Workflow with SharePoint using HTTPS over communication

Register-SPWorkflowService –SPSite http://yoursharepointsite –WorkflowHostUri http://workflowhosturl:12290 –AllowOAuthHttp

Create and deploy AlwaysOn in SQL server 2012

Creating AlwaysOn in SQL server 2012

I would like to share one of the main feature of SQL server 2012 AlwaysOn Availability Group.I have implemented in SharePoint 2013 production environment for disaster recovery which works awesome.

Using AlwaysOn High Availability you can keep multiple copies of your databases in different location for disaster recovery and also it’s allows take backup in Secondary replication location as well.

There are two level fail over options available such as manual failover and Automatic failover which we can achieve if primary Server is down.

To configure AlwaysOn availability Group, follow the below steps

  • · Install and configure windows failover clustering
  • · Install same version of SQL Instance on Primary and Secondary Servers
  • · Enable Always On Availability Group in SQL
  • · Create Always on Availability Group for your databases

1. Install and configure windows failover clustering

    image

    image

    image

     image

      image

      image

     image

      image

        image

         image

         image

         image

         image

2. Enable “Always On Availability Groups” in SQL the instance on all the Servers(Primary and Secondary)

image

3. Create new availability Group on the Primary Sql Server after you enable availability Group.

   image

     image

       image

      image

        image

         image

         image

       image 

          image

            image

4. Once you created and configured the AAG group, Now you could see the database available in the Secondary Server as synchronized

image

Thursday, February 6, 2014

New Switch Plan in office 365 without Migration

Microsoft Announced new switching plan which is very good for all business people who wants to change the Office 365 plan from Small business to Mid-Size or Enterprise Plans based on their requirement without migration from old tenant to new tenant.


Plans Eligible table is below

From plan
To plan
Office 365 Small Business
Office 365 Small Business Premium
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Small Business Premium
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Midsize Business
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise K1
Office 365 Enterprise K2
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise E3
Office 365 Enterprise E4
Lync Online (Plan 1)
Lync Online (Plan 2)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Lync Online (Plan 3)
Office 365 Enterprise E4
SharePoint Online (Plan 1)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
SharePoint Online (Plan 2)
Office 365 Enterprise E3
Office 365 Enterprise E4
Exchange Online (Plan 1)
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Exchange Online (Plan 2)
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Education A1
Office 365 Education A2
Office 365 Education A3
Office 365 Education A2
Office 365 Education A3
Office Web Apps with SharePoint Online Plan 1 or Plan 2
Office 365 Education A1
Office 365 Education A2
Office 365 Education A3
Office 365 Education A4
Exchange Online Kiosk
Office 365 Enterprise E1
Office 365 Enterprise E3
Office 365 Enterprise E4
Office 365 Enterprise K1
Exchange Online Plan 1
Exchange Online Plan 2

Wednesday, February 5, 2014

Operations Started by an earlier run of the farm configuration Wizard are still in progress

I ran the configuration Wizard to configure SharePoint workflow service in sharepoint 2013 and finally got some request time out. so again I was tried to reran the configuration and got the following error message in the central admin site page "Operations Started by an earlier run of the farm configuration Wizard are still in progress. you must wait for those operations to complete before running the wizard again. you can monitor the status of these operations by looking at the "Farm configuration Wizard" timer job on the timer job status page in the monitoring section of central administration"

For the above error message I was tried the below steps to solve this issue.
1. go to monitoring-> timer job definitions
2. find "Farm configuration Wizard" and delete that timer job