How can a computer be rebooted without using RUM?
Sometimes replication issues in AD could cause a problem and a reboot will not occur because of this..
Another reason could be - in AD domain there is a policy which does not allow to reboot a WS when accessing from network.
Rebooting a computer when migrating is not required and is not absolutely necessary, you can reboot migrated computers anytime later.
NOTE: information in this article is addressing issues typical for older versions of QMM.
One can decide to migrate without rebooting, and reboot eg. one minute later, in RUM if you select computers you can switch to Batch and run a command, eg:
shutdown /r /t 05 /f /m \\%COMPUTER%
An interesting workaround, heavily used in the past, was to add the target account you are using to local admins on each WS. This approach, even if it sounds complicated, is in fact the most elegant and gives you many advantages.
If you decide to do it this way - syntax would be:
Net LocalGroup Administrators Domain\User /Add
You can use any scripting approach or the Batch option in RUM, computer must be selected in RUM, if you select all computers and run this command it will add the account to local admins on each WS. When done with migration and cleaning up you can easily remove this account from local admins group using the same way.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center