Just looked at the article and see that some people want to execute DBCC commands on a remote server. I not sure you want to do this as it is a power full tool and you can really make a mess of things. To collect data and stats is one thing but to do anything else, I believe that you should be doing that on that server, not remotely.
I've written my own server farm code that performs the same function but I've been playing with Quest SpotLight for SQL Servers Enterprise and it really does the trick. If your company has 30+ servers that you are maint/manage/monitoring then you should get them to spend some money and get something with more teeth. The app does real time monitoring and historical data collection, which is great for diagnosing an issue. I also use another product call Capacity Manager from Quest (..no I don't work for or get kick backs from Quest!) it too has tons of information on growth, growth patterns, disk space etc.
Check them out I think you will find them worth the talk to you management.
On a side note, I use my "home grown" code to produce an hourly report that show all failed jobs on all SQL servers. The developer have access the test/uat/dev reports and we look at the production reports. It's a great way to see what's happened or happening on a job level.
Just my 3 cents worth : )