<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Tips on Improving MED-V Workspace Application Performance</title><link>http://blogs.technet.com/b/medv/archive/2011/06/13/tips-on-improving-med-v-workspace-application-performance.aspx</link><description>If you are still using MED-V version 1, UPGRADE! But, if you are unable to due to workflow or platform issues, here are some additional tips to improve application performance for your published MED-V guest applications. Disable Unnecessary Services and</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Tips on Improving MED-V Workspace Application Performance</title><link>http://blogs.technet.com/b/medv/archive/2011/06/13/tips-on-improving-med-v-workspace-application-performance.aspx#3451428</link><pubDate>Tue, 06 Sep 2011 19:52:36 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3451428</guid><dc:creator>Steve TH - MSFT</dc:creator><description>&lt;p&gt;One important item to remind everyone on. Until the International patch was released for v2, even with dynamic memory, it was not possible to get beyond 2GB for the workspace. That limitation was removed with the International patch as well.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3451428" width="1" height="1"&gt;</description></item><item><title>re: Tips on Improving MED-V Workspace Application Performance</title><link>http://blogs.technet.com/b/medv/archive/2011/06/13/tips-on-improving-med-v-workspace-application-performance.aspx#3435316</link><pubDate>Tue, 14 Jun 2011 10:33:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3435316</guid><dc:creator>Johan Jacobs</dc:creator><description>&lt;p&gt;Got it fixed. Regenerated the msi using powershell and New-Medvworkspace.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3435316" width="1" height="1"&gt;</description></item><item><title>re: Tips on Improving MED-V Workspace Application Performance</title><link>http://blogs.technet.com/b/medv/archive/2011/06/13/tips-on-improving-med-v-workspace-application-performance.aspx#3435275</link><pubDate>Tue, 14 Jun 2011 07:33:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3435275</guid><dc:creator>Johan Jacobs</dc:creator><description>&lt;p&gt;Hi JC. &lt;/p&gt;
&lt;p&gt;I am struggling to change the amout of memory allocated to my XP SP3 VM on Med-V 2. I have 4 GB on the host (32bit install) and would like 2 GB to go to the workspace and 1GB for the Windows 7 host. The VM however only gets 1GB if I look in the reg file as well as the powersehell script during the workspace packager setup. I added the &amp;quot;Memory&amp;quot; DWORD in the reg file with a vaule of 0x00000800 (2048) but it just ignored the setting. If I change the amount of memory on the VM once the workspace is setup, it resets back to 1GB as soon as I restart the machine.&lt;/p&gt;
&lt;p&gt;I cannot find any articles on changing the memory for initial setup or changing the memory after the setup has completed already.&lt;/p&gt;
&lt;p&gt;Any ideas?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3435275" width="1" height="1"&gt;</description></item></channel></rss>