If you want size guidance on other pieces
let me know. I can ask my buddy sitting over here again. He knows it well. I
know how to use it and how to ask for help when I don’t know the answer.
;) From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Perfect. That really helps and
tracks with what I was finding. Thanks for the help. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Eric Fleischman I’m sorry, I misunderstood. I thought
you meant what would be on the migrating computer (IE the db) not the agent on
client machines. This paragraph stolen directly from a
coworker who is an ADMT guru: AFAIK, the agent code is not of variable
size…. The more frequent stumbling block is the reporting piece of
it. After the agent is dispatched to do computer migration, security
translation, etc, it RPCs back to the box that launched ADMT to write the
results of its task. Depending on the OS level of his clients, he may see
some variance in agent size…. The NT4 agent lives in its own folder under
the ADMT install dir & goes about 1.15 MB. For uplevel clients, I
would investigate McsDctWorkerObjects.dll – I’m fairly sure
that’s the driver of the computer-based tasks. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Thanks for the help. Is the agent
size dependant on outside factors such as how many computers are being done at
one time? I thought (probably wrong) that the agent
would be the same for each machine. The question I'm trying to answer
(and cannot fully test in the lab) is how long should it take 20 to
30 machines to get the agent over a 24 k line without totally killing the
bandwidth. The remote sites have 20 to 30 machines and if the agent is
(for example) 2 meg that would take a while to get pushed down along with the
other traffic that I cannot control. As a side point it would be great if
ADMT had the option to pre load the agent and then execute the conversion at a
specific time. As for the numbers of workstations, right now the test
groups range from 10 to 50 users users/workstations a night, but in
two weeks, 1,500 workstation and 2,000 users will be converted all at the same
time. Due to the client requirements, I cannot simply take one of the
larger remote 24k sites and convert it early. That would be a good solution
and give a solid answer to my question so I'm forced back to trying to
approximate the conversion times. I'm talking about the agent that ADMT puts
on a workstation during the migration from one domain to another. The one
that gets put on, does it work changing domain membership and doing the
security conversion, and then gets deleted before the reboot. Just to explain more about why the size is
important, we are actually pushing three packages down the wire for this.
First a SMS package goes to prepare the workstation for migration (mainly
changing and adding permissions), then the ADMT agent runs changing the domain,
and finally another SMS package is run doing some cleanup. Cheers Steve From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fleischman Hi Steve, Can you clarify a bit? Do you mean during
a migration? If so, how large is the migration we’re talking about (how
many users/computers/groups/etc.)? With that I can probably scrounge up some
anecdotal numbers, but official is tough. I’ll see what I can do. Thanks! ~Eric From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Does anyone know the size of the agent
ADMT puts on the client computer during conversion? Thanks Steve |
Title: Message
- [ActiveDir] Quick question on ADMT Bell, Stephen
- RE: [ActiveDir] Quick question on ADMT Eric Fleischman
- RE: [ActiveDir] Quick question on ADMT Bell, Stephen
- RE: [ActiveDir] Quick question on ADMT Eric Fleischman
- RE: [ActiveDir] Quick question on ADMT Bell, Stephen
- RE: [ActiveDir] Quick question on ADMT Eric Fleischman
- RE: [ActiveDir] Quick question on ADMT Coleman, Hunter
- RE: [ActiveDir] Quick question on ADMT Bell, Stephen