Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog

Portable Slim Layer Exporter [Updated]

Created: 28 May 2008 • Updated: 29 Jul 2010 • 15 comments
FrankB's picture
0 0 Votes
Login to vote

Do you have a Virtual Application you want to share with your friends or colleagues? But you're not sure if any private information is given to them also?

Don't you want to distibute your layers to your environment in a clean state?

Make them smaller to ensure lower bandwidth usage?

Did you just Capture a new Virtual Application, and you want a clean export?

Here's your solution!

With (Portable) Slim Layer Exporter you can export your Layers in a clean and small state. Your userdata (Registry/Disk) won't be included in the Exported Layer.

Download it here.

P.S. U3 Version is also available.

Version v1.1
Added: Extensive exporting error reporting.

Comments 15 CommentsJump to latest comment

erikw's picture

Frank,

I downoloaded it, but i get a error 40 when trying to activate the package?
Something wrong, or am i doing something wrong?

Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

-2
Login to vote
FrankB's picture

I think you're missing .NET Framework 2.0?

It's tested in a Home & Corporate Environment, one is XP and the other is Vista.

And you need SVS installed of course :)

FrankB

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

0
Login to vote
erikw's picture

When trying to export a layer that gives a eror 18 in normal SVS, file is locked, does not give a error in the smart exporter, but when trying to import it comes with the eroor 40. Layer not complete.
Great job.
Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+4
Login to vote
FrankB's picture

Thnx ErikW, I'll have a look at this.

___________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

-4
Login to vote
Swami's picture

Opps! The application pops up saying that you need dot net 2 or higher and then crashes.
I have dot net in a layer which is currently not active & it got corrupted. Will try reloading it.
Any way, thanks for your good work.

0
Login to vote
FrankB's picture

Why virtualize .NET Framework?
It is a semipart of the OS, used by several apps, and doesn't slow down you machine.
I just installed it in the OS, makes life much easier :)

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

+2
Login to vote
erikw's picture

I followed the discussion about .net in a layer or not.
i have .net in my OS installed, but sometimes i need .net 3.0 or even 3.5
So i installed these in a layer.
The current SVS version starting with build 2084 have a component in the installation that prevents you from capturing .net inside a layer.
That is why i builded mines in the 2069 version.
The good news is that these also run on the 2084 and 2088 version.
The 2069 version is also the only version that can be used on a vista sp1 when trying to capture new apps.
The newer builds with the .net component inside will not do the job on vista sp1.

And to make a good discussion more comprehensive!
i love the 2069 and the 2084 build.
i do not like the 2088 build, and i stopped using the 3052 build. I see starnge behaviour in this beta build that i don't like.
Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

-6
Login to vote
Nebster's picture

You've successfully managed to get .net in a layer?
So I need the old version to be able to do this?

0
Login to vote
Swami's picture

Thanks for your advice. I have felt that, installing .NET in a machine is increasing the registry size. Most of the older machines (used for more than a period of one year with out formatting) showed over all slow response. This is my observation in several Solo core machines. Awaiting to try them on a multi core machines.

+2
Login to vote
Swami's picture

It worked fine. I was expecting some magically SLIM file size. But I could notice the change of few kBs only, when comparing the normal method of VSA creation. Again it may be the case with the software, which I have tried. Let try some things over the weekends & post it here.

0
Login to vote
FrankB's picture

Dear Swami,

It depends on how much User Data you have in your Layer, the more you have the smaller the vsa will be, it cleans and therefore it reduces the size of the vsa. Get it :)

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

+2
Login to vote
Swami's picture

Dear Frank Bastiaens,

Thanks for your reply. That is understandable. I was trying out an Industrial HMI software, which already uses lots of compressed files. Hence there was very less difference between the instale4d folder size and the VSA. This software uses very less user specific settings. So, the slim export has little thing to do.

Thanks,
Swami

-4
Login to vote
philbenson's picture

Hi Frank,
busy again as usual ;-)

I was just wondering, how you managed to 'clean' the user specific registry hives? Cleaning up the files is (fairly) straight forward, but the User Specific registry hives was probably a bit more work?

This is the main reason that we do not use the SVS Client to capture applications, but use the Virtual Package Editor for both capture and editing / cleaning up the package.

Was just wondering if you could share you knowledge regarding reg clean up.
Thanks and best regards
Phil

+2
Login to vote
FrankB's picture

Of Course I clean up the User Hives from the Registry, it is Called 'Slim' Layer Export, the word 'Slim' in Dutch means 'Smart' :)

I scan the RW Registry of a Layer, and when found remove the User Sids including Content, If you want more details, PM me :)

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

______________________________________________
Frank Bastiaens
Senior Technical Consultant
Vanderlet B.V.

0
Login to vote
Thunder-man's picture

Hey Frank, THX for this Tool.

Can we save the last "Export Path" and also "compressions Level" ?

greeting
FrankM

Google English…
SVSLoad.com

+4
Login to vote