-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quickcrosmove not moving devices #247
Comments
Sam,
Send me a Meet/Zoom invitation
ross.scroggs @ gamil.com
…On Wed, Mar 2, 2022 at 1:44 PM Sam ***@***.***> wrote:
gam cros_ou /Vendor update ou // quickcrosmove Getting all CrOS Devices
directly in the Organizational Unit for /Vendor, may take some time on a
large Organizational Unit... Got 2 CrOS Devices... Got 2 CrOS Devices
directly in the Organizational Unit for /Vendor
Running this command appears to execute without issue, but the Chrome OS
devices are still in the OU and haven't been moved, even after some time
(1hr+)
—
Reply to this email directly, view it on GitHub
<#247>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCTYL2LI3Y6POJCKBNJFKLU57OLRANCNFSM5PYVZV3A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Ross Scroggs
***@***.***
|
Sam, Replace the // with / Send me a Meet/Zoom invitation. Ross |
Tried that, I assumed // was escaping the / but perhaps not?
Emailed you a meet link, I'm available for the next 6 hours if you're available. |
@scv-m why are you moving devices to /? |
Without going into specifics, it's because of the way our managed networks are configured. |
I'm trying to move devices from the OU
/Vendor
to the root of my domain.Running this command appears to execute without issue, but the Chrome OS devices are still in the OU and haven't been moved, even after some time (1hr+)
The text was updated successfully, but these errors were encountered: