Unofficial Spiceworks managed to corner Kris (Spiceworks) for long enough to ask him some questions about the Spiceworks network and himself:
What state was the network in when you first started?
Ha! A single flat network defined by an unmanaged managed (meaning they were not actually managing it) Layer 2 switch with a Linksys router attached to it. They had tried to get an Asterisk-based PBX system to work, but were having a lot of problems.
What’s the infrastructure like now?
I have a hierarchical network with a core/distribution layer and an access layer. I have a mix of Cisco, Dell, and HP ProCurve switches providing access, and a Cisco core. The edge network is made up of a Cisco ASA 5505 firewall and a Celestix MSA VPN appliance. Wireless is provided by Cisco 1130AG access points. We are running multiple LAN segments, divided by function. Telephony is provided by an NEC IPKII PBX/Voicemail system, which is a hybrid VoIP/TDM system. We use Active Directory for central user and object management and I connect as many of our devices as possible (Windows, Mac, and Linux) into AD.
How do you cope with having to have lots of versions of Microsoft, Linux and Mac products for developers to test the Spiceworks Scanner with?
It can be complex. Many of our users prefer to use Mac, so we have integrated them pretty well. We have MSDN developer licenses, so we have access to MSDN versions of Microsoft products. Most of our test servers and workstations are run in a virtual environment hosted by VMWare ESXi. As far as Linux/UNIX goes, I am a real Linux geek, so I enjoy being able to play with different versions. We have Fedora, CentOS, Ubuntu, OpenSolaris, and even a FreeBSD (I think) in our environment.