Great work as always, thanks for this! Now just to get our hands on it… but since new volume licensing for 2008 is no longer being sold its inevitable at this point.
I wanted to note that this screws up communicator. I just discovered it today and I am kicking myself for not realizing it sooner. So FYI, if you use communicator, do NOT use this method 👿
Nate
*edit* This was microsoft being stupid again with their postflight scripts. See my latest post on this thread – [url]https://www.afp548.com/forum/viewtopic.php?showtopic=27797[/url]
I have a small problem with the Office 2011 installer which may be linked to the user account install also. When I put the Plist files in the user template they don’t work, well the problem is that they don’t get transferred to the new user account when it is created hence they don’t work and Office runs as if new with the setup assistant etc. If I install them in the user account, Libs/Prefs then it’s all good but this is not ideal for obvious reasons. Also the Public and Sites folders are not created in the new user account so there is something screwy with the new user account pkg or my implimentation of it. I’m just trying to get this method working before moving on to the first boot stuff. One step at a time eh?
On a image you created, don’t apply it to a machine, just double click to mount it and then browse to the User Template and make sure all the files are there. I would bet there is a small typo in the full path to the User Template or something of that sort (I’ve done it a few times myself).
Check out the new Office installer patcher, it fixes the Communicator issue I referenced in my post.
Comments are closed