What Office 2010 & Office 2013 Admins don’t know about Application Management

Office 2010 and Office 2013 simply don’t ship with the right tools to manage itself.

Managing Office 2010 and/or Office 2013 doesn’t have to be a beast. Once it’s deployed and “out there” you might need to make dynamic changes and ensure users’ settings.

In this whitepaper, understand exactly what the ADM and ADMX files from Microsoft can and cannot do, and see what you’re missing to complete this important job.

Who should read this whitepaper?

Anyone who has more than 20 seats of Microsoft Office deployed. In this paper you will learn:

  • Where Microsoft has major “gaps” in ADM and ADMX coverage
  • Which security settings you should have ON to ensure even “reasonable security” for Microsoft Office
  • Specific settings in each of Microsoft’ major Office pieces which you should ensure are on at all times.

Summary of the whitepaper:

Office 2010 and 2013 admins have it hard enough. Users are constantly making changes and working around your security.

Yes, Microsoft ships both ADM and ADMX templates for Office 2010 and Office 2013. But it’s a good idea to understand what they DO and DON’T DO.

What you don’t know could hurt you.

See how PolicyPak can fill in the gaps when it comes to managing your Office 2010 and/or Office 2013 on your desktops.

This paper is absolutely free. Enjoy!



WHITEPAPER SIGNUP

Your Details







Select Whitepapers

Please select as many as apply for your situation

Group Policy Admin
SCCM Admin
VDI Admin
Deep Freeze Admin
Internet Explorer Admin
Office 2010/2013 Admin
Windows 7 & 8 rollout
Windows 8 Tips for IT pros

PolicyPak in a Microsoft Enterprise
PolicyPak in a VMWare Enterprise
PolicyPak and SANS Alignment
State of Application Config Management

Get the Technical “Tip of the Week” from Jeremy Moskowitz