Overview
As part of the continuous development of IT services, the IT Center is discontinuing support for legacy Microsoft Office file formats dating back to the 1990s. The following formats are affected:
These formats will gradually be fully replaced by the modern XML-based Office formats:
The goal of this transition is to sustainably improve the security, stability, compatibility, and future viability of IT services.
A detailed and comprehensive description of the procedure can be found in the section Powershell Script
Download and extract the script:
Office_Scanner_und_Konvertierung
Open the script using PowerShell
(Note: If the script closes immediately after being launched, please open PowerShell manually as described in the detailed guide and execute the script from there.)
Specify the desired RootPath (Desktop in this example)
.\Skript_Office_Konvertierung.ps1 -rootPath "C:\Users\abc12345\Desktop\"
(Note: Running the script on network drives is generally possible. However, the conversion should be performed separately for each drive and carried out gradually depending on the number of files.)
After the scan, start the conversion by entering j + Enter
Afterwards, verify that the conversion was completed successfully.
This can be checked using the PowerShell output and the log files located in the script directory.
The original files are stored in the Backup_Originale folder.
Files that cannot be converted remain unchanged.
The discontinuation of legacy file formats is based on several factors:
A proper conversion is only possible by using “Open” and “Save As” in Microsoft Office or by using the provided script.
First determine: How many files, which formats, and where they are located.
There are several options:
System and application folders (`C:\Windows`, `Program Files`, `ProgramData`, `AppData`) must be excluded, as they contain application-managed files that must not be modified.
Depending on the number of files found, different conversion approaches may be appropriate.
A search path can be passed to this script. The specified path is searched recursively and all results are stored in a CSV file.
This script can be executed on all devices and is intended to provide an initial overview of affected files. No files are converted during this step.
The script can be downloaded here:
Office_Scanner_und_Konvertierung
Extract the file and copy it, for example, into a (temporary) folder on your desktop:
When executed, the script creates a CSV file in the same directory where the script is located.
.\Office97_Scanner.ps1 -rootPath "C:\Users\abc12345\Documents\"
Open the generated CSV file.
The report provides an overview of how many legacy files were found within the selected search path, where they are located, which internal format they use, and when they were last modified.
After reviewing the results, the files should either be converted, archived, or deleted.
If you do not wish to use the script, the files can also be located using File Explorer.
Open the desired folder in File Explorer.
In the folder, select “Sort”.
Sort or group the files by the “Type” column.
Legacy Office files will then be clearly displayed, for example as:
Microsoft Word 97–2003 Document (.doc) Microsoft Excel 97–2003 Worksheet (.xls) Microsoft PowerPoint 97–2003 Presentation (.ppt)
This makes it possible to reliably distinguish them from modern file formats.
Procedure in Microsoft Word / Excel / PowerPoint
1. Open the file in the legacy format (.doc, .xls, .ppt).
2. Select File → Save As.
3. Select the appropriate file type:
4. Save the file.
5. Briefly verify that the document is displayed correctly and functions as expected. If everything works properly, the file in the legacy format can be deleted.
Recommended for: Individual or infrequently used documents====== Converting Multiple Files at Once (Including Subdirectories) ======
If several files need to be converted at once, especially when they are distributed across many folders and subfolders, it is recommended to use the following PowerShell script.
Download: Office_Scanner_und_Konvertierung
.xls, .doc, .ppt) into the new formats (.xlsx, .docx, .pptx) using COM automation.Requirements / Limitations
The script only works on SCCM-managed devices, not on pure Intune-managed devices (due to stricter policies).
If there are Intune devices containing a large number of legacy files, the data must first be copied to an SCCM-managed PC, converted there, and then copied back to the original device.
Automated Conversion Process
(j/n). Conversion starts only after entering j. Any other input results in no changes being made.For each successfully converted file:
Backup_Originale\ – the source folder structure is mirrored (no naming conflicts).SourceFolder\Subfolder\file.xls ├─ Copy -> Backup_Originale\Subfolder\file.xls ├─ New -> SourceFolder\Subfolder\file.xlsx └─ Original file is then deleted
Files that cannot be converted are skipped unchanged and recorded in a log file.
Classification
Not all files are converted by this script.
In particular, very old files (internal BIFF2/3/4 format, Excel 2.0 - 4.0) as well as password-protected files cannot be converted automatically.
Files containing macros are skipped. In such cases, manual conversion and verification of functionality are recommended (.xls → .xlsm).
| Category | Behavior | Log |
|---|---|---|
| Convertible (OLE2, 97-2003 or 95) | converted | konvertierung.log |
| Contains Macros | skipped | makro_dateien.log |
| Password Protected | skipped | passwortgeschuetzt.log |
| Blocked by File Block (BIFF2/3/4) | skipped | blockiert_dateiblock.log |
| Other Scan Error | skipped | konvertierung.log |
A separate .log file is created for each category, containing all affected files.
Skipped files are not modified. They remain unchanged and can be reviewed individually using the corresponding .log file.
These files should subsequently be converted manually, archived, or deleted.
.\Skript.ps1 -rootPath “C:\Users\abc12345\Documents\”
Enter j in PowerShell to start the conversion.
Depending on the number and size of the files, this process may take some time. Progress is displayed directly in the PowerShell window.
Once the conversion has been completed, another summary and the paths to the individual log files are displayed.
Review the log files and process the affected files manually.
Keep the \Backup_Originale\ folder temporarily in case any problems occur during conversion.
If no issues (formatting, formulas, etc.) are found in the converted files, the folder may be deleted or archived.
Word (.doc → .docx)
Excel (.xls → .xlsx)
PowerPoint (.ppt → .pptx)
Files containing macros are automatically detected during saving. In this case, Microsoft Office will indicate that the .docm / .xlsm / .pptm format is required.
Use the following formats instead:
Please review macro-enabled files particularly carefully and consult the IT Center if you have any uncertainties.
If a file in a legacy format (.doc, .xls, .ppt) cannot be opened locally, it may be converted using the corresponding Office Online application.
Procedure:
Upload the file to OneDrive or SharePoint.
Open the file using Microsoft Office Online:
Confirm the notification regarding the “legacy file format”.
File → Save a Copy (online or locally).
The newly created copy will automatically be saved in the current format (.docx, .xlsx, .pptx).
The IT Center supports you via OTH Regensburg Support with: