RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

2004-02-10 Thread Celone, Mike
Title: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )





I haven't moved anymore machines in the lab yet. I'll be migrating about 25 machines or so Wed night and I can let you know how it goes then. 


Mike Celone
Systems Specialist
Radio Frequency Systems
v 203-630-3311 x1031 
f 203-634-2027
m 203-537-2406


-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]] 
Sent: Monday, February 09, 2004 11:02 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )


Thanks for the update Tim. 7 min calculation according to my testing in the lab. I believe Mike is also doing the same testing in the lab.

Mike, Do you have any update for us? 


Santhosh


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Wright, T. MR NSSB
Sent: Friday, February 06, 2004 9:21 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )


Santosh/Mike,
 We successfully migrated about 6000 computers using ADMT ver.2 set to reboot 1 min. after completion. Santosh, I'm not sure where you are getting the 7 min. from. ADMT issues a message to the workstation to start ADMTagent.exe, immediately after you click the close button. You can verify this by looking in Task Manager on the machine you are trying to migrate, you should see ADMTagent listed in the active processes. It could actually take much longer or much shorter depending on the amount of data and profiles that are on the machine which you are trying to migrate. The more data the longer it will take. We migrated a 2TB file server and it took about an hour.

HTH,


-Tim


-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 06, 2004 12:34 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )


Mike  Sudhir,


My computer migration problem has been fixed!  I learned something today, Be patient.  Here is the time calculation according to my testing.  If you select the 5 minutes option during the computer migration, the actual restart time = 7min + selected 5 min is a total of 12 min.  If you select 1 min, the restart time = 7 min + 1 min.

7 min is a fixed time for ADMT to issue a message to the workstation.  After that 7 min you will see the shutdown message and it will give you the selected time during the computer migration(5, 1 etc).  7 min is according to my testing in the lab but I think the MS actual value is 5 min.

Mike,
I would recommend you test in the lab with a 1 min option and wait for 8 min. You will see the restart message on the workstation.  Good luck and be patient :- ) 

Thanks,
Santhosh

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Santhosh Sivarajan
Sent: Friday, February 06, 2004 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT


Thanks Mike.  I am going to test your solution in the lab today!



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Celone, Mike
Sent: Friday, February 06, 2004 7:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT


Santosh, 
 
I moved a total of 3 machines yesterday in our lab and was able to get them to reboot successfully.  Instead of changing the time to 1 minute I left it at 5.  Those machines rebooted without issue.  I then tried again changing the time to 1 minute.  Those machines would not reboot.  It seems if you change the time to less than 5 minutes it does not issue a reboot.

 
As for the below error messages you will see them in the logs if you just do a test and not a migration.  Every test I've done using ADMT displays the 2nd error message in the logs.  

 
Mike



From: Sudhir Kaushal [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 06, 2004 12:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT Hi Santosh,
 
It is true that account is created but the machines just dont reboot. In my case i tried even changing the time from 1 min to 5 min. But the machines just dont reboot. Even after rebooting the machines manually, the domain name remained the same. After checking the logs on c:\temp on the clients machine i found this error failed to change the domain affiliation (hr=8007054b), the specified domain does not exist or could not be contacted . Because of this i concluded that account creation on the Target domain is may be because of ADMT agent, which gets properly installed on the client machine and do the necessary changes, but client is not able to contact the Target domain and hence dont reboot on their own.  

 
The other most common error i have seen in the logs is that hr=800706fb The security database on the server does not have a computer account for this workstation trust

RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

2004-02-09 Thread Santhosh Sivarajan
Thanks for the update Tim.  7 min calculation according to my testing in the
lab.  I believe Mike is also doing the same testing in the lab.

Mike, Do you have any update for us?  

Santhosh

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wright, T. MR NSSB
Sent: Friday, February 06, 2004 9:21 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

Santosh/Mike,
We successfully migrated about 6000 computers using ADMT ver.2 set
to reboot 1 min. after completion.  Santosh, I'm not sure where you are
getting the 7 min. from.  ADMT issues a message to the workstation to start
ADMTagent.exe, immediately after you click the close button.  You can verify
this by looking in Task Manager on the machine you are trying to migrate,
you should see ADMTagent listed in the active processes.  It could actually
take much longer or much shorter depending on the amount of data and
profiles that are on the machine which you are trying to migrate.  The more
data the longer it will take.  We migrated a 2TB file server and it took
about an hour.

HTH,

-Tim

-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:34 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

Mike  Sudhir,

My computer migration problem has been fixed!  I learned something today,
Be patient.  Here is the time calculation according to my testing.  If you
select the 5 minutes option during the computer migration, the actual
restart time = 7min + selected 5 min is a total of 12 min.  If you select 1
min, the restart time = 7 min + 1 min.

7 min is a fixed time for ADMT to issue a message to the workstation.  After
that 7 min you will see the shutdown message and it will give you the
selected time during the computer migration(5, 1 etc).  7 min is according
to my testing in the lab but I think the MS actual value is 5 min.

Mike, 
I would recommend you test in the lab with a 1 min option and wait for 8
min. You will see the restart message on the workstation.  Good luck and be
patient :- ) 

