Title: Message
The migrator console was giving a "catastrophic failure" pop-up when we'd try to connect to the exchange server. We're working through it with Quest tech support now and I expect resolution soon, but I needed something quick on the directory population. It's always fun when you get 3 weeks to plan, implement, and finish an AD migration. :-)
 
 

**********************
Charlie Kaiser
MCSE, CCNA
Systems Engineer
Essex Credit / Brickwalk
510 985 0975 x5083
**********************

-----Original Message-----
From: Pelle, Joe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 7:28 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] LDAP populate AD with Exchange 5.5 info

Charlie, 

 

We also use Fastlane - what were some of the issues you had with their exchange migration piece?

 

You can contact me via email off list if you would like.

 

Thanks!

 

Joe Pelle

Systems Analyst

Information Technology

Valassis / IT

19975 Victor Parkway Livonia, MI 48152

Tel 734.591.7324  Fax 734.632.6151

[EMAIL PROTECTED]

http://www.valassis.com/

 

This message may have included proprietary or protected information.  This message and the information contained herein are not to be further communicated without my express written consent.

 


From: Charlie Kaiser [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 9:18 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] LDAP populate AD with Exchange 5.5 info

 

I just finished a migration from NT4 to W3K AD. We had a tremendous amount of info in our exchange directory that we wanted in AD. I used the exchange 2003 ADC to populate the AD with the info from exchange once the accounts were built. It worked almost flawlessly. The only glitch I had was on a couple of accounts which were also associated with resource mailboxes, it changed the primary mailbox owner for that account to the new domain account before I was ready to cut that user over. Simple change back, though.

I had used Fastlane Migrator to migrate the user accounts, including SID history. It worked well. I had some issues with their exchange migration piece that I'm still working on resolving, but I think that product is capable of doing some of the exchange data import into AD. It also allows you to massage and manipulate the data. For us, the ADC was perfectly adequate.

Try it in your test lab first and see if it works...

 

**********************
Charlie Kaiser
MCSE, CCNA
Systems Engineer
Essex Credit / Brickwalk
510 985 0975 x5083
**********************

-----Original Message-----
From: Rich Milburn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 6:06 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] LDAP populate AD with Exchange 5.5 info

Does anyone have any experience pulling Exchange 5.5 data to populate AD with?  When you upgrade an NT4 domain you end up with almost no info on your AD accounts, but typically all that info exists in the Exchange 5.5 directory (have heard several recommendations against using the AD connector).  Searches in AD are poor to useless without some of this info.  I've done it before using LDIFDE and mailmerge in Word against the CSV file I exported, and that was a lot of work... probably a script with LDAP from Exchange to AD would be best but before I reinvent the wheel...

Also is this a good step prior to going to Exchange 2003 (sorry if that's a little OT) or is the migration going to take care of that for us?

Thanks

Rich

-------APPLEBEE'S INTERNATIONAL, INC. CONFIDENTIALITY NOTICE-------  PRIVILEGED / CONFIDENTIAL INFORMATION may be contained in this message or any attachments. This information is strictly confidential and may be subject to attorney-client privilege. This message is intended only for the use of the named addressee. If you are not the intended recipient of this message, unauthorized forwarding, printing, copying, distribution, or using such information is strictly prohibited and may be unlawful. If you have received this in error, you should kindly notify the sender by reply e-mail and immediately destroy this message. Unauthorized interception of this e-mail is a violation of federal criminal law. Applebee's International, Inc. reserves the right to monitor and review the content of all messages sent to and from this e-mail address. Messages sent to or from this e-mail address may be stored on the Applebee's International, Inc. e-mail system.

Reply via email to