Yep, sounds beautiful. Probably save me a few days as well! -Shawn ----- Shawn R. Quillman Robert Bosch Corporation RBNA/CIT7 38000 Hills Tech Drive Farmington Hills, MI 48331 (248) 553-1164 (P) (248) 848-2855 (F) shawn.quillman@xxxxxxxxxxxx -----Original Message----- From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] Sent: Thursday, August 08, 2002 12:43 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: ISAInfo.vbs http://www.ISAserver.org That's a job for an import/export tool and I'm trying to keep the functionality separate (otherwise it gets too hard to maintain). I'm already working on an update to the ISAExportImport script that will save/read using XML files, though; think that'll do the trick for you? Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison http://jalojash.org/isatools Read the books! ----- Original Message ----- From: "Quillman Shawn (RBNA/CIT7)" <Shawn.Quillman@xxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Thursday, August 08, 2002 7:00 AM Subject: [isalist] RE: ISAInfo.vbs http://www.ISAserver.org Save configuration (to a database?) then upload the saved configuration :) :) :) I've had this on my plate for a while. Would be really helpful for standalone server that can't save to AD! -Shawn ----- Shawn R. Quillman Robert Bosch Corporation RBNA/CIT7 38000 Hills Tech Drive Farmington Hills, MI 48331 (248) 553-1164 (P) (248) 848-2855 (F) shawn.quillman@xxxxxxxxxxxx -----Original Message----- From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] Sent: Wednesday, August 07, 2002 10:28 PM To: [ISAserver.org Discussion List] Subject: [isalist] ISAInfo.vbs http://www.ISAserver.org Hiya folks. I'm looking at updating the venerable ISAInfo script and I'd love to hear what your wish list includes for an ISA troubleshooting tool. Here are the present design goals:: 1. make it a compiled executable; it's gotten too large for VBScript (2K+ lines). I'm planning on VB6, since homey don't do C yet. 2. add local service enumeration and transport/port enumeration to assist with conflict resolution 3. add AD scanning to show what is actually contained in the CN=Fpc root (when appropriate) 4. change the output to XML-based, XSL-rendered so that it's easier to scan through These are not design goals: 1. Making "corrections" based on perceived problems; I hate programs that think they know everything 2. Selling it -- Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison http://jalojash.org/isatools Read the books! ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: shawn.quillman@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: shawn.quillman@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')