<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"><channel><title>AppTheory</title><link>http://www.apptheory.com</link><description>RSS feeds for AppTheory</description><ttl>60</ttl><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/541/Microsoft-Services-vs-Google-Apps-Premium.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=541</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=541&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Microsoft Services vs. Google Apps Premium</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/541/Microsoft-Services-vs-Google-Apps-Premium.aspx</link><description>I am currently looking into the possibility of using a hosted email environment.  AppTheory has used an internal Exchange server for mail since the company started.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 20 Nov 2009 21:28:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:541</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/532/Scaling-Out-DotNetNuke-Professional-on-Amazon-EC2.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=532</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=532&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Scaling Out DotNetNuke Professional on Amazon EC2</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/532/Scaling-Out-DotNetNuke-Professional-on-Amazon-EC2.aspx</link><description>Amazon Web Services (AWS) is a set of cloud based infrastructure web services that are offered to developers and companies.  These services provide expandable and flexible infrastructure to user.  The are several parts to the cloud infrastructure. Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides compute capacity in the cloud. This compute capacity is provided by Amazon Machine Instances (AMIs).  The machine instances can provide cloud based virtual servers with windows and *nix based operating systems.</description><dc:creator>Max Schneider</dc:creator><pubDate>Tue, 10 Nov 2009 02:21:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:532</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/526/Be-Careful-Applying-Permissions-between-Security-Groups-on-AWS-EC2.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=526</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=526&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Be Careful Applying Permissions between Security Groups on AWS EC2</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/526/Be-Careful-Applying-Permissions-between-Security-Groups-on-AWS-EC2.aspx</link><description>I have noticed that a couple of tutorials have gone into the basics for setting up DNN on AWS with two separate instances.  One instance is the frontend web server and the other instance is a backend SQL server. Two security groups are created one for the Web server (WebGroup) and one for the SQL server (SQLGroup). This is a common setup that we have performed many times at AppTheory.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 30 Oct 2009 19:38:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:526</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/519/Auto-Scaling-and-Elastic-Load-Balancing-with-Amazon-Elastic-Cloud-Computing.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=519</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=519&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Auto Scaling and Elastic Load Balancing with Amazon Elastic Cloud Computing</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/519/Auto-Scaling-and-Elastic-Load-Balancing-with-Amazon-Elastic-Cloud-Computing.aspx</link><description>Last week I talked about how AppTheory uses Amazon CloudWatch to help monitor our DNN instances on AWS EC2. CloudWatch also allows AWS EC2 users to enable Auto Scaling. Auto Scaling allows for the seamless scaling of Amazon EC2 instances “during demand spikes to maintain performance.”  Auto Scaling also allows for an application to gracefully scale down “during demand lulls to minimize costs.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 16 Oct 2009 21:40:43 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:519</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/517/CloudWatch-on-Amazon-Elastic-Cloud-Computing.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=517</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=517&amp;PortalID=2&amp;TabID=411</trackback:ping><title>CloudWatch on Amazon Elastic Cloud Computing</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/517/CloudWatch-on-Amazon-Elastic-Cloud-Computing.aspx</link><description>One of the tools that I have been using for quick monitoring of the DNN web and SQL instances AppTheory manages at AWS is CloudWatch. CloudWatch is a monitoring system much like the taskmgr on your server that lets you see a quickly monitor your instances CPU, Disk Reads/Writes, In/out network traffic.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 09 Oct 2009 19:39:16 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:517</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/511/Tools-for-Monitoring-Performance-Issues-on-AWS-Instances.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=511</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=511&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Tools for Monitoring Performance Issues on AWS Instances</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/511/Tools-for-Monitoring-Performance-Issues-on-AWS-Instances.aspx</link><description>Mysterious performance issues can occur with physical servers and virtual instances. I have been experiencing that issue with a client’s SQL server. This SQL server is the backend server for a couple of DNN web servers. The servers are all virtual instances on Amazon Web Services(AWS) Elastic Cloud Computing(EC2). One of my duties at AppTheory is to fix performance issues with client servers and instances. I thought a list of tools that can help detect and resolve performance issues would be handy. Here are the tools that I have used.  AWS Tools :  Cloud Watch – Allows for the monitoring of instances on AWS (CPU, Disk Activity, and Network)  Diagnostic Tools – These command line tools require AWS Premium Support&amp;#160; and collect System and Network information (If you instances are in production sign up for AWS support)  Windows Tools :  Perfmon – Server tool that provides performance counters for Monitoring system Performance (Good for web servers, SQL servers you name it)  Debug Diagnostic Tool – Great tool for troubleshooting hangs, slow performance, memory leaks, and crashes of processes. Special focus on IIS and COM+  SQL Profiler – Tool to monitor the performance of an SQL Server instance  Log Parser 2.2 – Universal query access to txt files, XML files, CSV files, Event Log, Registry, file system, and AD.  SQLdumper.exe – Generate dump files for SQL Server.  SQLdiag Utility – General diagnostic collection utility that can be run from console or as a service.  Process Explorer – Sysinternals answer to the Task Manager  Sysinternals Utilities – Besides Process Explorer Sysinternals has a collection of useful applications covering File and Disk, Networking, Processes, and System Information</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 02 Oct 2009 19:32:28 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:511</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/508/Managing-the-Root-Drive-Space-on-AWS-Instances.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=508</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=508&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Managing the Root Drive Space on AWS Instances</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/508/Managing-the-Root-Drive-Space-on-AWS-Instances.aspx</link><description>At AppTheory here is how I would become aware of a drive space problem. I would get an email notification from the monitoring system that a client DNN web site has suddenly become unavailable or it’s performance has started to decline. I would then remote into the server to identify the issue. I would see that the root drive was down to 100MB. After a little investigation I find that a log file or temp file is eating up the drive space. Has anyone seen a few 250 MB log files? The resolution is fairly simple, either delete or move the offending files to another drive.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 25 Sep 2009 20:32:16 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:508</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/504/Amazon-Elastic-Cloud-Computing-Bundle-Management.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=504</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=504&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Amazon Elastic Cloud Computing Bundle Management</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/504/Amazon-Elastic-Cloud-Computing-Bundle-Management.aspx</link><description>At Apptheory we have been using Amazon Web Service (AWS) Elastic Cloud Computing instance bundles as part of our backup strategy for clients.  The DotNetNuke (DNN) installs that we run for clients regularly receive updates to the operating system, new modules and DNN updates. Bundling instances while a nice option and a critical step is a bit cumbersome in its current configuration.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 18 Sep 2009 21:25:53 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:504</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/498/AWS-and-Spam.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=498</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=498&amp;PortalID=2&amp;TabID=411</trackback:ping><title>AWS and Spam</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/498/AWS-and-Spam.aspx</link><description>     If you plan on running a DotNetNuke solution on Amazon Web Services you need to lock down your servers.&amp;#160; This same rules that apply in a traditional hosted environment apply to a virtual environment like AWS. At Apptheory we specialize in deploying and managing secure DNN environments. For those of you out there that don’t think Amazon is paying attention to your server you were wrong.&amp;#160; Amazon does pay attention and if your server is not locked down you will get a nice email that starts with(instances and IP addresses have been edit to protect the victims):  Dear EC2 Customer,We have received a report that your instance(s):Instance ID: ******* IP Address: ***.***.***.**** Start date: 2009-**-** 09:15 +0000* End date: Nonehave been sending spam/unsolicited email.&amp;#160;

