SME Managed

SCE 2007: Configuring on SBS 2003 R2 Premium Edition - SQL Workgroup Edition Needs more work to get running

David Mackie — Tue, 08 Jan 2008 01:43:24 GMT

When I wrote the post about what SQL instance and version should we install SCE 2007 to, I was pretty sure my best practice would be the copy of Express that ships with SCE 2007

I do know that running SCE 2007 on SBS 2003 R2 Premium DOES work with the Express Database that ships with System Center Essentials 2007, and to be honest this really should be good enough given the cap of 75 Devices in SBS 2003 and the number of dedicated SQL Instances that get installed on an SBS Build. So what's one more in the scheme of things?

I have completed a build on the Default Instance of SQL Server 2005 Workgroup Edition which ships with SBS 2003 R2 and all things considered I would always recommend that the Express Instance be used.

That said here are the manual work around's I used which did not need to be done using the Express Instance:

Install SQL 2005 Workgroup edition according to the SBS Installation Instructions use the version from the web site as the version on the DVD is version 1, (make sure you do not install reporting services);
Rerun the installation of SQL 2005 Workgroup selecting Reporting Services, (do not configure reporting services);
Install SQL 2005 Service Pack 2
Run the Reporting Service Configuration....

I looked at the reporting services configuration as set in the "Express Build" and made it the same for the "Workgroup Build" which I hope you agree we do not recommend. Oh BTW did I mention the SCE Installation does this for you if you choose the SQL Express route.

	Select the Correct Instance and Click Connect
	Click Server Status; Check the Service Status: is Running
	Click Report Server Virtual Directory; Click New
	Select Default Web Site; Enter ReportServer; Click OK
	Click Report Manager Virtual Directory; Click New
	Select Default Web Site; Enter Reports; Click OK
	Click Windows Service Identity; Click Built-in Account; Select Local System
	Select Web Service Identity; Press New next to Report Server; Repeat for Report Manger
	Enter ReportServer or ReportManager in the application pool name; Select Built-in Account and select Local System
	Click Database Setup; Select the SBS Server Name and click Connect; Select ReportServer from the list of Databases; Select Service Credentials from the list Click Apply
	Click Email Settings; Enter and address for the Sender Address ie Reports@smemanaged.com; Enter the SMTP Server details
	Click Execution Account; The default is domain\administrator (however I suggest some effort be taken to find a least privilege alternative)

Install SCE 2007 IAW Installing System Center Essentials in SBS 2003 R2 Standard Edition

In the section that covers the removal of the SSL Certificates the following procedure should be followed instead, if the SSL Port remains configured SCE 2007 Install will report un-configured Reporting Services.

	Select the Default web and Right Click Properties
	Click Advanced
	Select the SSL Address and Click Remove; Click OK
	Select the Directory Security Tab; Click Server Certificate
	Click Next >
	Click Remove the current certificate; Click Next >
	Click Next >
	Click Finish

Return to the installation

When complete reverse this procedure

Was this post useful?

Yes
No
Other:

> View Results
PollDaddy.com

SCE 2007: Configuring on SBS 2003 R2 Premium Edition - SQL Workgroup?? or should we install to the Express Instance and be done?

David Mackie — Mon, 07 Jan 2008 02:31:18 GMT

When I asked around about issues people have had deploying SCE 2007 on SBS 2003 R2 Premium, I was told there were some issues with SQL Server (2005 Workgroup Edition). I have not been able to collect the exact issues because many of the people are working from memory.

I do know that running SCE 2007 on SBS 2003 R2 Premium DOES work with the Express Database that ships with System Center Essentials 2007, and to be honest this really should be good enough given the cap of 75 Devices in SBS 2003 and the number of dedicated SQL Instances that get installed on an SBS Build. So what's one more in the scheme of things?

The Installing SQL Server 2005 WorkGroup Edition in Windows Small Business Server 2003 R2 Document says:

Do not upgrade the instance of MSDE that is installed for Monitoring (MSSQL$SBSMONITORING), because this it is not supported.
Do not upgrade the instance of MSDE that is installed for Update Services (MSSQL$WSUS), because this is not supported.

and the Installation of ISA Server 2004 adds a (Microsoft ISA Server 2004 instance).

I am very much in favour of doing an upgrade of the MSSQL$SHAREPOINT instance to SQL 2005 Workgroup Edition so that Full Text Search is enabled for Windows Sharepoint Services, but if I didn't have a line of business application that needed SQL Server 2005 Workgroup then I wouldn't be installing a Default Instance just because I could.

Why all the cross posting to Mackie.is-a-geek.net?

David Mackie — Sun, 06 Jan 2008 23:13:40 GMT

When I created SME Managed I really wanted to keep all the design, support and management information in the SME space together where I could refer people to it. I already had Mackie.is-a-geek.net and it is a mix of all geeky things I want to talk about and I didn't necessarily want folk to go to two places to get everything.

Not to mention right now a very different group of people are getting to each blog, I expect it to converge over time but the automatic cross posts are here to stay unless I get massive negative feedback from this post of course.

Mackie.is-a-geek.net Traffic

SMEManaged.com Traffic

SCE 2007 Problem Reporting

David Mackie — Sun, 06 Jan 2008 13:36:04 GMT

In the course of developing some of the builds for SCE 2007 on SBS 2003, my server threw an error and asked permission to send error information. As you can see the dialogue box says Please tell SMEManaged01_MG about this problem. I am curious why this does not use the Organisation from the Servers Registration information. I'm of course in search of a way to change this to give the users a better experience.

SCE 2007 Fault Finding: Failure to Install with ISA 2004 Installed

David Mackie — Sun, 06 Jan 2008 04:16:01 GMT

