Select a language to translate this page!
Powered by Microsoft® Translator
Tomorrow, on January 11, 2011, the service providing free domain name resolution for Windows Home Server (v1), Windows Server Codename “Vail”, Windows Small Business Server 2011 Essentials Beta, and Windows Storage Server 2008 R2 Essentials Beta will be undergoing an upgrade to move the service to the Azure platform increasing the stability and performance of the service to support the new products releasing in first half of 2011. The service will be unavailable for updates during a 24 hour period. If your IP address changes during this time you will lose remote access to your home or business. This includes records on the .homeserver.com and .remotewebaccess.com domain names.
If your Internet Service Provider does not change your IP address during the outage time, you will not notice an outage. If your Internet Service Provider does change your IP address during this outage, you may see the following errors:
· Alerts from your server’s console stating a failure to update your custom domain name
· Clients on the Internet may fail to connect to the Remote Access website hosted on your server.
· Any 3rd party add-ins that rely on the remote access functionality may fail
When the service comes back online, no action is required. Your server will automatically correct its configuration, the health alerts will disappear and your remote clients will be able to correctly resolve your Home Server again.
If you are using a domain provider from your OEM such as the HP Personal Domain Name by TZO.com or TZO.com custom domain name providers, your domain and network will be unaffected during this outage. Additionally, if you are using a vanity domain name from eNom or GoDaddy for your server, then your domain and network will be unaffected by this outage.
When the upgrade is complete, this post will be updated with information. After the update, if you’re domain name is not working; you can do the following steps:
(1) Open the Windows Home Server Console (or Dashboard)
(2) Click on Settings
(3) Select the Remote Access item in the Settings page
(4) Click Repair and follow the instructions on the screen
Does it really matter since the new product is so delayed, and the current product is discontinued by so many manufacturers, the only way to get a Home server is to make one. MS is really trying to kill this market. Cloud, schmoud, I need a local server for Home and Small Business and I need it now!!
Thanks for the heads up, and thanks Sean for the info on how to extend the trial period. Mary's instructions worked fine, and I'm good through 3/15. DNS is working again without intervention.
As of now the service is back online and fully operational serving DNS Name resolutions for the .homeserver.com and .remotewebacces.com domain names. This means that alerts about your Internet Domain Name in your server console should disappear.
In the extremely rare case of the alerts persisting on your server console, please reboot your server.
If you continue to have problems and you have Windows Home Server v1, please request assistance via this forum - social.microsoft.com/.../67e03711-855d-4dcc-9885-be3ca368f7e4.
If you have Windows Home Server codename "Vail", you should use this forum - social.microsoft.com/.../7181c80d-a7ba-4192-814a-06ffb2740310
Thanks. When is the next beta coming? Is there any chance breckenridge will be public?
The outtage affects both WHS v1 and Vail. It is possible to extend the Vail beta using a work around Mary J Foley has posted as well as some MVPs. In regards to the WHS notifications, the curent notification system doesn't accept notifications from outside of the system.
Thanks for keeping us updated!
Thanks for the heads up!
Interesting contradiction. My server is evaluation period expires in an hour and according to the feedback log ID 634335 this is happening to all Vail users. If so why do we care about the DNS changes tomorrow? I am confused. See here for the source of my confusion: connect.microsoft.com/.../windows-server-2008-r2-trail-is-about-to-end
Thanks for the update. In the future, it might be a good idea to utilize WHS notifications for service notifications like this.