Browse by Tags
I don't normally advertise what's [hopefully] already known, but, 4.5 is a big step forward, and not just in the name change :) http://blogs.technet.com/smsandmom/archive/2007/11/12/microsoft-application-virtualization-4-5-is-open-for-public-beta.aspx
Read More...
Yes, When v4.5 is released we will support the client upgrade from 4.2 and respect the settings. [update 8th Nov] Ok, so what about your sequenced applications, will they work? Yes, we expect applications sequenced in 4.2 to work just fine on the new
Read More...
The recommended practice is to choose a virtual drive assignment and stick to it; commonly, this is drive Q: - so what happens if you want to change to something else, for example, V: If all applications were equal and followed recommended practice, then
Read More...
No. Not yet. AIS (Application Inventory Service, part of the Microsoft Desktop Optimisation pack (MDOP)), delves deeper into a machine than most inventory software services, besides the add/remove MSI components, it also checks the registry etc. However,
Read More...
The sequencer can be a real machine or a virtual machine; commonly, virtual machines are used for the following reasons:- They can be reverted back to a known consistent state via undo or simple file copy routines. They can be manipulated via scripts
Read More...
Compressing or not compressing during sequencing has benefits and disadvantages:- Compressed . The sequenced stream will be smaller; this can be useful where storage is of concern, or more probable, where the network utilisation is of concern. Compressing
Read More...
No. Once a computer is using virtual applications deployed in this way it can not longer 'switch' back to streaming mode. By 'switch' I mean run in mixed-mode or easily go back to streamed mode. The client will either work in machine context offline mode,
Read More...
The new MSI Utility has been announced (formally WiAVE); check out the product teams' blog here and for more information on client side application licensing see my blog entry here . Using the MSI Utility we are now pre-caching the virtual application
Read More...
There is a simple answer to this, and of course, a more complex one. Simple answer. No. The virtual application is read only and cannot be infected once it has been sequenced. Complex answer. There are several places a virus or malware can be introduced,
Read More...
I noted an issue yesterday where an application took over 40 seconds to launch on a Windows Vista client. After the usual investigation methods (was it sequenced on Vista, is the Cache ok, running performance monitoring tools, event logs, SG logs, etc)
Read More...
The simple answer is one (1). The sequencer is a single threaded application and will not take advantage of multi-core or multi-socket systems. Sequencer investments are better made in the disk I/O sub-system (see my item on disk performance). In theory,
Read More...
The sequencer, virtual or physical, should have two partitions (or disks), the first, normally C: is for the base build, and the 2 nd , normally Q: is for the installation of the application to be sequenced. Sequencing is a very disk I/O intensive operation.
Read More...
If a virtualised application writes to the event log, will the host machine (and therefore any event log monitoring services) have visibility. Yes. We don't virtualise the event log in the SystemGuard and therefore any applications that write to it, will
Read More...
SoftGrid 4.1 SP1 and 4.2 do not work on Windows Server 2008; therefore you cannot run a sequenced applications on the server; however, the release of version 4.5, although only for client based virtualisation, will work on Windows Server 2008 enabling
Read More...
SoftGrid does not change the licensing of any application; however, deploying an application through SoftGrid using the streaming protocol, only places the applications’ Icons on the Desktop. Until the user double-clicks the Icon and uses the application,
Read More...
