Re: R2 Incompatibilities
- From: "Jabez Gan [MVP]" <mingteikg@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Apr 2006 00:35:52 +0800
Feel free to drop me an email at mingteikg [ a t] mvps.org if you need
further assistance on this. :)
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
"Charlie" <baboon@xxxxxxxxxxxxxx> wrote in message
news:255FAB91-B849-4823-8CBA-39E6C303C91C@xxxxxxxxxxxxxxxx
Thanks very much for making me feel vindicated.
I was thinking along those lines, but I wanted it confirmed, especially
by
an MVP. I'm going to print out this post and bring it to my meeting
tomorrow. I'm sure I will be hearing that I should not have installed an
"unsupported" OS. But I have this and other evidence which suggests that
it
is a supported OS - Windows 2003, SP1.
"Jabez Gan [MVP]" wrote:
Hi Charlie,
Sorry to hear that you are having quite a few issues with R2.
Let me assure you that the crash isn't directly related to R2. Again, R2
is
all about adding new features to W2k3 SP1 and it contains no codebase
fixes.
It means that R2 doesn't contain security fixes/patches/updates to W2k3
SP1.
On why did it crash the server, try using WinDbg
(http://www.microsoft.com/whdc/devtools/debugging/default.mspx) to debug
the
..dmp file (that the crash created). You should be able to better
pinpoint
the problem.
Again, let me assure you that all programs which work on W2k3 SP1 must
work
with R2.
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net
"Charlie" <baboon@xxxxxxxxxxxxxx> wrote in message
news:0D6A3E1A-083E-40D4-B509-BA34DF419251@xxxxxxxxxxxxxxxx
I recently set up a file and print server using W2K3-R2. I didn't do a
whole
lot outside of a default installation, other than use the Security
Configuration Wizard. Of all the R2 components, I only installed the
ones
made for file and print management.
When finished, I tested the server and all was fine. I later found out
that
another branch of IT was taking it over and would be installing Black
Ice
Defender, which is something they routinely do on servers. I expressed
my
concern over this because of the security configurations that I had
made
using SCW.
Black Ice was installed sooner than I thought and without rolling back
the
security configurations. Right after the installation, the server
crashed.
The people from the IT department in question blamed it on the fact
that
the
OS is the R2 version. One person went so far as to say that it was
also
incompatible with VirusScan 8 and the Tivoli TSM Client (both installed
on
the server) as well as the ATI video driver. So far I have visited
the
McAfee and IBM websites where it clearly states that VS 8 and TSM are
compatible with R2. So thusfar this particular person has a
credibility
problem.
I have understood that R2 really is just W2K3 with SP1 and some extra
components. I also understand that when installed as a domain
controller,
the AD Schema must be upgraded, so that suggests than in some way it's
seen
as a different OS. Still, do any of the above contentions seem valid?
Is
anyone else seeing any compatilbility issues that they *know* are
related
to
R2? I'm guessing there may be some instances where problems caused by
SP
1
are being blamed on R2.
Any help on this would be greatly appreciated. Just looking for some
honest
feedback, even if it contadicts my assertion that R2 isn't the culprit.
Thanks.
.
- Follow-Ups:
- Re: R2 Incompatibilities
- From: Charlie
- Re: R2 Incompatibilities
- References:
- Re: R2 Incompatibilities
- From: Jabez Gan [MVP]
- Re: R2 Incompatibilities
- From: Charlie
- Re: R2 Incompatibilities
- Prev by Date: Re: Reinstall windows installer
- Next by Date: Re: certificate expiration date
- Previous by thread: Re: R2 Incompatibilities
- Next by thread: Re: R2 Incompatibilities
- Index(es):
Relevant Pages
|