How to keep devices from moving out of a specific OU?

The way we do this is by not mapping locations to OU’s and instead using the OU writeback based on filters. 

You can set a filter with a custom attribute (Ours is called “Device Role”) and if you want it to be in a specific OU you can point those that match that filter to that OU. If you really want to move them manually within GAC, you could exclude assets that have that custom attribute and IIQ will effectively ignore them for writeback.

@amac Thank you for submitting your question to our community! 😄

Thank you @spsalexs for adding your workflow. Is this what you were looking for @amac? 

I’m still pretty new with rules.  Need some more detail. Where do you build the filter? How does it get applied along with the custom attribute?

First navigate to Google Devices app 

Scroll down to this section:

Make sure orgUnitPath is selected and you can easily add a Filter to EXCLUDE whatever you want, we are simply doing it by a serial number. Then when you assign students to devices, the write back will ignore changing the OU of the excluded device.

If I read this correctly.  We can set a filter of OUs to be excluded then in the ORGUnit Path map we map all the school OUs for the devices that can move. Right?

@amac Select the OUs you wish not to move (make sure you hit exclude) and map the ones you want to move - that is correct! 😄

What if we have a chromebook OU that isn’t linked to a school\site?  We have a Warehouse 
OU that all the chromebooks live in until they get assigned to a school.  How would I map that or do I need to?

@amac I don’t think you would need to because they will move OUs when assigned to the school/student. 

Do just destinations need to be mapped not sources?

@amac I think this would best be handled by a meeting with your CSM. Please reach out to them to get a meeting set up. We want to make sure this is getting set up correctly for your specific site. 

Between the the OU exclusions and providing OU mappings, so far things are wokring correctly.  

@amac Glad to hear it!! 😄