if you take a snapshot of the metabase object i believe this will be available in the 'inventory / windows / metabase' area in query studio.
We don't have BDSA, only Bladelogic (Server Automation) 8.0 . The question is how to do it in Bladelogic only
The agent does show metabase in the console's server browse view - is there a way to query all agents from command line for example to dump metabase information (like sites, vdir, etc.)?
Take a snapshot, manually or use the blcli to dump the snapshot to a text file.
Tried to take snapshot of metabase from /w3svc/ down.
This never works, always end up with some errors. Tried to take snapshot of a smaller subset \w3svc\some app - it works but information exportde from its results is pretty useless.
Looks like i'll be using bladelogic to just run a vbscript locally on each server to write things like virtual directories, sites, apps (from metabase) into a text file.
Which I could do even without bladelogic on windows. Which is sad - I was hoping to leverage Bladelogic somehow since it does know what metabase is and displays its contents in a live browse view....
Any other ideas?
what sorts of errors do you get?
you can make the vbs script into an EO and snapshot that.
Bill, What we're trying to do is collect the information from every IIS server, consolidate it and analyze it later. For now I'm deploying a job with vbscript which queries metabase (locally) and stores results in CSV which is then copied to a central location for future processing and import into a database I'm not sure I understand how making this vbs into EO + snapshot will help us - we'll still have to dump the snapshot results into some text file, right (its not stored in the data1base)? An we'll have to make this script available on all target hosts in order for EO to work. Btw if we do include this EO, the script will be run every time Update Server Properties job runs (we run it nightly)?
it depends what you want to do w/ the data. if you wanted to view it in a bdssa report, then the snapshot would make sense. if you are importing to another db, then what you are doing makes sense. the USP won't trigger the EO.