i create a Software Jobs to deploy the new version of Microsoft Lync called Skype for Bussines, but i many object deployed return the mensage
exit code 30066 indicates possible error
exit code 1097 indicates possible error
i create package using reference Greenbook preparing to deploy office 2010
any idea what happens
Those are msi errors you need to look up what that error is with lyncs
Sent from my Verizon, Samsung Galaxy smartphone
HI, but in many computer installed succesfull this package and other say this error
If 1097 is a valid return code for a sucsesful job then add #ec 1097 as procedure options. This will force the job to return “OK” if a 1097 is received.
Principal Engineering Services Architect
Mobile: +1 703 655 7161 | Richard.Lechner@ca.com
Which mechanism do you use to deploy Skype? It's my understanding there may be a few options--
1- Office Customization Tool (OCT), which creates an MSP file.
2- Office Deployment Tool (ODT), which creates an XML file.
3- Standard command line, i.e. lyncentry_4417-1000_x86_en-us.exe /extract:%temp%\lync /log:%temp%\LyncSetup.log /quiet /passive /norestart
The reason I ask is because for the computers that fail installation/upgrade, with some unexpected error code, you need to review the log file to find the root cause. There must be some unexpected scenario that is causing these installation failures.
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)