Have you ever wanted to be able to access all of your important files, music, photos, and more from all computers in your home from one central server? Today we’ll take a look at Windows Home Server and show you how to install and configure it with other machines on your network.

Windows Home Server (WHS) is meant for your family needs or for use in a home or small office. It allows you to centralize your important documents and digital media files on one box and provides easy access from other machines on your network. It has the ability to backup 10 computers and restore them if needed. It acts as a media server, backup solution, data recovery, document management, and allows you to access what you need from anywhere there is a web connection. Using a personalized website address, it lets you securely download and upload your data files.??????

You can buy server machines that already have WHS installed on it, or you can create your own (which is a lot more geeky and fun). The cool thing is that you can repurpose an older desktop to run Windows Home Server. A machine with a 1GHz Pentium III, 512MB of RAM, and an 80GB Hard Drive will work as the minimum requirements, but as you know minimum and recommended requirements are completely different things. You can check out the minimum and recommended system requirements from Microsoft’s WHS PDF guide (link below).

Start the Installation

Installation is very straight forward and easy to do. Boot from the WHS installation disc and kick off the install wizard.

?

Select your region and keyboard settings…

Now choose the drive(s) that are in the machine. In this case there is only one, but if you have multiple drives, make sure they’re listed. If you want to add additional drives at a later time, it’s a simple process that we will cover in a future post.

Select New Installation…

Accept the Microsoft EULA…

Enter in your Windows Home Server Product Key…

Next it’s time to give your new Home Sever a name…

Again verify the hard drives that will be formatted…

It’s going to ask you again to make sure all the data will be deleted from the drives…

Finally it’s time to kick off the installation process. The amount of time it takes to complete will vary between systems. Count on the entire process taking a minimum of one hour and perhaps longer.

There is nothing needed from you while the install takes place. The system will reboot several times and you’ll see different screens displayed while the process completes…

Finish Installation

When you get to the following Welcome screen, you’re almost done.

Type in a password and password hint for the server.

Decide if you want to set up automatic updates or not…

Choose if you want to join the Customer Experience Improvement Program or not…

Choose if you want to turn on automatic Windows Error Reporting…

That’s all there is to it.? You don’t need to leave a keyboard, monitor, or mouse to the server. The only thing you needs to be connected is an Ethernet Cable running to your router (Wireless isn’t supported). You can administer the machine from any computer on your network after installing Windows Home Server Connector on the other machines.

Windows Home Server Console

To connect the computers on your network to the server, you’ll need to install the Windows Home Server Connector which is available as a separate download. You’ll need to install the WHS Connector to every computer on your network that you want to connect with the server. It connects your computers to WHS, allows for automatic nightly backups, monitors computer network health, and enables you to remotely administer the server from your computer.

If you don’t want to waste a CD to install it, you can use a free program like Virtual CloneDrive and mount the ISO and transfer the files to a a flash drive.

?

Before installing the connector on XP you’ll be required to install Microsoft .NET Framework 2.0 and it’ll guide you through the process if needed.

When you start WHS Connector Setup it will look for the Home Server…

Then it’s just a matter of working through the rest of the wizard.

During the process you’ll need to enter in the password you created for the server.

Decide if you want your computer to wake up if it’s in sleep mode to back it up…

When configuration is complete, we’re shown our settings — wake up the computer for backup between 12:00 and 6:00 AM. Also in this instance, we’re getting a message that one of the drives in the PC won’t be backed up. This is because it’s formatted as a FAT 32 volume and it will only backup drives formatted as NTFS.

The Home Server Console icon sits in the system tray and you can control some of it’s settings by right-clicking the icon.

It will display your network’s health and show security warnings (this feature can be easily turned off). In this instance we can see one of the machines on the network has its firewall turned off.

When you open up WHS Console, you’re prompted to log into the server. There are a few other features here to like having the password remembered, password hint, and resetting the console.

Once you’re signed in, you can configure and administer the server and its different functions. We’ll be taking a closer look at the WHS Console in future articles.

If you need to make more detailed changes to your server, another good option is to use Remote Desktop, which is easier than hooking up a monitor, keyboard, and mouse to it.

Download Updates

Now that installation is complete we need to add all the of the latest updates from Microsoft. Click on Start All Programs then Windows Updates. This will provide you with the latest server security updates and Power Pack updates as well. Power Packs are updates that add new features and provide fixes to known issues for Windows Home Server.

