There are a few explanations of the differences between WSS 3.0 and MOSS out there but this is by far the best I have come across.
Suzanne Ross who writes this SharePoint blog manages to cover the basics of SharePoint in a very strightforward and easy to understand way. I will definitely be pointing some of our users towards her blog posts in the future!
I have just downloaded and installed the SharePoint Learning Kit from Microsoft. This is a MOSS 2007 feature that allows trainers to create and manage online training.
As it is wrapped up as a feature it is very easy to install although you may have to alter the deploysolution.cmd file if your central admin web application isn't found at http://localhost.
Once installed and deployed the kit is fairly simple to use. It allows trainers to upload SCORM 1.2, SCORM 2004, and Class Server content to a document library and then assign these training modules to a user.
The user can complete the module and submit it to get feedback from the trainer. As someone who has to train people on SharePoint from time to time I can see this being an extremely useful tool to track who has been assigned which modules and what progress they have made.
The SharePoint Learning Kit can be downloaded here.
Joel Oleson has put together a great list of links to resources to help with deployment of a MOSS 2007 environment.
The usual LDAP query to import user profiles from AD into MOSS is:
The downside of this query is that you are also going to get your service accounts and any disabled accounts imported as well. This creates a lot of unnecessary clutter in people searches and greatly reduces the effectiveness of the people search scope.
To remove these accounts use the following:
- (!userAccountControl:1.2.840.1135184.108.40.2063:=2) - removes disabled accounts
- (!userAccountControl=65536) - removes accounts with password set to never expire
So the new LDAP query is:
For more ADSI userAccountControl flags go here: http://msdn2.microsoft.com/en-us/library/aa772300.aspx
Credit for this goes to Suman Chakrabarti's blog
Slides from a presentation given by Spencer Harbar recently at the Newcastle VBug/SharePoint User Group meeting
As a SharePoint developer you are going to be frequently using the STSADM tool deploying solutions, features and all number of other development related activities.
Rather than having to change the directory you are using every time you open up a command prompt there is a much simpler solution that will save you a few seconds everytime you come to use STSADM. We are going to add the path to the bin folder containing STSADM to the Path system variable. This will mean that you can just open up a command prompt type STSADM.exe add your parameters and hit enter - no need to change the directory path first!
To do this go to Control Panel and then System and select the Advanced tab.
Click "Environment Variables"
Under "System Variables" scroll down to "Path"
Select "Path" and click "Edit"
Add "%programfiles%\Common Files\Microsoft Shared\web server extensions\12\Bin" to the list of paths and make sure it is seperated with a ';'
Click OK three times to close all the windows
Restart your system
Go to Start - Run and type CMD
Type STSADM.exe in the command prompt and you will get the following screen showing that STSADM.exe can now be run without changing the directory path:
Hope that saves you some time!