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.
Some of today's 'desktop' mini-PCs make laptops seem downright bulky in comparison.
Google Photos and Drive complement each other in some ways and offer stark differences in others.
President-elect Trump has assembled a 16-member team of CEO-level executives to advise him on job...
Sponsored by Puppet
The YETI Hopper 20 ice-for-days portable cooler and is tough as nails so it can be hauled anywhere you...
A flash drive, reinvented. With the SanDisk Connect Stick in your pocket, in your bag or across the...
Instead of making unfashionable smart glasses, Apple will make fashionable glasses smart.