Amazon Web Services (AWS) offers an officially supported Amazon Machine Image (AMI), but it doesn't indicate which Linux distribution it's based upon.

Is the official Amazon Linux AMI based on another Linux distribution, and if so, which one?

I made the mistake of registering a domain with Arvixe. The domain name is artofshell.com, and I'm trying to delegate this domain over to Microsoft Azure's DNS service.

1. I created a DNS Zone in Azure, and set up several record sets
2. I verified, using PowerShell's Resolve-DnsName command, that the DNS servers are responding properly
3. I set up four (NS) records on Arvixe to point to the Azure DNS servers
4. DNS resolution against the records in Azure DNS fails

When I query for SOA records, I am seeing ns1.crowfoot.arvixe.com instead of the Azure DNS servers. Is that correct, or is something misconfigured on the Arvixe side? Whatever the case, they aren't routing traffic correctly.

Screenshot: NS Records pointing to Azure DNS

Screenshot: Azure DNS Zone

Screenshot: SOA Record for domain

I have the following configuration, with Varnish acting as a cache between the externally facing endpoint (NGINX) and Apache.

+-------+        +-------+       +------+
| NGINX |  +---> |Varnish| +---> |Apache|
+-------+        +-------+       +------+

I can't get my Apache VirtualHost configuration to match, when I call it from a browser. The configuration for my (single) VirtualHost looks like this:

<VirtualHost *:80>
    ServerName fabrikam.com
    ServerAlias fabrikam.com
    ServerAdmin myemailaddress
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access-mycustomlog.log combined
</VirtualHost>

Here's the Apache version:

root@localhost:/etc/apache2# apache2 -v
Server version: Apache/2.4.7 (Ubuntu)
Server built:   Jan 14 2016 17:45:23

Symptom

When I access https://fabrikam.com, it doesn't give me the root of the /var/www/html folder. Instead, it tries to access the root of /var/www, and because I disabled mod_index, it gives me a HTTP 404 Not Found error.

Any thoughts on how to get this VirtualHost configuration to "match" properly? When I access fabrikam.com, it should go to the /var/www/html folder, instead of /var/www in the apache2.conf file.

EDIT

Here's the output from apachectl -S

root@localhost:/etc/apache2# apachectl -S                                       
VirtualHost configuration:                                                                       
*:80                   fabrikam.com (/etc/apache2/sites-enabled/000-default.conf:1)   
ServerRoot: "/etc/apache2"                                                                    
Main DocumentRoot: "/var/www"                                                        
Main ErrorLog: "/var/log/apache2/error.log"                                      
Mutex default: dir="/var/lock/apache2" mechanism=fcntl               
Mutex mpm-accept: using_defaults                                                       
Mutex watchdog-callback: using_defaults                                            
PidFile: "/var/run/apache2/apache2.pid"                                             
Define: DUMP_VHOSTS                                                                            
Define: DUMP_RUN_CFG                                                                         
User: name="www-data" id=33                                                              
Group: name="www-data" id=33   

NGINX Configuration

### Rewrite non-HTTPS URLs to HTTPS
server {
    listen      80;
    server_name fabrikam.com;
    rewrite     ^   https://$server_name$request_uri?;
}

server {
        listen 443 ssl;

        server_name fabrikam.com;
        ssl_certificate /etc/letsencrypt/live/fabrikam.com/cert.pem;
        ssl_certificate_key /etc/letsencrypt/live/fabrikam.com/privkey.pem;

        location / {
            proxy_pass http://127.0.0.1:6081;
            proxy_set_header X-Real-IP  $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto https;
            proxy_set_header X-Forwarded-Port 443;
            proxy_set_header Host $host;
        }
}

Goal

I'm trying to install IP Address Management (IPAM) on a Windows Server 2012 R2 server, against a Microsoft SQL Server 2012 Service Pack 1 database engine instance, instead of using the Microsoft Windows Internal Database (WID).

Configuration

• VMware Workstation 10
• Microsoft Windows Server 2012 R2
• Microsoft SQL Server 2012 Enterprise Edition with Service Pack 1 (installed locally)

Problem

When I try to install IPAM through Server Manager, I get the message below.

IPAM Deployment failed with the following error.

Failed to create database schema.

CREATE DATABASE permission denied in database 'master'.

You can restart this provisioning wizard from the IPAM overview page.

Question

Does anyone know what SQL Server permissions are required to install IPAM using the IPAM server's credentials?

I'm running Outlook 2010 SP1 on Windows 7 x64 SP1, and I'm getting an error message saying

"Your Microsoft Exchange administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance."

I'm still able to log into my account using Outlook Web Access (OWA), so I know that my account is working just fine. Outlook 2010 with Service Pack 1 is the standard for Windows 7 client systems at this organization, and other people are able to access their e-mail just fine. When my account was initially configured, I was able to use Outlook for a couple of days, and then it suddenly stopped working, providing only the above error message.

Do you have any ideas on what I should look into to resolve this problem? Is there any information I can obtain on the client side that will help the Exchange folks investigate the issue further? Is there any verbose logging I can enable, or diagnostic logging in Outlook?

Cheers

Back in Windows Server 2008 R2, when stand-alone Managed Service Accounts (sMSA) were new, they could not be used to execute scheduled tasks. In Windows Server 2012 however, there is a new type of account called the Group Managed Service Account (gMSA). This type of account is supposedly capable of launching scheduled tasks in the task scheduler on clients & member servers inside of a Windows Server 2012 forest/domain functional level.

So far, I have:

• Established a Windows Server 2012 forest/domain
• Created a Group Managed Service Account (gMSA)
• Installed the gMSA on a Windows Server 2012 member server

And currently I'm having trouble with:

• Setting a scheduled task to use the gMSA

When I attempt to use a gMSA on a scheduled task, I get the error message that says "The object cannot be found" (paraphrased) message.

My question is: How do I configure a Scheduled Task to execute using a Group Managed Service Account (gMSA)?

Does SQL Server 2008 R2 Service Pack 2 include Cumulative Update 14, and prior, for SQL Server 2008 R2?