This is an interesting infographic I wanted to share. Get the full article here.

https://www.entrepreneur.com/article/228176

1. MS Web Eco System

2. Web Platform Installer

3. Web Deploy

4. Web Application Gallery 

For better visibility watch it in full view.

[View:~/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-84-99/Geek.mp4:0:0]

Personally, I love Windows Server 2003, one of the best servers created by Microsoft. I had amazing experiences deploying applications on IIS6 and also doing troubleshooting on this platform.

You should already be on Windows Server 2008 or 2012 and running IIS7.5 or IIS8 ; otherwise, start preparing your migration plan, Right away!. 

There is a good bunch of information been posted on different Microsoft Sites, and I will try to compile here those that I find most useful.

Don’t panic! We’ve got 10 resources to help you upgrade from Windows Server 2003
https://blogs.technet.com/b/mva/archive/2014/08/26/don-t-panic-we-ve-got-10-resources-to-help-you-upgrade-from-windows-server-2003.aspx

Windows Server 2003 end-of-support website
https://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/

Best Practices for Windows Server 2003 End-of-Support Migration
https://blogs.technet.com/b/server-cloud/archive/2014/08/26/best-practices-for-windows-server-2003-end-of-support-migration.aspx

Keep an eye on this post...

The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and user

Complete info here: https://heartbleed.com/s

The Heartbleed vulnerability in OpenSSL (CVE-2014-0160) has received a significant amount of attention recently. While the discovered issue is specific to OpenSSL, many customers are wondering whether this affects Microsoft’s offerings, specifically Windows and IIS.  Microsoft Account and Microsoft Azure, along with most Microsoft Services, were not impacted by the OpenSSL vulnerability. Windows’ implementation of SSL/TLS was also not impacted.

We also want to assure our customers that default configurations of Windows do not include OpenSSL, and are not impacted by this vulnerability.   Windows comes with its own encryption component called Secure Channel (a.k.a. SChannel), which is not susceptible to the Heartbleed vulnerability.

This applies to all Windows operating systems and IIS versions, up to and including IIS 8.5 running on any of the following operating systems:

•             Windows Server 2003 and 2003R2 
•             Windows Server 2008 
•             Windows Server 2008R2 
•             Windows Server 2012 
•             Windows Server 2012R2

Customers running software on Windows that uses OpenSSL instead of SChannel (for example, running the Windows version of Apache), may be vulnerable.  We recommend that all customers who may be vulnerable follow the guidance from their software distribution provider.  For more information and corrective action guidance, please see the information from US Cert here.

Source: https://blogs.technet.com/b/erezs_iis_blog/archive/2014/04/09/information-about-heartbleed-and-iis.aspx

Out of the box Hyper-V does not support connecting virtual machines to wireless network adapters.  As a primarily server focused product this is a reasonable limitation - especially given evils that we need to do to get wireless network adapters to work with virtual machines.  But all is not lost - it is possible to setup an internal virtual network (as discussed yesterday) and utilize Internet Connection Sharing (as discussed here) to get you up and going.

The first thing to do is to create a new internal virtual network switch:

1. Open the Hyper-V Manager and select your server.
2. Select Virtual Network Manager... from the action pane (on the right).
3. Select New virtual network and choose to Add an Internal network.
4. Give the new virtual network the name you want hit OK.

Now to setup Internet Connection Sharing:

1. Open the Control Panel and open Network and Sharing Center.
2. Select Manage network connections from the list on the left.
3. Locate the icon for your original wireless network adapter, right click on it and select Properties.
4. Change to the Sharing tab.
5. Check Allow other network users to connect through this computer's Internet connection.
6. If you have multiple network adapters you will need to select the specific entry for the internal virtual network switch.
7. Click OK.

You can now connect virtual machines to the internal virtual network and allow them to access the Internet through your wireless network adapter.

Both or your network adapters in your host machine

original and virtual shourl show that you have internet

A few months ago, netcraft.com reported about the growth of sites running on IIS, which was edging closer and closer to Apache's market share. This month (July 2014), NetCraft's web server survey confirms that this has finally happened and IIS is now the market leader with close to 374 millions sites and a 37.5% share of the market.

Microsoft now leads in hostnames, but Apache is still far ahead in terms of active sites

Read the full article here:

https://news.netcraft.com/archives/2014/07/31/july-2014-web-server-survey.html

So take a look at: https://blogs.msdn.com/b/debuggingtoolbox/archive/2014/05/13/debugging-low-level-software-analysis.aspx

and enjoy by courtesy of Roberto Farah (Senior Escalation Engineer at Microsoft)