Additional/Download information can be obtained from following links:

http://www.beautyoftheweb.com/

https://partner.microsoft.com/40146845

Following are some steps to follow, all unsigned/third party themes to work properly.

1. In order to use custom themes and MSStyles on your computer you need to patch up your Uxtheme.dll file. Otherwise you can only use signed themes  that are created by Microsoft.

The appropriate Uxtheme.dll file

If you are running Service Pack 1 then get this file.

If you are running Service Pack 2 then get this file.

Unzip the file, and execute it. Now you have successfully patched your Uxtheme.dll file.

2. Now download any custom theme file and paste it in the following directory: C:\WINDOWS\Resources\Themes
3. Now through properties windows change your theme and enjoy a great look of your XP interface.

Microsoft has changed User Access control features a little bit in Windows 7, and now it is some what better than its previous version of windows vista. Windows 7 UAC has options to set the level of different alerts and notification, much similar of defining security in Internet Explorer.

Easiest method to disable or turn off alerts and notifications for UAC is to going to Control Panel in User Accounts and Family Safety -> User Accounts -> User Account Control Setting

Move the slider to "Never Notify" to turn off UAC alert and notifications, and then reboot the system.

In order to implement SSL successfully on your IIS, you need to get a Server Certificate. Server Certificates can be obtained from a trusted 3rd party CA such as VeriSign or Thawte.

Steps for Configuring SSL

To configure SSL on your IIS web server please follow the following steps:

• Open IIS Manager.
• In IIS Manager, expand your SERVERNAME, and then websites node.
• Right click on "Default Website"

On properties dialog box select the "Directory Security" tab.

This problem occurs because the Windows kernel power manager cannot obtain the memory resources that are required to prepare the computer to hibernate.

A Microsoft KB article is also available here.

Another good article that explains this scenario is also available here.

Switch to the Service Tab :

Check "Run WWW Service in IIS 5.0 Isolation Mode".
You will be asked for Restart of IIS. Click yes to restart IIS. If you are not asked just restart IIS.

By default, remote access is configured to timeout after 20 minutes, which is adequate for uploading/downloading about 15 MB even at slow DSL speeds but if you are frequently seeing this error message, you’ll need to adjust the timeout value to something higher. Setting the timeout to 30 up to 60 minutes is reasonable if circumstances require it. Setting a timeout interval that’s too long increase your security risk and can consume an unreasonable amount of resources on a server.

It is easy to change this timeout value:

1. Using mstsc.exe, start a Remote Desktop Connection session to your home server.
2. Use notepad.exe, to edit C:\Inetpub\remote\web.config.
3. Locate the following line:
   <sessionState mode="InProc" cookieless="false" timeout="20″/>
4. Replace "20″ (which represents 20 minutes) with a larger number to allow your uploads to finish.
   If you change the timeout value to more than 200 minutes, you must also change the executionTimeoutvalue. Search for the following line
   <httpRuntime maxRequestLength="2097151″ executionTimeout="12000″/>
   and increase the executionTimeout value (measured in seconds) to the same or greater value than the timeout value (measured in minutes).
5. Save your change, close the file, restart the IIS after this edit or better still, restart the server. Any edit to IIS or a related issue with the web configuration will need the web services to be restarted and log off from your Remote Desktop Connection session.
6. Use Remote Access to upload your file or files to ensure that the timeout parameter you chose is sufficient to complete the upload.

If you are using a computer without the connector (console) software on it (e.g. at work trying to access your home server) and you try to connect to the web interface of WHS then the following error appears:

Home PCs with the connector/console software installed have the server’s certificate automatically installed during connector setup. Computers without the software installed don’t have this certificate and so the error message.

To stop this error appearing; when accessing the web interface we need to export the certificate from a PC with the connector/console software on it and then import it into the PC without the software on it.

EXPORT

1. So on the PC with the connector/console software on it open your web browser and type in your https://xxxx.livenode.com address
2. To the right of the address bar click on the Padlock icon and then View certificates
3. Click the Certification Path tab
4. Double click the long GUID number (root certificate)
5. Click the Details tab
6. Click the Copy to File… button
7. Export the certificate somewhere safe using default option

IMPORT

1. Move the certificate to the machine without the connector/console software
2. Double click the the .cer file and select Install Certificate… on the General tab
3. Click Next on the wizard that opens and place a dot in Place all certificates in the following store
4. Click Browse and select Trusted Root Certification Authorities and click OK
5. ClickNext and thenFinish

That’s it. You can now access your web interface on your PC without the connector/console software via your livenode.com dynamic address, your server name e.g. SERVER or localhost without getting the dreaded error html page.

Home PCs with the connector/console software installed have the server’s certificate automatically installed during connector setup. Computers without the software installed don’t have this certificate and so the error message.

To stop this error appearing; when accessing the web interface we need to export the certificate from a PC with the connector/console software on it and then import it into the PC without the software on it.

EXPORT

1. So on the PC with the connector/console software on it open your web browser and type in your https://xxxx.livenode.com address
2. To the right of the address bar click on the Padlock icon and then View certificates
3. Click the Certification Path tab
4. Double click the long GUID number (root certificate)
5. Click the Details tab
6. Click the Copy to File… button
7. Export the certificate somewhere safe using default option

IMPORT

1. Move the certificate to the machine without the connector/console software
2. Double click the the .cer file and select Install Certificate… on the General tab
3. Click Next on the wizard that opens and place a dot in Place all certificates in the following store
4. Click Browse and select Trusted Root Certification Authorities and click OK
5. ClickNext and thenFinish

That’s it. You can now access your web interface on your PC without the connector/console software via your livenode.com dynamic address, your server name e.g. SERVER or localhost without getting the dreaded error html page.

The software running on the WHS to facilitate the Remote Desktop connection will only allow for up to two simultaneous sessions. Active and disconnected sessions are calculated in this connection limit as is the Administrator account also. The console session, however, does not count against the connection limit.

If a third attempt is made to login to the server, the dreaded "The terminal server has exceeded the maximum number of allowed connections" error will be shown to the user, and they will be unable to complete the login process. You can’t even connect to disconnect the old sessions BUT there is a way around this:

Simply click OK to the error message and wait for unto 30 seconds for the window to close then simply type the following in a Start – RUN or CMD Prompt on your client machine.

mstsc /v:00.00.00.00 /f -console
Replace 00.00.00.00 with your server’s IP Address or server name. e.g.SERVER

Type in your administrator password. This will then connect you to the Console Session on the server and allow you to remote control the machine again.

Once in Click Start, point to All Programs, point to Administrative Tools, and then click Terminal Services Manager.

In the left hand column you should see your server name. Click on it once. Note the Users Tab in the right pane.

You should see a list of users. You need to reset the two "Disconnected" users. You can do this by right clicking the disconnected user and selecting "Reset." You should now be able to connect with RDP again after Start – Log Off.

When logging in under this special Console session always kill the inactive sessions first, because if you get disconnected again you will have to connect your monitor, keyboard and mouse.

Only use this session to terminate the other two sessions and not for any other use.

In future when you are done with a Remote Desktop session on WHS, you should always use "Log Off" rather than disconnecting by closing the RD window with the X as this will disconnect from the session but leave it active.