Managing Mailbox Size and Quota on Exchange Server 2016

See:

https://theitbros.com/mailbox-size-and-quota-exchange-server/

Global Settings:  You can configure mailbox quotas from the Exchange admin center (EAC) web interface. To do this, go to the section Servers > Databases > select the required databaseProperties > Limits.  Set the necessary quotas on the Limits tab.

 

 

Customize Per Mailbox:  Mailbox quota settings can also be changed from EAC (Recipients Mailboxes > Properties > Mailbox usage > More Options > Customize the quota settings for this mailbox).

 

Example:  Change to “unlimited” instead of 2GB default maximum.

Issue a warning at (GB)  9.9

Prohibit Send at (GB)  “unlimited”

Prohibit send and receive at (GB) “unlimited”

Click “Save”

 

Creating Redirect in IIS7 from HTTP to HTTPS after Installing SSL Certificate

IIS Redirect HTTP to HTTPS

Setting up an HTTP/HTTPS redirect in IIS

Once the SSL certificate is installed, your site still remains accessible via a regular insecure HTTP connection. To connect securely, visitors must specify the https:// prefix manually when entering your site’s address in their browsers.

In order to force a secure connection on your website, it is necessary to set up a certain HTTP/HTTPS redirection rule. This way, anyone who enters your site using a link like “yourdomain.com” will be redirected to “https://yourdomain.com” or “https://www.yourdomain.com” (depending on your choice) making the traffic encrypted between the server and the client side.

Below are steps to setup a IIS HTTPS redirect:

    1. Download and install the “URL Rewrite” module.
    2. Open the “IIS Manager” console and select the website you would like to apply the redirection to in the left-side menu:
    3. Double-click on the “URL Rewrite” icon.
    4. Click “Add Rule(s)” in the right-side menu.
    5. Select “Blank Rule” in the “Inbound” section, then press “OK”:
    6. Enter any rule name you wish.
    7. In the “Match URL” section:- Select “Matches the Pattern” in the “Requested URL” drop-down menu 
      – Select “Regular Expressions” in the “Using” drop-down menu 
      – Enter the following pattern in the “Match URL” section: “(.*)” 
      – Check the “Ignore case” box
    8. In the “Conditions” section, select “Match all” under the “Logical Grouping” drop-down menu and press “Add”.
    9. In the prompted window:
      – Enter “{HTTPS}” as a condition input 
      – Select “Matches the Pattern” from the drop-down menu 
      – Enter “^OFF$” as a pattern 
      – Press “OK”
    10. In the “Action” section, select “Redirect” as the action type and specify the following for “Redirect URL”:https://{HTTP_HOST}{REQUEST_URI}
    11. Check the “Append query string” box.
    12. Select the Redirection Type of your choice. The whole “Action” section should look like this:

NOTE: There are 4 redirect types of the redirect rule that can be selected in that menu: 
– Permanent (301) – preferable type in this case, which tells clients that the content of the site is permanently moved to the HTTPS version. Good for SEO, as it brings all the traffic to your HTTPS website making a positive effect on its ranking in search engines. 
– Found (302) – should be used only if you moved the content of certain pages to a new place *temporarily*. This way the SEO traffic goes in favour of the previous content’s location. This option is generally not recommended for a HTTP/HTTPS redirect. 
– See Other (303) – specific redirect type for GET requests. Not recommended for HTTP/HTTPS. 
– Temporary (307) – HTTP/1.1 successor of 302 redirect type. Not recommended for HTTP/HTTPS.

  1. Click on “Apply” on the right side of the “Actions” menu.

The IIS redirect can be checked by accessing your site via http:// specified in the URL. To make sure that your browser displays not the cached version of your site, you can use anonymous mode of the browser.

The rule is created in IIS, but the site is still not redirected to https://

