RE: Regarding SBS 2003 Reporting and Monitoring

Hi Jake,

Thanks for posting here.

The whole SBS 2003 SP1 package disks including:

**Windows Server 2003 SP1
**Windows SharePoint Services SP1
**Exchange Server 2003 SP1
**Outlook 2003 SP1 (applies to each client)
**Windows XP SP2 (applies to each client)
**Active Sync 3.8 (applies to each client)
**SBS 2003 SP1
**SQL Server 2000 SP4 (Premium only)
**ISA 2004 (Premium only)

After we applied them, the SBS 2003 SP1 has been merged with the SharePoint
Services SP1, exchange sp1 and so on. So if you move the SBS 2003 SP1 list
in Add/Remove programs console, you may need to apply all SPs except
Windows 2003 SP1. For your current situation, I suggest you move all SPs
include Windows SP1 and the SBS 2003 SP1, then re-apply them.

It is recommended you apply SBS sp1 follow installation guide provided by
Microsoft and you will not encounter many issues.

You can refer to the following link to apply SBS SP1:
http://www.smallbizserver.net/Default.aspx?PageContentID=62&tabid=236

In the following website you can find many useful resources related to SBS
SP1:
http://www.smallbizserver.net/Default.aspx?PageContentID=53&tabid=236

The website includes: What is SP1 for SBS 2003 and what you need to know |
Standard install step-by-step | Premium install step-by-step | Things to do
after the upgrade | Errors that can occur after the upgrade

*Note: To prepare Windows Small Business Server to deploy Windows XP SP2 to
client computers that are running Windows XP Professional, the steps to
uninstall the fax services:

1. Uninstall Fax Service via SBS Setup using component Selection screen,
set the Action to Uninstall for the Fax Service.
- May require you to Set the correct permissions on the Default Domain
Controller User Right Assignments

- under Group policy - Computer Configuration / Windows Settings / Local
Policys / User Rights Assignments

2. Complete the wizard.

3. Rename the following keys and files to *.old:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax
C:\Program Files\Microsoft Windows Small Business Server\fax
C:\Winnt\FaxSetup.log

4. Reboot the server
5. Reinstalled the fax service after you applied the whole SBS sp1.

Hope above information helps! If you have any further concern or question
on the issue please feel free to let me know. I am glad to help.

Have a nice day!

Sincerely,

Jenny Wu
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.

