THE OFFICIAL BLOG OF THE SBS "DIVA" : SBS 2003 r2

Funky Monitoring reports? Try this

bradley — Fri, 01 Aug 2008 04:08:00 GMT

http://msmvps.com/blogs/bradley/archive/2008/07/25/how-many-of-you-have-sbs-monitoring-reports-that-as-of-lately-have-gotten-a-little-funky.aspx

For all of those folks that have had "funky" monitoring reports since about mid July on your R2 boxes, I want you to try on a box or two the following test:

Subject: monitoring reports not working?

7/30/2008 7:18 AM PST

By:		Les Connor [SBS MVP]	In:		microsoft.public.windows.server.sbs

If you're on WSUS v3, try running the server cleanup wizard from within 
'options' in the WSUS console. Only tick the first box (deselect the rest, 
for now), and be warned, this could take 24 hours (or more) to complete so 
just let it go.

See if the monitoring report works after the cleanup. You can also select 
the other boxes on a subsequent run of the cleanup wizard.

-- 
Les Connor [SBS MVP]
________________________
Get the SBS BPA here:
http://support.microsoft.com/kb/940439/en-us

For those who installed IE7 before installing R2 - a challenge

bradley — Fri, 05 Jan 2007 08:50:00 GMT

http://www.sbslinks.com/r21.htm

That is a screen by screen view of a SBS 2003 sp1 box with IE 7 installed prior to the installation of R2. As you can see the install "appears" to fail, but really it doesn't. All that happens is that the R2 install can't patch IE 6 because IE 6 isn't on the system. Now then one can argue that IE 7 isn't needed (not yet anyway) on a server that shouldn't be surfing in the first place.. but the point is that regardless.. that an R2 install WILL complete successfully when IE 7 is installed as this KB documents:

Error message when you install Windows Internet Explorer 7 before you install Windows Small Business Server 2003 R2:
http://support.microsoft.com/?kbid=926638

So far the issues we've seen when R2 is having issues installing is not IE7 related ... it's something deeper like messed up installer files, broadcom nics and other such weirdness....but merely installing IE 7 should not stop/break/cause failure of the R2 install process.

But this is a challenge to all those folks who say that IE 7 is blocking their R2 install.... Send me a screen shot of your server management console without the R2 installed and the log file at
C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\Logs\R2_Setup.log

Test and confirm...because I'm not convinced that IE 7 is the cause of the failure of the install.

My ancestors come from Missouri the "Show me" state... you are just going to have to "show me" on this one, okay?

How to tell if SBS 2003 R2 is installed...

bradley — Thu, 04 Jan 2007 20:21:00 GMT

From the partner newsgroup I spotted this on how to tell if R2 is installed...

Basically speaking, we have a registry key which indicates if the SBS
Server 2003 R2 is successfully installed:

SBS related Registry Keys:

* HKLM\SOFTWARE\Microsoft\SmallBusinessServer\UpdateServices

* HKLM\SOFTWARE\Microsoft\SmallBusinessServer\setup\

* "R2"=dword:00000001

* HKLM\SOFTWARE\Microsoft\SmallBusinessServer\setup\R2\

In addition, I would like to provide some information regarding the SBS R2:

1. Once SBS R2 is installed, it will create 3 new GPOs, and 3 new
ScheduledTasks.

* Small Business Server Update Services Client Computers Policy
* Small Business Server Update Services Server Computers Policy
* Small Business Server Update Services Common Settings Policy

New Scheduled Tasks:

* Update Services configuration task
* Update Services synchronization task
* Update Services auto approval task

2. Changes made to IIS after the installation of SBS R2:

* New UpdateServices virtual directory under the Default Web Site (SBS)
* New ClientWebService virtual directory under the Default Web Site (part
of WSUS)
* New SelfUpdate virtual directory under the Default Web Site (part of WSUS)
* New WSUS Web Site on port 8530 (8531 for SSL)

3. After installing the SBS R2 component, we can analyze the R2 setup log
to see if there is any error during the upgrading process:

The log file is located at:

C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\Logs\R2_Setup.log

Want an easier way?

