vb.net gs1 128 Make note of these values because you will need them to both create and then manage the instance. in VS .NET

Printer Code 128 Code Set C in VS .NET Make note of these values because you will need them to both create and then manage the instance.

Purpose To upgrade the AD LDS schema to the latest version. Required as a prerequisite for synchronizing an instance with Active Directory in Windows Server 2003.

14

Purpose Required as a prerequisite for synchronizing an instance with Active Directory in Windows Server 2008. Required to synchronize data between an AD DS forest and an AD LDS instance through ADAMSync.

MS-ADLDS-DisplaySpecifiers.ldf Required for the Active Directory Sites and Services snap-in operation. MS-AZMan.ldf MS-InetOrgPerson.ldf MS-User.ldf MS-UserProxy.ldf MS-UserProxyFull.ldf Required to support the Windows Authorization Manager. Required to create inetOrgPerson user classes and attributes. Required to create user classes and attributes. Required to create a simple userProxy class. Required to create a full userProxy class. MS-UserProxy.ldf must be imported first.

After you have all these items in hand, you are ready to create your instance. Make sure the account you use has local administrative rights. There are two ways to create instances. The first is through the Active Directory Lightweight Services Setup Wizard, and the second is through the command line. You will use the wizard during the practice in this lesson. Using the command line is explained in a later section.

You can also perform unattended AD LDS instance creations. For example, to create instances on Server Core installations, you must use an unattended instance creation process because there is no graphical interface to run the wizard. Unattended instance creations are also useful when you need to create an instance for a distributed application on multiple servers. Make sure you prepare all the prerequisites for the instance as outlined in the Preparing for AD LDS Instance Creation section earlier in this lesson. The %SystemRoot%\ADAM folder includes an additional command, AdamInstall.exe, which can be run to perform unattended instance setups. As with the Dcpromo.exe command, this command requires a text file as input for the creation of the instance. You can run AdamInstall.exe on either a full installation or Server Core. Begin by creating this text file. 1. Launch Notepad 2. Type the text for the answer file. Include the following items:

InstanceName=InstanceName LocalLDAPPortToListenOn=PortNumber LocalSSLPortToListenOn=PortNumber NewApplicationPartitionToCreate=PartitionName DataFilesPath=D:\ADAMInstances\InstanceName\Data LogFilesPath=D:\ADAMInstances\InstanceName\Data ServiceAccount=DomainorMachineName\AccountName ServicePassword=Password Administrator=DomainorMachineName\GroupName ImportLDIFFiles= LDIFFilename1 LDIFFilename2 LDIFFilename3 SourceUserName=DomainorMachineName\AccountName SourcePassword=Password

Replace all names in italics with the appropriate values. Refer to the Preparing for AD LDS Instance Creation section earlier in this lesson to identify the required values. Use caution with this file because it includes passwords, and these passwords are displayed in clear text. The passwords are removed as soon as the file is used by the AD LDS instance creation tool. 3. Save the file in the %SystemRoot%\ADAM folder, and name it with the name of the instance you want to create. 4. Close Notepad.

For more information on AD LDS instance creation, go to http://technet2.microsoft.com/ windowsserver2008/en/library/141900a7-445c-4bd3-9ce3-5ff53d70d10a1033.mspx mfr=true.

Now you re ready to create your instance. Remember that you need local administrative rights. 1. Open an elevated command prompt from the Start menu by right-clicking Command Prompt and selecting Run As Administrator. 2. In the command prompt window, move to the %SystemRoot%\ADAM folder. Type the following command, and then press Enter.

4. Close the command prompt window. Your instance is ready. You can verify that the instance files have been created by going to the target folder and viewing its contents.

14

You can also migrate existing LDAP directories to AD LDS or upgrade instances of ADAM to AD LDS. You can do this by importing the contents of the older instances into a new instance of AD LDS. Importing data can be done either when you create the instance or after the instance is created. Both processes use the same approach because both rely on LDIF files or files with the .ldf extension. If you choose to import data after the instance is created, you will need to use the LDIFDE.exe command. Keep in mind that you must first export the data from the previous instance and place it into a file in LDIF format before you can import the data. You can use LDIFDE to export contents from legacy instances. Remember that you need local administrative rights as well as administrative rights to the instance to perform these operations. Also make sure you run the command prompt with elevated credentials. Use the following command structure: