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

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for about two years.

My main use case for Sharepoint 2010 on Windows server 2012r2-24x7 is to store documentation, images, and marketing materials, as well as using the planner as a Scrum board.

A specific example of how I use it for storing documentation or as a Scrum board is that the planner board we use to create stories on projects that the team will be working on, as well as assigning to individuals for specific topics that they will be handling and to be able to track the progression of where the project is. When we hold our daily stand-ups, we can go through the board quickly and everyone can discuss what is going on and if they have any hold-ups. Since we're a small company, we did not want to invest in a Jira board, and the planner board works out perfectly for us since we also use Sharepoint 2010 on Windows server 2012r2-24x7 to store all of our documentations and organize our marketing materials and images.

Sharepoint 2010 on Windows server 2012r2-24x7 offers the ability to send an email when you update an area if you want to tag somebody in it or they're already tagged in an area, and I also appreciate that the link is easy to copy and paste in Slack for the team to go directly to Sharepoint 2010 on Windows server 2012r2-24x7 to see what you've created and give it a review and edit it there.

I also value the permissions feature, so once a document is done, you can lock it and people can view it and share it, but it cannot be manipulated or changed if you are the owner of it. The integration with the planner tools is really helpful, allowing our team to use Sharepoint 2010 on Windows server 2012r2-24x7 in an agile way.

Sharepoint 2010 on Windows server 2012r2-24x7 has positively impacted our organization by keeping us organized, allowing us to share our documentation with clients, and helping our team review things in a timely fashion. I have noticed specific outcomes, such as fewer mistakes because we have documents that we can lock down and not have to worry about a client changing anything when we're making a deal.

I think Sharepoint 2010 on Windows server 2012r2-24x7 could be improved if the planner section had more features instead of the limited buckets such as in progress, complete, and future backlog. It would be beneficial to have options to indicate if you are held up and waiting for somebody else, so that they are tagged in that instead of having to write it in the comments, which would keep the status accurate on the project.

Regarding needed improvements, I think the interface can always be improved with AI. Everything can have a more modern appearance, and I think overall, brighter colors and faster speed would help with Sharepoint 2010 on Windows server 2012r2-24x7.

Sharepoint 2010 on Windows server 2012r2-24x7 appears to be stable.

As for scalability, as our usage increases and our team fluctuates, we have never encountered an issue. We can quickly add a user, get them set up, and access is never a problem. It is equally easy to remove somebody.

Customer support can sometimes involve long phone calls on hold if you call in directly. It would be beneficial if there was an AI option where you can get in contact with somebody much quicker instead of having to call.

I would rate customer support a seven, as once you finally speak to somebody, they are very knowledgeable and capable of helping you resolve the issue. However, the wait time to actually talk to someone is not that great.

I have not previously used a different solution.

While I do not have specific metrics, I can say that time is saved because of how easily we are able to create a planner board, save documents, and share them with our partners and clients. As a small group, we have a controlled environment for our documentation and marketing images, allowing us to quickly access them.

Regarding my experience with pricing, setup cost, and licensing, I do not handle that directly. I know we have a small team, and I'm assuming that our CEO finds the cost to be acceptable because we have been continuing to use it for two years.

Before choosing Sharepoint 2010 on Windows server 2012r2-24x7, we did not evaluate other options. The company only wanted Microsoft Office.

For others looking into using Sharepoint 2010 on Windows server 2012r2-24x7, I think it is a wonderful tool for a small team just starting in a startup, as well as for a large team, since there are many documentations that companies have. Sharepoint 2010 on Windows server 2012r2-24x7 helps organize them in a way that suits your needs and your company's needs. Additionally, there are other features if you do not want to buy additional applications that you can use similarly in Sharepoint 2010 on Windows server 2012r2-24x7, which is how we found the planner. I would rate this product a nine overall.

My main use case for Sharepoint 2010 on Windows server 2012r2-24x7 has been as an internal company intranet, serving as a repository for all our forms, procedures, and documents, as well as providing daily news and a monthly focus on a particular person. Primarily, it is the main company portal for all news, including how people submit expense reimbursements or apply for leave, making it the home place for all the company's internal forms and processes.

Before using Sharepoint 2010 on Windows server 2012r2-24x7, my team handled submitting forms and sharing news through shared file shares that were scattered across different locations, leading to issues such as misplaced files. News was primarily shared via email, creating a chaotic environment where new employees struggled to locate necessary documents, which became streamlined once we transitioned to Sharepoint 2010 on Windows server 2012r2-24x7.

