$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
Computers, Servers, Messaging, Unified Communications, Voice over IP, etc.
21 Dec // php the_time('Y') ?>
The problem is that Windows Updates will not run properly (giving you various errors) and when Roles or Features are selected un the Server Manager you get the following error:
Error: Cannot display data until your computer is restarted.
16 Dec // php the_time('Y') ?>
Exchange Outlook Web Access is a wonderful feature, but directing users to access it on their own can be a patience testing proposal if you’re not using URL redirection.
For example: you’ve installed Exchange 2010, configured all the appropriate roles, including the CAS (Client Access Server; responsible for OWA), and deserve a hero’s welcome, or at least a pat on the back. You then send an email to staff telling them that they can access webmail from the following public URL – https://webmail.domain.com/owa; easy enough right? Wrong! A few days later, calls come streaming in with users attempting to access OWA using incorrect URL’s: http instead of https, forgetting to append /owa to the URL, etc.
Well you can clear all of this up and make it transparent to the user, and they’ll never know you did it; it will just work.