PENDING Skype for Business 2016 opens Recording Manager

[tarinhtx]

I used OCT to create the msp file for my Office 2016 application deployment, which deployed and installed successfully. However, upon opening Skype for Business 2016 from the start menu it launched Skype Recording Manager. I've tried changing the target in the configuring shortcuts within the OCT but after saving the correct target it switches back to "Skype Recording Manager". Does anybody have any suggestions?

 

[Prajwal Desai]

Have you gone through this ? - https://sysadminblogger.wordpress.c...aunches-skype-for-business-recording-manager/

 

[tarinhtx]

Thanks for the reply Prajwal. I have a batch file that if I run locally on a test computer will correct the issue by replacing the shortcut with a functional one. However, I'm having trouble deploying application which would execute the batch file. The application deploys and "Installs" but for some reason the batch file doesn't run and complete the fix. Is there something I need to change on my Installation Program: filename.bat under the Programs tab or include something in the batch file?

@ECHO OFF

set SCRIPT="%TEMP%\%RANDOM%-%RANDOM%-%RANDOM%-%RANDOM%.vbs"

del "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Skype for Business 2016.lnk"
echo Set oWS = WScript.CreateObject("WScript.Shell") >> %SCRIPT%
echo sLinkFile = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Skype for Business 2016.lnk" >> %SCRIPT%
echo Set oLink = oWS.CreateShortcut(sLinkFile) >> %SCRIPT%
echo oLink.TargetPath = "C:\Program Files\Microsoft Office\Office16\lync.exe" >> %SCRIPT%
echo oLink.WorkingDirectory ="%SYSTEMDRIVE%\Program Files" >> %SCRIPT%
echo oLink.Save >> %SCRIPT%
cscript /nologo %SCRIPT%
del %SCRIPT%

 

[Prajwal Desai]

How are you deploying this batch file to remote computers ?. Using SCCM ?. If the script is working fine when you run it on manually on a computer then we need to investigate why the same isn't happening when deployed.

 

[tarinhtx]

Yes I'm using SCCM 2012 R2 to deploy my application. Here is a response I posted in another forum:

"If I copy the batch file to the user's desktop and double click to execute, it completes the shortcut "fix" which deletes the nonworking SFB start menu shortcut and pastes the functioning SFB shortcut. So after the application is deployed hidden and shows up on the client's System Center as "Installed" under status, the batch file fix never took place. I placed the filename.bat file you see above in my content location \\servername\d$\Installs."

I had one user respond by saying to check to see what context I'm running the batch file as "user or local system".