MSXML....

[Cary Shultz]

Howdy! Howdy!

Hey, I have been working on getting a nice WIN2000 SP3 RIS
installation going with all of the Critical and
Recommended updates ( $OEM$ ). With the help of a few
people in this NG I finally have a beat on MDAC. I am
going to do some testing tomorrow. This is done with a
simple .cmd "script".

This leaves MSXML left to figure out. I have been looking
and looking and looking - but have not found out any way
to install it via my script....

Well, let me clarify: I have a WIN2000 integrated SP3 RIS
image. I make use of $OEM$ and cmdlines.txt to take care
of most of the Critical and Recommended Updates during the
initial installation. I have 22 of them and use the
updated QChain. For the remaining nine or 10 updates I
run a simply batch file with QChain AFTER I install IE6
SP1. It looks like MDAC is going to have to be a separate
batch file - but that might change. That would leave
MSXML 3.0....

Does anyone have any hints for me? I am not able to find
anything...

Thanks all!

Cary

 

[NIC Student]

Thanks for all your updates Cary, we'll pass them along to others if the
questions reoccur.

 

[Gerry Hickman]

Just needed to to go to www.microsoft.com/xml and the
MSXML 4.0 SP2 has an .msi installer! Even better!

Thanks, I'll have a look.

 

[Gerry Hickman]

Hi Cary,

One more thing: my RIS Server is WIN2000 SP3. I am not
going to mess with SP4 because then I would need to create
a slipstreamed SP4 image and then do the slipstreamed SP3
image. With the potential problems with SP4 I do not want
to chance anything...not just yet!

Can you clarify the problems with SP4? I have it on my home computer
(which has just about every horrible app you can imagine), video capture
and editing, games, CD packet writing, VS.NET 2003, SQL2k "personal",
IIS, Corel, etc. - so far so good.

I've got a new user about to log into it first thing at work tomorrow,
so I hope it's going to be OK!

 

[Gerry Hickman]

Working on getting the SP3 RIS image perfected. I am
going to work on IE6 SP1 next - there is that .msi wrapper
that I am going to start attacking soon.