You have a 24 hour window within which to reply or face suspension of your instance or termination of your account. I would suggest several things to solve and prevent your instance being used for spam:


  Check your security groups and authorization&amp;#160; 

  Check your active sites for open relays 

  Audit your sites regularly 

  Read Amazon’s Whitepaper on securing your instances 
</description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 10 Sep 2009 15:40:28 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:498</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/497/Amazon-EC2-Wish-List.aspx#Comments</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=497</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=497&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Amazon EC2 Wish List</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/497/Amazon-EC2-Wish-List.aspx</link><description>For the last year I have been using Amazon Web Services(AWS) to host DotNetNuke(DNN). In that time I have noticed that AWS&amp;#160; Elastic Cloud Computing is missing a few features. Most of these missing features have not been deal breakers for our clients at AppTheory.&amp;#160; To truly offer a robust environment I believe that Amazon will need to start offering these features.&amp;#160;&amp;#160; In no particular order here are the features I have noticed that are missing are:     Multiple IPs         This is a must for servers that will house multiple sites with ssl.        Windows Server 2008         For windows users 2003 is nice but with the Windows Server 2008 R2 on the horizon it is time to look into making Windows Server 2008 available.        Reverse DNS         This is a standard feature provided by most ISP’s.        Reserved Windows Instances         They offer discounted reserved instances for linux servers but not for windows servers. I know it is most likely a licensing issue but reserved instances should be made available to windows instances.       Bundles Improvements         Bundling an instance should not require shutting down the instance. A graceful scale-up procedure would also be good. Amazon offers multiple instance types and for smaller companies you often need to scale-up before you scale-out. Scaling-up right now requires creation of a new instance making sure that it matches your current environment and rolling over to the new instance.        Elastic Volume Improvements         There needs to be shared volumes between instances.       Amazon is offering a great service with AWS but they need to start realizing that clients will expect to see a few things:     lower costs    scalability    a feature set that equals or rivals ISPs and Hosting solutions&amp;#160;  </description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 10 Sep 2009 15:06:42 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:497</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/492/Windows-7-using-VHDs-for-Development.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=492</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=492&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Windows 7 using VHDs for Development</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/492/Windows-7-using-VHDs-for-Development.aspx</link><description>Okay a cool feature included with Windows 7 Ultimate is the ability to boot from a VHD. These VHDs are treated as separate partitions and have a lot smaller performance hit than running a virtual instance. I have recently created two VHDs to boot from my windows 7 laptop.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 28 Aug 2009 21:09:35 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:492</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/488/Using-SQL-Server-2008-and-Visual-Studio-2008-on-Windows-7-RTM.aspx#Comments</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=488</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=488&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Using SQL Server 2008 and Visual Studio 2008 on Windows 7 RTM</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/488/Using-SQL-Server-2008-and-Visual-Studio-2008-on-Windows-7-RTM.aspx</link><description>Since the release of Windows 7 RTM most of us at AppTheory have installed it on a secondary system for testing with DotNetNuke.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 21 Aug 2009 16:08:26 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:488</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/483/Understanding-the-AWS-ec2bundleinstance-utility.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=483</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=483&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Understanding the AWS ec2-bundle-instance utility</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/483/Understanding-the-AWS-ec2bundleinstance-utility.aspx</link><description>At AppTheory we like to bundle our instances whenever a change to the root drive has occurred whether it be updates or adding new software. I have noticed that occasionally bundles will hang when executing a bundle tasks on AWS EC2. This happened the other night when I was bundling a DotNetNuke web server instance. The bundle task would update once and show the ‘waiting-to-shutdown’ as the bundle state.&amp;#160; The task never changed it’s status, after 40 minutes I cancelled the task.&amp;#160; I then performed a reboot of the server and attempted to perform the bundle again.&amp;#160; The bundle quickly went from a bundle state of ‘waiting-to-shutdown’ to ‘bundling 3%’&amp;#160; and completed in about 40 minutes. I was happy that the bundle had succeeded but I was also a bit worried about it failing. I decided to do some research to better understand the bundling process for AWS instances.  A couple of key point according to Amazon when you are bundling a server:      Instances are shut down and remote connections are disconnected     Only the root drive is bundled     Bundle start time can be reduced by deleting temporary using the Disk Cleanup tool, defragment the hard drive, and zero out free space with sdelete     The Ec2configSetup folder contains the info contains the logs and settings for reboots and bundles     On a 32 bit instance the Ec2configSetup is located at C:\Program Files\Amazon\     On a 64 bit instance Ec2ConfigSetup is located at C:\Program Files (x86)\Amazon\    Ec2ConfigSetup depends on .Net so don’t remove .Net    If you want to get a better idea of what goes on during a bundle take a look at the Ec2ConfigLog.txt. This contains the logs for bundles.&amp;#160; Look for the information after the line: action: shutdown reason: bundle-pending.&amp;#160; When I checked my log I did not see anything that would show the bundling process&amp;#160; as being failed.&amp;#160; I think that the bundle was waiting for a thread to close out. The thread would not gracefully close out so a restart was required. But without a specific error code I am not certain. I would like to see Amazon adopt a more detailed log of bundle events.&amp;#160; A format that would give error codes for bundle failures or timeouts to make troubleshooting a little easier. I am not to fond of the idea restarting a server to then have it shutdown for a bundle.&amp;#160;   &amp;#160;  &amp;#160;  &amp;#160;</description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 13 Aug 2009 21:20:49 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:483</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/478/Regularly-Audit-old-sites-ndash-donrsquot-abandon-sites.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=478</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=478&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Regularly Audit old sites &amp;ndash; don&amp;rsquo;t abandon sites</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/478/Regularly-Audit-old-sites-ndash-donrsquot-abandon-sites.aspx</link><description>According to netcraft there are 239,611,111 hostnames on the internet only about 72,000,000 of those hostnames are active sites. Some times these sites fall into a state of neglect. The client may loose interest in maintaining or updating the site. The site may not generate much traffic and not receive any updates.  The site may be considered a demo of past work. Last but not least the site might just be forgotten and ignored.  During my time at AppTheory I have seen several DotNetNuke sites suffer due to neglect or abandonment.</description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 06 Aug 2009 21:38:18 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:478</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/472/Protect-Ya-Neck-ndash-Bundle-your-AWS-EC2-instances.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=472</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=472&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Protect Ya Neck &amp;ndash; Bundle your AWS EC2 instances</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/472/Protect-Ya-Neck-ndash-Bundle-your-AWS-EC2-instances.aspx</link><description>At Apptheory we have been deploying  DotNetNuke instances on Amazon EC2 virtual servers.  Amazon EC2 is an Infrastructure as a Service run on Amazon’s data center. So how does the title to a song from Wutang Clan relate to DotNetNuke and Amazon EC2?  Bundles on EC2 help protect your data, protect your resources, and limit your downtime.  Bundle to “protect ya neck”.</description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 30 Jul 2009 17:14:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:472</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/455/Keep-the-Same-Name-for-Multiple-Instance-launches-on-AWS-EC2.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=455</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=455&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Keep the Same Name for Multiple Instance launches on AWS EC2</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/455/Keep-the-Same-Name-for-Multiple-Instance-launches-on-AWS-EC2.aspx</link><description>The nice thing about Amazon Web Services Elastic Cloud Computing is the ability to setup testing instances.  You only need these instances to be available part of the time. The problem with launching new bundles is that sysprep is run and the instance is renamed each time a launch occurs.</description><dc:creator>Max Schneider</dc:creator><pubDate>Thu, 25 Jun 2009 15:11:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:455</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/432/Questions-to-ask-before-migrating-DotNetNuke-to-the-cloud.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=432</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=432&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Questions to ask before migrating DotNetNuke to the cloud</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/432/Questions-to-ask-before-migrating-DotNetNuke-to-the-cloud.aspx</link><description>There are a lot of questions and concerns when it comes to moving your DotNetNuke installation to a cloud solution. I have currently been doing a lot of work with Amazon’s EC2 service.  There are other options that are available or quickly becoming available.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 01 May 2009 21:16:40 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:432</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/424/Manage-Multiple-DNN-instances-Easily-Switch-between-Amazon-EC2-accounts.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=424</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=424&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Manage Multiple DNN instances - Easily Switch between Amazon EC2 accounts</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/424/Manage-Multiple-DNN-instances-Easily-Switch-between-Amazon-EC2-accounts.aspx</link><description>In one of my earlier blogs I talked about tools to use with Amazon EC2 instances.&amp;#160; A common situation is managing multiple Amazon accounts for clients.&amp;#160;&amp;#160; I have user 1 who has his own EC2 account. I also have user 2 that has his own EC2 account.&amp;#160; I am provided the Access key and the private key for both their accounts.&amp;#160; How do I insure that I can easily switch between their two accounts with my different tools and have some separation between the accounts?  When using the AWS console I simply login as each user when I need to use the web based console.&amp;#160;   With Elastic Fox you are able to add multiple accounts to the add-on and then switch between the two.&amp;#160; This is done by selecting the Credentials button and adding your keys and the account name to Elastic Fox.&amp;#160; You can then switch by using the dropdown arrow in the Credentials box.  To get use of all the commands available with EC2 you will want to use the API tools.&amp;#160; To switch between clients I create a batch file for each client which will remap the EC2 API tools variables to the correct keys for each account.&amp;#160; I then create a shortcut to each batch file so that I can quickly change between the accounts. Another good idea is to add the API Tools bin folder to your path so that the commands are available outside the bin directory.   Below is an example of the batch file. Change the path to … to the physical path for the required file.     set EC2_CERT=path to your 509 key



  set EC2_PRIVATE_KEY=path to your private key
