Currently in our Windows 7 reference image (created in MDT) we perform an Office 2010 cache-only install.
Then, during the SCCM OSD task sequence we do an Office 2010 install from the cache.
The downside we're finding with this is that Windows patches are installed when the reference image is created, but not Office patches. So, when a machine is built and hits the user's desk they may very well have a fully patched copy of Windows, but a load of Office patches will be waiting.
So my question is are there likely to be any problems with Office 2010 being fully installed in the reference image? Or might we encounter issues (GUIDs .. SIDs ... whatever)? For sure the image will be slightly bigger, and take a little more time to deploy, but if it means less post-deployment hassle for our users then I'm happy with that.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi all
Currently in our Windows 7 reference image (created in MDT) we perform an Office 2010 cache-only install.
Then, during the SCCM OSD task sequence we do an Office 2010 install from the cache.
The downside we're finding with this is that Windows patches are installed when the reference image is created, but not Office patches. So, when a machine is built and hits the user's desk they may very well have a fully patched copy of Windows, but a load of Office patches will be waiting.
So my question is are there likely to be any problems with Office 2010 being fully installed in the reference image? Or might we encounter issues (GUIDs .. SIDs ... whatever)? For sure the image will be slightly bigger, and take a little more time to deploy, but if it means less post-deployment hassle for our users then I'm happy with that.
Thanks in advance for any advice.
Share this post
Link to post
Share on other sites