Ok, so you got Windows server 2008 R2 having some shares you want to add to your Windows 7 library. Here’s the guide to make it to work (without having the files available offline) [from here]:
On Windows 2008 R2 server, do NOT install the indexing service! It’s a Server 2003 version that is not recognized by Windows 7 clients. Instead, install the ”Windows Search Service” – you can only pick one or the other so make sure you select Windows Search Service – it’s one of the roles under File Services.
The install wizard should ask you which folders/drives you want to index – choose any data drive (recommend NOT selecting the system/boot drives) that contains files you want to include in your Windows 7 library on the workstations. If you missed this during the install, you can go back to CONTROL PANEL and type ”indexing” into the search box to find the indexing options and customize it there (exactly the same way you do with Windows 7).
As soon as the drives have been added, you can now include any locations on those drives in your Windows 7 workstation libraries (even before the server finishes indexing). You will no longer get any warnings that ”some locations are not indexed”…everything works as it should!
Make sure the SYSTEM account has full access to the folder you are trying to index
I noticed that the above steps might not be enough. If you are trying to add the network share to library using the computers smb name (e.g. someserver) it should work. Also the ip address should work all right according to my tests (I’ve read somewhere that it might cause problems…). However, In my case I have a dynamic dns service (dyndns.com) set up. Using that domain name (e.g. someserver.ath.cx) does not work when adding share to Windows 7 library. So always use the ip address or smb-name (not the domain name) when adding share to Windows 7 library.
Note that you can find some symbolic link trickery to fool windows to add unindexed folders to library. However, that just adds the folders to the library, but the searches will be slow!
Some time has gone since my previous tips for making video thumbnails work in Windows 7. For some reason these tricks doesn’t seem to work in Windows 7 (not at least in 64 bit). Here’s a guide to fix the thumbnails in Windows 7 (probably works in older versions too!)
Fortunately, there is an easy way to make mkv files show the thumbnails, just install the latest MKV on Windows 7 from divx. Now you are probably thinking that you don’t want to install divx — it’s so 90’s. Fortunately, you don’t have to install anything extra just install the parts you need (meaning that you don’t need any codecs).
The following picture shows the necessary parts you need to have mkv video thumbnails in 64bit Windows 7. This probably works for 32bit too.
Just install these components in DivX
You will also have to install 64 bit video codecs. I prefer ffdshow since it basically contains video codecs for every possible video, in addition it supports hardware accerelated video decoding. You can install ffdshow from here. Just select the 64 bit version under SVN Builds. Notice that the 64 bit ffdshow codecs are still experimental so they might prove to be unstable…I think choosing the ”H.264 Decoder” and DivX codec in DivX installer might work just as well for some people. To me it really doesn’t matter so much since the 64 bit codecs are used only for thumbnail generation. The video player I use (media player classic home cinema, available here) is 32bit and therefore it uses 32 bit codecs. Actually, the media player home cinema is bundled with internal h.264 decoder.
EDIT:Installing the direct show filters is no longer possible. One must install DivX Plus. Only the codec pack is mandatory for thumbnails.
If you install Dragon Age Origins to another drive, let’s say D:, it will cause Windows Backup tool to make image backup of D: drive too.
This is because Dragon Age contains ”Updater service” which Windows considers part of the ”core system” and that’s why it creates image backup of D: too. If you don’t want to backup D: drive one option is to move the update service to c: drive and update service’s registry entry accordingly. Please see above link for more details.
See this post. This can be used to replace notepad with other program, for example.
Under the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
create a subkey with the name of the exe you want replaced.
Add a string value called Debugger.
Modify Debugger with the command you want run.
When any user tries to run any executable with the name of the subkey, Windows executes the Debugger command with path\name of the original exe and all command line parameters appended. (Did that make sense?)
Wonder why your seed get queued even if you want them to be seeded?
The problem is vuze’s quite poor default values. To understand the problem let me explain a bit more how vuze determines whether to queue an item.
Vuze determines the queue status on few things (in this order):
First Priority rules (Options/Queue/Seeding/First Priority). Items matching the first priority rules go to the top of the queue. Please note that first priority have ignore rules which override the ”matching rules”
Ignore rules (Options/Queue/Seeding/Ignore rules). Items matching the ignore rules go to the bottom of the seeding queue and probably they will never seed.
Most forum posts mention ”correct” rules for ignore rules but fail to mention that First priority rules have their own ignore rules too.
I have attached my working settings but feel free to tune them for your connection and needs.