Re: SBS 2003 Windows Update Question

In lieu of fixing Microsoft, though, a CD-R copy of the installation
media ain't a bad idea.

On Feb 24, 11:26 am, "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
<sbrad...@xxxxxxxxxxx> wrote:
I hear you ...but it's near IMPOSSIBLE right now to get downgrade
media. Microsoft needs to be fixed first.



allanc wrote:
I am at the clients site now (Sat. 11 am EDT).
All CD media have 'R2' on the label except Office Outlook, Front Page
and the OEM Preinstallation Kit.

He must have 'borrowed' the media from another one of his clients.
So, the client has SQL 2000 installed but no media for it.
Now the client is up the creek if we need the CD for any reason.

This is (and has been) very upsetting for both my company and the
client.
There have been other irregularities that I really do not want to go
into in this open forum.

On Feb 24, 12:40 am, "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
<sbrad...@xxxxxxxxxxx> wrote:

The downgrade of SBS 2003 R2 premium is SBS 2003 sp1 premium.

Run MBSA on that server and see what versions you get.

On the Server Management console in the upper right corner (start, top
of the start menu is Server management), is there a "R2" logo in the
right corner and a "Update Services" button in there?

If so what he did was remove SQL 2005 and install a SQL 2000 sp3 media..
Now one could argue this is eula violation as the downgrade rights are
all or nothing ...but in the mood I'm in after the DST patch fiascos...
I don't really care. Technically speaking a "downgrade right" to SQL
2000 should have had him rolling back to SBS 2003 sp1 (no R2 WSUS parts)
and a new media kit that is darn near impossible to get because
Microsoft still hasn't gotten the media fulfillment fixed.

So I'm not going to stab that vendor in the back and say "OH he screwed
you up because he didn't get the proper downgrade right media" as he's
probably doing the best he can.

Run MBSA. That will tell you what's missing.

http://www.microsoft.com/technet/security/tools/mbsahome.mspx

allanc wrote:

The accounting application that we install requires SQL 2000.

In a nutshell another vendor installed SBS 2003 Standard.
We needed the Enterprise Manager and told him 'SBS 2003 Premium with
SQL 2000'. The next time we went back on site he somehow had installed
SQL 2005.
We complained again and finally he had installed SQL 2000 (with
Enterprise Manager).
We tried to migrate our accounting appliciation from an old server to
this new one but there were issues when we ran the application.
Based upon advice in this n.g., we insisted that he flatten the server
and install SBS 2003 Premium with SQL 2000.
Today, we see that SQL 2000 SP4 has not been installed and are
worrying about other service packs, patches, etc.
The sentence above is basically how I started this thread.
So, you are saying that if *all* CDs on site read 'R2' on their label
then there is no way that SQL 2000 could be legally installed? Could
he not have obtained a 'downgrade' (of SQL) and 'forget' to leave it
at the client's office?

On Feb 23, 11:29 pm, "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
<sbrad...@xxxxxxxxxxx> wrote:

Oh duh...he did say "R2"

uh then that's slightly in EULA violation....... R2 should have SQL 2005
but this could be an upgrade from SP1

Justin Brown - SYNACS wrote:

Just to interject... I deployed SBS 2003 Release 2 a few weeks ago,
and it included SQL 2005, not SQL 2000.

So the Premium Technologies disc included ISA 2004 and SQL 2005, even
before the R2 Technologies disc was applied. Is there a variation of
R2 that did not come with SQL 2005?

On Feb 23, 1:20 pm, "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
<sbrad...@xxxxxxxxxxx> wrote:

WSUS - the patch management engine.

If this person has an RTM version of SBS, yes they should have SP1 on it
but many firms do not keep up on service packs in general. SBSers are
not unique in this.

There is a 5 part service pack for SBS that makes up sp1 and the last
part includes SQL 2000 sp4.

allanc wrote:

WSUSable? That acronymn is not registering ... sorry :(.
So, you are saying that SBS 2003 sp1 is supposed to be installed with
the Premium Edition or not?
Again, sorry for my confusion.

On Feb 23, 2:07 pm, "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
<sbrad...@xxxxxxxxxxx> wrote:

SQL 2000 sp4 is not WSUSable as far as I remember (I will confirm but
I'm pretty sure creaky SQL 2000 can't be wsus'd until after SP4. This
comes in via SBS 2003 sp1 is applied.

allanc wrote:

My company did not install the SBS.
We have been called in to install an accounting app. that uses SQL
server.
We noticed that the SQL Server 2000 SP4 was not installed and
'complained' to the company that installed the SBS.
They said that there was no SQL 2000 SP4 since it did not
automatically appear when they clicked on Help then Windows Update.
So, to summarize - I *should* be concerned that there might be other
Service Packs and that the company that loaded the SBS is not
competent?

On Feb 23, 11:16 am, dami...@xxxxxxxxxxxxxxxxxxxx ("Damian N
Leibaschoff [MSFT]") wrote:

Hi,
Are you going to the Windows Update site or Microsoft Update?
You should be opening the Microsoft Update site to get updates for products
such as SQL and Exchange.

On the other hand, if they are running with the R2 technologies CD
installed, then the automatic updates client would be looking for the
information from the central Update Services location, only security and
critical updates would show up automatically, the rest would need to be
approved by an administrator for installation from the SBS Server
Management console, Update Services snap-in, Waiting for Review.

Regards,
Damian Leibaschoff

--------------------
| From: "allanc" <allan.for.g.gro...@xxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: SBS 2003 Windows Update Question
| Date: 23 Feb 2007 07:02:54 -0800
| Organization:http://groups.google.com
| Lines: 12
| Message-ID: <1172242974.264023.264...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 74.107.179.220
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1172242991 8837 127.0.0.1 (23 Feb 2007
15:03:11 GMT)
| X-Complaints-To: groups-ab...@xxxxxxxxxx
| NNTP-Posting-Date: Fri, 23 Feb 2007 15:03:11 +0000 (UTC)
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET
CLR 1.1.4322),gzip(gfe),gzip(gfe)
| Complaints-To: groups-ab...@xxxxxxxxxx
| Injection-Info: m58g2000cwm.googlegroups.com; posting-host=74.107.179.220;
| posting-account=4t0G4g0AAABIvbWzXyuCDY8yxfNv8vXt
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx..gbl!newsfeed­­­­­0
0.sul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dc­­­­­a
.giganews.com!nntp.giganews.com!postnews.google.com!m58g2000cwm.googlegroup­­­­­s
.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server..sbs:19191
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| A client has SBS 2003 Premium R2 installed.
| The SQL Server is 2000 version RTM.
|
| When we check for Windows Updates, service pack 4 for SQL 2000 *is not
| displayed*.
| That does not seem correct.
|
| Also, if the Windows Update is not functioning properly for SQL
| Server, should I also be concerned about Exchange, etc?
|
| TIA.
|
|- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


.