Search the Community

I'm starting to use SCCM 2012 and have to say I'm really impressed. There are a few things that really bug me, and one of those has presented me with an issue I'd like some advice on. SCCM2012 uses 'Applications' rather than packages to deliver content to a user or device based on certain circumstances, which is very useful. However, 'Applications' only understand apps that are installed via .MSI files, App-V files, etc. You can't use .exe files. And this is where it comes unstuck, because as we know, the best way to install Office 2010 is to use "setup.exe /adminfile.. /config.." So my question is do I: A: Create a 'Package' (old method) and use that for deploying Office during OSD AND also to Users when required B: Create a 'Package' for OSD AND an 'Application' for Users/Devices (from App-V package, perhaps?) C: Another method I haven't considered? What's the general consensus? Thanks!