Open a Terminal (CTRL+ALT+T)
sudo apt-get install python-software-properties pkg-config
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:team-xbmc/xbmc-nightly
sudo apt-get update
sudo apt-get install xbmc
exit
Originally Published on YouTube on Sep 23, 2014
See how To Install the Kodi Media Center (XBMC), In Ubuntu and Linux Mint from the nightly builds. Kodi is a free and open source media player and entertainment center for Linux, OS X, Windows, iOS and Android.
If you want to be able to see your Taskbar while KODI is running, then change your KODI video output display mode to “Windowed” rather than “Full Screen.” How?
In the sub-menu under “Systems” select “Settings.” Then from the left vertical menu select “System.” Then select “Video Output” and change Display Mode from “Full Screen #1” to “Windowed” under the drop down appearing on the right hand side across from “Display Mode.”
An easier way (less steps) is to select “SYSTEM” from the main KODI menu and then select “System” from the resulting “Settings” menu. Then change Video Output – Display Mode to “Windowed.”
You can do this regardless of whether your Settings Level is set to Basic, Standard, Advanced or Expert.
What is a CSR? A Certificate Signing Request or CSR is a specially formatted encrypted message sent from a Secure Sockets Layer (SSL) digital certificate applicant to a certificate authority (CA). The CSR validates the information the CA requires to issue a certificate. A CSR must be created before ordering and purchasing an SSL certificate (or activating an SSL certificate already purchased through your domain registrar). How a CSR is generated depends on the web server software used. Once the CSR is generated, it can be submitted to the CA. If the request is successfully validated, the CA will issue the SSL certificate.
Here are the steps to generate a CSR in IIS7 on Windows Server 2008 R2. Why might this be necessary? Well, you may want to install Microsoft Exchange and connect to it via Outlook or Outlook Web Access (OWA) which would require Secure Socket Layer (SSL).
Common Name: e.g. yourdomain.com or, if you are creating a CSR for your mail server’s subdomain, then enter something like this containing your server’s host header: mx.yourdomain.com or mail.yourdomain.com
Organization: MyCompany Ltd
Organization Unit (eg, section): Communications, IT, Support, Sales etc.
City/ Locality Name: Los Angeles
State or Province Name (full name): California
Country Name (2 letter code): US
You may view the CSR file using a text editor such as Notepad++ and the certificate request should appear like this:
Image Omitted for security reasons.
Note: When Installing the newly issued (renewal) certificate issued to you by your CA, you must first REMOVE the existing certificate from IIS7 because there will be an installation conflict (between the new certificate and the existing certificate that is still installed on the server. In other words, an error will occur during installation of the new certificate if the existing certificate is not first removed.
This article is based substantially upon Namecheap.com support knowledge base article:
https://www.namecheap.com/support/knowledgebase/article.aspx/9426/0/iis-7
After your new or renewal SSL certificate is issued to you and arrives via email, you may follow these instructions to install it on IIS7, but watch out for the known bug in IIS7.
When you click “Complete Certificate Request” in IIS7 management console, and then browse to find your newly issued *.cer file, when you click Open, you may receive an error message about a “Conflict” explaining that the CSR may not have been issued by the server where you are installing the *.cer file, which is nonsense.
Just continue hitting Retry or OK button a couple times, then hit the cancel button. Refresh the screen in IIS7 Management Console and see if your new certificate is listed there without a Friendly Name associated with it. That is GOOD. Do not remove the installed certificate. Now go to do the Bindings on the IIS7 Default Web Site. See the Second Link (last article) listed two paragraphs above.
Once the bindings are established to https on port 443, then you must restart the default website from within the management console.
Go test that your website can be viewed via https://
The last few lines of the tutorial say:
Click ‘OK’ on the ‘Web Site Bindings’ Window to complete the install.
Important: You must now restart IIS / the website to complete the install of the certificate.
Click See Microsoft Article
When Nokia Mail powered by Yahoo was discontinued, I used the Import-Export-Tools Extension of Mozilla Thunderbird in order to export and thereby backup email messages (EML files) from each Thunderbird folder that was previously connected to Nokia email (mail.ovi.com).
I setup a new gmail account and created a new profile using Thunderbird desktop client to connect to gmail via IMAP protocol. All online folders were then subscribed through Thunderbird.
Using Import-Export Tools in Thunderbird, I imported the back-up email files into my “local folders” in Thunderbird: Inbox, Sent, Drafts, Important, etc. Then, I selected all those imported files from a particular local folder in Thunderbird (such as the Inbox), and I marked all selected files as being ‘unread’ (i.e. bolded them), and then copied them to the appropriate target IMAP gmail folder within Thunderbird.
Thunderbird began uploading / synchronizing the email from the Inbox. I logged into the webmail interface of Gmail and discovered that many of the newly uploaded Inbox files were displaying the current date rather than the correct historical date received. I marked all uploaded files as having been ‘read’ and then re-marked and bolded only those files with the incorrect received dates being displayed. I copied these unread / bolded files into a temporary folder that I created in my Thunderbird “local folders.” IMPORTANT: I then used the web interface of Gmail to delete all the bolded messages in the Inbox. Further, I emptied the Trash folder on the Gmail Web Interface — permanently deleted the bolded messages — those containing the current date as a timestamp rather than the actual date received. Then, within Thunderbird, I copied the still-bolded messages from the Temporary Local folder and pasted them into the IMAP Inbox folder. Voila!!! The dates received are now displayed. It just takes a little coaxing.
Repeat this process for Sent Mail, Drafts, and Important folders in Gmail via Thunderbird using IMAP.
If your Thunderbird or Outlook client stopped working with Verizon email accounts, then this may be why.
Here is the article from Verizon Support:
Please Note: Verizon has recently updated our email client settings to improve security. Please review the settings below to verify that your email software client (e.g. Outlook, Outlook Express, etc.) has the most recent configuration.
Before you begin:
You’ll need the following email settings:
Incoming mail server (POP3): pop.verizon.net
Incoming Server Port Numbers: 995
Outgoing mail server (SMTP): smtp.verizon.net
Outgoing Server Port Numbers: 465 Why is this important?
Make sure SSL encryption is enabled for the incoming and outgoing mail server.
For more email and remote access configuration options see Verizon Online Email Settings
P.S. If you are using Avast Antivirus (which will scan encrypted email messages), then after you change your server names in Thunderbird, you will need to confirm a security exception for POP and SMTP server names in Thunderbird (for the avast scanner proxies to work properly) and also at some point re-enter your valid password and check the box to save and manage your password with the Thunderbird password manager.
Having your email collected using a perimeter server and forwarded to your local network exchange server?
Did you get this error yet when sending to your exchange domain?
Reason: Remote SMTP Server Returned: 550 5.7.1 Unable to relay
Then, try adding a Receive Connector like this.
To permit a non-Exchange server to relay mail to your internal exchange server, create a new Receive Connector on the Hub Transport server.
Note: Since the remote IP address (or range) has been restricted to the single IP address of the perimeter server, then any other servers trying to connect from a different IP addresses still will NOT be able to relay through the Exchange Server (which is as it is intended). In other words, relay will be denied from any other IP address not included in the remote IP address/range on the Receive Connector. If necessary, you can later try to add more IP addresses, IP ranges, or subnets to this receive connector, or possibly even add multiple IP addresses, but you may need to script this latter action.
If you have installed Exchange Server 2010 and want to send outgoing mail through your smart host or non-exchange perimeter server which already has MX records in DNS associated with the smart host, then add a Send Connector to Exchange as follows:
1. Choose Computer Name, like MAIL1. If the domain controller has already been established, then the name will already be something like MAIL1.yourdomain.lan. [NOTE: To establish and configure a domain controller on Server 2008 (64-bit) upon which Exchange 2010 can be installed (like a “One Box” setup), see this article at: http://www.sheldonsblog.com/index.php/configure-windows-server-2008-r2-sp1-for-exchange-server-2010/ ]
2. Make sure Administrative user is member of: Enterprise Admins and Schema Admins. Open Active Directory Users and Computers, under the windows domain, click Users folder, double click Administrator (or other logged in user account) and click properties, then click the tab Member Of, and make sure the user is a member of Enterprise Admins and Schema Admins..
3. Setting up Pre-requisite Roles. Open server management console, right click features and click add features, ADD FEATURES WIZARD opens, Select Features: add .NET Framework 3.5.1 (but this was already added when installing Active Directory services on server 2008 to convert to a domain controller), add RPC over HTTP Proxy and also click button to Add Required Role Services including Web Server (IIS) and Management Tools, Remote Server Admin Tools with Role Admin Tools; for Internet Framework expand the +WCF Activation and check HTTP Activation and Add Required Role Services (Web Server and Windows Process Activation Model), expand +Remote Server Administration Tools, expand Role Administration Tools (installed), make sure Web Server (IIS) Tools in checked, and Check AD LDS Snap-Ins And Command line tools. Next
4. Select Role Services link on Wizard left menu: Add ASP .NET +Add Required Role services, In security, make sure Basic Authentication checked, Make sure Windows Authentication checked, and check Digest Authentication, ALL IIS 6 Management Compatibility, including check IIS 6 Metabase compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, and IIS 6 Management Console. Click NEXT (leads to confirmation), Click INSTALL button. When done installing, click Close button.
5. Set Net.tcp Port Sharing Service Startup Type to Automatic (with Delayed Start). Go to Start, Administrative Tools, Select Services, Select Net.tcp Port Sharing Service, Properties, It is set to Disabled by default. Change Startup type to “Automatic (Delayed Start)” and click Apply and click OK. Close Services
6. Install Microsoft Office 2010 Filter Pack (index content of attachments, docx, xlsx). Note Adobe has its own filter pack for exchange. Office Filter Pack download 64-bit version: http://www.microsoft.com/download/en/details.aspx?id=17062
Microsoft filter pack 2.0 has completed successfully.
7. Install Exchange 2010
1. Insert Exchange 2010 DVD Install Disk in DVD drive. Run Setup.EXE
2. Step 3, Choose Exchange language option – Select install only languages from the DVD
3. Step 4, Click Install Microsoft Exchange, [echo: Microsoft Exchange Server 2010 Setup Initializing]
4. Exchange Server 2010 Setup screen, click Next.
5. Accept License Agreement (radio button), click Next.
6. Enable Error Reporting (this automatically sends error reports to Microsoft). It’s up to you to select Yes or No.
7. Installation Type: Select “Typical Exchange Server Installation” click Next (rather than custom which includes 2 extra items called Unified Messaging, and Edge Transport), and with Typical Installation these items are setup (along with path to Exchange Program Files):
1. Hub Transport
2. Client Access
3. Mailbox
4. Exchange Management Tools
8. Specify Name for Exchange Organization. Default is First Organization. Organization Name: Stored in Mail Database. First Organization – Use the name of your company.
9. Client Setting Do you have any client computers running Outlook 2003 or Entourage in your organization? Yes or No. Next. (Outlook 2003 clients will require setup of public folder database) Recommended: Select Yes. (Just in case), Click Next
10. Configure Client Access server external domain. For internet facing services, for example Exchange ActiveSync, Outlook Web App, Outlook Anywhere. This will allow clients to connect to your exchange deployment outside of your (internal windows) domain.
1. Check the box for The Client Access server role will be internet facing.
2. Enter the domain name you will use with your external Client Access Servers (for example, mail1.yourdomain.com. Click Next button.
11. Customer Experience Improvement Program –
1. The industry that best represents you organization. (Select drop down or not specified)
2. Join the Exchange Customer Experience Improvement Program (CEIP)
3. I don’t wish to join the program at this time.
4. Next button
12. Readiness Checks. Warnings.
1. Warning such as “Setup is going to prepare the organization for Exchange Server 2010 by using ‘Setup /PrepareAD’ and no Exchange Server 2007 roles have been detected in this topology. After this operation, it will be impossible to install any Exchange Server 2007 roles.” If you decide that you need to deploy an Exchange 2007 server prior to deploying Exchange 2010, the deployment of a single Exchange 2007 with all server roles is sufficient to enable the deployment of future Exchange 2007 servers in the organization. I doubt this warning is fatal. It applies mostly to 3rd party or custom apps built on Exchange 2007.
2. Setup cannot verify that the ‘Host’ (A) record for this computer exists within the DNS database on server 127.0.0.1. Check your internet connection. Also, verify on IP v4 connection the following DNS entries dns1 = 127.0.0.1 and dns 192.168.x.x of this servers NIC. Don’t use forwarders in DNS. Just show bind to all IP addresses of server.
13. Install. Click Install. Go find something to drink. It will take quite a while. 00:33:47
8. Finalize this Installation using the Exchange Management Console. (Configure Exchange.) Leave Checkbox Checked (to Finalize). And Click Finish Button which will close Exchange Server 2010 Setup, and will ADD Snap-in to Console.
1. Finalize Deployment Tasks (Checklist)
2. Enter Product Key. Exchange Management Console. Expand +Microsoft exchange On Premises; Click Organization Configuration, Exchange unlicensed, has 119 days remaining. Click Server configuration, and under the Exchange server node name on the right side menu, Click Enter Product Key, and enter it. The product key has been validated and the product ID has been successfully created. This change won’t take effect until the Information Store service has been restarted. Click Finish button, then go to Administrative Tools, Services, and restart the “Microsoft Exchange Information Store” service. Right click the name of the service and left click “Restart.”
THE REMAINDER OF THIS ARTICLE STILL WORK IN PROCESS:
3. Install Forefront Protection 2010 for Exchange Server. (Optional. MS download. Look into it.)
4. Another author reports that you may need to enable Exchange Search to index Microsoft Office 2007 file formats by registering the installed iFilters for Exchange 2010 by modifying the registry. It is suggested to perform this step after installing Exchange 2010. Ask yourself, did I not already install the 2010 filter pack? Note, the other author offered some script to save to file and run. Look into this.
5. Organization configuration, Mailbox. Client Access, Hub Transport most important to configure.
6. Send Connector, New Send Connector, name = internet, add type smtp, *, dns mx record. Next pick a server, this one. New, finish.
7. Server config, client access, owa, enable Outlook Anywhere. External hostname, same as previously named.
8. Exchange active sync.
9. Imap and pop3, enable. But still need to enable the services under admin tools, services. Change from manual to automatic, delayed start.
10. Allow Anonymous Access on the Server’s Default Receive Connector. Exchange Management Console, expand Server Configuration. Select “Hub Transport” Under “Receive Connectors” right click the “Default” Receive Connector, select Properties, select Permission Groups tab, to configure receiving on TCP Port 25 by enabling anonymous users (Specify who is allowed to connect to this Receive connector). Check the Anonymous Users checkbox, and click Apply button and click OK. DONE. Caution: My first guess is that this anonymous connectivity may create an open relay, unless mail can only be delivered to local exchange mailboxes from this Receive connector. Note: Port 587 will have no anonymous access on the other Receive connector here.
11. Recipient configuration. Mailbox. Where you configure all email accounts.
1. New mailbox, next, existing users, add, select the usernames to create mailboxes.
9. Configure Port forwarding on router, for ports 25, 80, 443.
10. Configure some things in IIS.
1. Certificates. Exchange creates default certificates for itself.
2. Default website. http redirect: ./owa checkbox only redirect requests to content in this directory (not subdirectory). This redirect works only with https not http, unless you put full url redirect in like this: https://etc/owa.
Install Windows Server 2008 R2 64 bit version
Exchange Server 2010 is a 64 bit application and requires a 64 bit Server Operating System
After Server 2008 installation, then set the clock and set the name of the Server
The server is presently configured as standalone with default settings
Configure a static IP address because the server will be configured as a domain controller
Go to the server manager screen and click View Network Connections
Double click the icon for the active network adapter (local area connection) to display the adapter status
In the Status screen, click the Properties button
Click to highlight the Internet Protocol Version 4 (TCP/Ipv4) and Click the Properties button
Click the radio button next to “Use the following IP address:” and then enter the IP address that you want to use for this server, for example, 192.168.1.2
After entering the IP address, click the “tab” key and the subnet mask 255.255.255.0 should appear in the entry boxes of the next line (which is fine)
Click the “tab” key and enter the default gateway IP address (which is the gateway address on the local network “LAN” side of you router which provides the network address translation “NAT” over to the public IP side “WAN side” of the router). This number is usually something like 192.168.1.1
Click the radio button next to “Use the following DNS server addresses:” and, under preferred DNS server, enter the same server IP address (that you chose) for the IP address of the server. It is important to include this server’s IP in the DNS server list as the first entry in the list of DNS servers. You can add other alternated DNS servers that you maintain or as provided by your ISP. Note that later when installing Exchange Server, it may be necessary to correct the first DNS to 127.0.0.1 (your server’s localhost) and secondary DNS to the local IP assigned to the network interface of the server, such as 192.168.1.2. Otherwise, Exchange installation wizard will give you a warning that an MX record or an Address (A) record cannot be verified on the IP address 127.0.0.1 (or on 192.168.1.1 as the case may be at the time).
Note: Exchange 2010 requires that you leave IP v6 enabled. So, do NOT disable IP v6 or else the Exchange Hub Transport Service will not start when exchange is installed.
Close the network connections screen
Install Active Directory. When Active Directory is both installed and configured (a two step process), then Windows Server will be a Domain Controller
Go to “Computer Management” screen and press the “Add Roles” link. Under “Server Roles” it says “Select one or more roles to install on this server.”
Check the box next to “Active Directory Domain Services” at which time the add roles wizard says that “you cannot install Active Directory Services unless the required features are also installed. The “Features:” list will include .NET Framework 3.5.1 Features
Click the Button for “Add Required Features” and acknowledge by clicking “Next”
The installation will scan and inform of any other prerequisites. If there are other prerequisites or errors, please correct these and repeat the add roles installation
When the Setup program says that all prerequisites are met, then click the install button to commence this installation process. The setup program will now install Active Directory on your Server
When the installation is completed, there should be a message indicating that the “Installation Succeeded”
Click “Close” to close the Add roles wizard’s “Installation Results” screen in order to return to the Server Management screen.
Configure Active Directory. You should see that the role of Active Directory Domain Services is installed when you are viewing the Server Manager page. It will show a red “x” to indicate the Active Directory Domain Services have errors, namely, that these Services have not been configured.
Click on the line under Roles that is labeled “Active Directory Domain Services” and the Server Manager will show you a page about the status of the Active Directory Role.
Click on the link that says “Run the Active Directory Services Installation Wizard (dcpromo.exe)” and click “Next” when the Active Directory Domain Services Installation Wizard appears.
The Active Directory Domain Services Installation Wizard will display information about Server 2008 domain controllers having a new more secure default for the security setting named “Allow cryptography algorithms compatible with Windows NT 4.0” (which setting is disabled or not configured by default). It explains that this setting prevents Windows and non-Microsoft SMB clients from using weaker NT 4.0 style cryptography algorithms. As a result, applications that require a security channel serviced by Server 2008 domain controllers might fail, for example, certain NAS devices that do not support stronger cryptography algorithms, and certain operations on clients running versino of Windows earlier than Vista SP1 are also impacted. If this is going to be a problem, see KB Article 942564 http://go.microsoft.com/fwlink/?LinkId=104751 The following hotfix package may be applied to computers that are running Windows XP or Windows Server 2003 to resolve this issue: http://support2.microsoft.com/kb/944043 Description of the Windows Server 2008 read-only domain controller compatibility pack for Windows Server 2003 clients and for Windows XP clients and for pre-sp1 Windows Vista. CLICK NEXT.
Choose a Deployment Configuration. At this point, you can create a domain controller for an existing forest or for a new forest.
If this Exchange Server will be the first Domain Controller, then choose the radio button for “create a new domain in a new forest” and click the Next button.
If there is an existing Domain Controller and you want to continue the same domain name, then you may wish to choose the radio button “Existing Forest” and the sub-radion button for either: “Add a domain controller to an existing domain” or “Create a new domain in an exiting forest” in which case this server will become the first domain controller in the newly created domain.” Click the Next button.
Enter the name of your local Domain, which will be the domain name that Exchange will associate with all of your email. When creating a new domain name in a new forest, this domain name becomes the “Name of the Forest Root Domain” because the first domain in the forest is the forest root domain. It’s name is also the name of the forest. Note: If you are on a local network (LAN) behind a router’s NAT firewall, then you may want to distinguish your local network domain name from your public domain name by using either the suffix “.local” or “.lan” instead of a public network domain suffix like “.com” or “.net.” Once you have decided on the name of your internal domain, this name will be your Active Directory Domain and the domain that is serviced by Exchange.
You will enter this internal domain name in the input box under the heading “FQDN of the forest root domain.” Click the Next button.
Set Forest Functional Level. The Installation Wizard will now ask you about compatibility of domain controller active directory servers at the forest level. If you plan to have domain controllers running various versions of Active Directory, then you will want to chose a function level to include the lowest version of Windows Server that you are using for domain controllers. For example, if you have and plan to keep a Windows 2003 domain controller in service, then select “Windows Server 2003” from the drop down list and click Next.
Set Domain Functional Level. The Installation Wizard will now ask you a similar question about domain controller active directory server compatibility at the domain level. Include the same function level namely the lowest version of Windows you plan to use for domain controllers. For example, if you have and plan to keep a Windows 2003 domain controller in service, then select “Windows Server 2003” from the drop down list and click Next.
Additional Domain Controller Options. The installation wizard recommends to install the DNS Server service on the first domain controller. So, if this is the first domain controller, check the box to add DNS Server service and make this domain controller a DNS server running locally. Note: The first domain controller in a forest must be a global catalog server and cannot be an RODC. The Installation Wizard will also automatically make this computer a global catalog server if a new forest and first domain are being created. Press Next.
Specify Location for Database, Log Files, and SYSVOL. You can specify where you want Active Directory to store its data. If you only have one drive in your Server, then it is recommended to use the prepopulated defaults. If you have multiple drives, you can select which drive to use. Click Next.
Directory Services Restore Mode Administrator Password. The Directory Services Restore Mode Administrator account is different from the domain Administrator account. Assign a password for the Adminstrator account that will be used when this domain controller is started in Directory Services Restore Mode. Write down the password. It is different than the domain Adminstrator password, and will not change when the domain Adminstrator password is changed.
Review Your Selections. The Installation Wizard will summarize the configuration that it is about to create. To start the process of configuring your new Domain Controller, click Next.
The Installation Wizard will show its progress as it configures your Server. This will take a long time. The installation wizard dialog says “The wizard is configuring Active Directory Domain Services. This process can take from a few minutes to several hours, depending on your environmnet and the options that you selected. . . . Installing Group Policy Management Console . . . ” No need to check the box that says Reboot on completion.
When the installation is complete, you will be shown a final screen. Click Finish.
Then, restart your computer. Click “Restart Now” to restart your computer so that the changes made by the Active Directory Domain Services Installation wizard will take effect.
After restarting, Windows should show the Server Manager. The Server Manager screen should show that Active Directory and DNS Server roles are installed. Also the process of installing Active Directory will add the features “Group Policy Management” and “Remote Server Administration Tools.”
