Would this virtualisation have anything to do with the advice seen in some
places and ridiculed in others to run installers as Admin and to set Admin
privileges on the legacy app itself/run it first time as Admin?
I have a lot of trouble with legacy apps and UAC etc. and trying to work out
what I should be doing to minimise downstream irritation.
"Ronnie Vernon MVP" wrote:
> Hi Stan
>
> A little background first.
>
> Vista is built on a new security model that is based on what's called a
> "Least User Privilege" environment. What this means is that for software to
> be compatible with Vista, it must be designed to run under a Standard User
> account. This means that software programs are no longer allowed to write to
> sensitive areas such as Program Files, System32 folder, HKey_Local_Machine
> in the registry, etc.
>
> Software developed for previous versions of Windows pretty much required
> that the user must use an administrative account to use that software
> because this software did write to these system wide, sensitive areas (even
> though the Microsoft guidelines for developing software tried to deter this
> practice). These developers designed their programs to have system wide
> access, even though this was not really required. This left the system wide
> open to attacks from malware that would use the privileges of the logged on
> user (administrator).
>
> Virtualization.
>
> Going to the next level, Vista now 'requires' that software programs 'must'
> use the least user privileges for software to be compatible with Vista.
> Microsoft recognized that this could have a disastrous effect since so many
> legacy programs would not be compatible with Vista so they implemented file
> and registry Virtualization.
>
> This Virtualization simply means that if a software program attempts to
> write to a restricted area, (such as C:\Program Files\software program
> folder) then that write function will be silently re-directed to a
> non-restricted area, such as C:\Users\username\Local\Virtual Store\Program
> Files\software program folder.
>
> This allows the program to run as designed while still protecting the
> system.
>
> However, file and registry Virtualization is not permanent. It is only there
> to allow the software developers time to update their programs to be
> compatible with Vista. Virtualization will disappear sometime in the near
> future and programs that are not compatible will simply not run on Vista.
>
> Here are some links with more information, if you want to dive deeper into
> this.
>
> Common file and registry virtualization issues in Windows Vista:
> http://support.microsoft.com/kb/927387
>
> Getting to Know User Account Control: MVP Article of the Month - October
> 2006:
> http://www.microsoft.com/technet/com...vp/sv1006.mspx
>
> Developer Best Practices and Guidelines for Applications in a Least
> Privileged Environment:
> http://msdn2.microsoft.com/en-us/lib...otvista_topic4
>
>
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Shell/User
>
>
> "Stan" <> wrote in message
> news:B5139EAC-421A-44CB-93B0-...
> > This is the first time I have seen anything about Virtualization. Did a
> > web
> > search but did not find any really useful info. What is it?
> >
> > Thanks
> >
> > Stan
> >
>