Open up the daily monitoring email and in the top right corner it says "R2" like this:

But better yet, just open up Server Management and you have two clues:

1. R2 in the right hand side...

2. Update services is now listed

But remember R2 merely goes ON TOP of SBS 2003 sp1... so that everyone builds the base of SBS 2003 sp 1 and then we add the R2 parts on top. So if you have R2 media and don't see these things... go back... you haven't finished your install.

For those that have a base install of SBS 2003 sp1 already, you just put the R2 cdrom disk(s) in and install the R2 parts. There's no need to reinstall the base of SBS 2003 sp1.

Upgrading to R2

bradley — Wed, 29 Nov 2006 20:29:00 GMT

So you have a SBS 2003 sp1 box and you just got your Action pack.... how do you update it? Do you

a. Merely stick in the dvd and it will automagically update or

b. Drill down to the R2 parts and run the individual cdroms?

The answer is b.

These disks make up the base:

Windows Small Business Server 2003 R2 Premium Edition CD1

Windows Small Business Server 2003 R2 Premium Edition CD2

Windows Small Business Server 2003 R2 Premium Edition CD3

Windows Small Business Server 2003 R2 Premium Edition CD4

Windows Small Business Server 2003 R2 Premium Edition - Office Outlook 2003

So if you already have SBS 2003 sp1... you already have that.

Windows Small Business Server 2003 R2 Premium Edition - Premium Technologies Disc 1

Windows Small Business Server 2003 R2 Premium Edition - Premium Technologies Disc 2

These two disks are ISA 2004 sp1 and SQL 2005 workgroup. If you have already applied ISA 2004 sp1 ... or you decide to not install it, you can just skip over the ISA install. If you already have SQL 2000 installed, you need to follow the upgrading steps at http://www.sbslinks.com/sql2005.htm . If you don't want to install SQL 2005, and instead just leave everything at MSDE, then you can skip these disks. Remember that you can't upgrade SBSmonitoring to SQL (2000 or 2005) and while WSUS 'can' be upgraded to SQL 2005... it runs just fine on MSDE.

Windows Small Business Server 2003 R2 Premium Edition - R2 Technologies CD

This disk is Exchange 2003 sp2, Sharepoint sp2 and the SBSized WSUS. If you've been a happy patcher, you will already have Exchange 2003 sp2 and Sharepoint sp2. If you've already installed WSUS, you can install the R2 version over the top and it will/it may change any customizations you've done. If you have never installed WSUS before.. now's your chance to install it. Once it's done installing...while you can use the 'normal' WSUS interface.. it's way way easier to just use the SBS 'update services' console in the home page. And remember.. while this can be installed remotely.. you MUST use the built in admin account to install it.

P.S. If you don't install the WSUS... you also won't get the new Update services part...

About that DVD media

bradley — Thu, 09 Nov 2006 05:39:00 GMT

http://msmvps.com/blogs/bradley/archive/2006/11/08/So-you-have-CDroms-and-want-a-DVD_3F00_.aspx

Does everyone realise that the base of SBS 2003 r2 is SBS 2003 sp1 standard?

SBS 2003 R2 ...the "R2" parts on are the disks at the end...they are not integrated with the install...thus if you are looking for a DVD of SBS 2003 sp1 for testing purposes... the base of the "R2" is SBS 2003 sp1 on that action pack DVD.

Now then... you cannot...and you should not...use the action pack media to install at your clients. Like media should be used for like media... so call that licensing department to see if a DVD that you can use in your clients can be obtained.

In the October Action pack

bradley — Mon, 09 Oct 2006 07:36:00 GMT

SBS 2003 R2 Internal-Use Software in October Action Pack

Look in your October Microsoft Action Pack for your internal-use software. Also, find out how you can get a free for-resale copy of Windows Small Business Server 2003 R2 (SBS 2003 R2)--a US$599 value. SBS 2003 R2 provides an integrated, cost-effective platform on which you can build a profitable business by offering small business services and IT consultancy.

Update Kits should be shipping around October 11, 2006. (Allow 10 – 15 business days to receive your kit.)

Installing SQL 2005 workgroup from a means 'other' than a cdrom

