Case Study: Pfizer’s MOSS 2007 Implementation

Interesting reading.

http://mediaproducts.gartner.com/reprints/microsoft/vol6/article8/article8.html

Microsoft / SharePoint / MOSS Single Sign-On Service not supported in non AD Environment?

After attempting for an hour or so to get the SSO service running on a MOSS system in a local machine (non Active Directory) environment, I discovered a couple of posts and some documentation from Microsoft which indicated that for the SSO service to be used with SharePoint/MOSS, the system must be integrated into an Active Directory system.

The problems come when you try to configure the SSO service in Central Admin, on the screen where you enter the Administration and Management credentials for the SSO service, when clicking OK here, you get presented with the Unknown Error Occurred or Access Denied error messages.

My MOSS/SharePoint Development VM Environment

Here’s my MOSS development VM environment;

1. VMWare Server 2.0 / VMWare Fusion / VMWare Workstation (installed on local machine)
2. Microsoft Windows Server 2003 SP2
3. Daemon Tools
4. IE7
5. .NET 2.0 / 3.0 / 3.5
6. Microsoft SQL Server 2005 SP2
7. Office 2007 (with InfoPath)
8. Microsoft Office SharePoint Server 2007
9. Microsoft Visual Studio 2008
10. Visual Studio 2008 Extensions for WSS 1.3
11. VSTO Visual Studio Tools for Office
12. WSS SDK
13. SharePoint Server 2007 SDK
14. Sysprep for Windows Server 2003 SP2

Synchronise Sharepoint User Profiles with Active Directory

Occasionally you may need to (re) synchronise your Sharepoint user profiles with their counterparts stored in Active Directory, particularly when the Active Directory information changes. Synchronisation occurs automatically when the SharePoint machine is restarted, and periodically acording to 2 SharePoint Timer jobs, “Profile Synchronization” and “Quick Profile Synchronization”.

If you need to do this manually, follow these steps;

1. Log into the Shared Services Administration site
2. Click on User Profiles and Properties
3. Click on Configure Profile Import
4. Under “Source” select the domain you wish to import from
5. Under “Default Access Account” select either the default content access account or specify account details – this account must have permission to access the Active Directory users (default) OU container
6. Click OK
7. Now select either a Full or Incremental import, a Full import will ensure that users deleted from Active Directory are removed from the profile database
8. Once the import has finished you can select “View Import Log” to reveal details about the import

Note. To perform incremental imports, the content access account must have the Replicate Changes permission for Windows 2000 Active Directory, this is not required for Windows Server 2003 Active Directory.

Windows Server 2008 as a Development Workstation

A great post which details a number of steps to take to configure Windows Server 2008 as a Workstation.