About Omneon MediaGrid - Harmonic Inc

About Omneon MediaGrid - Harmonic Inc About Omneon MediaGrid - Harmonic Inc

harmonicinc.com
from harmonicinc.com More from this publisher
29.11.2012 Views

System Configuration 3. Select a login protocol from the protocol buttons. Select SSH for the login session. 4. Click the Open button to connect to the ContentDirector. Editing the Samba Configuration File NOTE: The following procedure is only required if you are joining a Windows NT domain. To edit the file: 1. From your SSH terminal, open the following file using vi text editor: sudo vi /etc/samba/smb.conf 2. Make the following changes: • workgroup = Windows NT domain name • password server = domain controller name • security = DOMAIN 3. Enter the following to join the Windows domain: sudo net rpc join --workgroup=Windows NT domain name --server=domain controller name --user=_adminuser_ You should see the following message: Joined domain name of domain. 4. Type the following two lines to complete the installation: sudo chkconfig winbind on sudo service winbind start Starting the Winbind Service Complete the following at the command prompt to activate the winbind service, which enables ContentDirector and Active Directory communication. To start winbind: 1. Type the following to start the service: sudo service winbind start 2. Then type the following so that the service starts each time the ContentDirectors start up: sudo chkconfig winbind on NOTE: SystemManager provides winbind status (running or not) on the ContentDirector Properties page. See the Omneon SystemManager User Guide for details. Verifying Communication with the Domain Controller To verify communication: 100 Installation and Configuration Guide

System Configuration 1. After confirming that the winbind service is running, verify the connection and communication with the Domain Controller by typing the following: sudo wbinfo –u | less A list of users in the domain displays after a few seconds, for example: [ovnuser@cld-1 ~]$ sudo wbinfo -u | less SNV-ENG\eng-sysadmin SNV-ENG\guest SNV-ENG\support_388945a0 SNV-ENG\snv-eng-dc1$ SNV-ENG\krbtgt SNV-ENG\admin SNV-ENG\snv-eng-dc2$ SNV-ENG\qa1 SNV-ENG\qa2 SNV-ENG\qa3 SNV-ENG\qa4 2. Once this is verified, restart the omcld service so it can pick up the new domain configuration by typing the following: sudo service omcld restart About Joining a ContentBridge 2010B/2010C to an Active Directory Domain There are different methods for joining a ContentBridge 1000B or ContentBridge 2010B/2010C to an Active Directory Domain. One method involves the configuration assistant and the other involves manually modifying configuration files. Choose from the following: • Joining a ContentBridge 2010B/2010C to an Active Directory Domain Using the Configuration Assistant • Joining a ContentBridge 2010B/2010C to an Active Directory Domain Using the Manual Method • Joining a ContentBridge 1000B to an Active Directory Domain Using the Manual Method Joining a ContentBridge 2010B/2010C to an Active Directory Domain Using the Configuration Assistant A ContentBridge 2010B/2010C can be added to an Active Directory domain for Windows 2003 or Windows 2008. To add a single ContentBridge 2010B/2010C to an Active Directory domain, run the configuration assistant in manual mode, which allows you to configure the ContentBridge without affecting other devices, and enter the necessary Active Directory domain information. Omneon, Now Part of Harmonic 101

System Configuration<br />

3. Select a login protocol from the protocol buttons. Select SSH for the login session.<br />

4. Click the Open button to connect to the ContentDirector.<br />

Editing the Samba Configuration File<br />

NOTE: The following procedure is only required if you are joining a Windows NT domain.<br />

To edit the file:<br />

1. From your SSH terminal, open the following file using vi text editor:<br />

sudo vi /etc/samba/smb.conf<br />

2. Make the following changes:<br />

• workgroup = Windows NT domain name<br />

• password server = domain controller name<br />

• security = DOMAIN<br />

3. Enter the following to join the Windows domain:<br />

sudo net rpc join --workgroup=Windows NT domain name --server=domain controller<br />

name --user=_adminuser_<br />

You should see the following message:<br />

Joined domain name of domain.<br />

4. Type the following two lines to complete the installation:<br />

sudo chkconfig winbind on<br />

sudo service winbind start<br />

Starting the Winbind Service<br />

Complete the following at the command prompt to activate the winbind service, which enables<br />

ContentDirector and Active Directory communication.<br />

To start winbind:<br />

1. Type the following to start the service:<br />

sudo service winbind start<br />

2. Then type the following so that the service starts each time the ContentDirectors start up:<br />

sudo chkconfig winbind on<br />

NOTE: SystemManager provides winbind status (running or not) on the ContentDirector Properties page.<br />

See the <strong>Omneon</strong> SystemManager User Guide for details.<br />

Verifying Communication with the Domain Controller<br />

To verify communication:<br />

100 Installation and Configuration Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!