Thanks,
Santhosh

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Santhosh Sivarajan
Sent: Friday, February 06, 2004 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Thanks Mike.  I am going to test your solution in the lab today!


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Friday, February 06, 2004 7:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Santosh, 
 
I moved a total of 3 machines yesterday in our lab and was able to get them
to reboot successfully.  Instead of changing the time to 1 minute I left it
at 5.  Those machines rebooted without issue.  I then tried again changing
the time to 1 minute.  Those machines would not reboot.  It seems if you
change the time to less than 5 minutes it does not issue a reboot.
 
As for the below error messages you will see them in the logs if you just do
a test and not a migration.  Every test I've done using ADMT displays the
2nd error message in the logs.  
 
Mike


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Hi Santosh,
 
It is true that account is created but the machines just dont reboot. In my
case i tried even changing the time from 1 min to 5 min. But the machines
just dont reboot. Even after rebooting the machines manually, the domain
name remained the same. After checking the logs on c:\temp on the clients
machine i found this error failed to change the domain affiliation
(hr=8007054b), the specified domain does not exist or could not be
contacted . Because of this i concluded that account creation on the Target
domain is may be because of ADMT agent, which gets properly installed on the
client machine and do the necessary changes, but client is not able to
contact the Target domain and hence dont reboot on their own.  
 
The other most common error i have seen in the logs is that hr=800706fb The
security database on the server does not have a computer account for this
workstation trust relationship. Again I guess this is related with the
Administrative permission in the domain. 
 
Santosh what error you are getting in the logs? 
 
Regards,
Sudhir Kaushal 
Systems Administrator ( Hosted Team ) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20) 4228607, Ext-126 
-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 7:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Yes. you are right mike.  I don't think it is due to name

RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-06 Thread Celone, Mike
Title: RE: [ActiveDir] Computer Migration Issues with ADMT



Santosh, 

I moved a total of 3 machines yesterday in our lab and was 
able to get them to reboot successfully. Instead of changing the time to 1 
minute I left it at 5. Those machines rebooted without issue. I then 
tried again changing the time to 1 minute. Those machines would not 
reboot. It seems if you change the time to less than 5 minutes it does not 
issue a reboot.

As for the below error messages you will see them in the 
logs if you just do a test and not a migration. Every test I've done using 
ADMT displays the 2nd error message in the logs. 

Mike


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:17 AMTo: 
'[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
Migration Issues with ADMT

Hi 
Santosh,

It is 
true that account is created but the machines just dont reboot. In my case i 
tried even changing the time from 1 min to 5 min. But the machines just dont 
reboot. Even afterrebooting the machines manually, the domain name 
remained the same. After checking the logs on c:\temp on the clients machine i 
found this error "failed to change the domain 
affiliation (hr=8007054b), the specified domain does not exist or could not be 
contacted" . Because of thisi concluded that account 
creation on the Target domain is may be because of ADMT agent, which gets 
properly installed on the client machine and do the necessary changes, but 
client is not able to contact the Target domain and hence dont reboot on their 
own.

The 
other most common error i have seen in the logs is that "hr=800706fb 
The security database on the server does not have a computer account for this 
workstation trust relationship". Again I guess this is related with the Administrative 
permissionin the domain. 

Santosh what error you are getting in the logs? 

