Hey Nik! That's great to hear :) If you are looking to take a peak under the hood, Health Monitor is a great start. It will give you an indication of what and how the files are being indexed. If you run the Interplay Diagnostics application, and set the logging levels to finest, you will also see all of the procedure calls made during the indexing

Hi Oren, The ummdworker.exe is a thread that runs when the Media Indexer is scanning storage. This is the main purpose of the Media Indexer. You will usually see as many instances as you have processors. Each thread runs per processor. Indexing storage is a resource heavy task. However, that being said, if it is degrading the performance of your network

Hi Nik, That could very well be the problem. MI Server requires Windows 2003 server. Interplay Engine requires Win2k3 as well. I understand you aren't looking for performance, however baseline functionality requires the correct operating system. Even for a demo system, you should be using the correct OS build. I have seen problems where installations

Hi Nik, That's troubling to hear! I was actually here late last evening rebuilding one of my test systems to 1.6, and I had no problem. If this was just one version you were having a problem with, I would be inclined to suggest that there is a problem with the installer itself. However that doesn't seem to be the case. What are the platform

Hi Nik, The splash screens for different versions of Interplay can vary a little bit. However, typically when you first launch the installer there is a choice between "Clients" and "Servers". The correct build of the MI for Servers is under the Server option. (It's the same menu tree that you would use to install the Interplay

Hey Rob! Quick Answers to your questions. There is currently no relationship between the UMID on the XDCAM disks and the SourceID generated within the metadata clips. The SourceIDs generated for XDCAM clips are the same as any other piece of media. As of this writing, we aren't looking at the UMID data. As far as the XDCAM-EX, that's a good

Hi Dan, I noticed this post is over a month old with no reply. Have you received any assistance on this issue? I have seen a small drizzle of issues with machine policies being applied to Vista in a Win2k3 domain. MS Technet has had a few threads about it, but the issue seems sporadic at best. That being said, your case appears to be isolated to the

Hi Sebastien, 1.) You are correct. When we assign the disk label at import, the sourceID is created for the media that is being imported. Using the same source ID maintains the affinity between high and low resolution media, allowing the MultiRez/Dynamic Relink workflow to function as designed. 2.) Unfortunately, creating a tape name also assigns a

Hi Nik, It appears you have installed the "client" version of Media Indexer. The client version of MI has these fields deliberately removed in later versions of the software to prevent editing systems from accidentally being joined as a member of the HAG. (Client systems should be connected to the HAG for indexing requests, but should not