http://collaborate.extension.org/wiki/NETC08_session_1003?action=feed&mode=viewWatching: NETC08 session 10032009-11-22T09:31:02ZWiki page as htmlMediaWiki 1.14.0Contributorshttp://collaborate.extension.org/wiki/NETC08_session_1003/10704NETC08 session 10032008-03-12T14:33:22Z<div class="thumb tright"><div class="thumbinner" style="width:108px;"><a href="/wiki/File:NETC_logo_sm.jpg" class="image" title="NETC logo sm.jpg"><img alt="" src="/mediawiki/files/9/9d/NETC_logo_sm.jpg" width="106" height="45" border="0" class="thumbimage" /></a> <div class="thumbcaption"></div></div></div>
<p><b>Session Name: </b> <i>Virtualizing Your World</i><br />
<b>Session Number: </b>1003<br />
<b>Location: </b>Mendenhall<br />
<b>Day and Time: </b>Tuesday, 9:30 - 10:15 am<br />
<b>Format: </b> Presentation<br />
<b>Topic: </b> Systems, Networking and Firewalls<br />
<b>Level: </b>Introductory<br />
</p>
<hr />
<p><b>Session Abstract:</b> <br />
</p>
<dl><dd>Increasingly, IT staff are being asked to provide more services, faster implementations, and continuous up-time, all with limited staff and budgets. Converting traditional physical servers to virtual servers can enable systems administrators to meet these needs without losing their sanity, and even to provide new services.
</dd></dl>
<dl><dd>In this session, we examine the traditional server approach, the pros and cons of multi-use and single-use server structures. Then we compare the benefits of virtualization with VMWare, what its advantages are. We also look at the downside of virtual environments, the caveats of converting. Finally, we will look at the College of Agricultural and Environmental Sciences at UGA's conversion to VMWare, our experience with the conversion, and tips for others thinking about converting.
</dd></dl>
<p><br />
<b>Led By:</b> Diana Williams, Systems Administrator, UGA College of Agricultural and Environmental Sciences
<br />
</p><p><br />
</p>
<!--
NewPP limit report
Preprocessor node count: 57/1000000
Post-expand include size: 1303/2097152 bytes
Template argument size: 1024/2097152 bytes
Expensive parser function count: 0/100
-->
<!-- Saved in parser cache with key itwiki:pcache:idhash:2773-0!1!0!!en!2!edit=0 and timestamp 20091122072446 -->