bradley — Sat, 07 Oct 2006 22:48:00 GMT

So the other night I installed SQL 2005 workgroup on my R2 box and I had copied the cdroms up to the server and installed from there. When I did that, at the end of 'cdrom 1' I got this error.

But see it wasn't really an error, it was expecting the second cdrom. So I started up the setup.exe from the folder of cdrom 2 and if I remember right it was "client components" was on cdrom 2 that I checked to install and the install finished up without a hitch.

"Under Client Components, click Management Tools, and then click Entire feature will be installed on local hard drive. Click Next to continue, and then complete the wizard."

http://www.microsoft.com/downloads/details.aspx?FamilyID=29CB973D-41D8-4A5E-9312-90982A0FC164&displaylang=en

So if you have a dvd or you download the files to your server and don't use the cdrom... just pick it up where it left off and finish the install.

ISA 2004 on SBS 2003 R2

bradley — Sat, 07 Oct 2006 22:36:00 GMT

When you install R2, make sure you read the install instructions -- http://www.microsoft.com/downloads/details.aspx?FamilyID=29CB973D-41D8-4A5E-9312-90982A0FC164&displaylang=en

After you install ISA 2004 you'll need to install ISA 2004 sp2 for an issue with the MMC 3.0 and ISA 2004:

It is important that you install Service Pack 2 (SP2) for ISA Server 2004 if you are also installing the Windows SBS 2003 R2 Technologies. SP2 for ISA Server 2004 resolves a known compatibility issue with Microsoft Management Console (MMC) 3.0, which is included in the R2 Technologies. To obtain SP2 for ISA Server 2004, see the downloads page for ISA Server 2004 at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkID=22657).

Note
After you install SP2 for ISA Server 2004, you also need to install an update that resolves known HTTP issues in SP2. To obtain the update, see Article 916106 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=67767).

Got SBS 2003 R2?

bradley — Sat, 07 Oct 2006 09:11:00 GMT

This update corrects an issue that results in an error message when you use the Microsoft Connector for POP3 Mailboxes Snap-in with Microsoft Management Console (MMC) version 3.0.

http://www.support.microsoft.com/?id=921096

If you have SBS and WSUS installed, you'll see this offered up in your SBSized WSUS interface. It's due to the MMC 3.0 ..now mind you many a SBSer would say that you shouldn't see this anyway as you shouldn't use the pop connector program in the first place :-)

Upgrading to SQL 2005 workgroup from SQL 2000

bradley — Sun, 01 Oct 2006 01:24:00 GMT

When upgrading from SQL 2000 to SQL 2005 workgroup there's a couple of things you should read up ahead of time... the first being the "official" upgrade guide. the second is the "Susan" version of the document that just covers the needed steps for upgrading SQL 2000 to SQL 2005.

Extracting the XML files using the 'cab' method is much easier than typing in the command to extract (the first time I did it I obviously typed in the command wrong).

But if you are planning an upgrade, print out both documents 'and' the KBs and you'll be in good shape for the upgrade... uh.... just don't follow my lead and lock your car/office keys in the server room...that's not exactly a best practice I'd recommend to follow....

Installing the R2 disk over remote desktop

bradley — Thu, 14 Sep 2006 14:17:00 GMT

When you install the R2 disk over remote desktop the only caveat is that you need to be logged in as the built in administrator account (aka the "500" account)

It WILL work over a RDP session though and will install.

In general everything BUT ISA can be installed remotely as long as you use the built in admin account (and btw the use of the admin account is documented BOTH in the readme and on the SBS blog)

Can SBS work in more than one location?

bradley — Thu, 31 Aug 2006 04:54:00 GMT

Hi susan

Please advice us on the best possible solution for this scenario.

Currently we have only one office in B__. We are running SBS 2003 on our network. We use windows authentication extensively and also exchange for email. Right now we are not using Sharepoint server at all. All clients are Windows XP/Office 2003 Standard.

This month we are setting up a new office in D__i and within 2-3 months we will have another office in M__i followed by offices in all the metros. I wanted to set up a local windows server in each office to cater to the authentication needs of the systems in that office. Also, in the B__ e office I would like to setup a backup domain controller (to replicate active directory).

