Category Archives: Internet

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.




The Battle to Save Net Neutrality

The FCC votes to rescind the NET NEUTRALITY regulations on December 14, 2017.  We have only a couple weeks to contact Congress to stop the FCC from messing up our internet.

What CAN I DO RIGHT NOW?

Email Congress – Sample Letter Included

Call Congress from your PC – Sample Telephone Script Included

Attend a Protest at your local Verizon Store on December 7, 2017.

Read More on FCC plans to repeal net neutrality rules. Article by Margaret Harding McGill 11-20-2017 on Politico.com 

Read and download the FCC’s current Declaratory Ruling – WC Docket No. 17-108

Remove the Tab to Open Microsoft Edge in Internet Explorer of Windows 10

Starting with Windows 10 build 15002, a new tab called “Open Microsoft Edge” has been added to the tab bar of Internet Explorer.  This Edge Tab is situated next to the New Tab button on the Tab Bar.

This article will show you how to remove this Open Microsoft Edge Tab.

1. Click/tap on the Tools (Alt+X) button in Internet Explorer, and click/tap on Internet Options. (see screenshot below)

 

2. Click/tap on the Advanced tab in Internet Options, check (remove) or uncheck (default add) the Hide the button (next to the New Tab button) that open Microsoft Edge option under the Browsing section for what you want, and click/tap on OK. (see screenshot below).  Click Apply button, Click OK.

3. Close and reopen Internet Explorer to see that the change has been applied and that the unwanted Tab is gone.

Bye the way, Microsoft wants you to use the Edge browser because all of your searches and your browsing habits are stored to the BING CLOUD.  Microsoft can use your browsing habits to serve you targeted ads in Microsoft Edge.  So far, Microsoft has not chosen to do this when you use Internet Explorer.  I recommend disabling Edge to the maximum extent possible.  Don’t use the Windows 10 apps for “Contacts” or “Mail” or Calendar.  All the content of these Windows 10 Apps is sifted by Microsoft and the content is stored in the Bing Cloud.  Don’t use Cortana.  Same reasoning.  Disable it until it only serves as a file search box.  Finally, go into “Start,” “Settings,” and “Privacy,” and turn OFF as much information leaking functionality as possible, which would otherwise allow apps and Microsoft Windows 10 to store and use your personal information, and the personal information of your contacts, business associates, clients, etc.  Never Log into Windows 10 with your Windows Account ID.  Never authorize the use of your Windows Account ID as the default configuration.  As soon as you enable an APP from the Windows App store, you will be asked to make that default authorization.  You might skip right past it.  That is their intent. 

Allow Remote Desktop for Administration on Windows Server 2008 R2

https://technet.microsoft.com/en-us/library/cc742816(v=ws.11).aspx

Using Remote Desktop

Applies To: Windows Server 2008 R2

To allow remote connections for administrative purposes only, you do not have to install the RD Session Host role service. Instead, you enable Remote Desktop on the computer that you want to remotely administer.

noteNote
Remote Desktop supports only two concurrent remote connections to the computer. You do not need Remote Desktop Services client access licenses (RDS CALs) for these connections.

You can use the following procedure to enable Remote Desktop on a Windows Server 2008 R2 computer.

Membership in the local Administrators group, or equivalent, on the computer that you plan to configure, is the minimum required to complete this procedure.

To enable Remote Desktop

  1. Start the System tool. To start the System tool, click Start, click Run, type control system and then click OK.
  2. Under Tasks, click Remote settings.
  3. In the System Properties dialog box, on the Remote tab, click either of the following, depending on your environment:
    • Allow connections from computers running any version of Remote Desktop (less secure)
    • Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)

    For more information about the two options, click the Help me choose link on the Remote tab.

  4. Click Select Users to add the users and groups that need to connect to the computer by using Remote Desktop. The users and groups that you add are added to the Remote Desktop Users group.
    noteNote
    Members of the local Administrators group can connect even if they are not listed.

 

Install Apache, PHP and MySQL on Windows Server 2008 R2 SP1

 Apache doesn’t provide binaries for Windows, however Apache provides links to several third-party sites that do provide binaries, for example, Apache Lounge. From the Apache Lounge website, and depending on your Windows Server version (32bir-x86 or 64bit-x64 ) we can download either the 32-Bit version (win32) or the 64-Bit one (Win64)