--------------------
>Thread-Topic: Regarding SBS 2003 Reporting and Monitoring
>thread-index: AcYW7+WS/RAHtZORRx2l0fqloQNsAw==
>X-WBNR-Posting-Host: 85.95.105.245
>From: =?Utf-8?B?SmFrZSBFeXJl?= <JakeEyre@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <32454972-E477-466C-9421-22AD10B46B7A@xxxxxxxxxxxxx>
<VfnwCIqBGHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Regarding SBS 2003 Reporting and Monitoring
>Date: Wed, 11 Jan 2006 12:45:03 -0800
>Lines: 191
>Message-ID: <1BF9B126-067A-45E7-822B-2E5D66D5F454@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235888
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi jenny,
>
>Sorry to *** in on a thread.
>
>I had this same issue, and I am attempting to fix it using the method you
>recommend.
>
>However, I am doing this to a post SP1 server. When the install of the
>monitoring components is done, I am given a warning that my server may not
>function correctly, as newer versions of files have been overwritten by
older
>versions, and that I should re-install SBS SP1.
>
>My question is this: how many parts of the 5-part SBS SP1 upgrade do I
need
>to re-install? Surely not all 5 parts?
>
>I have Server 2003 SP1 and SBS 2003 SP1 install files. Which one should I
run?
>
>I am at the screen that tells me to reboot, and I'm not happy about
>rebooting until I know where I am!
>
>Thanks
>
>Jake Eyre
>
>""Jenny wu [MSFT]"" wrote:
>
>> Hi,
>>
>> Thanks for using the SBS newsgroup!
>>
>> For your description, I understand that Monitoring & Reporting wizard
>> failed to process the configurations on the SBS 2003 SP1 server box. If
I
>> am off base, please don't hesitate to let me know.
>>
>> Before we go further, please kindly help me collect some information to
>> isolate the issue:
>>
>> 1. Did the issue happen only after applied SBS 2003 SP1? Have you
applied
>> the whole SBS 2003 sp1 packages (Windows 2003 SP1, Windows SharePoint
>> Services SP1, Exchange Server 2003 SP1, SBS 2003 SP1)?
>>
>> 2. Can you find any other wizard has problem (such as backup wizard,
>> licensing wizard)? please try to test and let me know the result.
>>
>> 3. What is the accurate error message you got when you click "Setup
>> Monitoring reports and alerts"? Please reproduced the issue and catch a
>> screen shot for analyze.
>>
>> To make a screen shot:
>> A. Press Alt + Pr Scrn to capture a screen shot.
>> B. From Start, go to Run, enter pbrush in the Open box, and then click
OK.
>> C. Use Ctrl + V to paste the screen shot to the canvas.
>> D. From the File menu, go to Save and save as a JPG file.
>>
>> Please mail me the screen shot at: v-yanniw@xxxxxxxxxxxxx
>>
>> 4. Could you find any related error event logged in Event Viewer
>> (System/Application)? If yes, please paste the detail error information
in
>> the newsgroup.
>>
>> For your current situation, I would like to suggest you follow below
steps
>> to reinstall the monitoring and reporting component to see if thing is
>> getting well.
>>
>> Note: Please make a full backup of the SBS 2003 server before the
following
>> steps..
>>
>> I. Uninstall Monitoring
>>
>> 1. Click Start, click Control Panel, and then click Add or Remove
>> Programs.
>> 2. Select Windows Small Business Server 2003 and then click
>> Change/Remove. The Setup Wizard appears.
>> 3. Click Next to start the wizard.
>> 4. On the Windows Configuration page, click Next.
>> 5. On the Component Selection page, in the Action column, change
>> Server Tools to Maintenance, change Monitoring component to Remove, and
>> then click Next.
>> 6. On the Component Summary page, click Next.
>> 7. Click Finish.
>>
>> II. Uninstall Microsoft SQL Server Desktop Engine (SBSMONITORING)
>>
>> In Add or Remove Programs, select Microsoft SQL Server Desktop Engine
>> (SBSMONITORING) and then click Remove. A dialog box appears. To confirm
>> that you want to remove, click Yes.
>>
>> III. Rename the folder
>>
>> Start Windows Explorer, and then locate and rename the following folder:
>>
>> C:\Program Files\Microsoft SQL Server\MSSQL$SBSMONITORING
>>
>> to C:\Program Files\Microsoft SQL Server\Old.MSSQL$SBSMONITORING
>>
>> IV. Use Registry Editor to delete the following registry key:
>>
>> HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Monitoring
>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMonitoring
>>
>> V. Install the Monitoring component
>>
>> 1. In Add or Remove Programs, select Windows Small Business Server
>> 2003 and then click Change/Remove. The Setup Wizard appears.
>> 2. Click Next.
>> 3. On the Windows Configuration page, click Next.
>> 4. On the Component Selection page, in the Action column, change
>> Server Tools to Maintenance, change Monitoring component to Install, and
>> then click Next.
>> 5. On the Logon Information page, click Next.
>> 6. On the Component Summary page, click Next.
>> 7. Click Finish.
>>
>> And then try to test to see if the issue be fixed.
>>
>> I appreciate your time! I am happy to be assistance of you and look
forward
>> to your reply!
>>
>> Merry Christmas!
>>
>> Sincerely,
>>
>> Jenny Wu
>> 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.
>>
>> --------------------
>> >Thread-Topic: Regarding SBS 2003 Reporting and Monitoring
>> >thread-index: AcYFzGLuRZaiQlaoRkisoNKWjqLTAQ==
>> >X-WBNR-Posting-Host: 12.201.43.136
>> >From: "=?Utf-8?B?TmV3Ynk=?=" <Newby@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >Subject: Regarding SBS 2003 Reporting and Monitoring
>> >Date: Tue, 20 Dec 2005 17:18:02 -0800
>> >Lines: 9
>> >Message-ID: <32454972-E477-466C-9421-22AD10B46B7A@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:231556
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >I am currently running SBS 2003 with Service Pack 1 installed on an IBM
>> >server. I tried to configure the Reporting and Monitoring utility
within
>> the
>> >server management window. After I click "Setup and Monitoring and
>> Reports"
>> >SBS takes a few minutes and gives me an error message the utility could
>> not
>> >run and to re-install the service using the Windows SBS 2003
installation
>> >disks. I performed this task, rebooted the server, and attempted to
run
>> the
>> >"Setup and Monitoring and Reports" and again I received the same error
>> >message. Does and anyone have any ideas on how to fix this problem and
>> allow
>> >me to configure this utility. Thanks.
>> >
>>
>>
>

.

Loading