-->

Microsoft Office 95 (version 7.0), also known as Microsoft Office for Windows 95, was a major release of Microsoft Office released on August 24, 1995, along with Windows 95. It was the successor to Office 4.3 and was the first 32-bit version of Microsoft Office. Michael Smith, W3C HTML Activity Lead Last edited: $Date: 2016/09/07 14:16:54 $. Office 2016 and Office 2019 connections to Microsoft 365 services will be supported until October 2023. Note: Office 2019 is the latest version of Office available as a one-time purchase. Microsoft 365 is designed to work with the latest browsers and versions of Office.

Summary: Explains how to deploy Office Online Server on-premises for use by SharePoint Server, Skype for Business Server, and Exchange Server.

Audience: IT Professionals

Office Online Server is the next version of Office Web Apps Server. Deploying Office Online Server involves installing some prerequisite software and running a few Microsoft PowerShell commands, but overall the process is designed to be pretty straightforward. This article walks you through the procedures to get your servers ready, then gives you the Microsoft PowerShell commands to configure the on-premises Office Online Server farm.

Prepare servers to run Office Online Server

Perform these procedures on all servers that will run Office Online Server. This server must be Windows Server 2012 R2 or Windows Server 2016.

Important

Windows Server 2016 requires Office Online Server April 2017 or later. Windows Server 2019 is not supported at this time.

Office Online Server was designed and tested for server operating systems configured with default settings. If you need to deploy with non-default settings, it is recommended to begin installation and setup with the default settings. Once the system is verified as working, then incrementally add and test Group Policies, security settings and other modifications.

Step 1: Install prerequisite software for Office Online Server

To install Office Online Server

1. Open the Microsoft PowerShell prompt as an administrator and run this command to install the required roles and services.

   Windows Server 2012 R2:

Windows Server 2016:

If prompted, restart the server.

2. Install the following software:

Step 2: Install Office Online Server

Next, we'll install Office Online Server.

If you plan to use any Excel Online features that utilize external data access (such as Data Models, Power Pivot, or Power View), note that Office Online Server must reside in the same Active Directory forest as its users as well as any external data sources that you plan to access using Windows-based authentication.

Complete these steps on any servers that will run Office Online Server.

To install Office Online Server

1. Download Office Online Server from the Volume Licensing Service Center (VLSC). Office Online Server is a component of Office, so it is available under each of the product pages including Office Standard 2016, Office Professional Plus 2016, and Office 2015 for Mac Standard.

2. Run Setup.exe.

3. On the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and click Continue.

4. On the Choose a file location page, select the folder where you want the Office Online Server files to be installed (for example, C:Program FilesMicrosoft Office Web Apps) and select Install Now. If the folder you specified doesn't exist, Setup creates it for you.

   We recommend that you install Office Online Server on the system drive.

5. When Setup finishes installing Office Online Server, choose Close.

6. If you're planning to use Kerberos Constrained Delegation with Excel Online, then, in Services, set the Claims to Windows Token Serviceto start automatically on this server.

If you plan to use Kerberos Constrained Delegation with Excel Online, be sure to add each server in the Office Online Server farm to the Active Directory Domain Services delegation list.

Step 3: Install language packs for Office Online Server

Download Patch Microsoft Office 2016 For Mac Price

Office Online Server Language Packs let users view web-based Office files in multiple languages, whether they're opened from SharePoint document libraries or Outlook on the web.

To install the language packs, follow these steps.

1. Download the Office Online Server Language Packs from the Microsoft Download Center.

2. Run wacserverlanguagepack.exe.

3. In the Office Online Server Language Pack Wizard, on the Read the Microsoft Software License Terms page, select I accept the terms of this agreement and select Continue.

4. When Setup finishes installing Office Online Server, choose Close.

To patch language packs, deploy Office Online Updates after installing the Office Online Language Packs.

Important

To install language packs after the Office Online Server farm is created, you must remove a server from the farm, install the language pack on it, and then add the server back to the farm.> For a language pack to work correctly, you'll need to install it on all servers in the farm.

Deploy the Office Online Server farm

Follow the procedures in one of the following three sections, based on what kind of Office Online Server farm you want to create.

Tip

If Microsoft PowerShell doesn't recognize the New-OfficeWebAppsFarm cmdlet when you run it, you may need to import the OfficeWebApps module. Use this command:Import-Module -Name OfficeWebApps

Deploy a single-server Office Online Server farm that uses HTTP

If you're only deploying Office Online Server for testing or internal use, and you don't need to provide Office Online Server functionality to Skype for Business Server 2015, this procedure is for you. Here, you'll install a single-server Office Online Server farm that uses HTTP. You won't need a certificate or load balancer, but you will need a dedicated physical server or virtual machine instance that isn't running any other server application.

