Install Locate32 (64bit) on a Windows Server
Locate32 finds files and directories based on file names.
Brought to you by:
jmhuttun
Menu
▾
▴
View and moderate all "Locate32 support forum" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have a requirement to be able to index and search for files by file name, that are stored in a Folder on a Windows Server shared drive, in a network environment. Could you please help me with the following questions:
1) Can Locate32 be installed on a Windows server? if so what types (2008, 2012 etc.)
2) Can additional files be added to this location and indexed after the initial install and update of database?
3) How do the users on the network search for and view files that are located on the network share, do they need to have a "Search" copy of Locate32 installed on their PC's?
I would appreciate any assistance you could provide ASAP.
1) It should work. I haven't tried it by myself, but I cannot say anything why it would not work on server. You should try
2) Yes, but the database needs to be updated to see the added files
3) For example, you can keep the database file in the server and access it from the client PCs.
Remember to make sure that ALL users map the network share to the same letter. I know that there is a way to do that on a sever but you could also write a simple cmd script to do the same thing. The problem is that Locate32 will look for the dbs in the same location [X:\share\allusr\locate32\dbs\databaseXX.dbs]
The thing that I would do is setup Locate32 into the public share [X:\progfile\Tools\locate32\locate32-3.1.11.7100\locate32.exe]. I also keep the dbs there in a dir 'dbs', then configure Locate32 to look for the dbs there [X:\progfile\Tools\locate\locate32-3.1.11.7100\dbs\X.dbs]. Then provide users a shortcut to run it from there. The shorcut MUST use the '-i' arg. I have NO idea how Locate32 will handle multi users and could run into issues. It would be easier this way but probably is not safer.