Microsoft

SharePoint Search problems on Server 2008?

After installing WSS3 SP2 on a clean install of Server 2008 x86 SP2 STD, and using SQL 2008 SP1 as the backend, I could not get any search results.  The setup is about as simple of a farm installation you can get, it is for a small number of users, and demonstration purposes, so everything is installed on a single machine virtualized on an HP server running VMware ESXi 3.5.  There are two site collections using different application pools, one enabled for anonymous access, and the other not.

The search service is common to both, but the crawl account (data access) is unique.

Continue reading →

SharePoint SP2 Bug

!IMPORTANT!

All installations of Microsoft Office Server 2007 that have installed SP2 for SharePoint Services are affected by the following bulletin.  In short, it has reset your license key putting the product in trial mode, and it will expire in 180 days without notice.  See the below article for the resolution, and more details.

http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx

WSUS 3.0 SP1 Computers with no status

The setup: Server 2003 R2 SP2, DC & DNS Roles, WSUS SP1 Fresh install, default website (80).

The issue: No status  reported by clients (Servers and workstations), Event ID 13042 in the Application logs on the WSUS server Self-update is not working.

After researching, I came across these 2 forums:

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?pg=2&p=1&tid=853e8bb5-71c7-4bee-9392-d75dbbf21c6b&dg=microsoft.public.windowsupdate

http://blogs.msdn.com/jjameson/archive/2008/04/08/wsus-clients-failing-with-error-0×80244019-after-installing-wsus-sp1.aspx

The articles were close, but both addressed installing SP1 POST a typical WSUS 3 install, mine was a fresh install at the customer’s site.  Continue reading →

AD DS Security/Distribution Groups

With Exchange 2007 SP1, and Server 2008 Active Directory Domain Services, you may want to enable users to send emails to your security groups.  The dilema is that security groups will not show up in the Global Address List (GAL).  In order to mail-enable an AD DS security group, you must perform two steps:

1) Change the group properties to ensure that the group is a Universal, and not a Global group.  Otherwise Exchange 2007 will not see the group in order to mail-enable it.

2) Perform the following steps from within the Exchange Management Console:

1.     Start the Exchange Management Console.

2.     In the console tree, expand Recipient Configuration, and then click Distribution Group.

3.     In the action pane, click New Distribution Group. The New Distribution Group wizard appears.

4.     On the Introduction page, click Existing Group, and then click Browse.

5.     In Select Group dialog box, select the group that you want mail-enable, and then click OK.

6.     Click Next.

7.     On the Group Information page, complete the following fields:

·         Display name   By default, the display name is the same as the group name. You can modify the name in this field.

·         Alias   By default, the alias is the same as the group name. You can modify the name in this field.

8.     Click Next.

9.     On the New Distribution Group page, review the Configuration Summary. To make any configuration changes, click Back. To create the new distribution group, click New.

10.  On the Completion page, the Summary states whether the distribution group was successfully created. The summary also displays the Exchange Management Shell command that was used to create the distribution group.

11.  Click Finish.

Now, your users will be able to send notifications, etc. to their colleagues via their Outlook client and the GAL.