When I tried to install System Center Essentials 2007 on SBS 2003 R2 Premium Edition, I received an installation failure. Viewing the Setup log file revealed errors setting up reporting services.

--------------------------------------------------------------------------------

Machine : SMEMANAGED01

Product : Reporting Services

Error : The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation.

--------------------------------------------------------------------------------

Machine : SMEMANAGED01

Product : Reporting Services

Error : The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation.

--------------------------------------------------------------------------------

Machine : SMEMANAGED01

Product : Microsoft SQL Server 2005 Reporting Services

Product Version : 9.1.2047.00

Install : Failed

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_SMEMANAGED01_RS.log

Last Action : InstallFinalize

Error String : The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation.

Error Number : 29528

--------------------------------------------------------------------------------

This issue is caused by the Configure Email and Internet Connection Wizard setting the Default Web Site to the Local IP Address instead of the default All Unassigned. The fix is of course to reconfigure the Default Web temporarily to allow the installation to complete, this is described in a knowledge base article http://support.microsoft.com/?kbid=920803.

I have prepared a quick Visual Guide because some folk just like to see.

	Open IIS Manager; Select Default Web Site; Right click Properties
	Select IP Address; Choose (All Unassigned); Click Apply; Click OK Close IIS Manger

When SCE 2007 is successfully installed return the configuration to the internal IP address.

SCE Support on SBS 2003 SP1 / R2 - Good Idea??

David Mackie — Wed, 02 Jan 2008 22:19:00 GMT

I have spent some time this week installing System Center Essentials 2007 on SBS 2003 SP1 / R2 with some interesting conclusions, lets go on the journey. The first go through I installed an SBS 2003 R2 Standard Edition Server on VMware Server. I created the base server with: 127GB IDE disk,...(read more)

Installing System Center Essentials in SBS 2003 R2 Standard Edition - Computer and Device Management Wizard

David Mackie — Mon, 31 Dec 2007 13:03:00 GMT

I thought about only documenting the Device Management portion because we have a scheduled task to pick up all Servers and Workstations at 3AM Daily, but because I need instant gratification I thought so would many others. I don't actually have any other servers or desktops in the SCE Lodge right now so this would actually discover any computers but I want to follow the deployment process for installing a green field. ...(read more)

Installing System Center Essentials in SBS 2003 R2 Standard Edition - Configure Product Features

David Mackie — Mon, 31 Dec 2007 07:33:00 GMT

Assuming you conducted the installation I described for SBS 2003 SP1 / R2 the launch of the Essentials console and subsequent run of the initial configuration process is cancelled so we can cleanup the certificates for the default web....(read more)

Installing System Center Essentials in SBS 2003 R2 Standard Edition

David Mackie — Mon, 31 Dec 2007 02:03:00 GMT

There has been a good deal of Community conversation about the suitability of System Center Essentials 2007 for installation on Small Business Server 2003 SP1 / R2 and while I maintain the opinion that all SCE 2007 installs in SBS 2003 Networks should be done on dedicated Windows 2003 R2 Standard Edition servers, this build has (so far) not shown to cause significant issues with the Features or Functionality of the SBS 2003 R2 Server. This guide has been written with a Default Installation of an un-patched version of SBS 2003 R2 as the base. The configuration is Single NIC with Local Router. ...(read more)

SCE 2007 Fault Finding: Post Release Hotfix Rollup

David Mackie — Wed, 26 Dec 2007 09:12:40 GMT

When I start an install task, I try to gather as many of the required tools and fixes as possible. I knew there were some hotfixes available and was pretty happy to see there was a rollup which would save me some time. So I grabbed the executable so I could apply the fixes before I ran the configuration wizard especially since I already had one false start and wanted to get a good vanilla install so I could document it.

Here's the thing had I read the release notes I would have known this rollup patches the Installation Source and is a pre-install fix.

Here is what gets fixed...

This patch is a rollup of important post-release fixes for System Center Essentials 2007.
Included are:
(KB 936339) Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents
- Fixes a problem in which Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007. The WSUS component parts of Essentials 2007 also fail on the Essentials 2007 agents.

(KB 937831) The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted"
- Fixes a problem that occurs if the computer's NetBIOS domain name does not match the domain or if the computer's domain suffix does not match the domain.

SCE 2007 Fault Finding: OpsMgr Health Service startup problem

David Mackie — Tue, 25 Dec 2007 22:48:19 GMT

I installed SCE 2007 in my lab today, and as I do with all my Lab Machines had installed Logmein Free so I could show people features or builds when out and about. After all you can only share so much RDP in a NAT'ed Config.

After the install, the configuration wizard launched and over 80% of the config items failed. I checked that all the SCE Services were running and found I could not start the OpsMgr Health Service. A quick Live Search and discovered an Issue with Logmein.

I removed the Logmein Remote Control Tool and all is well with the world again.

The only other thing that I think is worth mentioning is when using the Microsoft Managed News Groups it would be cool if people fed back the Solutions to close the case properly.

Was this post useful?

Yes
No
Other:

> View Results
PollDaddy.com

What is this about?

David Mackie — Sun, 19 Aug 2007 05:32:00 GMT

I think System Center will become a core management piece in my Small to Medium Enterprise Networks, but didn't want to create a SCE2007, DPM2007..... set of blogs. I did want to get down on Paper (blogosphere) how I Design, Manage and Support all things SME.

I don't know that this is the absolute best format or layout but I really like Community Server and depending on user interest you can subscribe to the whole community feed or the individual areas of Design, Management or Support, obviously is you want to narrow in on a specific technology then you can just sub the tag.

So why not do this on Mackie.is-a-geek.net?? I think this is much more generic and will keep on topic much easier with a focus on what I do professionally instead of what just pops into my head.

So here is the start and let's see where it heads.