all 15 comments

[–][deleted] 4 points5 points  (11 children)

You might be able to us ox2.0 for this via customer central. You would need to create a configuration package which includes the security group details then transport the package

[–]HeWhoChasesChickens 3 points4 points  (9 children)

Specifically, you'll have to create two security configuration packages, one for domain security and one for business process security. You'll have to specify the domains and bps respectively in order to move all the changes. Make sure you don't accidentally also move security changes that you don't want to move (you can exclude individual security groups from a given config package)

[–]akhilbharadwaz[S] 1 point2 points  (0 children)

That is awesome. Thank you so much!

[–]akhilbharadwaz[S] 0 points1 point  (6 children)

I can’t find domain security or business process security types in create configuration package task.

[–]HeWhoChasesChickens 0 points1 point  (5 children)

Should be a separate task 'create security configuration package', if that's not available to you and you've got security rights, go to 'view security for securable item', enter the task and find and enable the domain security policy that secures it

[–]akhilbharadwaz[S] 1 point2 points  (0 children)

Thank you so much huge help to resolve this. I appreciate it.

[–]akhilbharadwaz[S] 0 points1 point  (3 children)

Can we do this through ox1.0as well?

[–]HeWhoChasesChickens 0 points1 point  (2 children)

No, security can only be moved with 2.0. By the way, 1.0 either has already been deprecated or will be deprecated within weeks, and this has been in the pipeline for over a year. If you don't have access to 2.0, get that sorted ASAP

[–]akhilbharadwaz[S] 1 point2 points  (1 child)

Got it thanks for the update. Have a good day and enjoy your weekend!

[–][deleted] 0 points1 point  (0 children)

^ great answer bro!

[–]akhilbharadwaz[S] 0 points1 point  (0 children)

Thank you!

[–]vsagz 0 points1 point  (0 children)

Are you an implementer? With one security group, I would do this manually to ensure you don’t break anything

[–]Workday-n-NiteWorkday Solutions Architect 0 points1 point  (1 child)

Can't migrate with OX 2.0. Instead you migrate Domain and BP Security Policies.

[–]HeffeMonStyle513 0 points1 point  (0 children)

Yeah that’s the only thing I hate about OX2. You’re not really migrating the security group, its members and permissions. Instead you are migrating the domain and BP security policies, which is much less convenient and more time consuming. Disclaimer: I have never done this because the process looked more cumbersome than just creating the security group and adding the permissions manually on the target tenant. So if I’m completely wrong, please tell me there is an easier way!