Sharepoint 2010 on Windows server 2012r2-24x7 has positively impacted our organization by consolidating all company forms and documents into a single repository, creating a great intranet that avoids the issues of scattered file shares and email communications. Setting the intranet as a homepage ensured that everyone had easy access to news and forms.

The best features Sharepoint 2010 on Windows server 2012r2-24x7 offers include a new Fluent ribbon-type interface that modernizes the look, making it more compatible with the changes in Office and still favored by Microsoft today, along with facilities for managing metadata. It also introduces Office Web Apps, allowing for direct editing of Word, Excel, and PowerPoint documents in the browser, which wasn't possible in previous versions, enhancing usability and collaboration capabilities.

My team responded positively to these changes, finding that collaboration improved significantly, as we previously faced constant complaints about locked Excel spreadsheets on file shares. The ability for multiple people to edit documents in Sharepoint 2010 on Windows server 2012r2-24x7 simultaneously transformed how we worked, as it eliminated the frustrations of file locking, making daily tasks much easier.

Regarding potential improvements for Sharepoint 2010 on Windows server 2012r2-24x7, I note that both products, including the server version, are out of support, so ideally, there should be extended long-term support for security fixes. For most users, I would recommend transitioning to a newer Sharepoint version or using the managed Sharepoint available in Office 365.

If I could change anything about Sharepoint 2010 on Windows server 2012r2-24x7, I sometimes wish it were as user-friendly as Lotus Notes, but overall, it was a great innovation that made Sharepoint more usable than previous versions.

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for about ten years.

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

Sharepoint 2010 on Windows server 2012r2-24x7 was scalable. You could add extra Sharepoint nodes into a cluster, host data on a SAN or NAS, and utilize additional Windows servers in Sharepoint 2010 on Windows server 2012r2-24x7 environment.

We never used customer support, but it was provided by Microsoft, which could be a hit or miss depending on the engineer's expertise.

We did not have a sophisticated solution before. We relied on file shares and email, which were unstructured and unorganized, prompting us to switch to Sharepoint 2010 on Windows server 2012r2-24x7.

I cannot recall specifics, but licensing was not a major issue at the time, and I believe Sharepoint 2010 on Windows server 2012r2-24x7 was available with Windows Server at no extra cost. We did bring in a consultant to help set up the intranet and provide best practice guidance, but apart from that, I do not remember any pricing issues.

While I do not have specific metrics, I can state that Sharepoint 2010 on Windows server 2012r2-24x7 led to significant time savings, particularly in collaboration, finding information, and onboarding new employees, but it did not directly affect our headcount or profitability.

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

We experienced a learning curve as we had little prior experience with Sharepoint 2010 on Windows server 2012r2-24x7, except for simple file repository use, which made managing permissions and creating a more attractive Sharepoint page a bit challenging for us.

My advice for others considering Sharepoint 2010 on Windows server 2012r2-24x7 is to assess whether they will connect their machine to the internet, as it is no longer supported and lacks security patches. If they already have the necessary hardware and licenses and prefer to avoid subscription fees, it is still a stable solution with plenty of resources available.

I would rate this product an eight overall.

My main use case for Sharepoint 2010 on Windows server 2012r2-24x7 is storing and backing up files from endpoint devices while sharing files securely across users.

The best features Sharepoint 2010 on Windows server 2012r2-24x7 offers include an audit feature and the ability to maintain a backup of all files remotely by an administrator.

Sharepoint 2010 on Windows server 2012r2-24x7 has positively impacted my organization by giving all users a backup, and whenever there are endpoint changes, they can easily switch over.

Sharepoint 2010 on Windows server 2012r2-24x7 can be improved by combining it with some other features, such as the ability to restrict a single file by an administrator.

That would be the feature that we can add to improve the product.

I have been using Sharepoint 2010 on Windows server 2012r2-24x7 for the past five years.

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

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

The customer support for Sharepoint 2010 on Windows server 2012r2-24x7 is good.

I did not previously use a different solution, and we did not search for any other solution.

I have not seen a return on investment for Sharepoint 2010 on Windows server 2012r2-24x7. I probably have not seen a clear use case for the return on investment, but it has been a value addition.

