I can't rely on restarting thier machines especially for new roll outs...
This has me confused. How are you supposed to image their machines if they can't reboot? You have to put them into WinPE at some point? It seems like the issue you are describing is an issue that occurs whether you include profile migration with your new OS rollout or not.
If you are not imaging, why migrate a profile?
Maybe you have a special use case. Since profile migration is for migrating from an older to a newer OS (or for rebuilding a box when needed), and to do that you have to reboot a couple of times. Boot to WinPE, WinPE boots to Sysprep mini-setup, which reboot again, which logs in using autologin, which installs the agent, which reboots again...
Maybe you have a use case I can't think of.
Also, with communication with your users goes a long way.
"You will be migrated to Windows 7 on this day: 4/x/2010
When you first login your current profile will apply and you
will be rebooted. Thank you, IT"
In the Best Known Methods for Profile Migration in LANDesk 9.0 document it describes how you can control the reboot options. Did you read the document?
Also, the old profile migration won't work for Vista or above, has known issues with accuracy and reliability on anything XP or newer, and struggles (or fails) if the profile you are restoring is for an account that has never been used on the new machine. The delayed apply phase is a big reason why it is successful.
The BKM is found here:
If you look on page 16 you will see how to control the reboot options. I recommend reading the entire document and becoming familiar with the tool before you attempt to migrate a large amount of profiles.
1 of 1 people found this helpful
I would not go back since ldprofile was nasty. Read the BKM that Mach6 provided and if you really want to fine tune it read the 142 page manual here:
We try to be a little anonymous when we deploy machines only because of the "Me Toos?" we have around here. The office principal is a bit too easy to get to and will cave quickly just to get someone out of his office so he can be billable again. That is why I do "stealth deployments" most of the time. Sorry about the clarity before, this is for new machine deployments. Currently we are still an XP house but once 7 x64 is verified to work properly with our apps we'll be deploying that.
Thanks again, didn't see that since XML code still makes my eyes spin. I will be giving that a try once I get this next round of deployments done.
Thanks a lot for that resource. It may be what i need to finally understand this thing.