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.
Over the past year, our resume experts and career consultants have helped numerous IT professionals put...
If you enjoy a sharply-worded insult, read on. This slideshow’s for you.
The source code behind proprietary software doesn’t always remain hidden forever. Here are a number of...
The design team working on C# are examining data management, performance, and reliability for the next...
The content could give a lift to Google in mobile search
The cluster-management software helps boost availability in the AWS cloud
Problem compounded by the fact that most countries do not have e-waste recycling facilities