Video Screencast Help
Endpoint Virtualization Community Blog
Showing posts tagged with Configuring
Showing posts in English
riva11 | 06 Jul 2006 | 0 comments

The original article Creating Printers in SVS Layers (e.g. Adobe PDF Printer) submitted by Adam Hall , can be read : here .

Se hai necessità di creare una stampante che sia inclusa in un layer SVS, allora è necessario anche eseguire un restart del Servizio Print Spooler dopo che il layer è attivato.

Per questa ripartenza , ho inserito nel layer di Adobe Acrobat Professional , uno script con un collegamento ,nella cartella di Esecuzione automatica. Quando il layer è attivato, lo script esegue il restart del servizio di Print Spooler service e rende la stampante disponibile all'uso.

Questo script è estremamente semplice :) sono sicuro che può essere scritto in WMI o VBS in modo da essere invisibile all'utente.

[quote]

@echo off
TITLE Adobe PDF Printer Creation
echo Creating Adobe PDF Printer ...
net stop "Print Spooler" >NUL...

Silas | 09 Jun 2006 | 1 comment

So you need to capture several applications into one layer because you have application that is dependent on other pre-installed components? Here's how I do it.

I use WISE Package Studio 5.1 to create a script which runs all the application setups from one EXE.

I begin by creating a blank script from Wise Script editor. I then create an Execute command for every application I desire to include in my SVS capture. Why do I use WPS? Because I can script everything I need to do, from running VBSscripts, editing registry settings, manually copying files, and much, much more.

So, after I've created my WPS script, I compile, start SVS, create new layer capture, and run the WPS script exe.

Whether you are creating a corporte virtualized application layer or a LAN Game party layer that contains all the Games in one simple layer -- This will make daisy-chaining installs and cofigurations that much easier.

Admin | 30 May 2006 | 2 comments

Q:
Conor asked, "Here's the deal, I created a layer (using WPS 7.0 beta) that inserts several icons into my personal start menu during installation. So I went into advanced layer properties and removed the icons out of my SID area (they still exist in the read-only section) and export the layer to .VSA. If another user imports that layer, and activates it, they get the icons in their start menu, but I don't until I reset the layer after activation. Should I remove all user specific information out of the read-write layer before I export the VSA?"

A:
Thanks for the question, Conor. Yes, if you are preparing a package for centralized distribution, one of the default cleanup actions you would want to do is - in the read-write sublayer - to delete any user folders (with SID folder names) from under "User-specific" in the file system and from under "HKEY_USERS" in the registry.

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...

Screenbert | 09 May 2006 | 2 comments

I recently created an SVS Layer that included a shortcut pointing to an executable inside my layer. There is nothing strange about this, but for the purpose of a demo (to our director) I wanted to show how a user could delete an entire directory and have it restored simply by resetting a layer.

This is where the fun began. You delete the directory and attempt to use the shortcut. It shouldn't work...right? Wrong. Microsoft Windows has a great little technology for when you try to launch a shortcut and the file it refers to is missing. Windows searches for another executable with the same name. It also deletes the old shortcut and creates a new one with the same name. This means the shortcut is no longer part of the SVS layer.

After deleting the folder that the shortcut originally pointed to, my shortcut now pointed to a folder called "c:\fslrdr". This is the SVS redirection area where there is an executable with the same name. Even after deactivating the layer or...

riva11 | 09 May 2006 | 0 comments

Recentemente ho 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 un nuovo 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...

Jared Payne | 18 Apr 2006 | 25 comments

If fonts are a sore spot between you and virtualized applications, here's a cure from Jared Payne that should clear things up.

A number of users have reported problem with fonts when using SVS. The reported problem causes applications like Outlook to not look and act properly. The only guaranteed workaround is to copy the fonts from the layer to the base system. You can manually do this by using the advanced editor in SVS Admin to drag the appropriate fonts to the system fonts directory.

Since you probably do not want to do this on every machine you manage I have created a tool to help you out; CopyFonts. CopyFonts needs to be run as a user with permission to add fonts. If your users are administrators, you can run this application whenever you want. If your users are not administrators, you will need to guarantee that this application is run as an administrator.

SVS has the ability to run an application when a...

Admin | 03 Apr 2006 | 2 comments

Q:
How can you do a "global exclude directory"? Is there a way to set a true "safe place" for downloads (like folder X is off-limits). Or is this on a per-app basis?

A:
See this article, "An Example Config for Excludes and Data Layers" While we don't have an actual "global exclude" option, we do have a tool that will apply an exclude list to all layers on a box.

Admin | 31 Mar 2006 | 0 comments

Q:
Chris wrote: If running an application that will not work with XP SP2 (only SP1), can it run in SP2 in a layer? I suspect it depends on what the incompatibility is. If it is a file conflict between the app and SP2 (eg SP2 updates a DLL and the app only works with a previous version of the DLL), it should be OK, correct?

A:
Good thinking, Chris.

The product install may not include all of the dependencies, so some things may need to be copied in manually after the capture. WPS ConflictManager would help identify exactly what files need to be included in the VSP to achieve the desired result. This is yet another example of the synergy between Wise and SVS!

RichC | 23 Mar 2006 | 0 comments

Generate a digital license after an application runs on the destination machine as a workaround to Office XP detecting a hardware change.

When packaging Office XP (or any portion of it) off of a CD and manually entering the Key when capturing, etc, you will run into an issue when bringing the VSA to a different PC. When launching the VSA on a new PC and trying to use the application, it will tell you that it has detected a significant machine change since it was installed and will give you only limited functionality. This is because of the digital license identification that Microsoft includes on this version of Office (I haven't seen this happen in any other version) is based on hardware. To fix this so that it will generate this digital license only after use on a new machine, you must do the following:

  1. Create an administrative share point from the setup.exe - enter the Office XP key and accept the license agreement. That way, all users running the install...