Question

Anybody done Google to Google migration after Sept 30th? (re: Drive single parent behaviour change)


Userlevel 2
Badge +1

anybody done google to google migration after september 30th? curious to see how single parenting behaviour changes affected end-user experience https://developers.google.com/drive/api/v3/ref-single-parent


18 replies

Userlevel 2
Badge +2

… This name made me laugh more than it should 😂



Sent via Slack Thread
Badge +1

We are going a Google to Google migration at the moment and had not thought or known about this.



Sent via Slack Thread
Userlevel 2
Badge +1

lol i like talking about orphans and single parents.. what tool are you using @colinmccarthy? probably worth having a conversation with the vendor



Sent via Slack Thread
Userlevel 2
Badge +1

i created a support ticket with cloudm.



Sent via Slack Thread
Badge +1

we are using the GSuite Migrate tool, so Google is the vendor 🙂



Sent via Slack Thread
Userlevel 2
Badge +1

ah! wonder how they are handling it. ideally it should be replaced with shortcuts, but i highly doubt that the geniuses at google thought about it (chrome policy name change breaking GPO-based policy, GCDS unable to support new SKUs, etc.)



Sent via Slack Thread
Badge +1

yeah they do struggle at time with QA and thinking like an Admin rather than a Computer Science major with no enterprise experience.



Sent via Slack Thread
Userlevel 5
Badge +1

Hadn't really thought about the impacts of this change, I guess it's nice now that files have a single location/path... I can see how it would cause problems for migration tools... seems like shortcuts must be the way to go. Also seems like if the tools that do this haven't updated there will be lots of failures:

Requests that temporarily orphan a file or attempt to place a file in multiple parent folders now fail. For example, in v2 of the API, you cannot move files by using the combinations of parents.delete() and parents.insert() or children.delete() and children.insert().


Sent via Slack Thread
Userlevel 5
Badge +1

Hadn't really thought about the impacts of this change, I guess it's nice now that files have a single location/path... I can see how it would cause problems for migration tools... seems like shortcuts must be the way to go. Also seems like if the tools that do this haven't updated there will be lots of failures:

Requests that temporarily orphan a file or attempt to place a file in multiple parent folders now fail. For example, in v2 of the API, you cannot move files by using the combinations of parents.delete() and parents.insert() or children.delete() and children.insert().


Sent via Slack Thread
Userlevel 5
Badge +1

Hadn't really thought about the impacts of this change, I guess it's nice now that files have a single location/path... I can see how it would cause problems for migration tools... seems like shortcuts must be the way to go. Also seems like if the tools that do this haven't updated there will be lots of failures:

Requests that temporarily orphan a file or attempt to place a file in multiple parent folders now fail. For example, in v2 of the API, you cannot move files by using the combinations of parents.delete() and parents.insert() or children.delete() and children.insert().


Sent via Slack Thread
Userlevel 2
Badge +1

i was happy to let google deal with it

The migration will remove all but one location of files that currently are in multiple locations, and will replace the removed files with shortcuts. 
The migration heuristics will be based primarily on original ownership, but will also take signals about access and activity on other parent folders into account, to ensure the least possible disruption for collaboration.  

but now i have a migration project

Sent via Slack Thread
Userlevel 2
Badge +1

i don't think the vendors are really equipped to deal with heuristics . especially hard if you are migrating from gsuite basic with no drive audit log



Sent via Slack Thread
Userlevel 2
Badge +1

i was happy to let google deal with it

The migration will remove all but one location of files that currently are in multiple locations, and will replace the removed files with shortcuts. 
The migration heuristics will be based primarily on original ownership, but will also take signals about access and activity on other parent folders into account, to ensure the least possible disruption for collaboration.  

but now i have a migration project

Sent via Slack Thread
Userlevel 5
Badge +1

The migration will remove all but one location of files that currently are in multiple locations


This is a bit too vague for my liking, but I get it, they have a tough problem to solve lol



Sent via Slack Thread
Userlevel 5
Badge +1

The migration will remove all but one location of files that currently are in multiple locations


This is a bit too vague for my liking, but I get it, they have a tough problem to solve lol



Sent via Slack Thread
Userlevel 5
Badge +1

The migration will remove all but one location of files that currently are in multiple locations


This is a bit too vague for my liking, but I get it, they have a tough problem to solve lol



Sent via Slack Thread
Userlevel 2
Badge +1

oh and if using shortcuts with drive file stream on windows, extra path that gets added with shortcuts causes problems for MS Office (259 characters for word/powerpoint, and 218 characters for excel).



Sent via Slack Thread
Userlevel 2
Badge +1

cloudm confirmed that they are exempt from this change.



Sent via Slack Thread

Reply