Collaboration between team members, work lists and item lists, and data export are my main use cases for Sharepoint 2010 on Windows server 2012r2-24x7. There are some Sharepoint custom apps that have been created as well.

Regarding collaboration in Sharepoint 2010 on Windows server 2012r2-24x7, messages are passed between team members through posts and replies to track progress on different work items. For the custom apps, one in particular was created for the MRI department where a custom list was established so users could request access. It is called badge request access, and there is a workflow for approval by senior staff.

The main use cases in Sharepoint 2010 on Windows server 2012r2-24x7 have been primarily for custom apps for different access requests, particularly the previously mentioned badge access application and for requesting access to other resources. Different Sharepoint groups were controlled through Active Directory, and information for each separate team was controlled by access through Active Directory.

I appreciate the way Sharepoint 2010 on Windows server 2012r2-24x7 allows you to set up workflows. The custom apps were particularly useful. Without the simplicity of creating these custom workflows in Sharepoint 2010 on Windows server 2012r2-24x7, I would have had to write custom applications, which obviously would have taken more time and effort for such a simple need.

There is definitely an improved turnaround because of using Sharepoint 2010 on Windows server 2012r2-24x7. Because the workflow is automated, any effort made to share files with people was reduced to virtually zero since they are automatically granted access to resources or by submitting their request for access. Instead of a user or staff member having to manually email files or provide links, they simply clicked a button to approve access. This greatly improved efficiency and reduced the time to provide that information, especially when it was automatic where there was no human intervention required, just Active Directory control.

The collaboration in Sharepoint 2010 on Windows server 2012r2-24x7 has been extremely helpful. I am not sure how we would share some of these resources as easily with another solution, especially being able to control who can access what at different levels and who can edit which files, who can upload, and who can see different things. This has been very useful.

Documentation for Sharepoint 2010 on Windows server 2012r2-24x7 can be improved. Sometimes when it came to finding certain features or when I had not done something in a while and could not remember it, I found it challenging to locate those instructions. The help section and support for Sharepoint was very lacking. Sometimes it would have been quicker to search outside of Microsoft or Sharepoint and use Google, or even find a YouTube video that explained how to do something, which should not be necessary for a Microsoft product that we pay for.

Better documentation for Sharepoint 2010 on Windows server 2012r2-24x7 would be beneficial, along with easier searchability for features and more refined how-to guides. I found it frustrating to discover how to do simple things, especially when it was something I only did a couple of times a year, so I would not remember it, and it would take considerable time to rediscover those features. I ended up having to create my own documentation on instructions for how to do some of these uncommon tasks. Microsoft should have better documentation, better help, and better how-to guides, even for the simple things.

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for over a decade now.

Sharepoint 2010 on Windows server 2012r2-24x7 is stable in my experience. I can only think of a few minor issues, which were more hardware related than software.

We did not have any problem scaling Sharepoint 2010 on Windows server 2012r2-24x7. We increased the memory and storage with no issues whatsoever. That was one of the reasons for the recent upgrade because there was limited space, and we did not experience any issues. It worked great.

I personally did not have to reach out to customer support for Sharepoint 2010 on Windows server 2012r2-24x7, but I know some of my colleagues did. I am aware there were some frustrations, but overall, I think it was very satisfactory. They got good results and everything is working, so it turned out okay.

My result with Sharepoint 2010 on Windows server 2012r2-24x7 has been pretty positive. I am not sure if anybody would be looking to jump to Sharepoint 2010 at this point if they are not already using it, especially since it is no longer supported since 2021. However, anyone coming into an environment that already had it implemented would find that it will go well, and I would encourage them to use it.

Sharepoint 2010 on Windows server 2012r2-24x7 has been a very successful program for Microsoft. I first started using Sharepoint when it was the 2007 version and moved to 2010. I cannot say that I have any negative impressions of it. I recommend any company use it as they will benefit from it. I would rate this solution an 8 out of 10.

I use Sharepoint 2010 on Windows server 2012r2-24x7 to automate paperwork using workflows, share documents between users, and create forms using Sharepoint lists while automating these forms with workflows.

An example of a process I automated with Sharepoint workflows is the petty cash form, where users fill it out for approval from their manager, which then gets sent to finance for review, CFO approval, and notifications are sent to the user at each step.

I use Sharepoint 2010 on Windows server 2012r2-24x7 as a shared folder, so anyone who would want to share anything with other teams or on their team can use it as a shared folder.

In my experience, the best feature Sharepoint 2010 on Windows server 2012r2-24x7 offers is the workflow, as it can be used to automate any kind of forms or any kind of paperwork that requires multiple approvals.

The workflow feature specifically helped my team by not only improving efficiency but also impacting our costs, as it saved on printer, paper, and ink consumption while allowing managers to approve requests from anywhere at any time.

Sharepoint 2010 on Windows server 2012r2-24x7 positively impacts my organization overall through time-saving, cost reduction, and improved collaboration, particularly by eliminating delays for approvals when managers are not on-site.

Regarding improvements for Sharepoint 2010 on Windows server 2012r2-24x7, I found that while it provides flexibility through Sharepoint Designer for creating workflows, there are limitations where I have to write code rather than using the GUI itself.

In my current field, which is IT, I have been working since 2004, which is around 20 to 22 years.

Sharepoint 2010 on Windows server 2012r2-24x7 is stable.

On a scale, I would say Sharepoint 2010 on Windows server 2012r2-24x7 scalability is about 8 or 9.

My experience with customer support for Sharepoint 2010 on Windows server 2012r2-24x7 is positive, as I did not have to contact Microsoft support.

We have previously used a built-in application because we had developers who were trying to build a custom workflow system to circulate paperwork.

I have seen a return on investment as I have been involved in each department to help automate at least one paperwork, even though I do not have exact numbers or specific metrics to share.

My experience with pricing, setup cost, and licensing is that it is reasonable.

Before choosing Sharepoint 2010 on Windows server 2012r2-24x7, I did not evaluate other options because we were already working with Microsoft products, so I decided to go with that.

I estimate that moving to Sharepoint workflows saves around 30 percent of costs, especially in paper, printer, and ink consumption.

I gave Sharepoint 2010 on Windows server 2012r2-24x7 an eight out of ten because there are some limitations in workflow cases where I have to write code instead of relying solely on the GUI.

My advice to others looking into using Sharepoint 2010 on Windows server 2012r2-24x7 is that if they want to save money, save time, and automate their paperwork, this is one of the best workflow cycles or applications they can use for customizable workflow approval cycles. I rate this solution at eight out of ten.