Regards,
Sudhir Kaushal Systems Administrator ( Hosted Team ) eGain Communications Pvt. Ltd. Hello - (+91 20) 4222812, (+91 20) 4228607, 
Ext-126 

  -Original Message-From: Santhosh Sivarajan 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, February 05, 
  2004 7:31 PMTo: [EMAIL PROTECTED]Subject: RE: 
  [ActiveDir] Computer Migration Issues with ADMT
  
  Yes. you are right 
  mike. I don't think it is due to name resolution 
  problem.
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  On Behalf Of Celone, 
  MikeSent: Thursday, February 
  05, 2004 7:38 AMTo: 
  '[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
  Migration Issues with ADMT
  
  So your saying that 
  the machines won't reboot because they can't resolve the target domain? This 
  can't be true because all the machines I tried it on join to the target domain 
  (I see the account created) but just don't reboot. After I reboot them 
  manually they log into the new domain without any issues. Why would the 
  machine have to resolve the target domain to reboot 
  anyways?
  
  Mike 
  Celone
  Systems 
  Specialist
  Radio Frequency 
  Systems
  v 203-630-3311 x1031 
  
  f 
  203-634-2027
  m 
  203-537-2406
  
  
  
  
  From: Sudhir 
  Kaushal [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 1:29 
  AMTo: '[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
  Migration Issues with ADMT
  Hi 
  Santosh, 
  I had 
  this problem while migrating the computer accounts and the things i concluded 
  are as follows: 
  This 
  error is because the ADMT agent on the source domain clients is not able to 
  resolve the target domain.  I tried first creating static WINS record of the 
  target domain in the source domain WINS server. Though MIcrosoft dont 
  recommend it. It didn't worked out for me, may be for the simple fact that 
  WINS resolution is not supported when ur target Win2K domain is using DNS for the 
  name resolution. I was migrating from NT 4.0 to Win2K. 
  
  If you r 
  using DNS in the source domain and if it doesn't have resource record of 
  Target domain, then create it. so that ADMT agent should be able to resolve 
  the Target domain name from the source domain DNS. Like "Targetdomain.com" . 
  
  If u r 
  using only WINS in the source domain, then make sure that u have the WINS 
  record of the target domain in the source domain WINS server. 
  
  If u r 
  using DHCP then u can make all ur source domain clients to use DNS of Target 
  domain by making the configuration for DNS in DHCP . So that ADMT agent could 
  able to resolve the target domain name from Target domain DNS server only. 
  
  For me 
  the first one worked out. I hope it works for u too. 
  
  Regards, Sudhir Kaushal Systems Administrator ( Hosted Team ) 
  eGain Communications Pvt. Ltd. 
  Hello - (+91 20) 
  4222812, (+91 20) 4228607, Ext-126 
  
  -Original Message- From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 05, 
  2004 4:18 AM To: 
  [EMAIL PROTECTED] 
  Subject: [ActiveDir] Computer 
  Migr

RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-06 Thread Santhosh Sivarajan
Title: RE: [ActiveDir] Computer Migration Issues with ADMT








Thanks Sudhir. I am not getting any error
message. But it wont restart the computer automatically. I have to manually
restart the computer!











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sudhir Kaushal
Sent: Thursday, February 05, 2004
11:17 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT







Hi Santosh,











It is true that account is created but the
machines just dont reboot. In my case i tried even changing the time from 1 min
to 5 min. But the machines just dont reboot. Even afterrebooting the
machines manually, the domain name remained the same. After checking the logs
on c:\temp on the clients machine i found this error failed to change the domain affiliation (hr=8007054b), the
specified domain does not exist or could not be contacted . Because of thisi concluded that account creation on the
Target domain is may be because of ADMT agent, which gets properly installed on
the client machine and do the necessary changes, but client is not able to
contact the Target domain and hence dont reboot on their own.











The other most common error i have seen in
the logs is that hr=800706fb
The security database on the server does not have a computer account for this
workstation trust relationship. Again I guess this is
related with the Administrative permissionin the domain. 











Santosh what error you are getting in the
logs? 











Regards,





Sudhir Kaushal 
Systems
Administrator ( Hosted Team ) 
eGain
Communications Pvt. Ltd. 
Hello - (+91
20) 4222812, (+91 20) 4228607, Ext-126 





-Original Message-
From: Santhosh
 Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004
7:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT

Yes. you are right mike. I
dont think it is due to name resolution problem.











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Thursday, February 05, 2004
7:38 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration
Issues with ADMT





So your saying that the machines won't
reboot because they can't resolve the target domain? This can't be true because
all the machines I tried it on join to the target domain (I see the account
created) but just don't reboot. After I reboot them manually they log
into the new domain without any issues. Why would the machine have to
resolve the target domain to reboot anyways?



Mike Celone

Systems Specialist

Radio Frequency Systems

v 203-630-3311 x1031 

f 203-634-2027

m 203-537-2406









From: Sudhir
Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 05, 2004
1:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT

Hi
Santosh, 

I had
this problem while migrating the computer accounts and the things i concluded
are as follows: 

This
error is because the ADMT agent on the source domain clients is not able to
resolve the target domain. 
 
I tried first creating static WINS
record of the target domain in the source domain WINS server. Though MIcrosoft
dont recommend it. It didn't worked out for me, may be for the simple fact that
WINS resolution is not supported when ur
target Win2K domain is using DNS for the name resolution. I was migrating from
NT 4.0 to Win2K. 

If you r
using DNS in the source domain and if it doesn't have resource record of Target
domain, then create it. so that ADMT agent should be able to resolve the Target
domain name from the source domain DNS. Like Targetdomain.com . 

If u r
using only WINS in the source domain, then make sure that u have the WINS
record of the target domain in the source domain WINS server. 

If u r
using DHCP then u can make all ur source domain clients to use DNS of Target
domain by making the configuration for DNS in DHCP . So that ADMT agent could
able to resolve the target domain name from Target domain DNS server only. 

For me
the first one worked out. I hope it works for u too. 

Regards,

Sudhir Kaushal 
Systems Administrator ( Hosted Team
) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20)
4228607, Ext-126 



