are you talking about whenever a layer is activated or when a new user SID is created inside of a layer?

the latter one.

That is the weardest request i ever saw?
What should be a reason for doing this?

It can be done pretty easy, but  need more detail on what you need.

I need to copy a custom configuration file onto a network drive for each user. (onto the homedrive)

but this file must be copied prior to first start of the application, and because there are so many potential
entry points (file extensions, progid, shortcuts) i cannot simply create a dummy bootstrapper (eg. vbscript).

My best guess would be a onevent that does it for you.
Make sure you understand that SVS cannot handle network drive mappings.

I'm aware of that and that's why im looking for a "hook" to execute a WiseScript(or anything else) to fulfill this task.

can't you just place this information in default user? so whenever a user is created it gets added?

Why not use a logon script to do this instead?
Otherwise you would need to change the executable that is launched by each "entrypoint" as ex. a vbscript to write the uniq configuration file to the users homedrive and then execute the actual executable.

Sounds like the first option would be easier :)

@AngelD
this was my first idea which came in mind, but i do not really like such solutions.

I'd like to deliver out of the box VSA Containers without any other gimmicks.

@Jordan
the user profiles already exist.

You're going to have to use "gimmicks".  You can use SVS's onEvent Notifications to trigger code to happen based off of certain SVS events, after a layer is activated for example, but there's no way to get at any info relating to before a process is ran from a layer (we don't keep track of that stuff much) or when the registry is mounted after an activation using the SDK.  We don't use any API that aren't in the SDK for SVSadmin or SVScmd so there's no hidden API that does this either.

Does the file really have to be on the network?
Why not somewhere in the user's profile?

because the location is predefined ;-)

So, can you post-define it :P
If it's hardcoded maybe you could solve it by shim