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.
PayPal has fixed a serious vulnerability in its back-end management system that could have allowed...
Android is better than ever, but it's still not perfect. These are the things we wish were included in...
Mocked and shunned by society for wearing Google's dorky face upgrade, Google Glass fans were right all...
Going back to school? Here are some of the best laptop backpacks for every situation, whether you're...
Stop going back and forth from indoors to outdoors to check up on your meat, and instead monitor it...
Opera's free VPN for all is now on Android with added features including a Wi-Fi network security test.
These nine cloud collaboration tools can help organizations communicate more effectively, share and...