Eddy Lab

Windows SBS 2008 Hands-On-Labs available for download from MS Connect

SharePoint Services 3 Search event errors after an SBS 2008 Update Rollup

[Today's post comes to us courtesy of Damian Leibaschoff]

After installing an SBS 2008 Update Rollup (2 or higher) you might see the following event in the application event log happening very 5 to 10 minutes:

Log Name:      Application
Source:        Windows SharePoint Services 3 Search
Date:          8/5/2009 10:10:02 AM
Event ID:      2424
Task Category: Gatherer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SBS01.wingtiptoys.local
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Application 'Search', Catalog 'index file on the search server Search'

New content will not be added to the search index and in consequence it will not be found when doing a full text search within the CompanyWeb application.

In order to resolve this issue, please follow the same resolution presented in this blog post, you will need to add the host name that you created using the Internet Address Management Wizard for public access, it will usually be in the form “Remote.Contoso.com”, If you are not sure on what URL to use, you can look for the event id 2436 as mentioned on the other blog post or you can do the following:

• Open an elevated command prompt by right-clicking on Command Prompt and choosing ‘Run as administrator’
• Navigate to the following folder:
  • CD C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
• Type the following command:
  • stsadm -o enumzoneurls
• The output will look like this:

<ZoneUrls>
  <Collection Name="Central Administration">
     <Default>http://sbs01:4721</Default>
  </Collection>
  <Collection Name="SBS SharePoint">
<Default>https://remote.Contoso.com:987</Default>
     <Intranet>http://companyweb</Intranet>
  </Collection>
</ZoneUrls>

• From this output, you are looking for the URL in the <DEFAULT> tags under the “SBS SharePoint” collection. You will only use the host.domain name portion and not the protocol or port, so, “Remote.Contoso.com” is what you are looking for to be added to the registry.

Articles referenced:   
http://blogs.technet.com/sbs/archive/2009/05/07/event-2436-for-sharepoint-services-3-search.aspx

Posted: Wednesday, August 05, 2009 1:34 PM by SBS Bloggers

 

 

http://blogs.technet.com/sbs/archive/2009/08/05/sharepoint-services-3-search-event-errors-after-an-sbs-2008-update-rollup.aspx

You Cannot Install the Hyper-V Role on the SBS 2008 Primary Server

[Today's post comes to us courtesy of Martina Grom, Technet Team Blog Austria]

When you install the Hyper-V Role on your SBS 2008 Primary Server the DHCP Service will no longer be able to assign IP addresses to your client machines. The reason for this is that we do not support the Hyper-V role on the SBS 2008 Primary Server. The SBS wizard expects only one network adapter and binds DHCP to that network interface.  Similar problems with DHCP can be experienced if you are using 2 NICs, this is also an unsupported topology, for more information on support network topologies for SBS 2008 see http://blogs.technet.com/sbs/archive/2008/09/16/sbs-2008-supported-networking-topology.aspx.

For more information, please read these KB Articles: KB968250 and KB958829.

We do support Hyper-V in SBS 2008 environments in three scenarios, which are described here: http://blogs.technet.com/sbs/archive/2008/09/15/sbs-2008-and-virtualization.aspx.

For further reading concerning Hyper-V and SBS 2008, please refer to: http://technet.microsoft.com/en-us/library/dd239207(WS.10).aspx.

Posted: Friday, August 07, 2009 2:38 PM by SBS Bloggers

Filed under: Networking, DHCP, Windows Small Business Server 2008, Virtualization

http://blogs.technet.com/sbs/archive/2009/08/07/you-cannot-install-the-hyper-v-role-on-the-sbs-2008-primary-server.aspx

Article ID: 973862 - Last Review: August 26, 2009 - Revision: 1.0

You cannot install Exchange Server 2007 Service Pack 2 on a Windows Small Business Server 2008-based computer

View products that this article applies to.

On This Page

• SYMPTOMS
• CAUSE
• RESOLUTION
• Known issues that may occur after Exchange Server 2007 SP2 is installed
  • Exchange Server 2007 does not work after you install Exchange Server 2007 SP2
  • The default Web site or the Small Business Server Web Applications site is stopped and cannot be restarted
  • You may be unable to browse https://sites/owa or https://sites/remote
  • You may be unable to browse https://remote.contoso.com/owa or https://remote.contoso.com/remote
  • You may be unable to use Remote Web Workplace or the Terminal Services Gateway service to connect to the server or client desktops

Expand all | Collapse all

SYMPTOMS

When you try to install Microsoft Exchange Server 2007 Service Pack 2 (SP2) on a...

When you try to install Microsoft Exchange Server 2007 Service Pack 2 (SP2) on a Windows Small Business Server 2008-based computer, the service pack Setup program will not start.

Back to the top

CAUSE

This problem occurs when you run Exchange Server 2007 SP2 Setup because the Exch...

This problem occurs when you run Exchange Server 2007 SP2 Setup because the Exchange Best Practice Analyzer detects the server as Small Business Server 2008 and will not allow for the service pack to install.

Back to the top

RESOLUTION

To resolve this problem, you must first create the following E12SP2READY registr...

To resolve this problem, you must first create the following E12SP2READY registry value, and then you must install Exchange Server 2007 SP2:

HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Exchange\E12SP2READY

Note We recommend that before you create the registry key and run Exchange Server 2007 SP2 Setup, you read this complete article to understand all the known issues that may occur after you install Exchange Server 2007 SP2. There are some manual steps that you will have to perform to install the service pack and to make sure all the services work correctly after the service pack setup is complete. Additionally, the Exchange Server 2007 SP2 installation will disable the Web services on the server. You cannot install the service pack while you are connected to the server by using remote Web workplace or the Terminal Services Gateway service. You can install it remotely while you are connected by using remote desktop or by using any other method that does not rely on the Web services.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To create the E12SP2READY registry value, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\Exchange

   Note If the Exchange subkey does not exist, you must create it. To do this, follow these steps:

   1. Right-click SmallBusinessServer, point to New on the Edit menu, and then click Key.
   2. Type Exchange and then press ENTER.
3. After you select the Exchange subkey that is specified in step 2, point to New on the Edit menu, and then click DWORD Value.
4. Type E12SP2READY, and then press ENTER.
5. Right-click E12SP2READY, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. On the File menu, click Exit to exit Registry Editor.

After you have created the E12SP2READY registry value, you can now start the Exchange Server 2007 SP2 Setup program.
Important If Forefront Security for Exchange is installed on the server, you will receive the following error message during the Readiness check:

Setup has detected that Forefront Security for Exchange Server is running on this server and has to be disabled before Exchange Server 2007 is upgraded.

When you receive this error message, follow these steps to disable Forefront Security for Exchange:

1. Stop the following services:
   • FSCController
   • Microsoft Exchange Information Store
   • Microsoft Exchange Transport
2. Open an Administrator command prompt.
3. Change to the following directory:

   C:\Program Files (x86)\Microsoft Forefront Security\Exchange Server

4. At the command prompt, run the following command:

   fscutility /disable

   After you run this command, you receive the following message:

   Removing dependencies...
   dependency on FSCController removed from Microsoft Information Store
   dependency on FSEIMC removed from Microsoft Exchange Transport Service
   Microsoft Exchange Transport Service Agent registration removed
   Status: Microsoft Forefront Server Security NOT Integrated.”

After the Forefront services are disabled, you can continue the Exchange Server 2007 SP2 Setup and then click Retry. Exchange Server 2007 SP2 should be installed correctly.
After the service pack setup is complete, you must enable Forefront Security for Exchange if you disabled it. To do this, follow these steps:

1. Stop the following services:
   • Microsoft Exchange Information Store
   • Microsoft Exchange Transport
2. Open an Administrator command prompt.
3. Change to the following directory:

   C:\Program Files (x86)\Microsoft Forefront Security\Exchange Server

4. At the command prompt, run the following command:

   fscutility /enable

5. Start the following services:
   • Microsoft Exchange Information Store
   • Microsoft Exchange Transport

Back to the top

Known issues that may occur after Exchange Server 2007 SP2 is installed

Exchange Server 2007 does not work after you install Exchange Server 2007 SP2To...

Exchange Server 2007 does not work after you install Exchange Server 2007 SP2

To resolve this issue, restart the computer or start the following services manually:

• Microsoft Exchange Information Store
• Microsoft Exchange Transport

Back to the top

The default Web site or the Small Business Server Web Applications site is stopped and cannot be restarted

To resolve this issue, remove the Secure Sockets Layer (SSL) settings from the default Web site. To do this, follow these steps:

1. Open Internet Information Services (IIS) Manager.
2. Expand the server.
3. Expand Sites.
4. Click Default Web Site, and then click SSL settings.
5. Click to clear the Require SSL check box, and then click Apply.
6. Right-click Default Web Site, and then click Edit Bindings.
7. Select HTTPs port 443, and then click Remove.
8. Right-click SBS Web Applications, click Manage Web Site, and then click Start.

Back to the top

You may be unable to browse https://sites/owa or https://sites/remote

To resolve this issue, edit the bindings for the SBS Web Applications site to select the correct certificate. This issue will occur only if the Internet Address Management Wizard has not been run. To do this, follow these steps:

1. Open Internet Information Services (IIS) Manager.
2. Expand the server.
3. Expand Sites.
4. Right-click the SBS Web Applications Web site, and then click Edit Bindings.
5. Select HTTPs port 443, and then click Edit.
6. Under SSL certificate, select the certificate that is named "Sites."

Back to the top

You may be unable to browse https://remote.contoso.com/owa or https://remote.contoso.com/remote

Note In this example, remote.contoso.com is the external domain name of your site. This issue may occur only if a third-party trusted certificate is installed on the server.
To resolve this issue, run the Fix My Network Wizard to add the trusted certificate back to the SBS Web Application site.

Back to the top

You may be unable to use Remote Web Workplace or the Terminal Services Gateway service to connect to the server or client desktops

To resolve this issue, install the certificate on the terminal server gateway. To do this, follow these steps:

1. Open Terminal Services Gateway Manager.
2. Open the properties of the server.
3. Click the SSL Certificates tab.
4. Click Browse Certificates, and then select the appropriate certificate.

Back to the top

---

APPLIES TO

• Windows Small Business Server 2008 Premium
• Windows Small Business Server 2008 Standard, when used with:
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition

Back to the top

Keywords: 

kbsetup kbupdateissue kbtshoot kbexpertiseinter kbsurveynew kbprb KB973862

Back to the top

http://support.microsoft.com/default.aspx?scid=kb;EN-US;973862

Using the POP3 Connector to download Windows Live E-Mail

If you haven’t heard, Windows Live Mail has recently made access to your mail via POP3 a standard account, instead of a premium paid account feature!  This means that you can configure your Small Business Server 2008 POP3 Connector to download mail directly from Windows Live Mail, making a transition from Windows Live Mail to Small Business Server and Exchange even easier!  You can do this for all your @hotmail.com, @live.com and @msn.com email addresses!

Simply use the following settings in your POP3 Connector UI:

• POP3 Server: pop3.live.com
• Port: 995
• Require SSL
• Logon Type: BASIC
• Provide your LiveID credentials

The UI will look like this:

While you’ll also notice you can send mail via Windows Live via their SMTP server (smtp.live.com, port 25), Live requires that you send as the LiveID you authenticate as, so while it might be tempting that you use Windows Live as your smart host, you won’t want to because all of your company email will come from one email address.  Furthermore, when you send mail through the Live Mail service, you are sending on behalf of that particular user.  If you send too many pieces of email, or too many NDRs, that particular user can be classified as a spammer, and limited in their ability to use their account.  So stay away from using this as a smart-host!

Enjoy your seamless transition to Exchange from Hotmail.

Labels: Exchange, SBS 2003, SBS 2008, Technology Timesavers, Windows Live Services

 

http://sbs.seandaniel.com/2009/06/using-pop3-connector-to-download.html

 

추가 내용으로 IMAP커넥터로 Exchange 2007 Server에서 Live E-mail로 다운로드를 받을 수 있는 설정 (SBS200)

받는 메일 서버유형 : IMPA 커넥터

받는 서버 : 현재 가지고 사용 중인 도메인 정보를 작성 하시면 됩니다.

ex) 즉 abc@goolge.com을 사용하신다면, goolge.com을 작성하시면 됩니다.

보안 연결(SSL)필요를 선택하여주시기 바랍니다.

 

로그인 ID 작성하시고

보내는 서버 : 상위에 있는 받는 서버와 동일 합니다.

보안 연결(SSL)필요를 선택하여주시기 바랍니다.

보내는 서버에서 인증 필요는 선택하지 말아 주시기 바랍니다.

 

이렇게 하시면 설정이 가능합니다.

 

물론 네트워크 밖에서는 되지 않을 것 입니다. (사내만 가능, 사외는 불가능 한 것으로 판단됩니다)

SBS2008 SETUP 설치 2

SBS2008 SETUP 설치 1 (영문)

SBS2008 – 내부웹사이트(WSS 3.0) 원격 컴퓨터에 서버의 보안 인증서를 설치

Sender ID Framework SPF Record Wizard

How does Sender ID Framework work?

1. Sender sends an e-mail to Receiver.
2. Receiver’s inbound e-mail server receives e-mail and calls its Sender ID Framework.
3. The Sender ID Framework looks up the SPF record of the domain that Sender is using for sending the mail.
4. The receiving Mail Transfer Agent (MTA) determines if the outbound Mail Server IP address matches IP addresses that are authorized to send mail for the user.

 http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/

Sender ID: Sender ID Overview

Sender ID: "Implementation Tips for the Sender ID Framework—Creating Your SPF Record"

Windows Small Business Server 2008 Premium Trial Software Download - 한국어