Alan Renouf is a busy man and always seems to be one step ahead of the game. This is certainly true of his latest creation – vDiagram. Many of you may be familiar with the Active Directory Topology Diagrammer (ADTD), a tool available from Microsoft that pulls information from Active Directory and draws it in a Visio diagram. The diagrams that it produces can save a lot of effort in technical documentation and the same sort of thing has been missing for Virtual Infrasructure for some time. Alan’s PowerShell script requires only PowerShell and Microsoft Visio 2003+ to produce a nice Visio diagram of your VI. Head on over to Alan’s site to download it and try it out.
Never leave home without it. No, it’s not an Amex card, it’s the VI3 Reference Card written by Forbes Guthrie. A lot of things on this little gem pop up or are useful in the VCP exam and day-to-day it’s come in handy a number of times. I’ll try and keep a link to it in my useful links sidebar but it’s well worth bookmarking it yourself.
Why oh why do people slow down for speed cameras? On a dual carriageway with a central reservation the speed limit is 70mph. A speed camera on this road will only take your picture if you’re going above that (well, probably above 73/74mph really). So why do people slow down to 60mph?
Here’s the scenario: You’ve just hit shut down in your remote desktop session. You’re logged off Windows Server 2003 and your RDP session is closed. You wait a while and try to login again. Surely the server must have rebooted by now. But try as you might, you cannot get back in. Port 3389 shows as open and the IP is pingable. So the options are: 1. Dig out iLO credentials (assuming that it is installed / setup) and force a reboot from a remote console. 2. Walk over to the server and force a reboot (the most recent time this has happenned to me, the server was in another building and it was raining heavily). 3. Use conventional Windows management tools to shut the server down remotely. 4. Use PowerShell. This last option is the one that we’re going […]
I’ve lost track of the number of clusters that I have implemented or supported over the last few years. With each edition of Windows server that comes out clustering has improved. It was a bit of a dark art with Windows 2000 and in Windows 2008 it’s pretty much all point and click (and not many clicks at that). Most clusters that I encounter at the moment are still 2003. In a lot of organisations the joys of 2008 are still to come. Clustering in 2003 offers few built in options for notifying anybody that a resource group has moved or failed over to another node. Ideally, the fact that it has should not be any cause for alarm but there are occasions when it is useful to know. Fortunately for some a well trained piece of monitoring software running […]