Skype for Business Autostart failing with AppVolumes Agent 2.15

[Anobix67]

Has anyone else seen this happening on their machines? We capture the Startup/Run piece from registry with UEM to mark Skype to autostart. When using AppVol Agent v2.14 everything works fine and S4B loads up without any issues at sign on. When running v2.15 (with or without any appstacks attached) the Skype for Business splash shows up like it is loading then either crashes out or hangs indefinitely. If we force-close the lync.exe and then proceed to open Outlook (which it then prompts for username and password) and then try to re-open Skype it works fine.

If we disable auto-start on Login from within Skype it will load fine manually as long as it isn't automatic.

Basic Stats:

Horizon 7.6 Environment

AppVolumes Server 2.15 (tested templates built on 2.14 and 2.15)

Windows 10 1709

Office 2016

Any ideas/advice would be helpful.

[Ray_handels]

Could be that the appstack hasn't been loaded yet and you are tyrying to autostart soemthing that's not fully "installed" yet.

Could you try and create a bat file that waits for about 10 or 20 seconds and starts S4B and see if that works?

[Anobix67]

Thanks for the feedback/ideas.

I thought about the AppStack piece, We have Office built into our golden image. If I unassigned all appstacks from the user/machine and sign in the issue is still present.

I was thinking about the .bat file piece or maybe trying to use UEM's creating a shortcut in startup instead of using the Windows registry piece.

I imagine that the .bat file would work as if we do not set to auto-start, but immediately after login go to open skype manually it loads without issue.

[Ray_handels]

If Skype is installed in the base image it should work. If you add the run key in either the GI or by using a policy it should still work.

Any strange error messages in Eventviewer you can see?

[Anobix67]

Yep, I confirmed it continued to not work on a different template as well as a persistent VM of mine (our test pools are instant clones).

Maybe I'm missing an acronym, GI?

The error I see in Event Viewer is:

Faulting application name: lync.exe, version: 16.0.4810.1000, time stamp: 0x5c3e53f4

Faulting module name: KERNELBASE.dll, version: 10.0.15063.1478, time stamp: 0x1f052e05

Exception code: 0xc06d007e

Fault offset: 0x000f07f2

Faulting process id: 0x2908

Faulting application start time: 0x01d4d4f02fd81aff

Faulting application path: C:\Program Files (x86)\Microsoft Office\Office16\lync.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 232d30c4-34db-4e43-b8dd-28b0a7c92d79

Faulting package full name:

Faulting package-relative application ID:

I'm awaiting further confirmation from other testers, but it appears that removing checking the Run registry key (from being set in the application from UEM) and instead setting up lync.exe as a shortcut and put into Startup via UEM shortcuts may do the trick.

[Ray_handels]

Strange. I'd suggest it should just work.

One thing though. Are you capturing this information with UEM also? It could be that UEM is importing the run key during logon because it runs async.. But that's just wild guessing to be honest.