We are pleased to present below all posts tagged with 'SharePoint 2010'. If you still can't find what you are looking for, try using the search box.
After having some pleasant discussions in the SharePoint Yammer SPYam community on this subject and finding almost no information online about this topic, I thought I’d put some fingers to keys and do my part to share some information. This post assumes you have basic concepts and knowledge of SharePoint taxonomies, but review TechNet if you need more info or to get up to speed on the basic concepts.
If you have ever managed an Anonymous SharePoint site you know that working with Office documents is a pain. SharePoint and Office try to be smart. SharePoint passes a path to the to the Office application and then the Office application goes out to the web application to get the file. This post is going to provide you with a way to override the default link for Office documents within SharePoint so you can avoid all the log-in prompts.
While working on a client request recently, I came across a way to easily work with date and time values in a SharePoint Designer 2010 workflow. I was able to solve this using only SharePoint Designer. I reviewed other solutions, and I will give links to a couple others in case they are needed. This worked for me, and I didn’t see anyone else with this exact solution so I thought I would share for the greater good.
While working on a PowerShell script to do some updating list items in SharePoint, I first had to get some properties from the user account in Active Directory. The end goal was to update a managed metadata field, choosing terms based on the root OU that the user resided in Active Directory. I found an easier way to do this with PowerShell and wanted to share.
If you’ve gotten to this page, it’s because you or your users make heavy use of SharePoint lists, and the inevitable request came up “Ok this is great, but I can’t print this item, help!”. Like most things with SharePoint, there is no one right answer (sometimes there is!), but some are definitely easier than others or better depending on your needs. I'll show you a couple different common solutions out there in one place, and what worked for me.
A client contacted me the other day about some help with printing a picture library. I found a simple way to do this, and I wanted to share to hopefully save someone some grief.
I've seen folks all over the interweb and even a client of mine hit this issue, so I wanted to take a moment in this blog to document it for posterity. It deals with the Usage logging features of SharePoint, and the all too familiar Microsoft bugs.
In this post I wanted to share a resolution to an issue I had with a client recently. At first I thought this was going to be a difficult issue, but as luck would have it the resolution was amazingly simple if you know what to look for.
When considering an upgrade to your SharePoint environment, there are three questions you should always ask before you start.
I’ve been fighting an interesting issue lately where some hidden taxonomy columns are becoming visible. In this environment, there are simple custom content types with some custom site columns, a few of which are managed metadata columns. The issue is that what seems randomly, some strange fields suddenly show up in the library columns, and on the list forms:
I was on a project in the past where I was upgrading SharePoint 2007 to 2010. I really didn’t want to move all the lists and libraries for 100+ sites manually, so I turned to PowerShell. The following script takes the current site URL, and the new site URL where the lists will go. It looks to see if there are actually items in the list, and only moves lists and libraries that actually have content.
Here’s the scenario: You have a picture library that stores employee photos. This might be the case if you’re not storing the photos in Active Directory yet perhaps. Now, HR comes to you and says, "We want to be sure that employees can’t set an alert, because then they would know if we remove a picture when an employee is terminated." Here is what you should do...
I recently had a client contact me recently with an interesting SharePoint issue. Seemingly out of the blue, their SharePoint 2010 server CPU started being consumed by two main processes with multiple instances: SPUCWorkerProcessProxy.exe
and conhost.exe. Read on to find out how I fixed this issue.
This entry includes script that was created for a recent client who asked me to make several columns required in their SharePoint 2010 site collection of approximately 25-30 subsites. This would've taken two minutes if all columns were site columns, however, that wasn't the case. As a result, the columns were not inheriting and I was forced to turn to PowerShell for a solution.
I recently completed a SharePoint migration for a client from 2007 to 2010. Overall the migration went well, however, we did have one small issue with the SharePoint 2010 Timer Service that I thought I should share with all of you. Read on for a brief explanation of the issue and my quick fix.
On a recent client project, we implemented a solution that heavily used article pages / page layouts from the SharePoint 2010 Pages library. Most of them had images. While working through use cases with these articles, I came across some strange behavior that someone else had found but not documented (to my knowledge). As a result, I wanted to blog about the topic to make it easier for others to find.
I had a client call me the other day as he was having an issue with a couple of his SharePoint 2010 sites that seemed strange, the sites just stopped working. When anyone tried to access the sites, they would get HTTP 500 errors. I was able to resolve this issue for the client so I thought I should share some of my troubleshooting tips.
For the IE users out there, I’m sure you’ve come across this dialog once or twice in your life. On several of our recent client projects we’ve been doing a lot of changing over from unsecure to secure URLs via SSL certificates in SharePoint. Invariably, as soon as you enable SSL and log in to SharePoint, you get this wonderful prompt: Do you want to view only the webpage content that was delivered securely? Find out how to get rid of this for good...
On a recent project I got to work with the out-of-the-box (OOTB) Chart Web Part in SharePoint 2010. My team just needed to chart some simple data, nothing fancy, but we had some fairly specific styling requirements. We tried Web parts from other vendors they already had and got close, but we just couldn’t get there. Luckily we were upgrading to Enterprise anyway, so that allowed us to use the Chart Web Part that comes with SharePoint OOTB.
In this post I explain how to use PowerShell to create a full SharePoint (2010 or 2013) training site or testing site environment. This is the process I used to prepare for a recent SharePoint training course where I needed each of my users to have their own site collection in my environment.
Over the time I’ve been using SharePoint, I’ve been taking notes on the tools and that make my job a little bit easier. Lately I’ve focused on collecting a ton of tips for working with branding in SharePoint2010. To help other people working with branding in SharePoint, I thought I should share some of my information.
If you’re like a lot of other folks, you’ve taken advantage of the Managed Metadata functionality in SharePoint. You’ve created your taxonomy group, specified your term sets, and created some terms. Then you’ve created your managed metadata column in your site collection, and pointed it to your specified term set. You’ve then uploaded a lot of documents and specified terms for the metadata column, everyone is “happy happy happy”.
But then you need to rename one of your terms currently called “Information Technology Department” to just “Information Technology”. No sweat, you go into the Term Store tool, rename the term. Done right? To your surprise, when you look at properties of various documents tagged with your term, they haven’t been renamed. Hmm … what gives?
I was working with PowerShell to update a managed metadata field that accepted multiple values in a publishing page library today and it was more difficult than it seemed like it should have been, so I’m posting here what actually worked for me. It turned out to be much simpler than I was trying to make it.
On a recent project, I hit an issue with databases that was interesting. We were restoring a lot of databases over to a development environment from production, as well as the managed metadata database. I had gone through the whole deal, backed up the database in the old server, restored it to the development SQL server, etc. There was an issue with the Managed Metadata service that required to have service application re-created. This lead to a situation where the service application database was unprovisioned, but not deleted.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.