OfficeStatus offers Windows desktop, web, and mobile web end user interface options. Regardless of which of these you choose, OfficeStatus can show dates and times in a locale-specific manner.
If you’re using OfficeStatus Windows Client, this happens automatically as long as each end user’s operating system is configured with the correct region and language settings. All versions of Windows allow the end user to specify their preferred date and time formats, and OfficeStatus Windows Client will honor those.
As for the web (and mobile web) interface, OfficeStatus will automatically adapt date/time displays based upon browser configuration. If no browser configuration language settings are available, the server locale will be used.
For example, let’s say I’m using Google’s Chrome web browser. If I navigate to Settings and click the Show advanced settings link, I can then click the Language and input settings button to reveal the following window:
Using the configuration above, the OfficeStatus web interface will display dates and times in U.S. English. However, if I’m from Latvia, Europe this may not be what I want. The solution is to click the Add button in the Languages window shown above and add the Latvian language to Chrome. Next, I drag and drop Latvian so that it appears at the top of my supported language list:
Now I can click the Done button in Chrome’s settings window and access the OfficeStatus web interface again. This time, I will see date and time values formatted specifically for the Latvian locale. Other browsers (besides Chrome) have similar settings.
If you don’t want to configure each user’s browser, another option is to force the OfficeStatus web interface to use a specific culture configuration. This can be done by modifying the web.config file that resides in the webroot folder below your OfficeStatus Server installation path (for example, “c:\program files\officestatus server\webroot\web.config”).
The web.config file is plain text, so you can edit it with any text editor (we recommend making a backup before editing it just to be safe). Start by finding the following entry:
<globalization culture="auto" uiCulture="auto" enableClientBasedCulture="true" />
If I wanted to force OfficeStatus Server to display dates and times better suited to the Latvian locale, I would change this value as follows:
<globalization culture="lv-LV" />
After making the above change, I save the web.config file and log back into the OfficeStatus web interface (note that all users will be logged out when you save a change to web.config). Again, I’ll see dates and times displayed as expected for the Latvian locale. This will be true for all users, regardless of browser settings.
For a full list of culture codes supported by the “culture” globalization setting above, please click here.
So, as you can see OfficeStatus offers a lot of flexibility in terms of locale support. If you need assistance with any of the above, please don’t hesitate to contact contact us.
Today, Key Metric Software proudly announces the general release of OfficeStatus 6.0.
This new release adds many new product capabilities and feature enhancements, while also striving to keep the product familiar for end users. Our customers indicated a desire for us to minimize user interface changes while moving the product forward in key areas. We believe we’ve achieve those goals with this new version.
Here’s a quick overview of what’s new in OfficeStatus 6:
- Scheduled status recurrence
- Greatly enhanced status board displays
- Redesigned public (large-screen) view
- Numerous reporting improvements
- Overhauled, modernized web interface
- Many improvement to OfficeStatus Windows Client
- Server side user inactivity monitoring
- Many enhancements to resource tracking
- Many administrative improvements
- Much more
For details, please see the following page of our brand new OfficeStatus website:
Since this is major version release, you’ll need to upgrade your existing OfficeStatus licenses before installing the new version. For information on major version upgrades, please see:
And, as always, please feel to reach out to us (email@example.com) if you have any questions.
OfficeStatus provides powerful Exchange calendar integration capabilities, allowing the system to update the status of your users based upon their Outlook calendar appointments.
In order to enable this capability, you’ll need to obtain the EWS (Exchange Web Services) URL of your Exchange installation. That URL is then entered into the Exchange Sync page of the OfficeStatus web interface (see screenshot below):
Below, you’ll find instructions for obtaining your Exchange Web Services (EWS) URL, regardless of whether you’re using Exchange Online, Office 365, or an on-premises Exchange installation.
For Exchange Online / Office 365
1. Access your mailbox account using Outlook Web App (OWA)
2. Click Options > See All Options > Account > My Account > Settings for POP, IMAP, and SMTP access
3. In the list of entries, locate the server name. The URL of EWS for the mailbox is the URL: https://<ONLINE_URL>/EWS/Exchange.asmx
For Microsoft Exchange (on-premises)
1. The URL will use the following format: https://<EXCHANGE_SERVER_HOSTNAME>/EWS/Exchange.asmx
The support team at Key Metric Software has developed and published a new guide entitled “Troubleshooting OfficeStatus Server Installations”. This guide provides detailed assistance with diagnosing OfficeStatus Server installations.
In fact, much of the guidance offered by this paper can be used to troubleshooting Windows Internet Information Services (IIS) and ASP.NET application errors in general.
Please find the guide in PDF format here:
Occasionally we’ll get a support request from an organization that’s attempting to evaluate OfficeStatus, but they are experiencing strange behaviors when attempting to access the OfficeStatus web interface from IE (Internet Explorer).
Typically the scenario goes something like this:
- Accessing the OfficeStatus web interface from IE fails. Specifically, they can’t get past the login page.
- Accessing the OfficeStatus web interface from other browsers (e.g. Chrome, etc.) works fine.
- Accessing OfficeStatus via the Windows Client also works fine.
When a customer experiences the above set of symptoms, usually we discover that they’ve installed OfficeStatus Server on a Windows Server machine that has an underscore in its name. It turns out that Internet Explorer will not accept cookies from a server if the server name contains invalid characters (such an underscore). And without cookies, the OfficeStatus web interface cannot function (because it cannot persist state).
More information can be found in the following Microsoft knowledge base article:
The workarounds are as follows:
- Rename the domain name and/or server name, and use only alphanumeric characters.
- Browse to the server by using the Internet Protocol (IP) address rather than the domain/server name.