Sharepoint 2010 on Windows server 2012r2-24x7 Supported by Cognosys

My main use case for Sharepoint 2010 on Windows server 2012r2-24x7 is updating a company intranet, and I have been using Sharepoint for many companies. I worked in a banking company, a healthcare company, a manufacturing company, and for all of those I used Sharepoint 2010 on Windows server 2012r2-24x7 as a company intranet page. That page consists of many organizational charts.

I use Sharepoint 2010 on Windows server 2012r2-24x7 specifically for a long-term project where I need to assess the list and the document library. There is one project, a big SAP-related project, where we have multiple timelines: the initiation, requirement gathering, development, UAT, and go live. We have collected a document library for each folder and then added whatever the file update, UAT script, or everything, serving as a repository. We have created a status and multiple metadata, including a status report or whose assignment it is, who is working on it, and how much it is completed, along with red, green, and blue buttons. Basically, that is one thing where I use Sharepoint 2010 on Windows server 2012r2-24x7 as a repository.

I have created a support website for Sharepoint 2010 on Windows server 2012r2-24x7. This website primarily serves as a Sharepoint support hub, where I created a form for enhancement, bug fix, update, or issue. This is sent to the entire company, and the entire company uses that form. We use that log report and have weekly meetings on top of that to discuss how much work is in our queue and how much work is done. We then send a weekly report to our management about what has been achieved and what is in the pipeline. So, that was one of the very interesting projects I have created on Sharepoint 2010 on Windows server 2012r2-24x7.

Workflow in Sharepoint 2010 on Windows server 2012r2-24x7 has helped my teams by using it for Sharepoint access request forms. The workflow I use involves submission, and when the submission happens, there is an approval of the form. Approval goes to the manager, and once he approves it, it goes to the next phase. For final acceptance, we send it to an end user so he can check mark on it or indicate that the work is done. These are the approval processes we utilize, including out-of-the-box email approval and alerts sent by the system.

Sharepoint 2010 on Windows server 2012r2-24x7 has saved time and improved productivity by enabling cost-saving measures. When using one place for all documents, your team can see everything in the latest mode. All they need to do is click the link to access the same place, and follow-up conversations occur on the same page. It definitely saves a lot of time and energy for teams, allowing them to focus less on email exchanges and more on project tasks.

Sharepoint 2010 on Windows server 2012r2-24x7 has positively impacted my organization by providing very good collaboration capability. It includes a list, calendar, permissions, and everything that works great for everyone. It offers one centralized place, so there is no need to configure or go to multiple places looking for the same information. Once I update information, everybody syncs on the same data. It also enables tracking changes, restoring previous versions, maintaining document history, and sharing team calendars, organizing the same vision with different kinds of access. This feature definitely contributes to good progress in teams, making it very useful for any organization.

Best features Sharepoint 2010 on Windows server 2012r2-24x7 offers include a list and permission capability, team collaboration capability, workflow and approval process capability. All of these capabilities are fantastic, including version control and permission-based access, providing one centralized place where everybody can see everything and update it. If we need to revert back, version control is there, and we can see how much use case it is. It is very efficient for business users. I am a Sharepoint user for a long time, so all of those features are fantastic.

Sharepoint 2010 on Windows server 2012r2-24x7 can be improved, particularly since Windows 2010 on R2 server is no longer supported by Microsoft. It still serves the same features, but we can definitely improve the search feature, which should crawl every page and every list to retrieve data. Additionally, mobile support has limitations for this Windows 2010 R2. Automation does not work 100 percent either; it does not seem perfectly integrated. Enhancements in integration with M365, including native apps such as Teams, OneDrive, and Power Apps, are other areas for improvement.

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for almost fifteen to twenty years. Initially, I used Sharepoint 2010 for many years. I do not remember exactly how many, but recently I am using Sharepoint Online. However, I recently used Sharepoint 2010 on Windows server 2012r2-24x7 for some special project where my friends needed my help with that. So that is my recent experience, within six months.

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

From a scalability perspective, Sharepoint 2010 on Windows server 2012r2-24x7 is good for its time, around seven to ten years, particularly for mid-sized organizations. However, for large organizations, I would recommend Sharepoint Online or cloud-based solutions as better options. For smaller use cases related to document libraries, workflows, and resources, it is adequate.

Customer support has not been extensively used by me, but I do know a go-to person for assistance. Sharepoint 2010 on Windows server 2012r2-24x7 is in an end-of-support era, so there is very limited customer support available.

I have not used any solution other than this, just homegrown solutions, including maybe an Excel sheet, which were not useful at all.

I do not have specific numbers regarding return on investment, but I can tell you that the processes that could be delayed due to ineffective collaboration could take six months to complete. With Sharepoint 2010 on Windows server 2012r2-24x7, the collaboration, versioning control, and data accuracy improved, allowing us to finish the project in just one month or two instead of six. This signifies a potential saving of four months worth of time and salary for the same project.

I did not evaluate other options before choosing Sharepoint 2010 on Windows server 2012r2-24x7. However, I was aware of Sharepoint's capabilities beforehand. Many people use Google Workspace, which can be useful, but I prefer Sharepoint 2010 on Windows server 2012r2-24x7 because I am very familiar with it. I know how to control the web parts and permissions, so I prefer using this one.

