point taken on the clean reboot - biggest issue has been the failure of user profile migration
MS have owned up on a workstation retaining some sort of lock on the user profile despite being logged out - err 7334 is generated on a more general note do people share my view that the level of documentation on the ADMT - error codes / reasons ... is to say the least a bit sparse !!?? GT ----- Original Message ----- From: "Fuller, Stuart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 15, 2003 5:15 PM Subject: RE: [ActiveDir] admt 2.0 - nt4 computer migration > GT, > > Mostly OT but is related if you are starting the workstation migration > journey... > > Rick's comment about the task manager and checking machines reminded me of > something else we did during the workstation migrations. Our operating > mantra during the process was "clean reboot...clean > reboot....ohmmmmmm....clean rebooot". :) > > We used batch files with a FOR statement to drive "shutdown.exe" and > "uptime.exe". Shutdown allowed us to force the list of workstations to > reboot right before the migration. The Uptime batch file (piped to a .csv > file) allowed us to monitor the reboot cycle and make sure all the machines > were ready to go. This had the side benefit of weeding out the problem > child machines. If shutdown didn't work then the ADMT agent would generally > bonk as well. Uptime was also useful in monitoring the reboot after the ADMT > agent was finished. Machines that took a long time with the agent could be > found and then checked. > > -Stuart > > ----------------------------------- > Example Shutdown batch file: > > REM **** Modify the line below for location of workstation list > set file=c:\temp\machineList.txt > > FOR /F "tokens=1 delims=, " %%i in (%file%) do shutdown \\%%i /R /c > > > > -----Original Message----- > From: Graham Turner [mailto:[EMAIL PROTECTED] > Sent: Monday, July 14, 2003 2:08 AM > To: [EMAIL PROTECTED] > Subject: Re: [ActiveDir] admt 2.0 - nt4 computer migration > > Gentlemen, thanks to all for your contributions to this. > > will be going to customer site later this week to do some exhaustive testing > on this issue > > (assuming of course that the computers have not melted in the ridiculously > warm weather we are having here !) > > any other things that you can add will be v gladly received. > > GT > > > ----- Original Message ----- > From: "Rick Kingslan" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, July 11, 2003 11:16 PM > Subject: RE: [ActiveDir] admt 2.0 - nt4 computer migration > > > > Stuart, Graham - > > > > The Agent exec is ADMTAGNT.EXE. Also, I don't remember it running > > under > the > > Explorer process, as when we did our migrations (well, the on-going > saga...) > > it was an easy matter to check how a machine was doing by bringing up > > task manager to determine status and load on the box. Had to do this > > numerous times as workstations took too long and we needed to > > determine the real status of the process. > > > > Rick Kingslan MCSE, MCSA, MCT > > Microsoft MVP - Active Directory > > Associate Expert > > Expert Zone - www.microsoft.com/windowsxp/expertzone > > > 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/