-Original
Message- 
From: Santhosh
 Sivarajan [mailto:[EMAIL PROTECTED]]

Sent: Thursday, February 05, 2004
4:18 AM 
To: [EMAIL PROTECTED]

Subject: [ActiveDir] Computer
Migration Issues with ADMT 



I
remember someone posted a message here 3 or 4 weeks ago with an ADMT and

computer migration question.
I have the same problem in the lab. After the 
computer migration, it won't
restart automatically. I have to manually 
restart the computer. Does
anyone remember that question? If you still 
have a copy of that email thread
could you forward it to me? 

Thanks,

Santhosh 

List
info : http://www.activedir.org/mail_list.htm 
List FAQ : http://www.activedir.org/list_faq.htm

List archive: http://www.mail-archive.com/activedir

RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-06 Thread Santhosh Sivarajan
Title: RE: [ActiveDir] Computer Migration Issues with ADMT








Thanks Mike. I am going to test your
solution in the lab today!











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Friday, February 06, 2004
7:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT





Santosh, 



I moved a total of 3 machines yesterday in
our lab and was able to get them to reboot successfully. Instead of
changing the time to 1 minute I left it at 5. Those machines rebooted
without issue. I then tried again changing the time to 1 minute.
Those machines would not reboot. It seems if you change the time to less
than 5 minutes it does not issue a reboot.



As for the below error messages you will
see them in the logs if you just do a test and not a migration. Every
test I've done using ADMT displays the 2nd error message in the logs. 



Mike









From: Sudhir
Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004
12:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT



Hi Santosh,











It is true that account is created but the
machines just dont reboot. In my case i tried even changing the time from 1 min
to 5 min. But the machines just dont reboot. Even afterrebooting the
machines manually, the domain name remained the same. After checking the logs
on c:\temp on the clients machine i found this error failed to change the domain affiliation (hr=8007054b), the
specified domain does not exist or could not be contacted . Because of thisi concluded that account creation on the
Target domain is may be because of ADMT agent, which gets properly installed on
the client machine and do the necessary changes, but client is not able to
contact the Target domain and hence dont reboot on their own.











The other most common error i have seen in
the logs is that hr=800706fb
The security database on the server does not have a computer account for this
workstation trust relationship. Again I guess this is
related with the Administrative permissionin the domain. 











Santosh what error you are getting in the
logs? 











Regards,





Sudhir Kaushal 
Systems
Administrator ( Hosted Team ) 
eGain
Communications Pvt. Ltd. 
Hello - (+91
20) 4222812, (+91 20) 4228607, Ext-126 





-Original Message-
From: Santhosh
 Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004
7:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT

Yes. you are right mike. I don't
think it is due to name resolution problem.











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Thursday, February 05, 2004
7:38 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT





So your saying that the machines won't
reboot because they can't resolve the target domain? This can't be true because
all the machines I tried it on join to the target domain (I see the account
created) but just don't reboot. After I reboot them manually they log into
the new domain without any issues. Why would the machine have to resolve
the target domain to reboot anyways?



Mike Celone

Systems Specialist

Radio Frequency Systems

v 203-630-3311 x1031 

f 203-634-2027

m 203-537-2406









From: Sudhir Kaushal
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 05, 2004
1:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT

Hi
Santosh, 

I had
this problem while migrating the computer accounts and the things i concluded
are as follows: 

This
error is because the ADMT agent on the source domain clients is not able to
resolve the target domain. 
 
I tried first creating static WINS
record of the target domain in the source domain WINS server. Though MIcrosoft
dont recommend it. It didn't worked out for me, may be for the simple fact that
WINS resolution is not supported when ur
target Win2K domain is using DNS for the name resolution. I was migrating from
NT 4.0 to Win2K. 

If you r
using DNS in the source domain and if it doesn't have resource record of Target
domain, then create it. so that ADMT agent should be able to resolve the Target
domain name from the source domain DNS. Like Targetdomain.com . 

If u r
using only WINS in the source domain, then make sure that u have the WINS
record of the target domain in the source domain WINS server. 

If u r
using DHCP then u can make all ur source domain clients to use DNS of Target
domain by making the configuration for DNS in DHCP . So that ADMT agent could
able to resolve the target domain name from Target domain DNS server only. 

For me
the first one worked out. I hope it works for u too. 

Regards,

Sudhir Kaushal 
Systems Administrator ( Hosted Team
) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20)
4228607, Ext-126 



-Original
Message- 
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED

RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

2004-02-06 Thread Santhosh Sivarajan
Mike  Sudhir,

