I got it installed and working. I ran Brian’s INF Parser against the INF file and did some guessing on the reg values the dll that my inf parser doesn’t know how to load sets. It works.

 

Thanks,
Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Rasmuson
Sent: Friday, October 21, 2005 1:47 PM
To: [email protected]
Subject: RE: [ActiveDir] ADMT3 Install

 

I have previously extracted the DomainMig.chm and here is the relevant section about installing to a preconfigured SQL database (see below).

 

Eric Rasmuson

IT System Administrator

MyFamily.com

 

To install ADMT using a preconfigured SQL database

If you plan to use multiple ADMT consoles or if you have a dedicated database server where you want to centralize your ADMT database, you can create another SQL Server database instance for ADMT instead of using the default local database. If you choose to install ADMT in an instance of SQL Server 2000, install SQL Server 2000 with SP4 and use the command line syntax in the following table from any server that can target the SQL server to create the ADMT instance on the SQL Server:

Syntax

Description

admtdb create /s|server: Server\Instance

Specifies the name of the SQL server and instance to connect to for the purpose of database creation. This is a required parameter.

admtdb create [/{i|import}: "v2 database path"

Specifies the fully qualified path to the protar.mdb database file that was used with a previous ADMT v2 installation.

Note:

Required /server parameter must be specified with this option.

ADMT v2 data can be imported at the time of creation, or later into an empty database using the admtdb import command.

For all admtdb.exe command line options, type admtdb /? at a command prompt.

After the database has been configured, navigate to the folder where you downloaded ADMT v3 and double-click admtsetup.exe.

In the Active Directory Migration Tool Installation Wizard, on the Database Selection page, select the Use an existing Microsoft SQL Server option and specify the server to connect to in the form of Server\Instance.

If you decide to use the local database after configuring a remote instance of a SQL Server database, do the following:

To use the default local database after configuring a remote instance of a SQL Server database

1.      On the local computer, click Start, point to Administrative Tools, and click Services.

2.      In the right pane, navigate to MSSQL$MS_ADMT and verify that the Status column displays Started, and that the Startup Type is set to Automatic. If the MSSQL$MS_ADMT service is not Started, right-click MSSQL$MS_ADMT and click Properties.

3.      On the General tab, in the Startup Type drop-down list, click Automatic.

4.      Under Service Status, click the Start button and click OK.

5.      Close Services.

6.      Open a command prompt and type:

admt config /setdatabase: Server\Instance. You can now use the default local database.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond
Sent: Friday, October 21, 2005 11:34 AM
To: [email protected]
Subject: [ActiveDir] ADMT3 Install

So everytime I goto load MSDE on my mgmt station it does some stuff and then I get this:

 

Failed to install Microsoft SQL Server Desktop Edition (Windows). Fatal error during installation.

 

Has anyone else encountered this? I’ve got a couple MSDE instances on here already and I suspect somebody else used instance 4 which is what this appears to be hardcoded to. Does anyone know if I can tell ADMT to use a SQL server that already exists?

 

Thanks,
Brian Desmond

[EMAIL PROTECTED]

 

c - 312.731.3132

 

 

 

Reply via email to