[sccm 2012] Task sequence Install Application step: There are no items to show in this view

[Garacesh]

I've added the Office installer scripts into (what I assume is) the Applications pool (Application Management, Applications) but I'm trying to add them as a step in the Task Sequence but it doesn't show them?

 

 

The scripts themselves are nothing fancy, just batch files with START /WAIT "Office 2016 Setup" "\\Server\Share$\Path\Setup.exe" /config "\\Server\Share$\Path\Config.xml"

 

I can't really find any information about this because it appears Microsoft use the same "There are no items to show in this view." error message across a bunch of other applications.

[Oaktech]

That seems overly complex...

 

 

setlocal

REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************

REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix. 
set ProductName=Office16.PROPLUS

REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\yourserver\yourpath\setup.exe /adminfile \\yourserver\yourpath\updates\yourschool.msp


REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\yourserver\yourpath\ProPlus.WW\config.xml

REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\yourserver\yourpath\logfiles

REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************

IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)

REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)

REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS) 
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto Office) else (goto End)

REM If 1 returned, the product was not found. Run setup here.
:Office
%DeployServer%

echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End

Endlocal

[Arthur]

I'm trying to add them as a step in the Task Sequence but it doesn't show them?

Did you check the following box in your application?

 

[Garacesh]

That seems overly complex...

Compared to your umpteen lines of code that has to check for OS architecture etc, mine seems complicated?

I could just add a Run Command Line step to run the batch, which would probably work, but there's more than Office that needs installing so I might as well do it 'properly'.

 

Did you check the following box in your application?

Yeah, that's ticked on all 4.

[Oaktech]

Compared to your umpteen lines of code that has to check for OS architecture etc, mine seems complicated?

 

I haven't had to generate that - that's from the technet article on deploying office. Really only the first 2 lines are necessary. My SCCM task is way simpler!

[Garacesh]

I haven't had to generate mine either. The Office setup comes with that lot bundled in. It's just "Here's the install exe, here's the config file, go."

 

Alas it's besides the point. There are more applications than Office that need to be installed during imaging. As much as I could do them all with command line tasks, I'd rather have them in as actual applications if possible. Just makes things easier to see what's going on, what we do and don't have getting deployed, etc.

[Oaktech]

I haven't had to generate mine either. The Office setup comes with that lot bundled in. It's just "Here's the install exe, here's the config file, go."

 

Alas it's besides the point. There are more applications than Office that need to be installed during imaging. As much as I could do them all with command line tasks, I'd rather have them in as actual applications if possible. Just makes things easier to see what's going on, what we do and don't have getting deployed, etc.

 

That's the only one I do like that because it just seems to work better - I started off with it as an Application like you did, and it was just unreliable so I gave up.

[Arthur]

mine seems complicated?

Yes.

 

My command-line is just this...

 

 

I have an .MSP file in the Updates subfolder and a Config.xml in the proplus.ww. The Office installer automatically finds these.

[Garacesh]

Deeeeerrrrrrp.

 

Stopped being techie about it (searching error messages) and started being an end-user about it (phrases like "not showing in list")

 

Application properties/Deployment Types/Deployment type properties/User Experience

Logon requirement: Only when a user is logged on

 

Changed that to "Whether or not a user is logged on" and it shows up.