Wednesday, March 19, 2014

Operations started by an earlier run of the farm configuration wizard are still in progress

Operations started by an earlier run of the farm configuration wizard are still in progress

“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.”
If we click on “Launch the Farm configuration wizard” in central administration will see the error                               


Cause: This issue will occur some times when we try to open the central administration after running the PSConfig.exe completes. The reason behind this is After the PSConfig completes, still  there are some tasks that are running. We can wait for some time or we can close the existing browser and open Central admin in another browser to work. If still not work, then follow the below steps to avoid the error.

If you want to avoid the error message you will need to delete the Job Definition for the Farm Configuration Wizard.

1.    Go to – Central Administration > Monitoring > Review Job Definitions

2.    Find the “Farm configuration wizard” job definition
3.    Click on the job, you can see the below screen. Delete the job by clicking on delete option   

4.    Do IISRESET if required

5.    Once delete the job you can see the Wizard page and you should see the  farm configuration wizard

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Trend Micro Antivirus Installation for SharePoint 2013

Trend Micro Antivirus Installation for SharePoint 2013

As I mentioned in my previous article, Trend Micro supports the SharePoint 2013.see the details of which Antivirus supports SharePoint in below.

I am giving the detailed installation steps for the trend micro PP for SharePoint. can get the PP(portal protect) from the below site.

Installation Steps:

1.   Ensure that the PP downloaded properly

2.   Double click on the PP and wait for the extraction to complete

3.   Click on Next

4.   Accept the Terms in License agreement 

5.   Choose the installation as depends on your farm, If it’s a Standalone server, choose the first, If it’s a farm environment(SP servers are more than 1) choose option 2. I am choosing as standalone server

6.   Click next

7.   Provide the Activation code(License code) as got from Trend Micro. Once provided Click on next

8.   We see a warning, ignore this message and proceed with “Ok”

9.   Select Install to local servers and click next

10. Choose the path as you required, if you want ,you can specify the different path where files need to store, click next
11.   Choose the Port number and select SSL if you have configured SSL. Click Next
12.       Select the SharePoint SQL server and provided the details of SQL server, Username and password. click on next

Note: The user name that you select, recommends Farm Admin account and have DB creator and DB owner permissions.
13.       Click on Next once provided all the details

14.       Select Use Local server Administrator Group, Click on Next

Note: the Account your using for the installation must be in Local server Administrator group                  

15.If you want to get the updates Directly from Internet Choose the Proxy server and provide the details, If you are willing to get the Updated from other central Trend micro server, not required to choose the option. I select None in this. Click on next once selected the option                              

16.       Select NO,I don’t want to participate(depends on your choice)click on next
17.       Select Register Portal protect agent to control manager server if you have central Trend micro server and get updates from there.

18.       Choose Connect using HTTPS, if you’re using SSL in your farm, click next

Note: Web Server Authentication is not necessary

19.       Specify SMTP settings if you  have PP central server. Configuration of a SMTP-Server at this point is only necessary if no central TMCM-Server is available in your network. Click Next

20.       Click Install

21.       The installation will start

            22.   Click on Next once Installation done
  23.   Click Finish to complete the installation

Post-Installation Steps

Trend Micro is successfully installed in SP server, now we need to connect to trend micro with SharePoint to Monitor. Follow the below steps to achieve this.

1.   Go to programs->portal protect management console

2.   Logon with local Administrator Account,Enable Two Way Communication Port Forwarding                                

3.   Enable Two Way Communication Port Forwarding
                                                 i.    Open menu “Administration>Control Manager Settings”
                                                ii.    Enable option „Enable two-way communication port forwarding“
                                               iii.    Enter IP address “IP address”
                                              iv.    Enter “16373” as “Port”
                                               v.    Save configuration with button “Update Settings”

SharePoint settings:

The SP settings also must enable for antivirus to monitor. Follow the below steps to do so.

1.   Central Administration->Security->Manage antivirus settings
2.   The options should be enabled as per requirements.

 Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Tuesday, March 18, 2014

Antivirus For SharePoint

Antivirus For SharePoint   
Recently, we have a requirement to do antivirus for our Satellite 2013 farms. For the reason, when I am checking and digging the information I come to know so much of valid information regarding Antivirus that supports SharePoint 2013.I find the information in Bits and pieces,putting altogether in one place for easy understanding and access.please find the details below.

1.   Forefront Protection for SharePoint 2010

This still will work  fine with SharePoint 2013. However as the product is discontinued, If you already have it, it will continue to be supported until December 31st 2015. You will receive AV definition updates until that date as well. After that you need to migrate to some other AV.

2.   AvePoint DocAve Antivirus for SharePoint

This product is discontinued. There is no option to choose this.  

3.   Trend Micro Portal Protect

This supports the SharePoint 2013.Trend Micro released Portal Protect SharePoint Security with SharePoint 2013 support:

4.   Bit Defender

This product is discontinued. There is no option to choose this. This one is not supported for SharePoint 2013.check the Details on below. Requirements

5.   Symantec Protection for SharePoint

This supports the SharePoint 2013.find the details below. Released Portal Protect SharePoint Security with SharePoint 2013 support

6.   McAfee Security for SharePoint

This supports the SharePoint 2013.McAfee updated Security for SharePoint with SharePoint 2013 support:

7.   Kapersky Security for SharePoint Server

This supports the SharePoint 2013.Kapersky Security supports SharePoint 2013.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

User profile synchronization service shows starting for long time

User profile synchronization service shows starting for long time

There could be many reasons for the service is in struck and shows starting only. .Why does it get stuck? Well, 15 provisioning runs will be attempted before it gives up. When we hit Start in Services in Server a series of tasks are run, which are to running the second stage of the Forefront Identity Manager setup. Those include things like setting up certificates, windows services, installing database schemas so on. If something is incorrect, it will try all tasks again, and more often than not, fail the service to start. That’s why it appears to be “stuck” when in fact its attempting each of the runs. Of course this can take a while, hence the appearance of being “stuck”. After around 20 to 45 minutes the status will return to Stopped, and you can attempt to start it again.

In some cases, the status will remain as “Starting” even after reboots. In this case something very bad has happened and you are best off throwing away the UPA service application and starting over.

You can however, manually start things back to the state before the starting of the UPS service instance. This can be necessary in some cases, but again, I strongly recommend you start clean by deleting and recreating the UPA. Before Re-creating the Service application ensure that all the below steps tried.

·        Ensure to restart the user profile service and synchronization service
·        Ensure to restart the FIM services
·        Ensure to do IISReset after the services starts
·        Ensure to reboot the server
·        Ensure to have the available space on DB server and SP server.

If all done but still issues not resolved, then try to Delete the Existing UPA service Application and create the new one and check the status.

To find the Error details,Please follow the below.

Browse to the location "C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell" and run miisclient.exe .it will show the actual error message which was causing the issue.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, March 17, 2014

SharePoint Roles

SharePoint Roles:

I am sharing this very simple Topic, because many of the Administrators want to know the difference and the responsibilities.

Owner:  Owner has a complete control over site, list, library and other content placed on site.

Designer: Users having designer role limited to certain activities. User can view, add, update, delete and approve content. Users can even customize the things, they have access to.

Editor: Editor role users are not allowed to customize site design or content. Users can add, edit, update and delete content from the site.

Contributor: Very limited role. They can delete content items which they have created but not by other.

Reader: Users are only allowed to view the content of site. Users are assigned to Reader roles can download and edit the content but cannot save it back on SharePoint site.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!