For this solution we will need to enable the “Windows Search Service” on the file server. The server will then generate an Index that is stored within our network shared location so that the clients can use this shared Index to find files. The following instructions are based on Windows Server 2008 R2 but the workflow is similar for each of the Windows Server operating systems.<\/P><\/p>\n
In order to install the “Windows Search Service”<\/SPAN>, the “File Services” role must be enabled on the server.It would be a safe bet that if you are already sharing files from the server that the File Services role is already enabled.However, just to double-check, on the server, select Start -> Administrative Tools -> Server Manager -> Roles.If “the File Services” role is not shown simply select “Add Roles” and click through the wizard prompts accepting the defaults to install the File Services role.<\/P><\/p>\n Once the File Services role is enabled, select Start -> Administrative Tools -> Server Manager -> Roles -> File Services -> Add Role Services.<\/P><\/p>\n If not all ready installed, we will need to install the Microsoft Visual C++runtime libraries. Use the following link to download and install the Microsoft Visual C++ 2012 Redistributable Package:<\/P> We are now ready to install the Insight provided IFilter to index the content of the Solid Edge draft files. To begin, you will need access to the Solid Edge Insight Server installation media. We are not going to install Insight or require SharePoint. We simply need access to the Insight Server media so that we can extract the Solid Edge IFilter.<\/P><\/p>\n If you do not have the install DVD available, download the latest version of Solid Edge Insight Server from the GTAC Download Server<\/A>.<\/P><\/p>\n Again using an archive utility, open this “Search~1.cab” file. Manually extract to disk the two files “F2066_SEFilter.dll” and “sefilterreg.exe”.<\/P><\/p>\n In Windows Explorer create the folder structure “C:Program FilesInsight ServerProgram”. We could theoretically name our folders something different but as the IFilter technology is provided by Insight, and for the sake of simplicity, we will keep the same folder structure as used by the Insight product.<\/P><\/p>\n Copy the “SEFilter.dll” and “sefilterreg.exe” manually extracted files from the Insight installation media into the “C:Program FilesInsight ServerProgram” folder.<\/P><\/p>\n Using your preferred text editing tool, edit and save “SEFilter.reg” with the following text:<\/P><\/p>\n A copy of this “SEFilter.reg” file has been attached at the bottom of this blog post for your convenience.<\/P> Run the command sefilterreg.exe TRUE “C:Program FilesInsight ServerProgramSEFilter.dll”.<\/P><\/p>\n The Solid Edge IFilter has now been installed. We can verify the IFilter is successfully installed by checking the Indexing Options used for the .dft file type. In the Start menu search on “index” and select “Control Panel” -> “Indexing Options”.<\/P><\/p>\n In Indexing Options select Advanced -> File Types -> dft. Notice that the Filter Description now states “Solid Edge Draft Document” and that the file type is set to “Index Properties and File Contents”.<\/P><\/p>\n Installation of the Windows Search Server with the Solid Edge IFilter is now complete. We must now configure our workstation to access the indexed Solid Edge files on the server. The workstation is now configured to use the indexing from the Windows Search Server.<\/P><\/p>\n Once indexing of the draft file content is complete on the server, you should now be able to search for text content within the Solid Edge draft files stored on the network. In the picture below notice the UNC path in the filename.<\/P><\/p>\n Note that depending on server activity and number of files, it may take several hours for all of your Solid Edge files to be fully indexed.<\/P> Two free IFIlters that I would think are a must have for any organization are the Microsoft Office 2010 Filter Pack<\/A> and Adobe PDF iFilter<\/A> so that the content of Office and PDF files stored on the network can be indexed and searched from the client workstation.<\/P><\/p>\n<\/P><\/p>\n
<\/P>
\n
Select “Windows Search Service” and press “Next >”.<\/P><\/p>\n<\/P>
\n
Do *not* select any volumes to index and press “Next >”.<\/P><\/p>\n<\/P>
\n
Select Install and complete the installation.<\/P><\/p>\n<\/P>
\n
Now that Windows Search Server is installed, we must add the location of our Solid Edge files to be included in the index. In the Start menu search on “index” and select “Control Panel” -> “Indexing Options”.<\/P><\/p>\n<\/P>
\n
In the Indexing Options select Modify and add the location of the Solid Edge files to the indexer.<\/P><\/p>\n<\/P>
\n
However, as Solid Edge has most probably not been installed on the server, the server is not configured to recognize the Solid Edge file formats including the .dft extension. We must now add the dft extension to the list of file types to be indexed. In Indexing Options select Advanced -> File Types and add “dft” to the extensions.<\/P><\/p>\n<\/P>
\n
We can confirm that Windows Search is now indexing Solid Edge drafts by looking at the Indexing Options for .dft files. However, note that out-of-the-box the Solid Edge files are being indexed using the default Windows file properties IFilter and is *not* indexing the content of the draft files.<\/P><\/p>\n<\/P><\/p>\n
\n
http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=30679<\/A><\/P><\/p>\n<\/P>
\n
Once you have downloaded the Insight Server install executable, using an archive utility such as 7-Zip<\/A>, manually extract to a temporary folder the downloaded .exe file.<\/P><\/p>\n<\/P>
\n
In Windows Explorer browse into the “Insight Server 2010” folder and locate the “Search~1.cab” file.<\/P><\/p>\n<\/P><\/p>\n
<\/P>
\n
Rename the extracted “F2066_SEFilter.dll” file to “SEFilter.dll”.<\/P><\/p>\n<\/P><\/p>\n
<\/P><\/p>\n
<\/P>
\n
In the “C:Program FilesInsight ServerProgram” folder create a text file “SEFilter.reg”.<\/P><\/p>\n<\/P><\/p>\n
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT.dft]
@=”SolidEdge.DraftDocument”
[HKEY_CLASSES_ROOT.dftPersistentHandler]
@=”{EE2DF029-5B0D-4427-8DCE-550F53D59A5A}”
[HKEY_CLASSES_ROOTSolidEdge.DraftDocument]
@=”Solid Edge Draft Document”
[HKEY_CLASSES_ROOTSolidEdge.DraftDocumentCLSID]
@=”{016B11FB-CDC0-11ce-A035-08003601E53B}”
[HKEY_CLASSES_ROOTCLSID{016B11FB-CDC0-11CE-a035-08003601E53B}]
@=”Solid Edge Draft Document”
[HKEY_CLASSES_ROOTCLSID{016B11FB-CDC0-11CE-a035-08003601E53B}PersistentHandler]
@=”{EE2DF029-5B0D-4427-8DCE-550F53D59A5A}”
[HKEY_CLASSES_ROOTCLSID{61CCDBA2-BDC8-4737-963F-D4356E7C1C8D}]
@=”Solid Edge Draft Document”
[HKEY_CLASSES_ROOTCLSID{61CCDBA2-BDC8-4737-963F-D4356E7C1C8D}InprocServer32]
@=”C:\\Program Files\\Insight Server\\Program\\SEFilter.dll”
[HKEY_CLASSES_ROOTCLSID{61CCDBA2-BDC8-4737-963F-D4356E7C1C8D}InprocServer32]
“ThreadingModel”=”Apartment”
[HKEY_CLASSES_ROOTCLSID{EE2DF029-5B0D-4427-8DCE-550F53D59A5A}]
@=”Solid Edge Draft Document Persistent Handler”
[HKEY_CLASSES_ROOTCLSID{EE2DF029-5B0D-4427-8DCE-550F53D59A5A}PersistentAddinsRegistered]
@=”{89BCB740-6119-101A-BCB7-00DD010655AF}”
[HKEY_CLASSES_ROOTCLSID{EE2DF029-5B0D-4427-8DCE-550F53D59A5A}PersistentAddinsRegistered{89BCB740-6119-101A-BCB7-00DD010655AF}]
@=”{61CCDBA2-BDC8-4737-963F-D4356E7C1C8D}”<\/PRE><\/p>\n
\n
Open a DOS command window and change directory to the “C:Program FilesInsight ServerProgram” folder.<\/P><\/p>\n<\/P><\/p>\n
<\/P>
\n
Double-click on the “SEFilter.reg” file to install the registry entries.<\/P><\/p>\n<\/P><\/p>\n
<\/P><\/p>\n
<\/P><\/p>\n
On each of the client workstations we must edit our Library properties to add the network folder to the Windows Libraries. In Windows Explorer expand Libraries and either create a new library or modify the properties of an existing library.<\/P><\/p>\n<\/P>
\n
Select “Include a folder\u2026”, browse to your network folder containing your Solid Edge files, and select “Include folder”.<\/P><\/p>\n<\/P><\/p>\n
<\/P><\/p>\n
\n
Once you have your server’s Search Service implemented and are indexing your Solid Edge draft files, consider further improving your network file searching capabilities by adding additional third party free<\/A> and commercially<\/A> available IFilters to your server’s search indexing.<\/P><\/p>\n