Deploying individual MS Office 2010 components through SCCM 2007 R2

[tedcbe]

I have been deploying Office 2010 without Access (X - Not Available - Microsoft Access in Set feature installation states) to the our customers through OCT.

I have all the .msp's in the root of the office folder along with the setup.exe.

I then use setup.exe /adminfile and the relevant msp.

 

I am now looking at a way of checking if Access is installed on any of the old versions (MS Office XP, 2003, 2007) and if so to install access, otherwise Access should not be installed through SCCM.

 

Has anyone done this and if so how did you go about this.

[cotagag]

The conditions you are looking for are quite easy to be implemented in a task sequence logic.

The only thing you will have to do is to find how to detect if certain version of Access is already installed in your target machine. You can use registry keys or even the path to access.exe to get the file version. You will find a lot of posts on how to detect if specific version of Access in already installed.Then add the installation of your Access package in a container in the task sequence and add the desired logic.