Download the Prerequisites – Example: 64bit versions:

Go to Apache Lounge: Apache2.4.25-win64-VC14
The File Download: (httpd-2.4.25-win64-VC14.zip)

Go to windows.php.net/download:  PHP-7.1-VC14-x64-Thread-Safe
The File Download: (php-7.1.5-Win32-VC14-x64.zip)

Find this at Microsoft:
C++RedistributableVisualStudio2015 (vc_redist.x64.exe)

Installation Instructions for Apache:

First Install the C++ Redistributable Visual Studio 2015.  It will show up in your Programs and Features in the Control Panel.  Using the PHP-7.15 VC14 x64 thread safe and the Apache2.4.25-Win64=VC14, you should also use the C++ VS2015 x64 redistributable (rather than VS2017 version).  Make everything match or you will have errors when you try to start Apache after you

Unzip the Apache2.4.25 VC14 and then copy the extracted contents to a new folder c:/Apache24 (that is the ServerRoot in the config).
Default folder for your your web pages is DocumentRoot “c:/Apache24/htdocs”

Note: If  you unzip to a location other than C:\Apache24, you will need to change ServerRoot in the httpd.conf, and also change in httpd.conf the Documenroot, Directories, ScriptAlias, also when you use the extra folder config file(s) change to your location there.

We may need to set up a fully qualified domain name at this point.

Starting Apache in a DOS box as Administrator.  In other words, ppen a command prompt “As Administrator.”

Change the directory as follow:
cd\apache24\bin

C:\apache24\bin> httpd.exe

At this point, It may appear to you that the system is hanging, but it is NOT hanging.  In fact, it means there are no errors, at least those that are reported at the moment, and that Apache is probably started and running.  Test Apache by opening a web browser and typing localhost in the address bar. Hit enter.  “IT WORKS!”

To “Break” from the “Hang” in the DOS command prompt:
C:\apache24\bin> Ctrl+C

After you install PHP7, then come back here and
Install Apache as a service:

C:\apache24\bin> httpd.exe -k install

Installation Instructions for Installing PHP7.1.5:

Using Windows Explorer (file explorer), create a new folder named php at the Windows C: drive root:

c:\php

Now, extract all the folders and files from php-7.1.5-Win32-VC14-x64.zip.

Then copy those extracted folders and file contents to the new folder:
C:\php

Now, go get and install Notepad++ if you have not already installed it.  This text editor (or one like it) is a must to open and edit various text configuration files for php and apache, etc.

Here is the download page for Notepad++:  https://notepad-plus-plus.org/download/v7.4.1.html  Get the 64-bit or 32-bit version of Notepad++ that your system requires:

But, here is the installer file for the 64-bit version of Notepad++

Within the php root c:\php, open the php.ini.production file and save it as a file named php.ini in the root folder c:\php

Using Windows Explorer (file explorer) find the file called php.ini.production.  Open it using Notepad++ editor.  Now, on the Notpad++ menu, click File, select SAVE AS and change the name of the file to php.ini before saving it. 

APPEND the following items to the existing items within the “PATH” System Environment Variable. Note a Semicolon ; must separate each path item.  If you don’t know how to do this, you must learn.

;c:\php;c:\apache24;c:\apache24\bin

Go to a Dos command prompt and type in:

path (press enter)

You will see a display of what is in the current path. At this point, the above-appended path items are not yet included in the current path.

Log Off Windows, then Ctrl-Alt-Del and log into Windows again.

Now, open a command prompt and type:

path (press enter)

You will see the existing path containing the above-appended path items. 

Integrate / Connect Apache2 to your PHP7:

Using Windows Explorer, go to c:\apache24\conf

Open with Notepad++ the file called httpd.conf
Scroll down within the httpd.conf file and just below all the “LoadModule” lines, insert the following new lines:

LoadModule php7_module C:/PHP/php7apache2_4.dll

<IfModule php7_module>
DirectoryIndex index.html index.php
AddHandler application/x-httpd-php .php
PHPIniDir “C:/PHP”
</IfModule>

Save the changes to httpd.conf file and then close Notepad++

Log off Windows, and log into Windows again.

