If you're reading this message, then it means that I managed to successfully migrate TheDailyWTf.com and the related settings from our old server (74.50.110.120) to the new server (162.252.83.113).

Shameless plug: I did all of this by setting up a configuration role in our internally-hosted Otter instance for both old and new servers (to make sure configuration was identical), deploying the last successful build to the new server using our internally-hosted BuildMaster instance, and then manually installing the certificate and configuring the database.

Here's what the OtterScript looks like for the server's configuration. I'd love to move this to a publically-hosted instance, soon!

# TheDailyWtf.com and Aliases
{
    IIS::Ensure-AppPool WtfAppPool
    (
	Runtime: v4.0,
	Pipeline: Integrated,
	IdentityType: ApplicationPoolIdentity
    );

    IIS::Ensure-Site TheDailyWtf.com
    (
	AppPool: WtfAppPool,
	Path: C:\Websites\TheDailyWTF\thedailywtf.com
    );

    IIS::Ensure-VirtualDirectory Images
    (
	Site: TheDailyWtf.com,
	PhysicalPath: c:\Websites\TheDailyWTF\WTF Images
    );

    IIS::Ensure-SiteBinding
    (
	Site: TheDailyWtf.com,
	Protocol: https,
	HostName: thedailywtf.com,
	Port: 443,
	Certificate: thedailywtf.com,
	CertificateStoreLocation: CurrentUser,
	CertificateStore: WebHosting
    );

    foreach $HostName in @(img.worsethanfailure.com, www.worsethanfailure.com,
	  worsethanfailure.com,img.thedailywtf.com,www.thedailywtf.com,thedailywtf.com)
    {
	IIS::Ensure-SiteBinding
	(
	    Site: TheDailyWtf.com,
	    HostName: $HostName
	);
    }
}

# Novelty Sites
{
    IIS::Ensure-AppPool StaticHtmlAppPool
    (
	Runtime: No Managed Code
    );

    foreach $Site in @(TheDailyWth.com, Virtudyne.com, Codethulhu.com)
    {
	IIS::Ensure-Site $Site
	(
	    AppPool: DefaultAppPool,
	    Path: C:\Websites\Novelty\$Site,
	    Bindings: @(%(IPAddress: *, Port: 80, HostName: $Site, Protocol: http))
	);
    }
}

Let me know if you notice any issues -- apapadimoulis at inedo dot com!

Update: Someone mentioned that the certificate on the new server doesn't include the img.thedailywtf.com sudomain, and that on some images that still use that subdomain, you may find images not loading if you're browsing over HTTPS. I forgot to add that to our certificate when we bought it, so I'll try to fix it soon.