All employees (across offices) will need domain.com email address. I have configured Outlook over http and want to use that for the time being. Hence, I require only Windows 2003 Server (with replicated active directory) at the branch offices. At a later point, I want to setup local exchange server as needed.

All offices are connected with ADSL lines to the internet and there is no inter-office link. This setup will not change (meaning we won't have inter-office linkage)

I did some research on this and found that SBS cannot support this scenario. Is that true? If yes, what is the best way to go about it?

Hi back at ya.... first off I'd like to bring up the idea of "branch offices" versus "branch computers"

Remember that with a SBS network we cannot do domain trusts..but we can have additional domain controllers to assure domain authentication. With the R2 era we can also add additional Exchange servers without adding cals.

Now then ... there is no wizards in this setup and any additional Exchange server would be manually set up. But that doesn't mean that SBS cannot be the base server of a small firm's domain. As long as you stay with the single domain setup ...and given that I know someone running umpteen computers in a workgroup... I personally think this is a do-able setup. Persistent VPNs and what not...but we're doing these sort of setups now with the SBS server as the base.

The problem is that SBS is just way too good of a base to not use in a small firm. Okay okay, the cheapness is a strong thing in it's favor...but given that SBS is the only one with RWW and the wizards it has.. it's too dang good to give up.

Microsoft tends to say that SBS is not for a branch office setup...but the other day Chad had a SBS network with 13 offsite "branch" connections to that SBS server ...all locations with one or two workstations. All with persistent VPNs. Is that a branch office? Probably not in Microsoft speak...but in a SBS domain?

..if it works... it works.

Want to read the retail R2 documentation?

bradley — Tue, 29 Aug 2006 03:11:00 GMT

Couple of interesting things in the R2 documentation...

15 gig recommended partition size
"If you are a Microsoft Premier Contract holder, please contact your TAM or ADC" (for a SBS box? Like I've ever seen a SBS customer have a TAM?)
I was surprised that they featured support from Gold Certified partners and not SBSC

Another good resource for SBS R2 info on SQL and downgrade rights is this link

When you receive your R2 media

bradley — Sat, 26 Aug 2006 05:40:00 GMT

Just play it safe and double check that the file folder of the Exchange sp2 on the R2 media NOT dated in May of 2006 but rather in July.

I literally just received today from a distributor a copy of R2 Standard upgrade and it wasn't the final parts but the old May version.

Review this for how to determine the good parts.

There's R2 parts on the Web

bradley — Thu, 24 Aug 2006 00:36:00 GMT

Okay so here's the scoop...while the outside of the screen appears that the MSDN/TechNet Plus is not the final R2 parts and the "printed" date on the file says 7/11/2006...when I burned it down, mounted a virtual cdrom you could tell the R2 cdrom was indeed the final parts. (all done, mind you, via RWW as my home PC could pull down the ISO faster than I could while wireless in Chicago Airport. Since I got at the airport at 5 p.m. Chicago time and am not flying out until 9 p.m. I figured it was way to keep me entertained and somewhat awake... I leave at 9 p.m. Chicago time and arrive home 1 a.m. Fresno time),

Bottom line, once you look under the hood, it's very obvious that the R2 parts are the final and real R2 parts.

That 6.5.7638.2 confirms that it's the .2 bits and thus the right final parts for one.

The fact that the "created" date on the SP2 folder is also July 21st is more proof that this is the updated version.

So even though "visually" it doesn't look like the bits are the final bits (it appears the original date of posting hasn't change) under the hood they are indeed the real and final parts.

Also looks like on the MSDN site the localized versions are starting to go up on the web:

So if you have TechNet or MSDN... the final R2 parts are finally here.

Amazingly it doesn't break as much as I thought it would

bradley — Sun, 20 Aug 2006 00:21:00 GMT

I didn't get a blue check.

I downloaded WSUS 3.0 on top of a beta test box of SBS 2003 R2 and I didn't get a blue check. Interestingly enough it didn't break as much as I thought it would. I still got the daily integrated email. I'm not sure if the 'approval' mechanism and SBSized reporting still works and all that... as I only have it on a server box that was patched....but I was actually very surprised that I didn't get a blue check and the SBSized console still controlled the "syncronize now" part.

http://blogs.technet.com/wsus/archive/2006/08/14/446775.aspx

Bottom line ... still DO NOT put this on a production server it is STILL a beta.... but I was actually surprised nonetheless.

R2 is still MIA

bradley — Sat, 19 Aug 2006 01:20:00 GMT

You see Andy.. it's like this... it's called burning in the media. There's more to delivery of software than 'just' getting the final bits. There's media that has to be pressed, product key stickers done, and all that lovely stuff. So while the patch for the 'non final bits' has been out on the web, it still takes time for the media to be done. I seriously doubt that you can find this in a retail store or online by the end of the month. Keep in mind that the application of SBS r2 part on "top" of SBS 2003 sp1 is nothing like the application of the service pack of SP1.

So.. R2 is still not yet in the channel yet... be patient...

And the iso/images up on the MSDN site appear to still be the July old bits ....so play with them if you want... but remember they are not the final final R2.

SBS 2003 R2 Tech Assessment Toolkit

bradley — Fri, 18 Aug 2006 05:23:00 GMT

http://www.microsoft.com/downloads/details.aspx?familyid=04c69807-3d58-4047-94df-723de8b5c764&displaylang=en

A step-by-step guide on how to assess the technology needs of small business customers

The MSDN bits are????

bradley — Mon, 14 Aug 2006 02:19:00 GMT

Robert reminded me that the SBS 2003 R2 is back on MSDN but the dates are still July...soooooo..hang loose until we figure out if these are good new bits... or someone forgot and put them back up there or what....

I pulled the R2 disk down and will burn it from the iso image just to see if the 'innards' are the final ones.

Update: Okay I just pulled down the iso's and burned them in.. and that's still the 6.5.7638.1 version and not the 6.5.7638.2 like I think it should be: Hang loose a bit and don't pull down this version until we get clarification as it does not appear to me to be the proper re-released parts.

http://support.microsoft.com/kb/923432/en-us

Exwriter.dll

To determine whether the update is installed correctly, verify that the properties for the files that are listed in the table display 06.05.7638.2 as the version level.

When Software Assurance just might make sense

bradley — Fri, 11 Aug 2006 07:20:00 GMT

An interesting factoid that we stumbled across the other day.. okay so you bought SBS 2003 a few years back.. and you didn't opt for software assurance (not the koolaid drinker). So here comes SBS 2003 R2. And lets say that for some bizarre reason you find R2 compelling. (Hey it's Friday... work with me here this is R2 Friday after all). So you buy the version upgrade ($299 to upgrade a Standard to R2 T72-01415, $699 to upgrade a Premium to R2 T75-01256. You could now.. add Software Assurance to that and lock in SBS Longhorn. Now keep in mind that Longhorn is based on the 64bit only platform so you need to either

make sure that the hardware you are buying now is 64bit capable ...most is
understand that you will be buying new hardware

It also means that there's no inplace migration... which .. personally... I prefer clean installs as the security and permission leves are way way better than an inplace upgrade from Windows 2000.

Now if I were you I'd buy three year SA not two year. You see last time I had to re-up for Software Assurance back in June of 2004... and I've been an SA customer since the beginning.. I looked at the Longhorn development and opted for three year SA thinking that I just might squeeze in Longhorn. Well come to find out it ended up that my three year SA ended up locking in R2. And at least that's a good thing because if I would have gone with just two year I would have had cold server rights, e-learning, and since March of this year, one phone support call, and web based email support.

Now I'll be horribly blunt here. Small businesses ... I don't think... get a value from that. They expect an upgrade to the OS for the Software Assurance. So if you think you have a firm that would be itching to get to a 64 bit platform.. and they can see/get the value in the SQL 2005 workgroup... and they can even get value from the expanded cal rights... see if they might be forward thinking enough for grabbing onto software assurance benefits.

Yeah.. it's a bit of a stretch for a small business... but there might be one or two insane folks out there that will do it.... you never know...