We initially attempted to implement System Center 2012 modularly, which is almost impossible, so we used the Unified Installer after reading the salient documents for each module, then installed each module into its own VM, combining SQLServer resources where necessary. We recommend that up to four SQL Server instances may be necessary for protecting all of the modules.
We controlled the test of the modules in our lab, and deployed instances both locally into Dell 1950 servers (2-CPU/8Core, 12GB memory, lots of disk) connected into a switch, then to our network operations center at nFrame. At nFrame, we housed two HP servers, a DL580 (16core, 32GB, big disk), a DL585 (16core, 32GB, big disk), and several other, smaller servers that shared a Compellent hefty SAN system that were all interconnected with an Extreme switch.
We exercised the basic functionality of each module against our Windows Servers, and VMware, XenServer, and KVM-based hardware using both Windows 7 virtual machines, and Lenovo T520 notebooks (2core/i5 with 8GB of DRAM and 300GB drives) in a Gigabit Ethernet switched Ethernet environment.
Read more about software in Network World's Software section.
This story, "How we tested Microsoft's System Center 2012" was originally published by Network World.
The company is removing UML support in Visual Studio 15 due to a lack of usage
Picking an Android phone can be difficult, but we're here to help. These are the top Android phones you...
Google's first in-house phone is a delightful holistic experience that might make you think twice about...
Apple and IBM this week released their first iOS app for academia. IBM Watson Element for Educators is...
Two innovative startups figured out all-day video chat sessions, without making it weird
The U.S. has charged a suspected Russian hacker with stealing information from LinkedIn, Dropbox and a...