Re: New User Not in GAL, Recipient Policy Not Applied

Hi Steve,

Thanks for your updating.

I made deep research on the MPS Report, please take the following steps:

Step 1: Restart System Attendant service and check again.

Step 2: Restart SBS server and check again.

Step 3: If you have additional DC on network, please check the following:

1. Right click Recipient Update Service (Domain) and select properties.
2. Check the Exchange Server name.

Since the SBS is a DC, also many application is running on it, so please
don't run setup /domainprep now. Also, I didn't find related AD errors on
the report. Please let me know the KB number.

I am looking forward to hear from you.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================

This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<From: "spm" <nospam@xxxxxxxxxxxxxxxxxx>
<Subject: Re: New User Not in GAL, Recipient Policy Not Applied
<References: <xn0f73mgako039000@xxxxxxxxxxxxxxxxxx>
<bWVExTBqHHA.2300@xxxxxxxxxxxxxxxxxxxxxx>
<Organization: CoCo Systems Ltd.
<User-Agent: XanaNews/1.18.1.6
<Message-ID: <xn0f74o6e50ds8000@xxxxxxxxxxxxxxxxxx>
<X-Ref: news.microsoft.com ~XNS:00000112
<MIME-Version: 1.0
<Content-Type: text/plain; charset=iso-8859-1
<Newsgroups: microsoft.public.windows.server.sbs
<Date: Wed, 06 Jun 2007 02:51:13 -0700
<NNTP-Posting-Host: cocohome.co.uk 80.229.190.27
<Lines: 1
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:42030
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<Hi Robert,
<
<I have completed all your suggested tasks...
<
<> Step1. Check Default GAL.
<>
<> 1. Open Exchange System Manager.
<> 2. Open the default Global Address List properties, and then make
<> sure that the Search filter looks like the following one:
<> (& (mailnickname=*) (|
<> (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHome
<> Se
<> rverName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(
<> ms
<> ExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))
<> (o bjectCategory=group)(objectCategory=publicFolder) )) 3, If the
<> filter displays incorrectly, please refer to the method in the
<> article below to troubleshoot this issue:
<
<The search filter here was slightly different, thus:
<
<(& (mailnickname=*) (|
<(&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeSe
<rverName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(ms
<ExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(o
<bjectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchD
<ynamicDistributionList) ))
<
<I changed the filter as advised, rebuilt the RUS and re-applied the
<default recipient policy (the only one I have) but the problem persists.
<
<> Step 3: Please install the hotfix KB 837444
<
<This KB article simply advises that the latest Exchange service pack is
<installed. I have Exchange SP2 installed, and further SBS 2003 R2 and
<SP2.
<
<> Step 4: The new user is not appear in GAL, this issue may occur if
<> the clients use Outlook 2003 with cached Exchange mode enabled. If
<> this is the case, I therefore suggest us create a new profile without
<> cached Exchange mode enabled to test this issue.
<
<Tried this, again the problem persists.
<
<> Actually, we can disable this feature in Outlook client side. To do
<> so, please follow the steps below...
<
<Tried this too - problem persists.
<
<> 5. Send the .cab file directly to v-robeli@xxxxxxxxxxxxx with
<> subject: 39474410-New User Not in GAL, Recipient Policy Not Applied.
<
<Done.
<
<While I don't wish to pre-empt your analysis of the system reports, I
<have analysed the events created with increased diagnostic logging of
<the recipient update process, and the relevant 8012 event IDs suggest
<no users are found to process. According to the KBs I've read this
<suggests a permissions problem in the AD hierarchy, but I can find no
<real info on how to correct this (assuming that to be the case). I see
<suggestions of running setup /domainprep, but I am reluctant to do that
<without confirmation that is the way to go. I'll await your response.
<Thanks for your help.
<
<--
<Regards,
<Steve.
<

.

Relevant Pages