Video Screencast Help
Endpoint Virtualization Community Blog
Showing posts tagged with Workspace Virtualization
Showing posts in English
Admin | 30 May 2006 | 2 comments

Q:
Dave asked, "When I'm doing an installation into an app layer, at the end of the install sequence (.msi, .exe or whatever) I'm prompted to reboot as part of the installation process. What is the best practice on how to handle the reboot?"

A:
Good question Dave. That's one we hear a lot. And the answer is usually simple.

As a rule, you should cancel any request for reboot during the capture process. Let the capture end. The layer will come up active, but we don't execute startup events then. Deactivate it and then re-activate it and SVS will run the startup events (service spin-up/register, run and runonce commands, delete after reboot entries, etc.). This is usually all that's required.

It gets more complex when the setup is designed to resume after reboot. When that's the case, before re-activating the layer you need to delete the runonce key that starts the setup back up; otherwise when you re-activate...

Admin | 26 May 2006 | 0 comments

Install, Deploy, Heal & Switch Applications With A Click Of The Mouse

Anyone who has ever upgraded from one version of an application to another and had problems will immediately see why you need something like SVS. The upgrade scenario is just one of the key areas that SVS addresses.

"We see SVS as a key tool to help system administrators simplify the overall software management process," says Rich Bently, market segment manager for client and mobile products at Altiris.

Read the full article here.

Admin | 24 May 2006 | 43 comments

Q:
Roie asked, "Have you guys tested a version of SVS on either Vista or 64-bit Windows or both? I just set up a prototype Athlon 64 with the latest beta version of Vista 64, and would love to try out SVS on that. I am also working with a Windows Professional 64 on the same machine."

A:
Hi Roie. Support for servers, Vista, and 64-bit Windows are all slated for the next major SVS release, Lightning, which will be part of the Altiris 7/Polaris launch early next year.

Admin | 23 May 2006 | 3 comments

Q:
Jim wrote: I want to create a data layer to distribute a set of files to all users but I've run into an issue.

Files in the User Specific section under the [PERSONAL] variable are not accessible to the users distributed to –- they are only accessible under the SID of the user that created the layer. The User we distribute the layer to automatically generates a new SID in the User Specific area and the files aren't under that user's SID.

Is there any way to accomplish this and get around the SID issue in the User Specific area and not distribute files off the root?

Thanks for the help.

A:
Jim, that is what USER_TEMPLATE is for in the read-only sublayer. Perhaps this article will help.

Admin | 18 May 2006 | 0 comments

Q:
Joe asked, "Thank you for making the Holy Grail of applications. I have a question about making limited licensing software available to end users. Is there a way to 'check out' VSA's? ... and how are VSA's handled by application metering?"

A:
Thanks for the question, Joe. The Altiris Software Portal (which is included with SVS in Altiris Client Management Suite) is a great way to let users self-provision software while enforcing licensing policies via integration with Altiris Asset Management. See this great article on how to use Software Portal with SVS.

We hope to have another feature article soon on Asset Management integration.

Admin | 18 May 2006 | 2 comments

Q:
Hi there! We have been working for almost 2 years with VMware for OS Virtualization.

I have a question for you: Can we install SVS in a virtual machine (Hosted WinXP or Win2k3 with Terminal Services)? Do you have a solution for deployment to final users (does it sound like VMware ACE)?

Best regards, and keep it going!

A:
The SVS Virtual Software Packages can be deployed to any client -- whether it's a physical machine or a virtual machine -- using your existing software deployment tools. So we don't need a special distribution mechanism like ACE, though SVS will run great inside VM's served up by VMware ACE!

Admin | 12 May 2006 | 1 comment

Q:
Paul asked, "SVS redirects just the C: drive (op sys drive), right? Even if the app installed on a different partition?"

A:
Yes. But you can move the redirect area. See
"Changing the fslrdr Location"
.

Eventually we'll support reading from multiple redirect areas, so stuff on C: will really be on C: and stuff on D: will really be on D:. Or, far more intriguing, you might be looking at your collection of data under "My Documents" in Windows Explorer, but in reality the physical data actually exists on half a dozen servers out on the Internet cloud.

hansh | 11 May 2006 | 1 comment

Q:
Hello All,

I'm trying to virtualize Cisco IP Communicator (which basically is a Softphone for use with their VOIP systems)

As the system requires a reboot to install correctly, how do I virtualize it?

Kind regards,

Hans Hinnekint

Admin | 10 May 2006 | 2 comments

Q:
Craig asked, "Why is this space so important when there is more of a move to web-based / on-demand applications? Do you think the Internet browser will be the client of choice moving forward?"

A:
Thanks for the question, Craig.

History has shown that the Web can't solve all business problems -- the market wants a mixture of Web and "fat client" apps.

Application virtualization can provide an on-demand experience for all types of applications. It gives customers the benefit they're really after -- increased accessibility and reduced cost of ownership -- and allows application developers to select the development environments most suited to the application's requirements.

riva11 | 09 May 2006 | 1 comment

Ho recentemente creato un layer SVS che includeva un collegamento che puntava a un eseguibile all'interno del mio layer. Niente di strano fino a questo momento, ma per una demo (al nostro direttore) ho voluto mostrare come un utente può cancellare una intera directory e poi in un secondo momento ripristinarla semplicemente resettando il layer.

E qui è dove comincia il divertimento. Cancelli la directory e provi a usare il collegamento. Non dovrebbe funzionare .... vero ? Sbagliato. Microsoft Windows ha una piccola ma grande tecnologia che entra in gioco quando provi a eseguire una collegamento e il file a cui si riferisce è mancante. Windows ricerca un altro eseguibile con lo stesso nome. Inoltre cancella il vecchio collegamento e ne crea unnuovo con lo stesso nome. Questo implica che il nuovo collegamento non è più parte del layer SVS.

Dopo la cancellazione della cartella dove puntava il collegamento originale , il nuovo collegamento adesso punta alla cartella...