My computer migration problem has been fixed!  I learned something today,
“Be patient”.  Here is the time calculation according to my testing.  If you
select the 5 minutes option during the computer migration, the actual
restart time = 7min + selected 5 min is a total of 12 min.  If you select 1
min, the restart time = 7 min + 1 min.

7 min is a fixed time for ADMT to issue a message to the workstation.  After
that 7 min you will see the shutdown message and it will give you the
selected time during the computer migration(5, 1 etc).  7 min is according
to my testing in the lab but I think the MS actual value is 5 min.

Mike, 
I would recommend you test in the lab with a 1 min option and wait for 8
min. You will see the restart message on the workstation.  Good luck and be
patient :- ) 

Thanks,
Santhosh

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Santhosh Sivarajan
Sent: Friday, February 06, 2004 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Thanks Mike.  I am going to test your solution in the lab today!


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Friday, February 06, 2004 7:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Santosh, 
 
I moved a total of 3 machines yesterday in our lab and was able to get them
to reboot successfully.  Instead of changing the time to 1 minute I left it
at 5.  Those machines rebooted without issue.  I then tried again changing
the time to 1 minute.  Those machines would not reboot.  It seems if you
change the time to less than 5 minutes it does not issue a reboot.
 
As for the below error messages you will see them in the logs if you just do
a test and not a migration.  Every test I've done using ADMT displays the
2nd error message in the logs.  
 
Mike


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Hi Santosh,
 
It is true that account is created but the machines just dont reboot. In my
case i tried even changing the time from 1 min to 5 min. But the machines
just dont reboot. Even after rebooting the machines manually, the domain
name remained the same. After checking the logs on c:\temp on the clients
machine i found this error failed to change the domain affiliation
(hr=8007054b), the specified domain does not exist or could not be
contacted . Because of this i concluded that account creation on the Target
domain is may be because of ADMT agent, which gets properly installed on the
client machine and do the necessary changes, but client is not able to
contact the Target domain and hence dont reboot on their own.  
 
The other most common error i have seen in the logs is that hr=800706fb The
security database on the server does not have a computer account for this
workstation trust relationship. Again I guess this is related with the
Administrative permission in the domain. 
 
Santosh what error you are getting in the logs? 
 
Regards,
Sudhir Kaushal 
Systems Administrator ( Hosted Team ) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20) 4228607, Ext-126 
-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 7:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Yes. you are right mike.  I don't think it is due to name resolution
problem.


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Thursday, February 05, 2004 7:38 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

So your saying that the machines won't reboot because they can't resolve the
target domain? This can't be true because all the machines I tried it on
join to the target domain (I see the account created) but just don't
reboot.  After I reboot them manually they log into the new domain without
any issues.  Why would the machine have to resolve the target domain to
reboot anyways?
 
Mike Celone
Systems Specialist
Radio Frequency Systems
v 203-630-3311 x1031 
f 203-634-2027
m 203-537-2406


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 05, 2004 1:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Hi Santosh, 
I had this problem while migrating the computer accounts and the things i
concluded are as follows: 
This error is because the ADMT agent on the source domain clients is not
able to resolve the target domain. 
  
I tried first creating static WINS record of the target domain in the source
domain WINS server. Though MIcrosoft dont recommend it. It didn't worked out
for me

RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

2004-02-06 Thread Wright, T. MR NSSB
Santosh/Mike,
We successfully migrated about 6000 computers using ADMT ver.2 set to reboot 1 
min. after completion.  Santosh, I'm not sure where you are getting the 7 min. from.  
ADMT issues a message to the workstation to start ADMTagent.exe, immediately after you 
click the close button.  You can verify this by looking in Task Manager on the machine 
you are trying to migrate, you should see ADMTagent listed in the active processes.  
It could actually take much longer or much shorter depending on the amount of data and 
profiles that are on the machine which you are trying to migrate.  The more data the 
longer it will take.  We migrated a 2TB file server and it took about an hour.

HTH,

-Tim

-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:34 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT - FIXED :- )

Mike  Sudhir,

My computer migration problem has been fixed!  I learned something today,
Be patient.  Here is the time calculation according to my testing.  If you
select the 5 minutes option during the computer migration, the actual
restart time = 7min + selected 5 min is a total of 12 min.  If you select 1
min, the restart time = 7 min + 1 min.

7 min is a fixed time for ADMT to issue a message to the workstation.  After
that 7 min you will see the shutdown message and it will give you the
selected time during the computer migration(5, 1 etc).  7 min is according
to my testing in the lab but I think the MS actual value is 5 min.

Mike, 
I would recommend you test in the lab with a 1 min option and wait for 8
min. You will see the restart message on the workstation.  Good luck and be
patient :- ) 

