Vista - CDOSYS.dll missing - How do I config Win 2003 to get VBScript emai

I am trying to use CDO in VBScript to send email from one server to a
separate exchange server. The article at
http://support.microsoft.com/kb/171440/ states that CDOSYS version 6 library
is obtained "through installation" of Windows 2003 but alas, email does not
work and I am unable to locate the CDOSYS.dll on my Windows 2003 system.

I have tried configuring SMTP with Control Panel -> Add or Remove Programs
-> Add/Remove Windows Components -> Application Server -> Internet
Information Services (IIS) -> SMTP Service) but that didn't give me the
CDOSYS.dll or CDO functionality either.

What "installation" feature do I need to install/configure, to get this
functionality?

Note to moderator: I have first been here with the scripting guys:
http://social.technet.microsoft.com/...0-22e07d70d8ea
then was told to go here at server setup:
http://social.technet.microsoft.com/...9-e80f83d0679c
That moderator (I believe errantly) sent me to:
http://social.msdn.microsoft.com/For...1-c40a43902192
A member there, suggested that I come here to your forum. When you suggest
another place to take this, be specific, and try to avoid sending me to one
of the forums that I've already been to.

Thanks in advance.

"Drummer_Geek" <Drummer_Geek@newsgroup> wrote in message
news:5FCD12EC-4B70-4566-91FC-54837D00D7AF@newsgroupThis is an unmoderated newsgroup - no point in sending notes to the
moderator. I do not have immediate access to a Windows 2003 Server but on my
WinXP/Win2000 machines there is a copy of CDOSYS.dll in the System32 folder,
which makes me suspect that it's on the respective installation CDs.

I suppose you will have to replace the word "moderator" with "reader" for
now. I'd edit it if I knew how.

Yes, it's in your system32 folder, and should be in mine too. What did you
do to put it there? Likely nothing, which is why I wonder why extra steps
would be needed, but ok.

Is there anyone who has Windows 2003 who might know how they got theirs
there, either by default settings or by specific action? What actually
should be configured or installed?

"Hand" copying and registering would be my last resort, but I'll take that
over nothing. I'd like to include this step as part of the O/S install, so
that all my future server installs will have this as a standard part of their
build.

Anyone up to the challenge?
--
It''s my faults that keep me humble


"Pegasus [MVP]" wrote: