It's been a while, but I'll now continue this series of basic tips in the hope to help avoid some deployment unpleasantness that you might rub shoulders with at some point! In this post I'll explain 5 common errors that people make when configuring their newly deployed Windows 7, and what you should really be doing instead... if there is an "instead".
Recommendation: If there is nothing stopping you using Office 2010 x64, then go for it but test it carefully. Otherwise, the best combination at the moment is Windows 7 x64 and Office 2010 x86.
Recommendation: The only recommendation really is to do nothing at all. A good explanation of the "what" and the "why" is available here: http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx
Recommendation: Don't remove any of the default tasks. This page details what they all do: http://support.microsoft.com/kb/939039
Recommendation: If you want to change a setting, such as the log retention policy for example, then use this tool rather than going editing the registry directly. More information here: http://technet.microsoft.com/en-us/library/cc721981.aspx
Recommendation: Turn the Windows Firewall feature off via Group Policy rather disable the service. More information: http://technet.microsoft.com/en-us/library/cc766337(WS.10).aspx
This post was contributed by Daniel Oxley, a Consultant with Microsoft Services Spain
That's a great list Daniel - any chance of a similar small list stating "The things you really should do"...?
Not using a domain admin account as your build account for example...stuff like that?
Good idea, I'll make that the next one!
Office 2010 introduces native 64-bit versions of Office products to support 64-bit processors. Office 2010 also provides support for 32-bit Office 2010 applications that run on 64-bit Windows operating systems by using Windows-32-on-Windows-64 (WOW64). However, the version of Office 2010 to install should not be simply dependent on the Operating System architecture of a master image.
Microsoft makes direct recommendations on TechNet <link> for which version of Office 2010 to install (as well as specific advantages and disadvantages):
• If users in your organization depend on existing extensions to Office, such as ActiveX controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office, we recommend that you install 32-bit Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.
• If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 2 gigabytes (GB), they can install the 64-bit edition of Office 2010. In addition, if you have in-house solution developers, we recommend that those developers have access to the 64-bit edition of Office 2010 so that they can test and update your in-house solutions on the 64-bit edition of Office 2010.
Additional guidance is also given on MSDN <link>:
When should I use the 64-bit version of Microsoft Office?
This is more a matter of which host application (Excel, Word, and so forth) you are using. For example, Excel is able to handle much larger worksheets with the 64-bit version of Microsoft Office.
Generally, it is recommended to install Office 2010 32-bit as part of a master image for performance advantages, unless there is a requirement for users to work with large files larger than 2GB.
Microsoft makes direct recommendations on TechNet <technet.microsoft.com/.../ee681792.aspx> for which version of Office 2010 to install (as well as specific advantages and disadvantages):
Additional guidance is also given on MSDN <msdn.microsoft.com/.../ee691831(office.14).aspx>:
And ugh, dangling prepositions.