Thanks,
Santhosh

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Santhosh Sivarajan
Sent: Friday, February 06, 2004 8:43 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Thanks Mike.  I am going to test your solution in the lab today!


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Friday, February 06, 2004 7:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

Santosh, 
 
I moved a total of 3 machines yesterday in our lab and was able to get them
to reboot successfully.  Instead of changing the time to 1 minute I left it
at 5.  Those machines rebooted without issue.  I then tried again changing
the time to 1 minute.  Those machines would not reboot.  It seems if you
change the time to less than 5 minutes it does not issue a reboot.
 
As for the below error messages you will see them in the logs if you just do
a test and not a migration.  Every test I've done using ADMT displays the
2nd error message in the logs.  
 
Mike


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 06, 2004 12:17 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Hi Santosh,
 
It is true that account is created but the machines just dont reboot. In my
case i tried even changing the time from 1 min to 5 min. But the machines
just dont reboot. Even after rebooting the machines manually, the domain
name remained the same. After checking the logs on c:\temp on the clients
machine i found this error failed to change the domain affiliation
(hr=8007054b), the specified domain does not exist or could not be
contacted . Because of this i concluded that account creation on the Target
domain is may be because of ADMT agent, which gets properly installed on the
client machine and do the necessary changes, but client is not able to
contact the Target domain and hence dont reboot on their own.  
 
The other most common error i have seen in the logs is that hr=800706fb The
security database on the server does not have a computer account for this
workstation trust relationship. Again I guess this is related with the
Administrative permission in the domain. 
 
Santosh what error you are getting in the logs? 
 
Regards,
Sudhir Kaushal 
Systems Administrator ( Hosted Team ) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20) 4228607, Ext-126 
-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 05, 2004 7:31 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT
Yes. you are right mike.  I don't think it is due to name resolution
problem.


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike
Sent: Thursday, February 05, 2004 7:38 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer Migration Issues with ADMT

So your saying that the machines won't reboot because they can't resolve the
target domain? This can't be true because all the machines I tried it on
join

RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-05 Thread Celone, Mike
Title: RE: [ActiveDir] Computer Migration Issues with ADMT



So your saying that the machines won't reboot because they 
can't resolve the target domain? This can't be true because all the machines I 
tried it on join to the target domain (I see the account created) but just don't 
reboot. After I reboot them manually they log into the new domain without 
any issues. Why would the machine have to resolve the target domain to 
reboot anyways?


Mike Celone
Systems Specialist
Radio Frequency 
Systems
v 203-630-3311 x1031 
f 203-634-2027
m 
203-537-2406