You can use this Office Online Server farm to provide Office Online functionality to SharePoint Server 2016 and Exchange Server 2016.

Note

It is strongly recommended to use HTTPS (TLS) regardless of environment as Office Online Server uses OAuth tokens to communicate with external services, such as SharePoint or Exchange Server. OAuth tokens contain information that can potentially be intercepted and replayed by an attacker, granting the attacker the same rights as the user making the request to Office Online Server.

Step 1: Create the Office Online Server farm

Use the New-OfficeWebAppsFarm command to create a new Office Online Server farm that consists of a single server, as shown in the following example.

Parameters

• -InternalURL is the name of the server that runs Office Online Server, such as http://servername.

• -AllowHttp configures the farm to use HTTP.

• -EditingEnabled enables editing in Office Online when used with SharePoint Server. This parameter isn't used by Skype for Business Server 2015 or Exchange Server because those hosts don't support editing.

Step 2: Verify that the Office Online Server farm was created successfully

After the farm is created, details about the farm are displayed in the Microsoft PowerShell prompt. To verify that Office Online Server is installed and configured correctly, use a web browser to access the Office Online Server discovery URL, as shown in the following example. The discovery URL is the InternalUrl parameter you specified when you configured your Office Online Server farm, followed by /hosting/discovery, for example:

