IIS 6 MetaBase Explorer

[milanbenes]

something like that Dad

Milan.

[DimPrawn]

Oh yes some more stuff (not googled just dredged up from the twisted brain wrong of a one off man mental).

This IIS6 box, does it talk to Exchange? The metabase is a fragile thing, and once it's gone it's gone.
Before doing anything like this, take full backups. You should also frequently back up your metabase and system state (particularly from the server at the root of the AD forest)

What are you talking about?

Most (public facing) web servers should be in a DMZ and therefore aren't part of a domain for (very good) security reasons.

Jeez man.

(PS I'm just trying to avoid answering Milan's dumb ass question here).

[suityou01]

What are you talking about?

Most (public facing) web servers should be in a DMZ and therefore aren't part of a domain for (very good) security reasons.Jeez man.

(PS I'm just trying to avoid answering Milan's dumb ass question here).

Typical developer living in the perfect world

You are of course right, but two bit ClientCo's don't even have a DMZ, or more than a couple of servers.

[DimPrawn]

Typical developer living in the perfect world

You are of course right, but two bit ClientCo's don't even have a DMZ, or more than a couple of servers.

Would you recommend IPSec and group policies to achieve domain isolation in this case?

Or would you recommend a read only domain controller for the web servers (Win Server 2008 R2 only) and a one way trust?

(PS I'm just trying to avoid answering Milan's dumb ass question here).

[suityou01]

oh dear

just what I didn't want to happen

I've awoken the microsoft anoraks and got them all excited about their active directory forests and sharepoint farms

look lads, simple IIS Web Server 6.0 and the MetaBase Explorer install keeps failing with the message...

'The wizard was interrupted before the IIS 6.0 Resource Kit Tools could be completely installed.'

That's the message - this is microshaft remember, but on the other side it does pay the bills so who cares eh

So ms anoraks, forget about your farms and your forests and your wizards, this is not a game of dungeons and dragons, focus on the problem in hand and find some answers

good lads

ta

Milan.

Two most likely things

1) Need to update the Windows installer thingy
2) .Net Framework is borked.

There is a command line to rejig the DNF but I can't remember what it is. GIFFS.

[suityou01]

Would you recommend IPSec and group policies to achieve domain isolation in this case?

Or would you recommend a read only domain controller for the web servers (Win Server 2008 R2 only) and a one way trust?

(PS I'm just trying to avoid answering Milan's dumb ass question here).

Typical developer missing the actual point.

I wouldn't work for a two bit ClientCo.

Fook am I starting to sound like SasGuru?

[milanbenes]

feck's sake even the microsoft anoraks are arguing about what they don't understand now

Milan.

[DimPrawn]

feck's sake even the microsoft anoraks are arguing about what they don't understand now

Milan.

Try installing it with logging:

msiexec /i <path to msi file> /l*vx C:\SomeDirectory\SomeFilename.log

Jeez!

Then obviously tell us what the log file contains.

[milanbenes]

ok you MSDN certified experts I found an alternative tool to do the job

didn't solve the problem though

kerching

Milan.

[amcdonald]

ok you MSDN certified experts I found an alternative tool to do the job

didn't solve the problem though

kerching

Milan.

You subcontracted your work to a bob ?