ÁghyBlog

This workspace is designed for governance and manageability samples and tools designed to help IT Professionals.

The Content Type Toolbar is a simple add-on that will enhance the use of SharePoint Content Types in large deployments.

The use of content types in SharePoint 2007 has a number of benefits and businesses may spend a considerable amount of time planning and deploying content type to help support their business processes. Unfortunately, the default methods of using content types may not be intuitive for most users who do not have experience with SharePoint. This problem will lead to content types not being used or being neglected by the end users. This can be avoided by training your end users, but it may be sometime before all your users receive the appropriate level of training, so in the meantime the content types are still neglected.

"Paul, can you tell me the difference between SharePoint and Skype?"

Reduce Man Hours by allowing faster locating of information
2. Reduce Man Hours by increasing use of electronic forms
3. Reduce Costs of stationary by increasing use of electronic forms
4. Reduce Licensing Costs for 3rd Party business systems (SharePoint can replace many of these systems)
5. Reduce Costs of development work for 3rd Party business systems
6. Reduce IT Support Costs
7. Reduce IT Training Costs
8. Reduce Website Costs (using SharePoint system both Intranet and website).
9. Reduce response times to Sales leads (employees can access SharePoint remotely)
10. Reduce response times to possible problems (with ProActive Alerts with SharePoint Workflow)

With the current economy, projects such as those involving SharePoint will most likely be cut unless they can be associated with cost reduction or some sort of ROI. For example, helping to reduce travel costs. Combine SharePoint with OCS and LiveMeeting and you have a solution that can help reduce travel costs in some cases.

So if you want to enter this space, what do you need to do and when can you expect results? Here are some points to think about before making the move:

Frequently changing farm credentials and security account passwords are important measures for keeping a Microsoft Office SharePoint Server (MOSS) farm secure. Yet for administrators, these tasks are tedious and repetitive. The tools are difficult to use, the underlying processes are complex, good documentation is hard to find, and there is a certain risk of corrupting the server farm even when following all of the proper procedures.

I have been hearing more and more questions recently about Active Directory migrations with relation to SharePoint deployments. It could be from some organizational changes, or because business managers just like to keep people busy.

When I had to go through this process during the summer of 2008 I found much less information that I expected so I had to work through some of the problems myself. Here is the result of what I found. Hopefully it can assist other organizations in the process.

I have broken everything into five steps; Prep, Server Move, Service Updates, Migrating User Accounts, and Post-Migration Validation.

I have a bunch of documents that need to be audited every six months. Is there a way that a reminder can be set up to remind the owner of the document that its time to review the document?

Laura Rogers suggested the following for Microsoft Office SharePoint 2007:

If you have MOSS, you can use the information management policy settings in the document library. You can set it to: Modified Date + 6 months. Then, make it kick off a workflow at that point. Use an OOB one, or create your own "review" workflow that will "Collect data from a user" in the workflow.

Maurice is using WSS so here is a solution to utilitze on top of WSS.

This tool provides a way to import/export site collections, webs, lists, and files or list items, either between farms or between different sites in the same farm - the Codeplex site has more details. As previously mentioned, the key new additional functionality in this release is:

* Command-line support
* Support for saving of import/export settings to a file (in the Windows Forms app) for later re-use
* An installer

A tag cloud is merely a collection of terms, typically used as "tags" or "keywords". These terms are represented graphically. Font sizes are increased for popular tags and decreased for less popular tags. A tag cloud is a "heat map" for keywords, enabling users at a glance to scan a list of terms and derive a sense of what's hot and what's not.

This article describes why it is so useful to use child master pages for MOSS publishing sites and how to migrate your existing publishing solution to make use of child master pages.

Have you faced any issue with Managed Paths (with Explicit Inclusion) in SharePoint when you try publishing an InfoPath form to this managed path? If yes, read through this post. It might be helpful.

The SharePoint Data Zoom Web Part is a free tool which allows SharePoint users to easily build dynamic, data-driven content on any page. Data from SharePoint Sites, SharePoint Lists and virtually any other source can be aggregated and formatted with ease.

The RSSBus SharePoint Web Part™ includes a ready-to-use Web Part that requires no programming or other WSS DAL, CAML or ADO.NET configuration. The Web Part works by calling RSSBus Simple Services or standard data feeds, and formatting the output using simple HTML templates. Use the RSSBus SharePoint Web Part™ with RSSBus Server to quickly and easily access hundreds of information services inside and outside of your organization!

The nice thing is that the policy framework is an extensibly framework, so you can write your own information management policies. This will be the first of a number of posts on this topic. The first part shows you how to create and register a policy so that it can be used. The scenario I used for this example is not very useful, but I wanted to have a simple policy to start with.

Today I came across a requirement of showing an swf file in the webpart. So I thought I will upload the swf file in folder and give its url to the webpart. But then that will be hardcoded path. What will happen if the user deleted that folder or rather deleted that file itself? So my webpart will not run.

So I found some alternative to this and thought of embedding my swf file and js file in webpart itself. I googled on how can I do this, and here are the steps for embedding the files in the webpart itself.