We're deploying Windows onto PCs with a very simple VM image setup, capture, and deploy using WinPE and imagex to create a single .wim with no network dependencies or capabilities involved in the setup process aside from adding the PC to the domain using our naming convention. It's quite a humble and truly "thrown together" solution, but it works well enough for our purposes (despite demonstrated need for more attention paid, but I digress).
The only true issue I'm having with this is our Office 2010 install. I've installed Office, repaired it, and reinstalled it several times (all pre-sysprep, as it must be there before sysprep), but I always get this error pop-up on the first run of any Office application that reads:
"Microsoft Access 2010 requires Visual Basic for Applications. If you continue, Visual Basic for Applications will be installed."
The message specifies Access no matter which Office application runs. Even after this goes through, Outlook no longer recognizes and sets itself up with domain usernames. It must be done manually. However, it Office has a repair operation run before any Office application is launched, everything works perfectly and without error.
Given the rest of the machine works perfectly on deployment, I'm heavily leaning toward the sentiment that Office was never meant to be deployed via sysprep & image capture.
Is this true? More to the point, is there a way around this without spreading the system into MDT, SCCM, etc?