[Skip to #6 and #7 Below “SOLVED.” This is my recommended tip which I doubt that you will find elsewhere on the net.  You will see the logic.]

Normally, the redirection rule gets written into the web.config file located in the document root directory of your website. If the redirection does not work for some reason, make sure that web.config exists and check if it contains the appropriate rule.

To do this, follow these steps:

  1. In the sites list of IIS, right-click on your site. Choose the “Explore” option:
  2. “Explore” will open the document root directory of the site. Check if the web.config file is there.
  3. The web.config file must have the following code block:
    <configuration>
     <system.webServer>
     <rewrite>
     <rules>
     <rule name="HTTPS force" enabled="true" stopProcessing="true">
     <match url="(.*)" />
     <conditions>
     <add input="{HTTPS}" pattern="^OFF$" />
     </conditions>
     <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" />
     </rule>
     </rules>
     </rewrite>
     </system.webServer>
    </configuration>
  4. In Windows File Explorer on the IIS Server, open the web.config file using a good editor like Notepad++.  Make sure the elements of this rule are contained between one set of beginning and ending rule elements, that is between <rule> {redirect rule code goes here] </rule>.  There may have been one or more existing rules already configured between the “<rules></rules>” elements.
  5. If the web.config file is missing, you can create a new .txt file, put the aforementioned code there, save and then rename the file to web.config.
  6. [SOLVED]  Go into your IIS Management Console and click to select your website name on the left menu.  Click “Bindings” on the far right action column.  In the bindings page dialog, you should see an existing “https” host header for yourdomain.com that has the SSL certificate bind to it in order to handle SSL.  Make sure you ADD an http: host header for www.yourdomain.com and ADD an http: host header for yourdomain.com (without the www) to handle Non-SSL.  YOU NEED THE NON-SSL headers to capture the web query before it can be redirected to https SSL for the encryption to be handled by your SSL Certificate.
  7. [SOLVED] ALSO, make sure NOT to require SSL from within IIS.  Select your website on the left.  Double click on the SSL icon in the middle pane.  CLEAR THE CHECKBOX THAT WOULD REQUIRE SSL.  APPLY.
  8. Click the text Restart link on the far right pane / column of the IIS management console (mmc snapin) to restart the websits.
  9. Open and CMD.exe prompt from the Start / Run in Windows Server.
  10. Stop and Start the Web Service.  In the command prompt window, type “net start w3svc” and [Enter]. Wait until the service is stopped.  Then, type “net start w3svc” and [Enter]. Wait until the service is started.  Close the command prompt window (X out or exit).
  11. Go test the website from a remote browser by typing in the address bar www.yourdomain.com and it should properly redirect to https//your domain.com.  Accomplished.  

If this article helped you and saved considerable time and effort, please consider donating a little something through paypal to support continued hosting of this site.  Thank you.




Fix VSS Writer Errors for Windows Backup Errors on Server 2008 R2 with Exchange 2010

This article applies to Windows XP, 7 and Server 2003.  It also works in Server 2008 R2 SP1 when trying to uses Windows Backup with Exchange 2010.

Having trouble running Windows Backup on Windows Server 2008 R2 SP1 with Exchange 2010 Installed?  Do you keep getting errors with Backup Failed? See the following URL and the following instructions.

https://kb.datto.com/hc/en-us/articles/200554775-Resolving-VSS-Writer-Errors-in-Windows-XP-Windows-7-and-Windows-Server-2003

Open a command prompt selecting “Run As Administrator” 

Run the command line command:

vss list writers

Write down each writer service that shows an error.  Then, match each writer with an error to each Service Name shown in the table at the above URL.

Then, open Administrative Tools, Services, and find each service that you have in your error list, and restart each service that shows an error after you ran the command vss list writers.

Re-run the command vss list writers. Repeat the service restart of each writer with an error.

Reboot if you can’t get rid of all errors.

Run the command vss list writers.

If no error, run Windows Backup.

 

Installing Windows Server Backup Features on Server 2008 R2

Even though Windows Server Backup may be listed in your Administrative Tools, we still need to actually install the Windows Server Backup feature. The easiest way to install Windows Server Backup and the Backup Tools is by using Add Features in the Server Manager.

  1. Log into Windows as Administrator or with a different account having administrative privileges.
  2. Select Start, All Programs, Administrative Tools, and finally Server Manager.
  3. Select  the Add Features link on the right panel and the Add Features Wizard will start.
  4. Select the plus sign next to Windows Server Backup Features. Check the box next to Windows Server Backup Features and then also check the sub box next to Command Line Tools to make sure they are installed as well.  In other words, both sub boxes under Windows Server Backup Features will be checked. Then, click the Next button.
  5. Review the Confirm Installation Selections page and then click the Install button.
  6. After installation of Windows Backup Server Features is complete, review the installation results and then click the Close button.

Exchange 2010 OWA Options or Inbox Rules Will Not Load – Server 2008 R2

When you are logged into Outlook Web Access (OWA) and you try to access “Options” such as “Create Inbox Rule” or “All Options,” you get redirect to an error message page that says, “Unexpected Error – An error has occurred and your request couldn’t be completed. Please try again.”

When you load (run) the performance monitor

Start > Run > c:\perfmon (Enter)

you may see this alert box for “Performance Monitor Control” when you select, or whenthe snap-in console is focused on, “Performance” in the left menu: 

 

WARNING:  DO THIS AT YOUR OWN RISK.  I DISCLAIM ALL RESPONSIBILITY FOR YOUR RESULTS AND/OR THE AFFECT ON YOUR SERVER SYSTEM AND REGISTRY.  I TOOK THE CHANCE AND IT SOLVED MY IMMEDIATE OWA PROBLEMS.

Rebuilding the Performance Counter Setting, using the lodctr /R command from a command prompt (opened with Run as Administrator) allows the Options pages in OWA to properly load:

On the server, click Start , in the search box, type, cmd.exe

In the search results shown above the search you performed, right-click on the “cmd.exe” result, and left-click on and to select the option to “Run As Administrator.”

When the command window opens, make sure that your command prompt shows:

C:\Windows\System32>

otherwise, enter this to change directory:

cd\Windows\System32 (Press Enter key on your keyboard)

Then enter the following command to rebuild the performance counter setting:

lodctr /R (Press Enter key on your keyboard)

It takes quite a while for the lodctr /r command to completely execute, and there is no progress indicator!  BE PATIENT AND LET IT RUN TO CONCLUSION.  The cursor just seems to hang after you enter the lodctr /R command and press (Enter).  Remember to also “resetiis” from the command window after successfully rebuilding performance counter setting. 

Here are a few articles that I found which address these issues and possibly your issues:

https://support.microsoft.com/en-us/help/2554336/how-to-manually-rebuild-performance-counters-for-windows-server-2008-6

https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/perfmon-problems-unable-to-add-counters/e90f231d-0014-457d-8b1f-5f342971597a?auth=1

https://coredumpelf.wordpress.com/2016/03/30/exchange-2010-sp1-ecp-wont-load