Latest Posts

One of the nice things about SharePoint 2007 is that you now have the ability to control what permissions are available for a given web application. As an administrator this is nice because you can now prevent site collection administrators from handing out permissions which violate your security policies.

The following is a list of quota related commands that I have created and are available for download from this site. gl-createquotatemplate Creating a quota template can be done using the central administration tool by going to “Central Administration > Application Management > Quota Templates”.

Update 9/17/2007: This command has been made obsolete and removed from the package. Please use gl-setsitegeneralsettings instead. Sorry for any inconvenience this may have caused. This is one of those that I thought I needed because during the upgrade the mysites application got hosed so was expecting to have to set the title manually.

Update 9/18/2007: I’ve modified this command so that it no longer manipulates the database directly. The content below has been updated to reflect the changes. This particular command which I called gl-setuserprofileimportschedule, really drove me nuts.

One of the things I needed my upgrade script to do was to set the master site directory. This can be done easily enough using the central admin tool (Central Administration > Operations > Site Directory Settings).

Within our SPS 2003 environment we stored employee pictures in a picture library. We then set the users Picture URL profile property to point to their picture in this library. The problem was that as soon as we upgraded the paths to these pictures no longer worked.

For some web applications you’re going to need to have tight controls over who can create sites and who can’t. One simple thing you can do to prevent users from creating sites is to disable self service site creation.

In SharePoint Portal Server 2003 we had allowed users to add web parts from the online web part gallery. In going to MOSS 2007 we decided that we no longer wanted users to be able to do this as it tended to reduce the security of the site and adversely affect performance (not to mention that fact that it was annoying having a weather web part on every page).

One of things I found that I had to do a lot with the upgraded site (or even a new, from scratch, portal) was to connect the various web applications and site collections to the main portal (results in adding a link to the top left bread crumb trail).

As we were doing our upgrade we realized early on that we did not want to keep the SSP as it was migrated during the upgrade process. The upgraded version just locked us into to many things that we didn’t like.