From: Sudhir Kaushal [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 05, 2004 1:29 AMTo: 
'[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
Migration Issues with ADMT

Hi Santosh, 
I had this problem while migrating the computer accounts and the 
things i concluded are as follows: 
This error is because the ADMT agent on the source domain 
clients is not able to resolve the target domain.  I tried first creating static WINS record 
of the target domain in the source domain WINS server. Though MIcrosoft dont 
recommend it. It didn't worked out for me, may be for the simple fact that WINS 
resolution is not supported when ur target Win2K domain is using DNS for the 
name resolution. I was migrating from NT 4.0 to Win2K. 
If you r using DNS in the source domain and if it doesn't have 
resource record of Target domain, then create it. so that ADMT agent should be 
able to resolve the Target domain name from the source domain DNS. Like 
"Targetdomain.com" . 
If u r using only WINS in the source domain, then make sure that 
u have the WINS record of the target domain in the source domain WINS server. 

If u r using DHCP then u can make all ur source domain clients 
to use DNS of Target domain by making the configuration for DNS in DHCP . So 
that ADMT agent could able to resolve the target domain name from Target domain 
DNS server only. 
For me the first one worked out. I hope it works for u too. 

Regards, Sudhir Kaushal Systems Administrator ( Hosted Team ) eGain 
Communications Pvt. Ltd. Hello - (+91 20) 4222812, (+91 
20) 4228607, Ext-126 
-Original Message- From: 
Santhosh Sivarajan [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 05, 2004 4:18 AM To: [EMAIL PROTECTED] Subject: 
[ActiveDir] Computer Migration Issues with ADMT 
I remember someone posted a message here 3 or 4 weeks ago with 
an ADMT and computer migration question. I have 
the same problem in the lab. After the computer 
migration, it won't restart automatically. I have to manually 
restart the computer. Does anyone remember that 
question? If you still have a copy of that email 
thread could you forward it to me? 
Thanks, Santhosh 
List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ 



RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-05 Thread Santhosh Sivarajan
Title: RE: [ActiveDir] Computer Migration Issues with ADMT








Thanks Sudhir. I have DHCP in the lab with
DNS and WINS entry. I dont have name resolution problem. I
can resolve Target and Source domain from the workstation. I think my problem is
something else or something related to Time Sync. I used Shutdown.exe to
restart workstation remotely without any problem. 



As mike mentioned, I am going to test Restart
after 1 or 5 min option in the lab today. I believe this is something
related to time sync configuration. I dont have a time server
configured in the DHCP scope.



Santhosh











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sudhir Kaushal
Sent: Thursday, February 05, 2004
12:29 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Computer
Migration Issues with ADMT





Hi
Santosh, 

I had
this problem while migrating the computer accounts and the things i concluded
are as follows: 

This
error is because the ADMT agent on the source domain clients is not able to
resolve the target domain. 
 
I tried first creating static WINS
record of the target domain in the source domain WINS server. Though MIcrosoft
dont recommend it. It didn't worked out for me, may be for the simple fact that
WINS resolution is not supported when ur
target Win2K domain is using DNS for the name resolution. I was migrating from
NT 4.0 to Win2K. 

If you r
using DNS in the source domain and if it doesn't have resource record of Target
domain, then create it. so that ADMT agent should be able to resolve the Target
domain name from the source domain DNS. Like Targetdomain.com . 

If u r
using only WINS in the source domain, then make sure that u have the WINS
record of the target domain in the source domain WINS server. 

If u r
using DHCP then u can make all ur source domain clients to use DNS of Target
domain by making the configuration for DNS in DHCP . So that ADMT agent could
able to resolve the target domain name from Target domain DNS server only. 

For me
the first one worked out. I hope it works for u too. 

Regards,

Sudhir Kaushal 
Systems Administrator ( Hosted Team
) 
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20)
4228607, Ext-126 



-Original
Message- 
From: Santhosh
 Sivarajan [mailto:[EMAIL PROTECTED]]

Sent: Thursday, February 05, 2004
4:18 AM 
To: [EMAIL PROTECTED]

Subject: [ActiveDir] Computer
Migration Issues with ADMT 



I
remember someone posted a message here 3 or 4 weeks ago with an ADMT and

computer migration question.
I have the same problem in the lab. After the 
computer migration, it won't
restart automatically. I have to manually 
restart the computer. Does
anyone remember that question? If you still 
have a copy of that email thread
could you forward it to me? 

Thanks,

Santhosh 

List
info : http://www.activedir.org/mail_list.htm 
List FAQ : http://www.activedir.org/list_faq.htm

List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/









RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-05 Thread Sudhir Kaushal
Title: RE: [ActiveDir] Computer Migration Issues with ADMT



Hi 
Santosh,

It is 
true that account is created but the machines just dont reboot. In my case i 
tried even changing the time from 1 min to 5 min. But the machines just dont 
reboot. Even afterrebooting the machines manually, the domain name 
remained the same. After checking the logs on c:\temp on the clients machine i 
found this error "failed to change the domain 
affiliation (hr=8007054b), the specified domain does not exist or could not be 
contacted" . Because of thisi concluded that account 
creation on the Target domain is may be because of ADMT agent, which gets 
properly installed on the client machine and do the necessary changes, but 
client is not able to contact the Target domain and hence dont reboot on their 
own.

The 
other most common error i have seen in the logs is that "hr=800706fb 
The security database on the server does not have a computer account for this 
workstation trust relationship". Again I guess this is related with the Administrative 
permissionin the domain. 

Santosh what error you are getting in the logs? 

Regards,
Sudhir Kaushal Systems Administrator ( Hosted Team ) eGain Communications Pvt. Ltd. Hello - (+91 20) 4222812, (+91 20) 4228607, 
Ext-126 

  -Original Message-From: Santhosh Sivarajan 
  [mailto:[EMAIL PROTECTED]Sent: Thursday, February 05, 
  2004 7:31 PMTo: [EMAIL PROTECTED]Subject: RE: 
  [ActiveDir] Computer Migration Issues with ADMT
  
  Yes. you are right 
  mike. I dont think it is due to name resolution 
  problem.
  
  
  
  
  
  From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  On Behalf Of Celone, 
  MikeSent: Thursday, February 
  05, 2004 7:38 AMTo: 
  '[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
  Migration Issues with ADMT
  
  So your saying that 
  the machines won't reboot because they can't resolve the target domain? This 
  can't be true because all the machines I tried it on join to the target domain 
  (I see the account created) but just don't reboot. After I reboot them 
  manually they log into the new domain without any issues. Why would the 
  machine have to resolve the target domain to reboot 
  anyways?
  
  Mike 
  Celone
  Systems 
  Specialist
  Radio Frequency 
  Systems
  v 203-630-3311 x1031 
  
  f 
  203-634-2027
  m 
  203-537-2406
  
  
  
  
  From: Sudhir 
  Kaushal [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 1:29 
  AMTo: '[EMAIL PROTECTED]'Subject: RE: [ActiveDir] Computer 
  Migration Issues with ADMT
  Hi 
  Santosh, 
  I had 
  this problem while migrating the computer accounts and the things i concluded 
  are as follows: 
  This 
  error is because the ADMT agent on the source domain clients is not able to 
  resolve the target domain.  I tried first creating static WINS record of the 
  target domain in the source domain WINS server. Though MIcrosoft dont 
  recommend it. It didn't worked out for me, may be for the simple fact that 
  WINS resolution is not supported when ur target Win2K domain is using DNS for the 
  name resolution. I was migrating from NT 4.0 to Win2K. 
  
  If you r 
  using DNS in the source domain and if it doesn't have resource record of 
  Target domain, then create it. so that ADMT agent should be able to resolve 
  the Target domain name from the source domain DNS. Like "Targetdomain.com" . 
  
  If u r 
  using only WINS in the source domain, then make sure that u have the WINS 
  record of the target domain in the source domain WINS server. 
  
  If u r 
  using DHCP then u can make all ur source domain clients to use DNS of Target 
  domain by making the configuration for DNS in DHCP . So that ADMT agent could 
  able to resolve the target domain name from Target domain DNS server only. 
  
  For me 
  the first one worked out. I hope it works for u too. 
  
  Regards, Sudhir Kaushal Systems Administrator ( Hosted Team ) 
  eGain Communications Pvt. Ltd. 
  Hello - (+91 20) 
  4222812, (+91 20) 4228607, Ext-126 
  
  -Original Message- From: Santhosh 
  Sivarajan [mailto:[EMAIL PROTECTED]] 
  Sent: Thursday, February 05, 
  2004 4:18 AM To: 
  [EMAIL PROTECTED] 
  Subject: [ActiveDir] Computer 
  Migration Issues with ADMT 
  
  I 
  remember someone posted a message here 3 or 4 weeks ago with an ADMT 
  and computer 
  migration question. I have the same problem in the lab. After 
  the computer 
  migration, it won't restart automatically. I have to 
  manually restart 
  the computer. Does anyone remember that question? If you 
  still have a copy 
  of that email thread could you forward it to me? 
  Thanks, Santhosh 
  List 
  info : http://www.activedir.org/mail_list.htm 
  List FAQ : http://www.activedir.org/list_faq.htm 
  List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ 
  


RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-04 Thread Mike Celone
I have the same problem.  I have been trying this in a lab over the past day and it 
never reboots the machines automatically.  The only change I made was to change the 
time after the wizard finishes to 1 minute instead of 5.  Could that be doing it?

Mike

-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 5:48 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Computer Migration Issues with ADMT


I remember someone posted a message here 3 or 4 weeks ago with an ADMT and
computer migration question.  I have the same problem in the lab.  After the
computer migration, it won't restart automatically.  I have to manually
restart the computer.  Does anyone remember that question?  If you still
have a copy of that email thread could you forward it to me?

Thanks,
Santhosh

List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info   : http://www.activedir.org/mail_list.htm
List FAQ: http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/


RE: [ActiveDir] Computer Migration Issues with ADMT

2004-02-04 Thread Sudhir Kaushal
Title: RE: [ActiveDir] Computer Migration Issues with ADMT





Hi Santosh,


I had this problem while migrating the computer accounts and the things i concluded are as follows:


This error is because the ADMT agent on the source domain clients is not able to resolve the target domain. 

I tried first creating static WINS record of the target domain in the source domain WINS server. Though MIcrosoft dont recommend it. It didn't worked out for me, may be for the simple fact that WINS resolution is not supported when ur target Win2K domain is using DNS for the name resolution. I was migrating from NT 4.0 to Win2K. 

If you r using DNS in the source domain and if it doesn't have resource record of Target domain, then create it. so that ADMT agent should be able to resolve the Target domain name from the source domain DNS. Like Targetdomain.com . 

If u r using only WINS in the source domain, then make sure that u have the WINS record of the target domain in the source domain WINS server. 

If u r using DHCP then u can make all ur source domain clients to use DNS of Target domain by making the configuration for DNS in DHCP . So that ADMT agent could able to resolve the target domain name from Target domain DNS server only. 

For me the first one worked out. I hope it works for u too. 


Regards,
Sudhir Kaushal
Systems Administrator ( Hosted Team )
eGain Communications Pvt. Ltd. 
Hello - (+91 20) 4222812, (+91 20) 4228607, Ext-126




-Original Message-
From: Santhosh Sivarajan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 05, 2004 4:18 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Computer Migration Issues with ADMT



I remember someone posted a message here 3 or 4 weeks ago with an ADMT and
computer migration question. I have the same problem in the lab. After the
computer migration, it won't restart automatically. I have to manually
restart the computer. Does anyone remember that question? If you still
have a copy of that email thread could you forward it to me?


Thanks,
Santhosh


List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/