If Office Online Server is working as expected, you should see a Web Application Open Platform Interface Protocol (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example.

Step 3: Configure Secure Store access (optional)

If you're planning to use the Secure Store service in SharePoint Server in an HTTP environment, there's a parameter that you need to set to enable this. (If you're not planning to use Secure Store in SharePoint Server with Excel Online, you can skip this step.)

When Office Online Server attempts to refresh data in a workbook or ODC file that is stored in an HTTP path, that data refresh will fail if you have not configured Office Online Server to allow Secure Store connections over HTTP.

Use the Set-OfficeWebAppsFarm cmdlet to configure the Secure Store over HTTP settings:

Keep in mind that the contents of the workbook or ODC file will be transmitted in clear text over HTTP. Data connected workbooks and ODC files contain database connection information, and can contain passwords.

Step 4: Configure the host

The farm is now ready to provide Office Online functionality to hosts over HTTP. Visit the following articles for more information about how to configure hosts.

Download Patch Microsoft Office 2016 For Mac free. download full Version

Deploy a single-server Office Online Server farm that uses HTTPS

For most production environments, we strongly recommend the use of HTTPS for its security features. Also, HTTPS is required if you want to provide Office Online Server functionality to Skype for Business Server 2015, which lets users view PowerPoint broadcasts in a browser. Here's how to install a single-server Office Online Server farm that uses HTTPS. You'll need to install a certificate on the server.

This Office Online Server farm will provide Office Online functionality to SharePoint Server, Skype for Business Server 2015, and Exchange Server 2016.

Step 1: Create the Office Online Server farm

Use the New-OfficeWebAppsFarm command to create a new Office Online Server farm that consists of a single server, as shown in the following example.

Parameters

• -InternalURL is the fully qualified domain name (FQDN) of the server that runs Office Online Server, such as http://servername.contoso.com.

• -ExternalURL is the FQDN that can be accessed on the Internet.

• -CertificateName is the friendly name of the certificate.

• -EditingEnabled is optional and enables editing in Office Online when used with SharePoint Server. This parameter isn't used by Skype for Business Server 2015 or Exchange Server because those hosts don't support editing.

Step 2: Verify that the Office Online Server farm was created successfully

After the farm is created, details about the farm are displayed in the Microsoft PowerShell prompt. To verify that Office Online Server is installed and configured correctly, use a web browser to access the Office Online Server discovery URL, as shown in the following example. The discovery URL is the InternalUrl parameter you specified when you configured your Office Online Server farm, followed by /hosting/discovery, for example:

If Office Online Server works as expected, you should see a Web Application Open Platform Interface Protocol (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

Note

Depending on the security settings of your web browser, you might see a message that prompts you to select Show all content before the contents of the discovery XML file are displayed.

Step 3: Configure the host

The farm is now ready to provide Office Online functionality to hosts over HTTPS. Visit the following articles for more information about how to configure hosts.

Deploy a multi-server, load-balanced Office Online Server farm that uses HTTPS

If you anticipate lots of traffic to your Office Online Server farm, and you want it to be available over the Internet as well as on your internal network, this type of topology is the way to go. This section shows how to install a multi-server Office Online Server farm that uses a load balancer and HTTPS.

Before you begin, make sure your load balancer is configured. Also, you'll need to install a certificate on the load balancer. This Office Online Server farm will provide Office Online functionality to SharePoint Server, Skype for Business Server 2015, and Exchange Server 2016.

Step 1: Create the Office Online Server farm on the first server

Use the New-OfficeWebAppsFarm command to create a new Office Online Server farm on the first server, as shown in the following example.

Parameters

• -InternalURL is the fully qualified domain name (FQDN) of the server that runs Office Online Server, such as http://servername.contoso.com.

• -ExternalURL is the FQDN name that can be accessed on the Internet.

• -SSLOffloaded enables offloading SSL termination to the load balancer.

• -EditingEnabled is optional and enables editing in Office Online when used with SharePoint Server. This parameter isn't used by Skype for Business Server 2015 or Exchange Server because those hosts don't support editing.

Step 2: Add more servers to the farm

After the first server is running Office Online Server, run the New-OfficeWebAppsMachine command on each server you want to add to the Office Online Server farm. For the -MachineToJoin parameter, use the computer name of a server that's already in the Office Online Server farm. For example, if server1.contoso.com is already in the farm, use the following:

Step 3: Verify that the Office Online Server farm was created successfully

After the farm is created, details about the farm are displayed in the Microsoft PowerShell prompt. To verify that Office Online Server is installed and configured correctly, use a web browser to access the Office Online Server discovery URL, as shown in the following example. The discovery URL is the InternalUrl parameter you specified when you configured your Office Online Server farm, followed by /hosting/discovery. For example:

If Office Online Server works as expected, you should see a Web Application Open Platform Interface Protocol (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

Note

Depending on the security settings of your web browser, you might see a message that prompts you to select Show all content before the contents of the discovery XML file are displayed.

Step 4: Configure the host

The farm is now ready to provide Office Online functionality to hosts over HTTPS. Visit the following articles for more information about how to configure hosts.

If you see '500 Web Service Exceptions' or '500.21 - Internal Server Error' messages

If features of the .NET Framework 4.6 were installed and then removed, you might see '500 Web Service Exceptions' or '500.21 - Internal Server Error' messages when you run OfficeWebApps cmdlets. To fix this, run the following sample commands from an elevated command prompt to clean up settings that could prevent Office Online Server from functioning correctly:

For Windows Server 2012 R2 or Windows Server 2016

See also

Microsoft Office 95 (version 7.0), also known as Microsoft Office for Windows 95, was a major release of Microsoft Office released on August 24, 1995,^[5] along with Windows 95. It was the successor to Office 4.3 and was the first 32-bit version of Microsoft Office. While designed specifically for Windows 95, it was compatible with Windows NT 3.51, Windows NT 4.0, and Windows 98. As it was 32-bit, it did not run on Windows 3.x or earlier versions of Windows. It was also not officially supported on Windows NT 3.1 or Windows NT 3.5.^[3] Office 95 was succeeded by Office 97 on November 19, 1996. Support for Microsoft Office 95 ended on December 31, 2001, the same day as Windows 95.^[6]

Features[edit]

Microsoft Office 95 included six applications: Word (a word processor), Excel (a spreadsheet), PowerPoint (a presentation program), Access (a database management system), Schedule+ (a time management app) and Binder (a program for binding the work of the mentioned apps together). The CD-ROM version also included Microsoft Bookshelf.

True to its namesake, this suite was designed specifically for Windows 95. Previously, Microsoft had released Office 4.2 for Windows NT for several architectures,^[7] which included 32‑bit Word 6.0 for Windows NT and Excel 5.0 for Windows NT,^[8] but PowerPoint 4.0 was 16‑bit. With Office for Windows 95, all components in the suite were 32-bit. All the Office 95 programs were OLE 2-enabled, meaning that they allowed interoperability between themselves, as well as all other applications that support this data interchange protocol. Binder used this protocol to bind OLE objects together.^[4]

Office for Windows 95 moved the version number of its applications to 7.0 to match Word's version number. Other components also bore the same version numbers to show that they were contemporaries, although their predecessors were not version 6.0. The previous versions of components were Word 6.0, Excel 5.0, PowerPoint 4.0, Schedule+ 1.0 and Access 2.0. Binder was a new app at the time with no predecessor.

The Office 95 programs utilized a two-tone gradient in the title bar at the top of the window, gradually turning from black at the left side to dark blue at the right. At the time, this was unique to Office 95, no other program running under Windows 95 or Windows NT utilized gradient title bars. This feature was eventually incorporated into the shell of Windows 98 and later, which would allow customizable gradient colors and extend the feature to include dialog boxes as well.

Microsoft Excel contained an easter egg, a hidden Doom–like game called Hall of Tortured Souls crediting the application's writers.

Contemporaneous components[edit]

Several additional programs were marketed as 'compatible with Microsoft Office 95':

Download Patch Microsoft Office 2016 For Mac

• Microsoft Project for Windows 95 (Version 4.1a)
• Microsoft Publisher for Windows 95 (Version 3.0)
• Microsoft FrontPage 1.1
• Office Small Business Pack for Office 95
• Small Business Financial Manager for Excel^[9]

Other contemporaneous Microsoft products were:

• Microsoft Works 4.0
• Microsoft Money 4.0

Download Patch Microsoft Office 2016 For Mac Download

Editions[edit]

Office 95 was available in two versions. They contained the following applications:^[10]

Updates[edit]

Two updated versions, 7.0a^[18] and 7.0b^[2] were released to fix bugs in the applications, including a fix for a screen redraw problem in PowerPoint. The updates could be ordered from Microsoft Support. A downloadable update was released in 1999 to address issues related to the Year 2000 problem.^[19]

Issues[edit]

Versions 3.0 and 3.5 of the Microsoft Jet database engine, used by Access for Windows 95 (Access 7.0) and the later released Access 97 respectively, had a critical issue which made these versions of Access unusable on a computer with more than 1 GB of memory.^[20] While this problem was fixed for Jet 3.5/Access 97, it was never fixed for Jet 3.0 or Access 95.

System requirements[edit]

Microsoft Office 95 requires a 386DX or higher CPU, and either Windows 95 or Windows NT 3.51. It also requires 8 MB of RAM for typical use. Regarding hard disk space, compact installations require 28 MB, 'typical' installations require 55 MB, and full installations require 88 MB.^[3]

References[edit]

1. ^'Microsoft Office 95 And Windows 95 Scheduled To Be Available Simultaneously'. PR Newswire. Cision. July 10, 1995. Archived from the original on December 6, 2015. Retrieved August 21, 2019 – via The Free Dictionary.
2. ^ ^ab'OFF95: Summary List of Fixed Bugs in Microsoft Office Version 7.0b (Revision 1.3)'. Support. Microsoft. July 18, 2007. Retrieved May 2, 2013.
3. ^ ^abc'Microsoft Office 95 (v. 7.0) - box pack - 1 user'. CNET. CBS Interactive. Retrieved June 14, 2017.
4. ^ ^abSolomon, Christine (1996). Developing applications with Microsoft Office 95. Redmond, WA: Microsoft Press. ISBN9781556158988.
5. ^Zisman, Alan (October 1995). 'This Suite smells of success: MS Office 95 review of new features'. Zisman.ca. Retrieved May 2, 2013.
6. ^'Microsoft Office Products Support Lifecycle FAQ'. Support. Microsoft. April 1, 2013. Retrieved May 30, 2014.
7. ^'Microsoft readies supporting versions of Microsoft Excel and Word for Windows NT The PowerPC'. Thefreelibrary.com. Farlex. PR Newswire. June 12, 1995. Retrieved May 2, 2013.
8. ^'Microsoft announced Word 6.0 and Excel 5.0 for Windows NT Workstation'. Thefreelibrary.com. Farlex. PR Newswire. September 19, 1994. Retrieved May 2, 2013.
9. ^'Microsoft Announces Small Business Financial Manager'. Stories. February 6, 1996. Retrieved July 29, 2020.
10. ^Microsoft Press, Issue #3 1997, sales catalogue Part No. 098-69985
11. ^Microsoft Word for Windows 95 - Step by step. ISBN1-55615-828-9.
12. ^Microsoft Excel for Windows 95 - Step by step. 1995. ISBN1-55615-825-4.
13. ^Microsoft PowerPoint for Windows 95 - Step by step. ISBN1-55615-829-7.
14. ^'TOC - 10 Minute Guide to Schedule+ for Windows 95'. ssuet.edu.pk. June 21, 2002. Archived from the original on June 21, 2002. Retrieved June 9, 2013.
15. ^'Description of Office Binder support with Office 2003 and Office XP products'. Support. Microsoft. February 5, 2007. Retrieved June 14, 2013.
16. ^Running Microsoft Access for Windows 95. ISBN1-55615-886-6.
17. ^Microsoft Bookshelf for Windows 95. Microsoft Press. August 1995. ISBN978-1-57231-159-6.
18. ^'List of Fixed Bugs in Word 7.0a for Windows 95 (Revision 1.1)'. Microsoft Support. Microsoft. August 31, 2005. Archived from the original on October 24, 2012. Retrieved May 2, 2013.
19. ^Luening, Erich (March 17, 1997). 'Microsoft offers Y2K patch for Office 95'. CNET. CBS Interactive. Retrieved May 2, 2013.
20. ^''Out of memory' error starting Microsoft Access'. Support (5.1 ed.). Microsoft. January 19, 2007. Archived from the original on August 25, 2014. Retrieved June 18, 2019.