Re: Unghosted pages in SharePoint 2007

On Dec 27, 1:24 pm, vkb <v...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Is there a query or a tool that I can run to determine which pages in the
SharePoint 2007 (MOSS) farm have been customized and become unghosted.  I
want to run this in a farm with a few hundred top-level site collections.  
Running something per site collection would be too cumbersome.  In SharePoint
2003 I was able to use the ReGhost.net tool.  I have not found anything that
can be used with SharePoint 2007.  

Thank you.

The WSS3 SDK says:

"You can use the vti_hasdefaultcontent field obtained through the
Properties property of the SPFile class to determine whether a file is
ghosted."

I can't imagine it would be that difficult to write a little console
application to loop through all your sites and tell you which were
unghosted.

Richard

.

Relevant Pages

  • Re: WSS MSDE DB Location Change Nightmare
    ... Site Collections are just how they sound, they are a collection of sites. ... After you get MSDE ... I have a single Sharepoint instance with 6 "subsites" ... STS_servername_1 database. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Configuration Failed / Accidentally deleted Central Admin
    ... You could create a sceond farm and attach the content datbase from your ... I'm getting a error Configuration Failed while trying to fix ... initialize SharePoint Products and Technologies upgrade. ... I tried running SharePoint Products and Technologies Configuration ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Sharepoint 3 Portal Server versus Stand Alone Sharepoint 3 wit
    ... It sounds like you want to run SharePoint 3 / 2007, be able to connect to a remote SQL server, and have a farm installation allowing the option to grow/expand the farm in the future if you need to. ... First - as I mentioned before, there is not good way to link different SharePoint farms together, especially when they're running different versions of SharePoint (e.g. SBS 2003's companyweb running WSS 2.0 and another SharePoint farm running WSS 3.0). ...
    (microsoft.public.windows.server.sbs)
  • RE: Name Changes & Site Collections
    ... Odd thing being the user info in the _CONTENT DBO was correct; ... > address) - any Site Collections that they have permissions to do NOT get ... > the site with their new name - however if the actual permissions are examined ... > profile is updated within SharePoint. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: WSS V3 - Migrate from WMSDE to SQL Server 2005
    ... I cannot see in central admin where I create a new sharepoint farm. ... services I installed with a WMSDE not a sql server. ...
    (microsoft.public.sharepoint.windowsservices)