Test Apache now having php referenced from the httpd.conf of Apache.  How, just like we did above.

Start Apache in a DOS box as Administrator.  In other words, open a command prompt “As Administrator.”

Change the directory as follow:
cd\apache24\bin

and type httpd.exe at the prompt (and press enter).

C:\apache24\bin> httpd.exe

If it “hangs” without errors, you are good!  Open a browser and input localhost in the address bar.  IT WORK! 

In the command prompt window, enter Ctrl+C in order to break to the C:\> prompt.

In Windows, click Start, point at Administrative Tools, and select Services.  Then, in the Services list, find the Apache service near the beginning of the list, right-click the Apache service and left click /or select Properties. Find the correct TAB to STOP the Apache service.

Remember that I said above, after you install PHP7, then come back here and

Install Apache as a service:

C:\apache24\bin> httpd.exe -k install

Test localhost in your Web Browser.  IT WORKS!

Displaying PHP INFO:

Open Notepad++ text editor and create a new file (on the menu, click file, new).  Now, save the new with a filename of phpinfo.php

While you still have the new “phpinfo.php” file displayed within Notepad++, now insert the following contents on line 1 of the new file.

<?php phpinfo() ; ?>

Save the file named phpinfo.php with only this one line of content.  Copy or save this file to the root folder of the Apache http docs. In other words, save or copy the new phpinfo.php file into the following target sub-folder.

c:\apache24\htdocs\

Open a web browser, type into the address bar:

localhost/phpinfo.php

Voila!!!

Open TCP Port 80 In Windows Firewall

https://wiki.mcneel.com/zoo/window7firewall

Open TCP Port 443 in Windows Firewall the same way.

Configure httdd.conf using Notepad++

Find httpd.conf in C:\apache24\conf\
#ServerName www.example.com
#Insert next line & change svr (host header domain com or net)
ServerName svr.yourdomain.tld

Restart Apache service in the Services Module
Start, Administrative Tools, Services.

Set Up a DNS Entry — “A” (Address) record, pointing to your server’s fully qualified domain name and the IP address

You should now be able to connect from a remote 

 = = = = = = To be continued = = = =

ApacheMonitor:

Double click ApacheMonitor.exe, or put it in your Startup folder.

How to Identify and Stop and Remove a Docker Container

This pertains to Ubuntu Server 16.04 running Apache2.x, PHP7.x, and MySQL.  NextCloud 12 is installed and running on a domain with an SSL certificate issued by a public CA (on www.mydomain.tld and mydomain.tld).  I tried to integrate Collabora (Docker) obtaining its own SSL on a subdomain (office.mydomain.tld)

It became necessary to remove and reinstall the Collabora docker container / image. My two SSL certificates were conflicting after Collabora was installed and enabled in NextCloud 12. There was a failed configuration when I following the guided instructions for integrating Collabora online with NextCloud.  Incidentally, the installation mistake occurred  during the “run” phase. I mistakenly (and understandably) entered the sub-domain “office.mydomain.tld” (i.e. the subdomain where my collabora SSL certificate will address) rather than entering the already configured nextcloud domain www.mydomain.tld.  See the correct run command at the end of this Article.

Open terminal or putty ssh connection:

To See All docker containers:
sudo docker ps -a

To Stop a running docker container:
sudo docker stop <container id>
Example:
sudo docker stop 94fc7ad48626

Check the status again:
sudo docker ps -a

To Remove a stopped docker container:
sudo docker rm <container id>
Example:
sudo docker rm 94fc7ad48626

If there is an error at the removal step, it may be necessary to either restart apache or reboot the system.  Restarting Apache did not work for me.  I rebooted the system.

After reboot, check the status again and the container ID should be gone/empty. CONGRATULATIONS.  

When you reinstall Collabora:

Example to run the docker container referencing correct sub-domain of the previously installed nextcloud:
sudo docker run -t -d -p 127.0.0.1:9980:9980 -e ‘domain=nextcloud\\.your-domain\\.com’ –restart always –cap-add MKNOD collabora/code

I am not sure whether I should again first pull the docker Collabora/code before the docker run.  I will let you know.

 

Footnotes:  URL References / Credits:

https://docs.docker.com/engine/reference/commandline/stop/

https://help.nextcloud.com/t/collabora-docker-remove/4851