i. Control: Status 3. Review the basic operation of the Remote Imaging Viewer: W

Question

i. Control: Status

3. Review the basic operation of the Remote Imaging Viewer: When started, the Network Connection Unit verifies that is has the appropriate network parameters for communication. The results (valid / not-valid) are passed to the Control Unit via Status. If not-valid, a Status Message is passed to the Image Display Unit, indicating the type of network problem. If valid, a Status Message is passed to the Display Unit requesting the Username and Password. When these are supplied they are sent to the User Unit, which uses Control and Data to pass the Username and Password to the Remote Server. Upon authentication the Remote Server passes a verified / not-verified status back via Data to the User Unit. The Image Display Unit is used to indicate the results of the authentication. If not verified, the username / password process repeats. If verified, the File Access Unit then obtains the File Path for the desired image file and passes this information to the Remote Server. If the file is not found, a status message is passed back and the Image Display Unit reports the error message. If the file is found, a decryption key is sent back first and passed to the Cryptography Unit. Then the file is sent (encrypted) to the File Access Unit and stored as File. The Cryptography Unit then decrypts the File and passes it to the Image Display Unit for viewing. The Image Manipulation Unit is given control so any changes can be made while viewing. If a new version of the file must be uploaded, the Cryptography Unit is engaged, the file is encrypted, and passed to the File Access Unit for uploading via the Remote Server connection.

5. Examine the following flowchart for the Remote Imaging Viewer. This flowchart covers startup and Login processes.

7. Now consider the simplified flowchart for the imaging processes:

8. Analyze the flowchart for the imaging process and provide your perspectives on the process flow. Would you consider it complete or recommend any additions. Explain your answer clearly.

9. Develop the flowcharts for the Download File process, the Manipulate File process, and the Upload File process.

10. Develop a data flow diagram for the entire system. Show each process and its data flow to its associated processes.

Narrative

In addition to answering questions posed in the procedure and submitting any diagrams or figures or other necessary items, if they are required, please also provide a detailed narrative of your experience with the lab, and how you think it applies to the material covered in the chapters assigned to the module.

Explanation / Answer

Viewing LDIFDE general parameters

General Parameters

Export Specific Parameters

Import Specific Parameter

Credentials Parameters

Note This tool is very flexible and offers a number of command-line switches and arguments. The utility is included in Windows 2000 Server, but not with Windows 2000 Professional. The LDIFDE program can be copied to a computer running Windows 2000 Professional and be run remotely against the Windows 2000 Server Active Directory.

Using LDIFDE to export and to import directory objects

The following is a step-by-step process to import and export Organizational Units (OUs) and user accounts from one Windows 2000 Active Directory to another. For this example, "Export" is the name of the domain from which objects are exported and "Import" is the name of the domain in which objects are imported. LDIFDE can also be used to import most third-party folders to Active Directory.

Export the organizational units from the source domain

ldifde -f exportOu.ldf -s Server1 -d "dc=Export,dc=com" -p subtree -r "(objectCategory=organizationalUnit)" -l "cn,objectclass,ou"

Export the user accounts from the source domain

At the command prompt, type:

ldifde -f Exportuser.ldf -s Server1 -d "dc=Export,dc=com" -p subtree -r "(&(objectCategory=person)(objectClass=User)(givenname=*))" -l "cn,givenName,objectclass,samAccountName"

Running this command exports all users in the Export domain into a file named Exportuser.ldf. If you do not have all the required attributes, the import operation does not work. The attributes objectclass and samAccountName are required, but more can be added as needed.

Note Built-in accounts, such as Administrator, do not have a given name. By default, the LDAP filter used above does not export those accounts. LDIFDE does not support exporting passwords.

Note When you omit the -s parameter, LDIFDE chooses a global catalog for exports. Depending on the domain controller placement, this server might be a domain controller for a different domain, and exports might fail. You see this when you examine the output of LDIFDE. In this case, specify a local domain controller of the domain in which the objects are hosted.

Import the organizational units from Export to Import

ldifde -i -f ExportOU.ldf -s Server2

You should see a message stating the number of entries that have been modified and that the command completed successfully.

Note In this situation, you must complete the first step prior to completing the second step so that the OUs are available to contain the users.

Import the users from Export to Import

ldifde -i -f Exportuser.ldf -s Server2

NOTE: Because LDIFDE does not export passwords, when the users are imported into the directory, the account is disabled and the password is set to null. This is done for security reasons. Also, the account option "User must change password at next logon" is selected.

Exporting objects from an entire forest

If you need to export OUs, users, and groups from an entire forest, you may either run the above LDIFDE export commands against each domain in the forest, or alternatively, run the query once against the global catalog (GC). To do this, ensure that the domain controller that is specified by the -s switch is a GC, and additionally, specify the GC port using the -t switch. The GC port number is 3268.

For example, to perform the export operation outlined against a GC, the LDIFDE command would be:

ldifde -f Exportuser.ldf -s Server1 -t 3268 -d "dc=Export,dc=com" -p subtree -r "(&(objectCategory=person)(objectClass=User)(givenname=*))" -l "cn,givenName,objectclass,sAMAccountName"

Note To Modify attributes in AD it is very important that the following format be followed for the import file, especially the "-" on a single line followed by a completely blank line on the next line. To import this file all you need to do is run: ldifde -i -f Import.ldf -s Server.

Sample Import/Modify File Format:

Importing multivalued attributes

Import files with multivalued attributes have the form of:
dn: distinguishedName
changetype: modify
replace: attribute
modify replace: attribute [this is the attribute to be changed]
attribute: value1
attribute: value2
attribute: valueN [where N is the next value] - [hyphen, required to terminate input file]
example:
dn: CN=Connector for Lotus Notes (EX1),CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=VINC,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=vinc,DC=biz changetype: modify replace: msExchExportContainersLinked msExchExportContainersLinked: OU=GroupWise Users,DC=vinc,DC=biz msExchExportContainersLinked: OU=AD Users,DC=vinc,DC=biz msExchExportContainersLinked: CN=Users,DC=vinc,DC=biz

Related Questions

Navigate

• Browse (All)
• Browse I
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.