Most of the Macs we have are running Mountain Lion, but we have a few newer machines running Mavericks. We have a mixed client environment, some PCs, and some Macs. I am curious if anyone else has experienced the issues that my company is experiencing. Would it have to be done on each Mac that accesses the Share? ![]() Would this work? If so, how would you setup a scheduled run? ![]() My thought was to schedule a Terminal file to execute each night with the mdutil code. So, how can we keep the index up-to-date? I have used the mdutil /Volumes/name -i on, and it seems to work.īut, if I understand it correctly, it is a one-time indexing - the index is NOT keep up-to-date with changes. To check the status of indexing on a connected network drive:Īnd, I found this on the Synology NAS forums: To disable the indexing of a connected network drive: To enable spotlight indexing on a network drive: It appears that there still is NOT a good, reliable solution. My thanks to everyone who has contributed to solving this problem here. Apparently Windows Cluster does not support Windows Search ExtremeZ-IP talk about providing access to NAS servers, this is actually exactly the same trick I described to use a Mac to 're-share' the NAS so while it is useful it is not a major feature of ExtremeZ-IP except they use a Windows server to do it. Windows Server + Windows Search + ExtremeZ-IP = searching for Windows AND Mac So Windows Server + Windows Search = searching for Windows only Note: ExtremeZ-IP apparently utilises Windows Search to do the indexing, Windows clients connecting to the same Windows Server via their normal SMB connection can therefore do searching pretty much like Spotlight. It turns out that ExtremeZ-IP does now have the ability to do Spotlight indexing! So a Windows server running ExtremeZ-IP would be a solution. Windows Servers themselves dropped support for AFP many years ago. This product runs on Windows servers and adds AppleShare i.e. I had been aware for many years of a package called ExtremeZ-IP from Group Logic, in fact many years ago I worked for the UK distributor for this product. There is another option which I was not aware of until I checked just now. This would be particularly pointless in this case. If you use a standard Windows server then it does not have built-in Spotight capabilities so again a workaround would be to use a Mac server to 're-share' it and do the indexing. Is there a way to make SL work with a windows server? Some people use iSCSI or NFS to connect to the QNAP (or similar NAS system), while the Mac clients would use AFP or SMB to connect to the Mac server as normal. This would add a network traffic overhead and this could be reduced by having two network connections on the Mac server, one to the LAN with the Mac clients, and a second dedicated on just to the QNAP. logins, and would also do the Spotlight indexing. The Mac server would then handle all the user-authentication i.e. Mac clients would then access it via the Mac server. See (I would not advise buying this particular solution now - it is possitively ancient and Spotlight would be the better choice.)Ī possible option would be to have a Mac server and have the Mac server mount the QNAP as a drive, and then have the Mac server re-share the QNAP. I used to work for a company and run the IT for them and we used a tool called 'Sonar' which did this. There are some third-party products you can buy which can do their own file content indexing and these provide their own search clients. You would still be able to do a basic filename search but not a file content search. Unfortunately Spotlight is proprietary to Apple so no-one else can add it to their product. Realistically this sort of system has to be done on the server itself, therefore it is the server supplier who has to provide this capability. Spotlight on a Mac server is also clever enough to not only be able to index files owned by everyone, but to also only return the search results that user is allowed to access, therefore you will not see in the list of results files private to other users. Therefore userA is not going to be able to access and index files restricted to userB, hence as described above the special Spotlight system account on a Mac server. With a server obviously the usual situation is that there are multiple different users and each user normally has different access permissions such that userA may not be able to access files owned by userB.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |