Grass Valley Aurora Browse v.7.0 Installation - Manual (Page 132)

132 Aurora Browse Installation and Configuration Guide April 6, 2010
Chapter 5 Configuring the system
in the past.
3. The purge process polls at configured intervals. To expedite testing go to the
Windows services panel and restart the Asset Manager process. This will cause the
cycle to be reset and assets meeting expiration criteria will be processed
immediately.
4. Refresh the search results list by pressing the go button with no criteria specified.
5. Verify that asset components noted earlier no longer exist in the system. You will
have to look at the NAS for the specific paths to proxy asset components. The asset
on the high-res storage should also be removed.
Add Aurora Browse Clients
The Aurora Browse client application can be installed from the MediaFrame Server.
Before giving the users the path to the Aurora Browse installer, an administrator needs
to set up roles and licenses for the user.
If the Aurora Browse user has administrator privileges you can use setup.exe to install
the Aurora Browse application on the client PC. The executable file installs the
prerequisites and the Aurora Browse application.
If the Aurora Browse user does not have administrator privileges, an administrator
needs to install all the prerequisites for the user. The user then can install the Aurora
Browse application by using the AuroraBrowse.application installer.
You can find the installer on the MediaFrame server share:
\\MediaFrameServer\AuroraBrowse.
Do the following tasks to enable PCs to act as a Aurora Browse clients and run the
Aurora Browse application.
• “Connect server and NAS to customer LAN” on page 132
• “Configure Aurora Browse Licenses” on page 133
• “Managing Aurora Browse User sessions” on page 135
Connect server and NAS to customer LAN
The MediaFrame server and NAS machines must have network access to the external
LAN of the Aurora Browse client PCs. Work with the IT personnel at the customer
site to configure Domain, DNS suffix, or any other settings required by the site’s
LAN.
If you have MediaFrame client applications on a different Windows domain from the
MediaFrame server, you need to define a trust relationship (one way or two way). For
example, you could have your MediaFrame system on Windows domain A with a
trust in the B domain. Applications running on Windows domain B can then connect
to the MediaFrame server on Windows domain A.
Also, make sure that permissions are correct for access to the MediaFrame server
website, which serves the Aurora Browse application. The website uses Integrated
Windows Authentication.