SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After running preupgrade check, I found a few instances of some web parts I'd like to further investigate. These are 3rd party web parts that I'd like to know where they are actually being used.

For example, Id = f9699ea3-fbf1-9ff7-99f6-17c856b8e3e9, Type = CorasWSC.Site.WorkSpace.Viewer, Reference = 79, Status = Installed

It's listed as being used in 79 locations. Is there a program (codeplex perhaps?), stsadm, or powershell command that could find the 79 site location URLs where this is being used?

share|improve this question
up vote 5 down vote accepted

The stsadm command enumallwebs can be used with the -includewebparts option to work out in which sites the web parts are being referenced.

share|improve this answer
That was it, I forgot about all the switches in enumallwebs which aren't documented at all on the stsadm index page, – Eric Alexander Dec 28 '10 at 19:13


It looks like you already worked a solution, but I'll also offer this up. Phil Childs has some documented PowerShell over on his blog that will actually identify the specific page that contains a given web part. I've needed to dig down to that level a few times during upgrade work; it's a good reference to have in your back pocket:

share|improve this answer
Thanks Mike, I'll check it out. – Eric Alexander Oct 27 '11 at 15:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.