Skip to main content

Wordpress to Blogger migration; Publish to personal domain name 1and1

How to migrate from Wordpress to Blogger and to publish your blogspot.com address to your personal domain name - e.g. publishing www.syswow64.blogspot.com at www.syswow64.co.uk

NOTE: Work in progress
  1. Log in to blogger, select your Blog
  2. Select Settings > Basic > Publishing
  3. Click Advanced settings and enter your personal domain name and hit save.

  4.  
    • You will receive an error message since you do not have proven ownership of the domain
  5. If you have your domain name registered with 1and1.co.uk (basic account) you will not be able to follow the instructions as the CNAME is too long (more than 32 characters).
  6. I suggest you change your NameServer to point at byethost.com. You will not only be able to take full control of long CNAMES but you will be able to add 5 domains and share 1000MB for free.
1and1 nameserver instructions:

  1. Login to 1and1 and go to the "Domain Overview"
  2. Select the domain name and edit the DNS settings to point to byethost.com.





















Byethost Setup instructions:
  1. Register a free account with Byethost.com
(More to follow)

Comments

Post a Comment

Popular posts from this blog

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Sharepoint documents will not open in Word/Excel

Sharepoint documents will not open in Word/Excel Today I have been dealing with a very interesting Office 365 / SharePoint issue. It was reported that the Edit in Application button within SharePoint i.e. “Edit in Excel” “Edit in Word” is not working correctly and results in an empty Spreadsheet or empty Word document. Viewing and Editing within the browser is fully functional and the behaviour varies depending on computers within specific OU in active directory.  It is worth noting at this point the estate consisted of Office 2013 ProPlus installations running on Windows 8.1. The fact that identical systems with identical software versions patch to the same level, resulted in different behaviour could only mean Group Policy was different between them. I was quickly able to find the offending policy; " Block signing into Office: Enabled ". The screen shot above details a systems policy with the issue. With the Standard Workstation GPO's the policy "Block signing into...