ADMT 3.0

First, Thanks very much for the fast response.

Perhaps I mis-stated, but aI will try to clarify. I am well aware of the migration
prcedures and infact can get it going with V2. The issue is with V3 and the doc
you mentioned does not address the issue. The Known bugs are not the symtoms
I am having. The ADMT does not see that the PES dll is even running when I use
V3. I find that odd as ALL steps I have ever used in the past with V2 are in place
in this case too.

Any ideas on specific issues with passwords with V3?

Thanks again.

razz

Wow you are fast....Thanks! I am marking this unacceptable but please know that
when all is said I will ask you to post if needed for points.

Great question. Yes, I used ListDlls and Process Explorer to verify that pwmig.dll,
The Password Migration Module, is running under LSASS process. Actually the
password migration dll does not show under services and it is not supposed to. It
shows under Add/Remove Programs which is normal for 2.0. Now, 3.0 does ask
for service info and I believe that is the issue. PES 3.0 does appear to run but the
service is not running as an acct or the local service I bet.

All I know is the V2 installs and after setting the AllowPasswordExport to 1 it
works. For V3, The groups ar set for auditing , the AllowPasswordExport is at 1
and does not exist until I install the dll, and I even did the TcpipClientSupport
entry to 1.

Because the scenario is NT4 domain to SBS 2003 there can not be a trust. The
standard bypass is to run the ADMT tool with a custom runas command.

I have read evrey doc there is including the "Migrating from Small Business Server
4.5 or Windows NT 4 to Windows Small Business Server 2003". Everything is
based on V2 of ADMT but I wanted to use V3. Newer and all, ya know? But I just
found this thread that says if you had 2.0 ADMT and 2.0 PES that when you move
the ADMT to 3.0 you do not need to change the PES or keys. Hum. I will attempt a
3.0 ADMT to a 2.0 PES and see what happens.

Also, no test feature in 3.0 Odd I think. I would love to find the "Test the
migration settings and migrate later option in 3.0.

UPDATE: I just ran ADMT 3.0 from the SBS2003 and migrated from NT4. The key?
I had the 2.0 version of PES installed on the NT VM. So, The PES 3 service appears
to not like NT. Has any one gotten it to run? Because it does not show as a
service, which is normal for 2.0 but I don't know about 3.0, I can not start or
stop it.

I may be leaning to the 2.0 ADMT and PES at this point. I am concerned with
mixing versions even though it worked, and liked the Test Migrate feature in 2.

razz

Neil, I have no idea what sarcasm you mean. Your answers came through within hours, not the normal wait time of days. I was impressed and saying that I really appreciated the fast response time and your time. I have read the post over and over and still see no way to get an insult out of what I said. But, that is the issue with written communication of all forms, misunderstanding. I have been a member of TR for years and have always tried to help on those areas I can because I think that is the best use of knowledge. When I run into an issue I always try to figure it out myself before asking. I am therefore grateful for any time others take to help. So, I am sorry if you took my statement wrong. Thanks for the help anyway.

razz

Neither do I, but some do and not knowing I wanted to make sure you knew the unacceptable marks were only so you would be emailed that I had responded. If they had mattered, you would have gotten them.

Thanks anyway.

Having tested many things at this point I am debating two paths and I am curious
as to what you would choose if this were your client.

Path 1 is to use the ADMT 3.0 for stability and features on the new server with
PES from 2.0 because it works on the old servers.

Advantages are (based on Microsoft notes) better logging and a new backend
database, support for simultaneous migration tasks, multiple ADMT consoles
with delegated tasks, agent enhancements, full object rename etc.

Disadvantages are no "Test the migration settings and migrate later" option, and
worries about the mix of 2.0 PES with 3.0 ADMT (although it appears fine).

Path 2 is to just use the ADMT and PES 2.0.

Advantages are it works and gives the test option.

Disavantages are few. But, No access to the improved agents is a bummer.

I am leaning to path 1 but welcome and outside observations I may have over-
looked.

Again, thanks in advance for your time,

Razz