</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 24 Apr 2009 15:33:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:424</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/417/DNN-in-the-Cloud-ndash-Root-Drive-Management.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=417</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=417&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DNN in the Cloud &amp;ndash; Root Drive Management</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/417/DNN-in-the-Cloud-ndash-Root-Drive-Management.aspx</link><description>The question that will make most IT staff cringe “Hey the site is down, any idea why?”&amp;#160; This is a question you don’t want to have to answer.&amp;#160; Well someone asked me that question the other day.&amp;#160; After a moment of panic, I logged into the web server and found that the root drive only had about 50MB available.&amp;#160; This had caused the site to go down.   The server in question was a DNN web server.&amp;#160; The server was also a virtual instance hosted in the cloud at Amazon.&amp;#160;&amp;#160; One thing to note with Amazon hosted and created EC2 instances is that your root drive is limited to 10GB.&amp;#160; This not a problem if you plan carefully.&amp;#160; You must take into account all applications that might write to the root drive.&amp;#160; I would suggest moving any logs, cache files, configuration setting, and any files that might increase in size to another EBS drive.&amp;#160;&amp;#160;   After some quick investigation with&amp;#160; portable version of WinDirStat on the root drive it appeared that a third party application had been installed and the the cache and log files had been left on the C drive.&amp;#160; I quickly cleared the cache for the application and moved the the cache folder and log folder to another drive.&amp;#160; This released about 5GB of space on the root drive and the site was up and running.&amp;#160;   Here are a few pointers for managing drive space in the cloud:     Know your programs log and cache settings don’t settle for the defaults.    If a folder our file can live on another drive besides the root, move it.    Use portable versions of tools (WinDirStat) and leave them on a utility drive which can be mounted when needed.    Monitor your root drive to minimize surprises. </description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 17 Apr 2009 16:51:39 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:417</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/411/Tools-for-using-Amazon-Web-Services.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=411</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=411&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Tools for using Amazon Web Services</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/411/Tools-for-using-Amazon-Web-Services.aspx</link><description>We have recently moved a few DNN instances to the Elastic Compute Cloud(EC2) on Amazon Web Services(AWS).  I had a friend ask me a question, “ What tools do I need to use Amazon Web Services to setup and manage my DNN instance?”   The answer is just a few tools.  The tools are all provided by Amazon Web Services (AWS).  Here is a description of a few free tools that you can use to setup and manage EC2 on AWS.
AWS  Management Console
The AWS Management Console is a web-based user interface that allows management of your cloud environment.  Management Console features include the option to start new instances, view and register AMIs, bundle instances, create EBS volumes, make EBS snapshots, configure elastic IPs, configure key pairs, and configure security groups.
The Management Console is a work in progress with Amazon offering more services and features in the future.  To get an idea of what is new or coming soon check  https://console.aws.amazon.com/.
Elasticfox
Elasticfox is a firefox plugin that  acts as a browser based management console for EC2.  The options that are available in the AWS Management Console are also in Elasticfox.  Elasticfox can be downloaded from http://developer.amazonwebservices.com/connect/entry.jspa?externalID=609.  There is also a quick start guide on using Elasticfox at http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1797.  
The nice thing about Elasticfox is that the source code is available on sourceforge http://sourceforge.net/projects/elasticfox/. 
Amazon EC2 API Tools
The API tools are the command line version of the management console.  The API tools does not handle the bundling and uploading of AMIs.  The API Tools are available at http://developer.amazonwebservices.com/connect/entry.jspa?externalID=351&amp;amp;categoryID=251.  
With these three tools you can setup and manage your EC2 on AWS.
</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 10 Apr 2009 17:00:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:411</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/287/Installing-DotNetNuke-5RC2-on-Server-2008.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=287</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=287&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Installing DotNetNuke 5RC2 on Server 2008</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/287/Installing-DotNetNuke-5RC2-on-Server-2008.aspx</link><description>DotNetNuke provides two ways to associate help with any module. The first way is referred to as module online help and will touch on it in a moment. The second way, referred to as module help, is controlled via localization and module actions.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 05 Dec 2008 18:07:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:287</guid></item></channel></rss>