?

Conclusion

This guide should get you started using your new Home Server. It comes in handy in a lot of cool ways if you want to centralize your digital entertainment and access it from any machine running XP or above. Or if you have a home or small office and want to be able to access your work from anywhere there is a web connection. There are several good reasons to have your own server at home, if you’re a power user. Over the next year we will be bringing you more detailed tutorials on how to set up and use your Home Server. If you happen to have an extra desktop you’re not using and can dedicate as a server, they offer a free 30 Day trial so you can try it out for yourself. If you like it, you can purchase a full license and I have seen it around the web for around $99 or a little cheaper depending on where you look.?

Download Windows Home Server 30 Day Trial

Download Windows Home Server Connector Software CD

Windows Home Server Getting Started Guide (PDF)

Similar Articles	Productive Geek Tips
GMedia Blog: Setting Up a Windows Home Server Installing Windows Home Server Share Ubuntu Home Directories using Samba Setup OpenSSH Server on Ubuntu Linux Another Blog You Should Subscribe To	Monochrome Grey Desktop Get Better Functionality Stacks with no Extra Software How to Find Sleep When It Escapes You The Anatomy of Salary Negotiations Arguing Productively Leads to a Lasting Relationship Tips and Advice on Saving Money Today
Latest Software Reviews	Tinyhacker Random Tips
Revo Uninstaller Pro Registry Mechanic 9 for Windows PC Tools Internet Security Suite 2010 PCmover Professional	LOVE Wallpaper from Love Park, Philadelphia Run Windows 7 on a Mac using Boot Camp Tiny Sticky Note Can Be Run From Your Tray Romantic Valentine’s Day Win7 Theme Compare Google Search Suggestions View any string of dates in Outlook ‘07

• 0 Comments

This is only a quick tutorial, there are literally hundreds of little tricks you can do with a DNS, but this will get your basics up and running. I’m assuming you want to setup a windows DNS server, but the principals will work for most servers.

You will need..

• 1) A domain name over which you have full control
• 2) DNS server software(Windows server always comes with one of these)
• 3) At least one fixed IP address, allthough two is highly desirable
• 4) An idea of what services you want on your server

The first thing you need to do is create your new domain entry. In windows this is called a “Zone” and you will have one for every domain name you have. Add your main domain in the forward lookup zone as a Primary zone, which will be in the format “Domainname.com”, or .co.uk, or whatever, you shouldn’t need any more details for this bit. Do *not* allow dynamic updates unless this is a local network DNS. Once it is created you will have 2 entry’s under your new domain, “SOA”(Or Start of Authority) and “NS”(Or Name server). If you want a 100% compliant DNS then you should now follow the same process but adding a domain as a reverse lookup zone. Any changes you make to the forward lookup should have the “Update Reverse Lookup” option ticked if its available, if not you must update the reverse zone manually(This is very important).

Now edit the “NS” entry in your forward zone to “NS0.DomainName.Com”, and set it to the relevant IP address. Add another (NS) record and set it to “NS1.DomainName.Com”. If using 2 IP address, try to make NS0 the first IP. Now you need to configure the SOA entry in the forward lookup zone. The serial number should be changed to a date followed by a number in this format “YYYYMMDDnn”, this is not required, but is advised by RIPE. The primary server will be the “NS0.domainname.com” entry you just made and the responsible person should be left for now. The refresh interval should be set somewhere between 1200 to 43200 seconds, the retry should be between 120-7200 seconds and the expires after should be around 2-4 weeks(I’ll let you work out the seconds for that). The minimum TTL is quite important, and depending on what you are going to do with the domain, you might need to tweak this a bit. Typically a value between 1-3 hours should be used. Now go to your “Name server” settings in your SOA record(In windows this is a tab in the same window) remove the defaults, and add your two Name servers that you just setup. We will come back to the SOA record later, but for now we need to do some more stuff.

If you want a website, then your going to want the WWW. setting up. We will set it up as an “A” record, which means it is a separate top level record and will be populated separately from other entries. So add an “A” to your forward lookup zone and put the entry as “WWW”, and set the IP address to wherever you want the website to be. This will be where the domain always goes, and it could be anywhere. Just make sure there is a web server waiting there for it. If you want FTP, then setup the same thing but with “FTP” in the entry. You will now also have to setup “A” records for the NS0 and NS1 name servers that you added previously, just make them the same as WWW and FTP, but make sure the IP addresses match the ones used for setting up the “NS” records. Also add a blank “A” record, this will make sure that “domainname.com” works as well as “www.domainname.com”.

