OS of Server: Windows Server 2008R2
SCCM:         SCCM 2012 R2 without any CU
I recently added a new model in our TS and when deploying this model the office 2010 x32bit installation
always fails with error message:

Another installation is already in progress. Complete that installation before proceeding with this install

This problem occurs only when I install this specific new device model HP Elitebook 820 G2

I added a restart step before and after the Office 2010 package.

Any ideas?

Error: Failed to configure: {90140000-006E-040B-0000-0000000FF1CE} ErrorCode: 1618(0x652). 
Error: Failed to configure: {90140000-006E-0411-0000-0000000FF1CE} ErrorCode: 1618(0x652). 
Error: Failed to configure: {90140000-006E-0414-0000-0000000FF1CE} ErrorCode: 1618(0x652). 
MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PROBLEM = ........................................................................... ................................................................................................ C:\WINDOWS\TEMP\Setup000001d0\PSS10R.CHM..............................'
MSI(INFO): 'Property(S): ERRORSUPPORTTEXT_PERMISSION = .................................................................................................................................... ................................................................................................ C:\WINDOWS\TEMP\Setup000001d0\PSS10R.CHM..............................'
MSI(INFO): 'Property(S): ERRORSUPPORTTEXT = ....................................... ................................................................................................ C:\WINDOWS\TEMP\Setup000001d0\PSS10R.CHM..............................'

Have you tried to install the package on the device outside of OSD?

Yes and it is working, only via OSD and only on this model, other models it is installing

Although I would have expected the restart before to likely remedy the situation, you may try opening a cmd prompt and attempt to determine if msiexec is indeed already in use and by what.  I would check like the %TEMP% directory to see if something is installing and logging there.  You might also check the event viewer.

What do you have installing right before Office?

I have this this type of issue where an installer is actually a simple bootstrapper that calls other installation processes then exits. The TS engine sees the bootstrapper exit so it happily proceeds to the next step in the TS but is completely ignorant of things that the bootstrapper launched other processes which still running, cause a conflict.

The easy way around this, if this is indeed the case, is to wrap the bootstrapper in a batch file that adds an arbitrary delay after launching the bootstrapper which gives the spawned processes time to finish. Alternatively, you could figure out the processes that is spawns and wait on the to exit with in the wrapper s