Skip to main content

Andy Pauls's Library tagged sharepoint →  View Popular

Gabe Wishnie: Updating Existing Content Types in Sharepoint 2007

  • Now I alse have a custom workflow attached to my doc library so I thought currently running workflows would hang onto my old content type and new ones would pick up the content type with the new field.
22 Oct 08

Missing Completed Workflows History : SharePoint - Workflow : SharePoint Products and Technologies : MSDN Forums

  • SharePoint is not the answer to all problems and honestly one of the biggest problems it faces is that people try to make it that answer.  It isn't, folks.  It's a tool.  Use it for the right job and you'll be fine.  Use it for the wrong job and you deserve whatever headaches you ge
  • Maybe a little late on this one but I was just reading the workflow chapter in the new Best Practices for Sharepoint 2007 by Ben Curry and he covered a bit on this.  From an audit standpoint, the workflow history is just a doc lib and there can be edit/updated/deleted which is not good for audit standpoint.   The book suggested using the records management piece of Sharepoint to store audit logs of workflow (or anything else) if you want to guarantee it is accurate can not be altered.

Huge MOSS Workflow Issue... What is Microsoft Thinking!!!! - Dave Wollerman's SharePoint Blog

  • SharepointUser
    said:



    We had the same issue and it impacted us alot and wasted alot of our time and resources. We restored our database, called Micro$oft and spent over $250 and finally and they can't find out the problem!


    We found the solution ourselves by figuring out that there is a  "Workflow Auto Cleanup " option available which is available under the MOSS 2007 Central Administration located at "Central Administration > Operations > Timer Job Definitions    


    Timer Job Definitions > Workflow Auto Cleanup"


    Microsoft stupidly set the option to have the workflows to be deleted after a certain time. By disabling that option, we can aviod our workflow history being deleted. Thank you Microsoft! DUH!

15 Oct 08

Mainsoft- Frequently Asked Questions about SharePoint Integration Products

  • client-side
    plug-in for Lotus Notes
  • SharePoint sidebar displays the author or last modifier of a document with Sametime
    presence awareness
  • 12 more annotations...
06 Oct 08

Joel Oleson's Blog - SharePoint Land : Best Practice on Backups

  • You mention stsadm as a tool to export individual sites, ready for import as restore. However, we found that when you import a site exported in this way to a new server several things are broken - e.g. site columns have their inheritance broken from parent site columns, list GUIDS are different in the restored version so Content Query webparts need re-configuring etc.


    Are we doing something wrong, or is there a way round this behaviour? We were hoping to use this mechanism both for backup/recovery and as a dev-test-production model for site lifecycle.

SharePoint 2007 - Best Practices for Collaborative Portals

How a company developed a custom solution using sharepoint
Best practices for how to deal with dev/prod/uat

dotnet.sys-con.com/...461380 - Preview

Prod to Dev sharepoint

  • When the limits of SharePoint's built-in capabilities are exhausted, a gap analysis is performed and any features that require custom code development are now defined and designed. Content is pushed back from production to development, by way of staging. From there, custom code is developed as a Feature (a package of deployable code in SharePoint 2007) and pushed forward to staging and then production.
02 Oct 08

Plan for software boundaries (Office SharePoint Server)

  • Security principal



    2,000 per Web site



    The size of the access control list is limited to a few thousand security principals (users and groups in the Web site).

Joel Oleson's Blog - SharePoint Land : SharePoint Groups, Permissions, Site Security, and Depreciated Site Groups

  • For sensitive sites at the site collection level - least priviledged access, don't delegate the site owner or admin roles, you should have a couple of site administrators and/or site owners, using individuals here is a good practice.  You'd think why not create a group, but at this level it's good to have an individual owner that has an email address that will ensure the site auto delete features do what you'd expect. 

  • Dev Tip from Jim Sturms: You cannot create groups or permission levels declaratively in XML – you’ll need to create these using the OM with a solution.


    Although permissions inheritance is easily broken and granularized, I don't recommend it unless you need to.  It's a pain to manage, let me tell you.  There are a bunch of partners out there that would love to help you manage your site permissions and help you add users across all the sites when someone joins the group.  It's a ton better to add security groups and users at the site collection level and use the sharepoint groups and add people to those roles that you see right out of the box.  Sure you can break inheritance on special sites, but I'd recommend not making that the rule more the exception.

  • 2 more annotations...

Restore a production sharepoint web farm to a new web farm - Sam's Blog

  •  If you have a production WSS 3.0 sharepoint environment and need to copy the production data into a test environment web farm (different web farm), it can be done using SQL backups and restore.
1 - 14 of 14
Showing 20▼ items per page

Selected Tags

Related Tags

Sponsored Links

Ads by Google

Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »

Join Diigo