http://blogs.msdn.com/rflaming/archive/tags/SoftGrid+virtualization+lore/default.aspxTags: SoftGrid virtualization loreen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/rflaming/archive/2008/04/07/why-the-q-drive.aspxMon, 07 Apr 2008 17:37:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8365530rflaming0http://blogs.msdn.com/rflaming/comments/8365530.aspxhttp://blogs.msdn.com/rflaming/commentrss.aspx?PostID=8365530<P>Overheard an interesting discussion on SoftGrid.&nbsp; Here's my spin on their talking points.</P> <P><STRONG>Q</STRONG>: Why is the q:\ drive needed?</P> <P><STRONG>A</STRONG>: Some applications write paths to the system in which they need a full path including the root.&nbsp; Given migrating to SoftGrid in IT is principally done via repackaging (via a tool called a sequencer) the repackager needs to provide the application install a reasonable facsilime of the system.&nbsp; With the Q drive provided by SoftGrid, the legacy application installer can then sprinkle a fully qualified path to settings locations such as the registry, ini files, and XML config files.</P> <P>More SoftGrid specific detail is available in Knowledge Base article 931626: <A class="" title="How to hide and to restrict access to the SoftGrid Client drive letter" href="http://support.microsoft.com/kb/931626" mce_href="http://support.microsoft.com/kb/931626">How to hide and to restrict access to the SoftGrid Client drive letter</A></P> <P>The Group Policy specific ability to hide drives is described in Knowledge Base article 231289: <A class="" title="Using Group Policy Objects to hide specified drives" href="http://support.microsoft.com/kb/231289/" mce_href="http://support.microsoft.com/kb/231289/">Using Group Policy Objects to hide specified drives</A></P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8365530" width="1" height="1">SoftGrid virtualization lore