I packaged Skype for Business Basic 2016 and did mass deployment recently.
Ended up creating fairly complex batch file to install it. Lot of criteria like Office 2016 already includes Skype for Business 2016, so no need to install those. SBB 2016 is part of Office 2016 family, LYNCENTRY technically.
30066 is generic from Office installer check %WINDIR%\TEMP\SetupExe*.log, should show why failed. Many reasons, low disk space, Office 365 installed, can't install prerequisites, etc.
1097 - Typically means installing wrong version. So if you have Office 2013 x64 and trying to install SBB 2016 x86 it will cause that. Also seen that with stupid configurations like someone installing Office 2007 after Office 2010 x64 installed. Again typically linked to mixing x86 & x64 Office suites.
Logging on Office installers not so great. If you can find Office CLI option to change the log location that is way to go. I ended up using below section from batch script to rename the log and output back to SD job output. Having the log in SD output is valuable for debugging failures.
IF EXIST %TEMP%\SetupExe*.log (
MOVE /Y %TEMP%\SetupExe*.log %TEMP%\%INSTLOG% >NUL
ECHO Output of %TEMP%\%INSTLOG% :
TYPE "%TEMP%\%INSTLOG%"
ECHO ==================
) ELSE (
ECHO %PRODUCT% Logs NOT present
SET INSTERROR=999
)