Grass Valley Aurora Browse v.6.5 Installation - Manual (Page 47)

November 1, 2008 Aurora Browse Installation and Configuration Guide 47
About the administrator account
About the administrator account
You must have the same local username and password, with administrative privileges,
across all the machines in your Aurora Browse system. This account is critical for
most Aurora Browse proxy access, as explained in this section.
The same local administrator account is required on the following machines:
• Proxy NAS machines
• Aurora Proxy Encoder
• SmartBin encoder
• MDI server
• MediaFrame server
• Aurora DSM
• K2 systems
• M-Series iVDR
• Profile XP
All NAS machines require that an administrator account has permission to the folder
on the NAS that the encoders write to, and that the MediaFrame server reads from.
The basic principle is that any service that requires write access to the Proxy NAS
must run as the same administrator account. This is a local machine account (NOT a
domain account). This includes all encoders, the MediaFrame server, the News MDI,
the Proxy MDI (which deletes files off of the Proxy NAS) and the Profile MDI.
On K2 systems and M-Series iVDRs, security is invoked, which requires
administrator privilege. This privilege comes from the administrator account,
(identical username and password) on the local machine, which is identical with the
administrator account on the other devices.
From a Windows networking perspective, when a user account is defined on a local
computer rather than a Domain Controller, the account is a “local” account, whose
complete name is \, rather than
\. For example, with an encoder named Encoder1, a
MediaFrame server named Server1, and a NAS named NAS1, there are three separate
local accounts: Encoder1\admin, Server1\admin, and NAS1\admin.
The Windows network automatically maps a local account from one computer onto
the local account of another computer—as long as both the account name and the
password are identical. To enable this mapping to occur, the Windows Domain
Controller “synchronizes” the local accounts on computers at the time they join the
Domain. Therefore, if the administrator account is added to the NAS machine after
the Windows NAS has joined the Windows Domain, this synchronization does not
occur. If the proper sequence is not followed and the problem does occur, the
workaround is to remove the NAS from the Windows Domain and then re-add it
immediately thereafter.