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.
A study shows that if the U.S. mandates backdoors to decrypt secret messages, there are hundreds of...
KDE's recently announced Linux distro, KDE Neon, seems like a questionable move that has the potential...
A prominent Linux kernel developer announced today in a blog post that she would step down from her...
As enterprises struggle to keep up with their internal demand for mobile apps, more are turning to more...
Amazon does a great job with infrastructure, but securing your cloud applications and environment is up...
Not quite 2:1 adoption rate for ACI like last fall, but close
When it comes to gripes about IT, CIOs need to go back to basics to address the needs of their most...