I don't know because I deploy office by using a task sequence in MDT.
You can create an admin mst file to deploy office with your serial and settings. It's better that way so you can include all the office updates in the installation folder.
if you need further help for that create a topic or PM.
Last edited by steewy; 3rd July 2013 at 02:54 PM.
as long as you sysprep office before imaging no
Hello all, only just registered as this topic peaked my interest...
Some things I have picked up on this subject and thought I would share...
If you are going to Capture an Image, ALWAYS use a VM enviroment (VMWare / Hyper-V etc) As doing it off a real device means you have real device issues. Perhaps you have to install a little applicaiton to get the keyboard working, or a reg key under HKLM to get it to do what you want - These things will be in your reference Image!! - Also snapshots and cscript.exe %scriptroot%\ltisuspend.wsf are a life saver here.
There are 3 types of Images Thin, Think and Hybrid.
A. Thin Imags - This is just the out of the box ISO from MS.
B. Thick Images - Everything, Apps, updates kitchen sinks...
C. Hybrid - A bit of both
All have their advantages. For me I use hybrid. Some closer to Thin than others. I would play with thin and Hybrid on your network, see how each pan out. (time them both on your network) use the faster and or most stable. (I have AV issues scanning my deployment share, I argue it doesnt need it, but the guys above me say it needs to).
Finally, if your not using drivergroups and using a seperate task sequence per model, PM I will walk you through it. All you need is a TS per OS (Win7pro / Win7Ent etc) Some clever work and your life becomes easier.
There is no right or wrong with them. Use whatever works.
Last edited by warren17c; 1st August 2013 at 01:17 PM.
There are currently 2 users browsing this thread. (0 members and 2 guests)