My experience with pricing, setup cost, and licensing for Sharepoint 2010 on Windows server 2012r2-24x7 has been transparent and on par with other Microsoft products.

Before choosing Sharepoint 2010 on Windows server 2012r2-24x7, I did not evaluate other options.

On a scale of one to ten, I would rate Sharepoint 2010 on Windows server 2012r2-24x7 a nine.

I chose nine out of ten for Sharepoint 2010 on Windows server 2012r2-24x7 because it is good software and it is reliable, robust, and scalable.

Regarding Sharepoint 2010 on Windows server 2012r2-24x7's governance and security, I think they are good and on par with other software.

Regarding Sharepoint 2010 on Windows server 2012r2-24x7's accuracy and reliability of output, I find it to be accurate and reliable.

My advice to others looking into using Sharepoint 2010 on Windows server 2012r2-24x7 is that if you are looking for a hassle-free implementation, go for it.

My overall review rating for Sharepoint 2010 on Windows server 2012r2-24x7 is nine out of ten.

My customer uses Sharepoint 2010 on Windows server 2012r2-24x7 for sharing files and content. I work in the development of an application that traces all the files and the permissions in the file. The goal of this application is to ensure that there is no user that is not approved or has been removed or needs to be removed in order to maintain updates and user access to files.

Sharepoint 2010 on Windows server 2012r2-24x7 serves as a repository of project documentation for the customer. There is a folder structure with a root folder for each project. In the folder, the structure is defined in a way to have the same route and the same contents for each project. The main folders are related to contract offerings, technical documents, sales, and each meeting that advances the project.

The main feature is the ease of use of Sharepoint 2010 on Windows server 2012r2-24x7. A minor area for improvement is the search functionality. Sometimes it is difficult to search some content by key or by key tag. However, the other functionality is very good.

I also appreciate the tag functionality of Sharepoint 2010 on Windows server 2012r2-24x7. I can tag a folder in order to search all folders by tag.

The main feature of Sharepoint 2010 on Windows server 2012r2-24x7 is making document management easier. Because it is very simple to use, I can use the console web to share documents from some users. It is very fast to edit the document together with other colleagues and share it without sending emails.

The customer can see in a fast way if there is a user that needs to be removed because there are many documents and many users can use these documents. Very often, users can change their areas. When a user changes area, they cannot access some documents or some projects. Then the customer needs a fast way to check if a user is correctly removed or a fast way to remove a user from a folder.

Because sometimes I cannot find some documents by searching for words in Sharepoint 2010 on Windows server 2012r2-24x7, I don't know why, but it can be improved.

If you can improve the search in Sharepoint 2010 on Windows server 2012r2-24x7, I could give a ten. At the moment, I give eight because it is easy to use and it works very well.

I used Sharepoint 2010 on Windows server 2012r2-24x7 five years ago for one year.

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

When I used Sharepoint 2010 on Windows server 2012r2-24x7, I did not have any problems with performance.

I have not needed customer support for Sharepoint 2010 on Windows server 2012r2-24x7.

I used an internal solution and ECM before Sharepoint 2010 on Windows server 2012r2-24x7. I used Exo Portal and Liferay as content management systems.

I have given the metrics relevant to Sharepoint 2010 on Windows server 2012r2-24x7, but I need my users to save a lot of time. Before using Sharepoint 2010 on Windows server 2012r2-24x7, they had to share files by email. They also shared files by USB key. With Sharepoint 2010 on Windows server 2012r2-24x7 instead, they can collaborate in a very fast way.

I evaluated OpenText before choosing Sharepoint 2010 on Windows server 2012r2-24x7, but the cost of licenses is high.

I developed this application with API. I use Sharepoint API to create this application. I created an executable file that the IT user can run and check the permissions.

I give the advice to ensure and give a stable Sharepoint 2010 on Windows server 2012r2-24x7.

I have not used the AI capabilities of Sharepoint 2010 on Windows server 2012r2-24x7 because I did not need this feature. If it works, my installation does not have AI features because I used it five or three years ago.

In my project, I do not use AI functionalities of Sharepoint 2010 on Windows server 2012r2-24x7. I do not know if it is available.

I work in the office with Sharepoint 2010 on Windows server 2012r2-24x7. I do not work in the office that handles the provisioning of the server and the installation. I only use the installation as a user, which my IT department set up.

I have given this product a review rating of eight.

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.