Here's what I did. Install Downloaded version 3.1 of uTorrent from the official web page and copied the installer to my server then installed just the program, not the browser bar or any of the other guff. I also did not request starting the program when Windows starts. Configure I went into Preferences and set up my directory structure: New Downloads: D: ServerFolders Torrents Incomplete Completed Downloads: D: ServerFolders Torrents Complete Load Torrents from: D: ServerFolders Torrents Dropbox (with 'Delete loaded.torrents' checked) I also enabled and configured the scheduler - I like my evening and weekend bandwidth. The 'Remote' function is new to me, so I expanded the 'Advanced' setting and selected Web UI, then enabled the Web UI and confirmed the alternative listening port. Test I accessed the Web UI from the server locally, then from my desktop. Finally, I tried using my remote access address.
This didn't initially work because I had the wrong IP Address in my port forwarding, but a quick change fixed this. Schedule I started Task Scheduler, selected 'Create Task', called the new task 'TorrentService', selected 'Run whether user is logged on or not', and under 'Configure for' selected 'Windows 7, Windows Server 2008 R2'. Under the Triggers tab I clicked New and selected 'Begin the task At startup'. Under the Actions tab I clicked New and selected 'STart a program' and navigated to 'C: Program Files (x86) uTorrent ' to select uTorrent.exe I checked the Conditions tab. Under the Settings tab I unchecked 'Stop the task if it runs longer than: 3 days'. When I clicked OK the system asked me for my administration password, which I entered.
I confirmed the task 'TorrentService' was running, and rebooted my server to test it. Server Folder After confirming that on reboot I could access the Web UI both locally and using the Remote Web access I opened the Dashboard, went to Server Folders and Hard Drives, and added a new Server folder called 'Torrents' and set the Location to D: ServerFolders Torrents Dropped a torrent into the Dropbox and I can confirm this is working a treat.
By on July 02nd, 2007 I used to use my PC to download torrent files whilst sleeping, but since my PCs are now turned off overnight and Windows Home Server is on 24/7 it seemed logical to install uTorrent onto WHS. The other advantage of installing it on the server was that if more than one of us in the house was using uTorrent it would not cause a lot of traffic on the connection and most importantly by the time you finish this tutorial it will also run without a logged-in user. Create the New User First of all we need to. This is done for security reasons as we do not want to install uTorrent under the default Administrator account. Once this step is completed you may continue with the following. Install and Configure Connect via the Remote Desktop Connection as the user you have just created e.g.
“WHS” and your newly created password. Download the and install rktools.exe using the default options.
Next install the using the default options. If this is the first time you have installed uTorrent on your server then a dialogue will appear asking if you want to associate.torrent files with µTorrent. If a Windows Security Alert pops up asking if you want to Block or Unblock uTorrent Click Unblock and if the Speed Guide appears set your Connection Type and the Current Port that you would like to use. You will now need to forward the port you selected above into your router. Details of router setup screens can be found at (select your router and then uTorrent) In uTorrent select Options then Preferences. Make sure your General screen matches this one: Make sure that your download screen matches the one below.
You can change the location for your Put new downloads in but do NOT use a server share. It has to be under a drive letter on the WHS otherwise the Drive Extender Migrator Service will cause data corruption errors as it tries to move the file onto another drive while uTorrent is in the middle of writing to it, or just before uTorrent tries to open the file to write to it again. The Move completed downloads to can be changed to any server share location. The other screen should match this one.
Once again the Automatic load torrents in directory location can be changed to any server share location. This setup enables uTorrent to monitor this specific folder for.torrent files and start downloading them automatically. All you have to do to start a download is place the.torrent file in that folder and uTorrent will do its stuff. Using the Scheduler tab you can set your downloads to occur during “off-peak” periods by setting up a schedule if you so require.
As below, under Advanced Web UI Enable Web Interface and configure a Username and secure Password of your choice. Click the OK button and close uTorrent. Next and extract webui.zip from the rar archive.
Click Start then Run and type%AppData% uTorrent. Place the webui.zip into this opened folder (do NOT unzip it). Next download the uTorrent add-in for the Windows Home Server Console from. Do NOT run it but place it in your Add-Ins Shared Folder ( SERVER Software Add-Ins).
Log In to your WHS console and go to Settings, Add-ins the Available tab and then click Install under “Windows Home Server – uTorrent”. Once the console re-starts log back in to the console and go to Settings, uTorrent and for Server type in e.g.
YourIP is your server name or IP address and Port is the uTorrent Port that you set up earlier. Next insert your User Name and Password as set up earlier.
You can press Test Configuration to check all is OK. Red is not and green is fine. You may now OK out of the Settings and close the Console.
Create the User-Defined Service From your Windows Home Server click Start then Run and type cmd. In the window that opens type the following which is all on one line, including the quotation marks. 'c: Program Files Windows Resource Kits Tools instsrv.exe' uTorrent 'c: Program Files Windows Resource Kits Tools srvany.exe' NOTE: Cut and paste will not work, instead highlight and copy the above line and then right-click in the open CMD window and select paste.
Press Enter on your keyboard. Once the screen displays The service was successfully added! You may close the cmd box. We need to now create a.Reg file using notepad and paste in the 3 lines of code below. Windows Registry Editor Version 5.00 HKEYLOCALMACHINE SYSTEM CurrentControlSet Services uTorrent Parameters 'Application'='C: Program Files utorrent utorrent.exe' When saving make sure that Save as type is set to All Files. and save as service.reg. Double click on this saved file to import the settings into the registry on your server.
Now click the Start button and then select All Programs, Administrative Tools and then Services. Find uTorrent right-click and select Properties. Select the Log On tab. Click the This account button and enter WHS as the This account and enter the Password you setup earlier for this user account and confirm the Password. OK out and close the Services dialog. Click Start, Shut Down then Restart.
That’s it job completed. You can now connect to uTorrent either via the web interface using your browser using the format or via the WHS console (uTorrent heading). All you have to do to start a torrent download automatically is place the.torrent file in the SERVER Public Torrents folder and forget about it. Whose of you with Windows Vista may like to know that there is a sidebar gadget called that enables you to Start, pause or stop any torrent and allows you to view the stats and files for each torrent separately, all from the desktop sidebar within Vista. Share this WHS Article with Others.
I really like when you click a torrent file on a website and it starts to download in utorrent automatically. To get this on the WHS you could do this on the client: Type this in BAT script ( ex WHSTorrent.bat ): @copy%1 your server name torrent folder Associate the filetype.torrent with the script, in the example it is WHSTorrent.bat. If your browser is configured to open.torrent files automatically it should now be copied to your server and as utorrent is monitoring the folder it starts to download. I bet you could do this in a better way or maybe in a another scriptinglanguage. I’m just a novice at scripting.
I take that back. I ALMOST got it to work. If works if modify permissions but the minute you reboot, WHS reassigns all permissions for all folders to match the console preference. Basically this means that you cant transfer files from the “temporary downloads” folder to the share folder. If you create your own share folder independent of the console via Server 2003 network it should work or you have to burn an account in the WHS console so that every time the system reboots the permissions are set properly.
Kind of a pain in the buttI dont understand why WHS needs to reset permission every time it reboots, seems a little excessive to me. Couple of questions if you don’t mind -Can you setup RSS feeds that will auto download torrents (obviously uTorrent has this ability, can you make use of it after installing onto a WHS)? -The other thing, when you setup a filter for a RSS, you can select what folder the torrent gets downloaded to, can you set this to a share?
(and is the share corruption issue due to the data corruption issued that has been fixed with PP1-RC1? Will we ever be able to get around not being able to save torrents directly to a share?). Hi Phillp, Your quide was the clearest I have found, thanks a bunch. I only have a few questions which I am not sure how to handle. I completed your setup to the letter and used the exact suggestions you had in the examples except for the passwords and my server IP and port number. The only problem is that the consule interface does not work, and neither does the webGUI.
When I use either of them the show absolutely no downloads even though one is running in an RDC session. I used the following format in the uTorrent Add-In under settings. Which maps to my server internally and to the port. When I test I get a green bar so that should be fine, and when I RDC to the server as either the WHS or my user account the port comes back as open during the uTorrent installation. That leads to my next question.
Should I intall uTorrent under the WHS, Admin or my user account and which is actually running when I close the console or RDC? To be safe I installed the program under them all, but only tested it under my user account. In the WebUI in the Add-In do I use this IP or my phantom IP for the server from TZO? Is it because I need to do the RDC with the WHS user, or should I use the Administrator or my user account? I am a little lost here. Hi, just incase anyone is wondering ive found a way to get homeserver downloading torrents via rss feeds automatically.its not a perfect method but untill rss is implemented in webgui it will do.
Sorry, I had tried to reply a while back and it wouldn’t let me. The problem is with the logged in users at the server itself.
You can’t be logged into the server through terminal services as a new user when you add the torrents. It won’t let me put the link in my post “Log off (Don’t simply disconnect) all users on the server. Then go Start -= Run -= mstsc /console And then log in. When you remote desktop into a windows server version without /console it creates a NEW user session. You can see this when you open the Users tab on the Task Manager in the remote session. You’ll see your username twice.
This also means a second session of µtorrent was started which will fail to listen on the utorrent port (check the logger tab of µtorrent) because the original µtorrent session is listening there. Which means the webui still connects to the first µtorrent session while your remote desktop session is looking at the the second µtorrent session.”.
I followed the guide and uTorrent is installed on my windows home server and is working nicely. However I was wondering what the point of having the uTorrent installed into the console is. I have the application running as if it were in windows 7, and it is down in my taskbar. I can maximize it from there and mouse over it to see my dl/ul speeds etc. When I put torrents into my folder that I have utorrent watching it then sends the command to either my console utorrent or my full app utorrent.
For instance if I put 5 differerent torrents into the folder im having uTorrent monitor, the first 2 will be processed by the application and the final 3 will be processed/shown by the uTorrent instance in my home server console. Whats the point of having it in both places?