Now you should decide whether or not you want to have mail on this domain. It is Hegel advisable that you set one up, even if it just to catch domain mail about abuse or potential problems that might occur. You can find plenty of high quality free mail servers out there, but I would recommend “Mail Enable”, its free and provides everything you would want, but if you want webmail you do have to pay something extra for it. We will now configure the MX records. Add an “A” name for your mail server, you can add 2 if you want, but for simplicity I would advise staying with 1. We will call ours “Mail.domainname.com”, and point it to one of our IP addresses. Now add an “MX” record in the Forward Lookup zone, giving it the full “A” record you just entered “Mail.domainname.com”, and do not setup a host or child domain, just leave it blank.

This next step isn’t needed, but is again highly recommended.

Now to finish the SOA you need to add two more records. A “RP” entry, which is a Responsible Person, and they will be the contact point for domain complaints and a “MB” entry, which is a mailbox entry. The “MB” should just be pointed to the mail server domain name “Mail.domainname.com”, and the “RP” should have the host or domain set to the name of your mail box. So for this server it will be “Tony.Domainname.com”, and the mailbox will be set to the “MB” record you just made. Don’t worry about the RP address having no “@” in it, this is the expected format for an “RP” entry. You will now have to go back into the SOA and change the responsible person to the new “RP” record you just made.

And thats it, your done! You can add as many “A” records as you like to point to other web servers, or a multitude of FTP sites. And you can add “CNAME” records to basically point to another name, usually an “A” record, like an alias.

Now before you switch your domain on, you need to check that the server is performing properly. So go to www.dnsreport.com, and run the report on your domain “domainname.com”, and it will give you a very detailed report of any problems, and even a short description of how to fix the problems. If all is OK, then you are ready to go live. If your domain name is new, or not currently hosted anywhere then the first thing you should do is re-point the domain at your new server. You will typically do this with the provider who owns the domain, and it will be different with all hosts. But the basic settings are the same. You will be asked for at least 2 name servers and ip addresses to go with them. Just put in “NS0.domainname.com” and “NS1.domainname.com” and put in the correct IP addresses. Make sure you do not mess this up, as changes to your main NS servers could potentially take several days to straighten themselves out. Update these settings, and then sit back and wait. You can do a whois on the main DNS server of your domain provider to check if the settings have worked, but again this doesn’t always work. For the big 3 domains(.com .net .org) you can do a whois on the network associates site to see the changes instantly. You can also track the progress of the domain changes by doing an NSLookup in dos, like this…

c:\nslookup ns0.domainname.com NS0.yourprovidersdns.com

That will give you the entries your domain provider has

c:\nslookup www.domainname.com ns0.domainname.com

And this will tell you if the changes for your domain have gone through to your ISPs DNS yet. It should give you back the IP address of your new DNS server.

You should always make sure your server is backed up, and that you refresh or update the DNS when you are making changes.

• 0 Comments

There is no point in building a website unless there are visitors coming in. A major source of traffic for most sites on the Internet is search engines like Google, Yahoo!, MSN, Altavista and so on. Hence, by designing a search engine friendly site, you will be able to rank easily in search engines and obtain more visitors.

Major search engines use programs called crawlers or robots to index websites to list on their search result pages. They follow links to a page, reads the content of the page and record it in their own database, pulling up the listing as people search for it.

If you want to make your site indexed easily, you should avoid using frames on your website. Frames will only confuse search engine robots and they might even abandon your site because of that. Moreover, frames make it difficult for users to bookmark a specific page on your site without using long, complicated scripts.

Do not present important information in Flash movies or in images. Search engine robots can only read text on your source code so if you present important words in Flash movies and images rather than textual form, your search engine ranking will be affected dramatically.

Use meta tags accordingly on each and every page of your site so that search engine robots know at first glance what that particular page is about and whether or not to index it. By using meta tags, you are making the search engine robot’s job easier so they will crawl and index your site more frequently.

Stop using wrong HTML tags like <font> to style your page. Use CSS (Cascading Style Sheets) instead because they are more effective and efficient. By using CSS, you can eliminate redundant HTML tags and make your pages much lighter and faster to load.

• 0 Comments