You can launch an IEAK build from a command line (I think but haven't
actually done it yet), or you can also "include" it in an unattended
build (again, as far as I know but I haven't actually done it).

Currently, I insert a boot floppy and type "Go"; this nukes the machine
and installs Win2k SP4, then about half an hour later I log on locally
and type \\server\share\ie6setup.exe and about 10 minutes later I do
office 2000. I could probably automate these steps, but it's only 3
"clicks" and it's built.

BTW - I figured out how to get DirectX 9.0a installed. I
downloaded the DX9NTopk.exe from the Microsoft OEM site

Very cool! Is this a public site?

Not sure what you mean with your last sentence: IIS/Index
Server/RDS now included? With what?

I was saying, I think the updates for IIS are NOW in the service packs,
but under NT4 I don't think they were, and Index server was elusive in
the extreme.

And what is RDS?

Remote Data Services; lots of exploits to look out for - now mainly
patched, but some may need "administrative action".

I
know about and use RDP a great deal...

What the hell is that?

 

[Cary Shultz]

Gerry, inline....

-----Original Message-----


You can launch an IEAK build from a command line (I think but haven't
actually done it yet), or you can also "include" it in an unattended
build (again, as far as I know but I haven't actually

done it).

Gerry, I am going to start messing with both the IEAK as
well as that nice little .msi wrapper...

It looks like IF I can get the .msi wrapper to work then I
can automate this whole thing...I could assign IE6SP1 GPO
to the computer configuarion and then those "secondary
updates" - sorry, do not remember if I have mentioned them
in this string. Essentially I do the $OEM$ with the 23
hotfixes with QCHAIN that I can get with the RIS image.
That runs nicely. I then have to manually install IE6SP1
and then apply the "secondary" hotfixes - like the IE6SP1
patch and the OE6 patch - via a .cmd file. These
secondary patches I could run via RunOnce .

Currently, I insert a boot floppy and type "Go"; this nukes the machine
and installs Win2k SP4, then about half an hour later I log on locally
and type \\server\share\ie6setup.exe and about 10 minutes later I do
office 2000. I could probably automate these steps, but it's only 3
"clicks" and it's built.

That makes things nice. I remember messing with the
WIN2000 CD and the winnt.sif floppy. That was nice for a
beginning...moved on to RIS and have been trying to
automate as much as possible....

Very cool! Is this a public site?

Yes, well, er, sorta. It is http://oem.microsoft.com.
You have to have a user account and password. For this,
you need to have your own company or work for a company
that builds Computers....you register and a whole new
world is open to you....I think that I saw a post in here -
or Setup - where Oli mentioned it..

I was saying, I think the updates for IIS are NOW in the service packs,
but under NT4 I don't think they were, and Index server was elusive in
the extreme.

Not sure about his. I seem to recall that there is a
little something out there specifically for IIS. The only
time I deal with IIS is when I am installing Exchange
2000. I usually do the IIS Lockdown and URLScan tools. I
would have to look. And I do not run IIS on any DCs or
File/Print Servers...is a service is not needed it aint
running!

Remote Data Services; lots of exploits to look out for - now mainly
patched, but some may need "administrative action".

Thanks for that tip. Ignornance is not always bliss!

What the hell is that?

I did not know about that until two months ago. It is
Remote Desktop Protocol and runs on port 3389 ( I
think ). It comes built in with WINXP ( Start | Programs
| Accessories | Communications ). What it allows you to
do is to connect to a Terminal Server ( instead of using
those dastardly little floppy disks with the Terminal
Server Client ). I use it all the time to connect to
Servers in "remote" locations ( here in Southwest Viginia
there is a lot of "country"! ). It is very very nice....



Cary


PS Sorry for the delay. I have spent the last three days
at two of those "remote" locations...

 

[Gerry Hickman]

Gerry, I am going to start messing with both the IEAK as
well as that nice little .msi wrapper...

Let me know if you want to discuss IEAK. the NG is dead and no one seems
to understand it very well. (there's some aspects I also don't
understand too)

It looks like IF I can get the .msi wrapper to work then I
can automate this whole thing...

One interesting aspect of the IEAK is you can use AutoConfig - it's an
INS file that allows you to change settings on the fly.

e.g. suddenly change everyone's home page to BadGrrrls.com, or more
usefully, adjust everything ready for your massive server migraion plan.

Some of this crosses over into GPO so gets a bit confusing. As far as I
know, you can do more with IEAK than GPO at present, but we don't have
GPOs yet, so I may be wrong about that.

That makes things nice. I remember messing with the
WIN2000 CD and the winnt.sif floppy. That was nice for a
beginning...moved on to RIS and have been trying to
automate as much as possible....

We don't have DHCP so I use unattend.txt, but no CDs, just boot floppy,
network access and off it goes...

I'm hoping to try a memory stick version soon. If we ever get DHCP, I'll
try RIS. I'm not sure of the future for unattend, as they may kill NTLM
at some point.

Yes, well, er, sorta. It is http://oem.microsoft.com.
You have to have a user account and password.

OK, I'll look into it. Thanks.

would have to look. And I do not run IIS on any DCs or
File/Print Servers...is a service is not needed it aint
running!

I'm running a production world wide web server with it. We installed it
the day after Nimda struck. There's no URLScan or "lockdown" nonsense,
and it's not in a DMZ. We had Apache before, but wanted to run .NET and
SQL 2000. So far we've had no downtime except for adding the odd patch.

I did not know about that until two months ago. It is
Remote Desktop Protocol and runs on port 3389 ( I
think ). It comes built in with WINXP ( Start | Programs
| Accessories | Communications ). What it allows you to
do is to connect to a Terminal Server

Ah OK.