OEM Preinstall Guidance
1. Update Rollup 3 support OEM preload before server setup. Please follow the general preinstall steps.
2. As part of UR3, you also need to install KB 2578133 from http://support.microsoft.com/kb/2578133 as part of the preloading package.
3. After preloading, Open the dashboard and Help->About, make sure the Dashboard version is 6.1.8800.16397
4. Complete the IC setup, and follow the test guidance as descripted below.
3. Bug List and test guidance
Issue 1- Windows 8 client hits an error when connecting to WHS 2011
Test Steps:
Connect a Windows 8 client computer to Windows Home Server 2011, verify that the client is connected successfully without errors; Verify that the client features, including the client backup, Launchpad works afterwards.
Issue 2 – RWA folder cannot display thumbnails correctly on Windows 8 client.
Test Steps:
Launch RWA from Windows 8 client machine (Internet Explorer 10); Verify the thumbnail for folder and files are displayed correctly, instead of a black square.
Issue 3 – Power settings for backup does not work on Windows 8 clients.
Test Steps:
Connect a Windows 8 client to the server, and set the client backup property to “Automatically wake this computer up from sleep or hibernation to run a scheduled backup”.
Set the client computer to sleep or hibernate, verify it will wake up and run the scheduled backup successfully.
Issue 4- “Computer Monitoring Error” Alerts are generated every 30 minutes
Following issues have been fixed:
1. Computer monitoring Error alert triggered by client synchronization timeout.
2. Computer monitoring Error alert due to staled computer record of a client computer that was removed. (Hotfix KB2686867, KB 2685867, KB 2686857)
3. Computer Monitoring Error Alert when Router Manufactory information cannot be retrieved.
4. Computer Monitoring Error Alert when a RWA Domain socket connection was aborted.
In addition, the alert description will display the failed component name, to improve trouble shooting experiences.
Test Steps:
If your computer had this issue, after applying UR3, check whether the alerts are disappeared.
If the alert still exist, please file a connect bug with logs and error descriptions.
Note, if the alert shows that the failed component is from 3-rd party Add-ins, please work with the 3-rd part for fixes.
Issue 5 – Launchpad could be configured to start minimized.
Test Steps:
On the Launchpad setting page , check “Always minimize the Launchpad at start”, and verify the Launchpad starts minimized.
Issue 6 – Incorrect warning alerts when UPNP on the router is not available
Test Steps:
You may receive following alert because your router’s UPNP is not available:
“The router is not configured correctly for Anywhere Access. You must configure the router to remotely access the network”. After UR3, Verify that this alert is not generated.
Issue 7- Launchpad does not link to the right RWA site if the RWA domain is set manually.
Configure your RWA domain manually, Verify the “Remote Web Access” link on your Launchpad can correctly pointing to the new RWA domain, instead of https://[servername]/remote
Issue 8 – Client Computer Connecting fails if the domain name is more than 15 characters
Test Steps:
Verify client connector can complete successfully if server’s domain name contains more than 15 characters. Note normally server’s domain name can be longer than 15 characters if it is migrated from Small Business Server 2011 Standard or earlier version.
