Leo, 

I complained about this in one of my comments about the release notes . They stopped listed any type of resolved issues so you really don't know to rush deploy something that contains a fix that you have been waiting on for awhile ... i hope that this is changed soon

Hey Leonard, I also work at a school district with around 20 virtual apps on most of our computers.  We are having the exact same issues that you are having.  We found that the more local profiles on the computer the longer it takes to get to the Windows Login screen  We have seen around 6-10 minute boot times wiht 60+ profiles.  If we delete all but around 10 of the profiles the machines will get to the login in around 2.5 minutes.  This seems to fix the issue but is only a band-aid until we can find what the actual problem is.   Did you ever find a final resolution to this issue?

Hi,

try using to partially activate a layer. This should solve (workaround) your problem. Use svscmd for it and take a look into the manual for further explanation.

greetz
Sundance

PS: at least the 64Bit version of SWV got that option. Haven't looked at the 32Bit version. The partially activation functions also works in combination with the autostart option.

Try DVS SMART. It works similar as Trinket, but it does not need power user or administrator privileges.

DVS SMART is free software and can be downloaded from www.dinamiqs.com.
In 6 weeks DVS SMART will contain the newest version of the logonhook that enables users to go throught the whole login tasks, while the computer is activating layers. This will solve long login times very easely. We are now integrating the new logonhook into our DVS management console, and in the SVS user admin.
DVS SMART and the new logonhook work on Windows XP, Windows Vista and Windows 7 32 and 64 bit versions.

I'm having the same issue...seeing it more in Windows 7 than anything else, but having anything marked to 'Activate on Startup' significantly slows login times and just slows the machine in general once logged in.   If I deactivate and then re-activate again, it seems to resolve the issue for a little while.  Is there potentially a memory leak?

when I say 'potentially a memory leak', my only reference is that regardless of Trinket, if I activate the application on startup or activate it after i'm already logged in i begin to see things start to take longer than they should. 

in one case, i had a layer activated at startup - i tried to get into the systems manager and the UAC took almost 5 seconds to show up.  upon deactivating the layer and trying the same thing it popped up immediately.   i re-activated the layer again and noticed that it took maybe a half second longer to retry the same thing again.  over time, this seems to grow longer by a second or two, but it most noticeably seems to drag if activated at startup.

maybe i'm just losing my mind?  :-)

This gives me an idea.

Here is a quick little VBScript that you can call from a shortcut that will activate an SVS layer if the layer is deactivated and then executes the layers program. if the layer is already active then it will run the executable. It's not perfect and still very rough but I want to go home and I felt compelled to share..

' Filename:
'	DynamicSVS.vbs
' Parameters:
'	Guid of SVS Layer		Example: 5e7ebc06-1a78-4b8f-8866-209bc119aba8 
'	Path of target Executable	Example: %PROGRAMFILES%\7-Zip\7zFM.exe
'
' Example:
'	 WScript.exe DynamicSVS.vbs 5e7ebc06-1a78-4b8f-8866-209bc119aba8 "%PROGRAMFILES%\7-Zip\7zFM.exe"

Dim WshShell, fso, objWMIService, colItems
Set WshShell = CreateObject("Wscript.Shell")
Set fso = WScript.CreateObject("Scripting.Filesystemobject")

Dim Guid, Command, Params, cmd

If WScript.Arguments.Count < 2 Then
	MsgBox "Parameter missing!", 0, "Dynamic SYS"
	WScript.Quit 1
End If

With WScript.Arguments
	Guid = .Item(0)
	Command = WshShell.ExpandEnvironmentStrings(.Item(1))
	If .Count >= 3 Then Params = .Item(2)
End With

cmd = """" & Command & """"
If Params <> "" Then cmd = cmd & " " & Params

If Not fso.FileExists(Command) Then	
	'## Looks like the Layer is disabled.
		Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default") 
		Set colItems = objWMIService.ExecQuery("Select * from VirtualSoftwarePackage Where Id ='" & Guid & "'")
		
		For Each objItem In colItems
			If objItem.Active Then
				MsgBox "Target command was not found!", 0, "Dynamic SYS"
				WScript.Quit 2
			End If
			objItem.Activate
			Exit For
		Next
End If

WshShell.Exec cmd

We have done a lot of additional testing on this issue and found that the SWV agent with lots of local profiles is definitely causing the issue.  It doesn’t matter what virtual applications are running on the local machine, even empty layers causes a significant slowdown.  We have a case open with Altiris support and they were able to replicate the issue in their lab.  The case has been escalated to the SWV Dev team.  I’ll post again if we get a solution from support.

Here are the details of our testing

     Freshly Imaged Windows XP computer with 100 local profiles and 5 empty SWV layers took over 10
     minutes to boot up and the Procmon Boot log was 1.7gig.

     On the same computer with the same 100 local profiles WITHOUT the SWV agent installed it took 2   
      minutes to boot up and the Procmon Boot Log was only 137mb.