Governance and security in Sharepoint 2010 on Windows server 2012r2-24x7 are similar to those in other Sharepoint versions.

If your company is mid-sized or small and does not require complicated data management, Sharepoint 2010 on Windows server 2012r2-24x7 could be a way to go.

I would not put much pressure on recommending Sharepoint 2010 on Windows server 2012r2-24x7 to a company, considering cloud-based alternatives with better features. While security and other aspects do not present issues, the better alternatives in the market should be considered. If you are currently using it, continue using it, but you do not need to go ahead and buy a new one. I gave this review a rating of seven out of ten.

One of the main use cases for Sharepoint 2010 on Windows server 2012r2-24x7 is to store all the documents in one place in a centralized location, collaborate with my other team members and stakeholders, edit, and create new folders. Additionally, I connect that to Power BI to generate dashboards, and I use that as my central repository.

Collaboration with my team using Sharepoint 2010 on Windows server 2012r2-24x7 is mainly through document editing, but not limited to just that. I upload many documents to Sharepoint, whether it is a Word document, an Excel spreadsheet, or a PDF. The way I collaborate is that other team members or stakeholders come in, they comment, they review it, there is back and forth conversation, we add comments, and we do the version control for these documents.

One of the unique things about my main use case for Sharepoint 2010 on Windows server 2012r2-24x7 is that we have many documents, and I connect that to the Power BI dashboard to generate interactive visual reporting and dashboards.

The best features Sharepoint 2010 on Windows server 2012r2-24x7 offers are the centralized location that enables collaboration with the larger team that I work with.

The search functionality works great in Sharepoint 2010 on Windows server 2012r2-24x7 because I have a ton of documents, and it helps me search quickly. Sometimes I can use searches at the column level to filter the documents instead of using the global search. I can filter by date and by other kinds of formats, so that works great for me. Permissions are also a great feature because we all have role-based access level permissions, ensuring that not everyone gets to view every document. I can ensure that a specific set of team members can view only certain documents or have edit, comment, and viewing permissions, which works really well. Workflow automation is something I use a lot; I use it to create forms. I automate the Sharepoint list with Power BI integration, and that works as well.

Sharepoint 2010 on Windows server 2012r2-24x7 has definitely impacted my organization positively because now we don't have to manually create folder structures in our local desktops. Everyone can view at one place at one time, so all the online copies are there and that opens on desktop as well as the mobile version. Specific outcomes include faster access to the files instead of spending tedious amounts of time just looking for them. Time saved is definitely one of the metrics I would say, and I am able to input keywords for them for easy retrieval, so that works well.

With the wave of AI, I would love to see more AI tools that can be integrated within Sharepoint 2010 on Windows server 2012r2-24x7. Integrating Copilot within Sharepoint would help me understand a specific use case. For example, if there is a folder that has ten files in it, and as a first-time user, I do not have the time to go into each of these documents to understand them. If Copilot could read these documents and provide a summary or a synopsis, that would be great.

I would like to see more of AI's analytics and observations come into Sharepoint 2010 on Windows server 2012r2-24x7, particularly regarding user interface, speed, or integration with other tools.

Although I'm really happy with the current way Sharepoint 2010 on Windows server 2012r2-24x7 works, I think there is still room for some improvement, enhancement, and refinement in its accuracy and reliability of output.

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for about four to five years now.

I find Sharepoint 2010 on Windows server 2012r2-24x7 stable when I'm using it.

I am confident about Sharepoint 2010 on Windows server 2012r2-24x7's scalability at my organization since it is a large organization, and we have not had any showstopper issues.

The customer support for Sharepoint 2010 on Windows server 2012r2-24x7 has been great; it has been a positive experience. I would rate the customer support for Sharepoint 2010 on Windows server 2012r2-24x7 an eight out of ten.

There was no different solution I used before Sharepoint 2010 on Windows server 2012r2-24x7.

I have definitely seen a return on investment with Sharepoint 2010 on Windows server 2012r2-24x7. Earlier, we used to keep all the files on our local desktop, which caused a lot of friction and time loss when collaborating. Now, we can work and share live documents; they can see the real-time changes being made, and we can even get on a meeting and work on the document at the same time. Relevant metrics would include money and time saved, which is significant. However, I cannot provide specifics about fewer employees needed or how much money we saved, but considering time is money, I believe time has been saved.

I really use Sharepoint 2010 on Windows server 2012r2-24x7 for my day-to-day activities in my project, so I am not sure about the pricing, setup cost, and licensing details as the IT team in my organization handles it.

Before choosing Sharepoint 2010 on Windows server 2012r2-24x7, we did not evaluate any other options, as it was always Sharepoint.

For those looking into using Sharepoint 2010 on Windows server 2012r2-24x7, I would highly recommend going through the user manual or the training guides that Microsoft Sharepoint has published on their community page, as they help give a good sense of understanding about the features before starting.

My additional thoughts about Sharepoint 2010 on Windows server 2012r2-24x7 would be to bring in more AI capabilities into it and integrate it with other outside applications, such as Jira or project management tools. I would also love if Sharepoint could be integrated into other CRMs as well to ensure that the entire ecosystem works well for anyone working on a large project. I would rate this review a seven out of ten.

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.