Skip to main content

Force file format in Office via GPO.

By
When in the process of upgrading from Office 2003 to Office 2007, the file types for Word, Excel, and PowerPoint change. This will result in your Office 2003 users not being able to open the documents from the 2007 version. There are two mitigations for this issue.

The first one is to deploy the Office 2007 Compatibility Pack to your Office 2003 users. This will allow your Office 2003 users to load and save documents in the new 2007 format. You can get a copy of the Office 2007 Compatibility pack from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=941b3470-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en

The second option is to force your Office 2007 users to save all files in the Office 2003 format. You can do this during deployment using the Office Customization Toolkit, or by using Group Policy. By using Group Policy, you can more easily reverse this option once all clients have been upgraded to Office 2007.
The first step is to download the Office 2007 Administrative Templates for Group Policy Manager. You can download them here: http://www.microsoft.com/downloads/details.aspx?FamilyId=73d955c0-da87-4bc2-bbf6-260e700519a8&displaylang=en


Once you add the administrative templates into your GPO, follow these instructions:
  • In the left pane of the Group Policy Management Console, double-click User Configuration and double-click Administrative Templates (Classic Administrative Templates (ADM) in Windows Vista).
  • To change default file save options in Office Excel 2007:
  • Double-click Microsoft Office Excel 2007, double-click Excel Options, and click Save.
  • In the right pane, right-click Save Excel files as, and selects Properties.
  • In Save files in this format, select Enabled.
  • In the drop-down box, select a default file save format.
  • Click Apply to save the settings.
  • To change default file save options in Office PowerPoint 2007:
  • Double-click Microsoft Office PowerPoint 2007, double-click PowerPoint Options, and click Save.
  • In the right pane, right-click Save files in this format, and select Properties.
  • In Save files in this format, select Enabled.
  • In the drop-down box, select a default file save format.
  • Click Apply to save the settings.
  • To change default file save options in Office Word 2007:
  • Double-click Microsoft Office Word 2007, double-click Word Options, and click Save.
  • In the right pane, right-click Save files in this format, and select Properties.
  • In Save files in this format, select Enabled.
  • In the drop-down box, select a default file save format.
  • Click Apply to save the settings.
Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more