SVC on Twitter    SVC on Facebook    SVC on LinkedIn

 

Coming Home to Windows Home Server Part 35

Jan 3, 2011 12:00 PM, By Eric B. Rux


   Follow us on Twitter    

Figure 2. Start by copying smaller folders first. Depending on the size of your Home Server, the transfer could take minutes, hours, or even days.

Figure 2. Start by copying smaller folders first. Depending on the size of your Home Server, the transfer could take minutes, hours, or even days.

Click Start > Run (XP), or Start > Search (Win7) and enter in the name of your old Home Server: "\\OldHomeServer" (the name of your server will obviously be different). Note that these slashes start from the bottom and go to the left. These are "back slashes" and are above the Enter key on most keyboards. The slash on the question mark key is different. That's a forward slash, and it will not work for this task.

If both servers are talking correctly, you should see the network shares of the old Home Server show up in an Explorer window. Move this window to the side of the left side of the screen for later use.

Now, click Start > Windows Explorer and locate the folders that will hold the data. In some cases, you may have to create the folders. However, be sure to use the Windows Home Server Console/Dashboard to accomplish this task! Do not use Windows Explorer to create the folders.

You are now ready to start copying data. I suggest starting small and working your way up. For example, I copied my family's folders under "Users" first. These folders had Word, Excel, and Power Point files, so they copied pretty quickly. I then tackled the Music folder, then the Photos folder, and finally the Videos. I also had some folders on my old Home Server that didn't exist on the new server, so I simply created those via the Console/Dashboard first, and then copied the data.

Select the data from the Explorer window on the left, and drag the folder(s) to the appropriate folders on the new Home Server as Figure 2 shows.

Depending on the size of your Home Server, the copy process could take a few minutes, a couple of hours, or even a day or two. It's not a hard process, just time-consuming.

Configure the server (Remote Access, etc.)

After the data has been copied to the new server, you can pat yourself on the back—you're on the home stretch.

Configuring the new server is as simple as comparing the old and the new Console/Dashboard to the new Console/Dashboard. For example, Remote Access will need to be set up. Click on Settings > Remote Access and follow the wizards. Be sure to turn off Remote Access on the old server, too.

Go through each tab and setting to ensure that the new server matches the old server.

Connect the clients to the new server

If you want to rename the new Home Server so that it has the same name as the old one, do this now. First shut off the old Home Server. Then rename the new Home Server just like you would Windows XP or Windows 7. Click Start > Right Click on My Computer and choose Properties. Click the Computer Name Tab > Change. Enter in the name that you want in the Computer name box.

The last step is to point each Windows XP and Windows 7 computer to the new server. I recommend uninstalling the Windows Home Server Connector on each computer via Add/Remove Programs (Programs in Win7), which can be found in the Control Panel. Then, reinstall the connector using new connector software (\\NewHomeServer\Software). This method ensures that you are using the correct connector software and is easier than fiddling with the Registry, etc.

So there you have it. That's how I spent the weekend with my 14-year-old (between being beaten soundly in ping pong). I hope you find this step-by-step useful. If you have questions, please do not hesitate to email me, and I will try to answer your questions.

Next month, I want to get back into Vail.

Oh, and happy New Year!

Eric B. Rux is a contributing editor for Windows IT Pro, and he writes a monthly column for Residential AV Presents Connected Home. Rux is the manager of Technical Support Services for Eastern Washington University and teaches the Microsoft Certified IT Professional (MCITP) certification program at a technical college.



Acceptable Use Policy
blog comments powered by Disqus

Browse Back Issues
BROWSE ISSUES
  November 2014 Sound & Video Contractor Cover October 2014 Sound & Video Contractor Cover September 2014 Sound & Video Contractor Cover August 2014 Sound & Video Contractor Cover July 2014 Sound & Video Contractor Cover June 2014 Sound & Video Contractor Cover  
November 2014 October 2014 September 2014 August 2014 July 2014 June 2014