Move update set from a standalone instance to a specific domain on a domain separated instance

[Mahira]

Hi all,

I have an update set which was created in a stand alone instance. I would like to export and commit this update set to a domain separated instance and commit the changes to a particular domain in my domain separated instance. What is the best way to do this?

When I try to modify the Update Set XML there are too many occurrences of the "sys_domain" or "global", so I got confused where all I should be changing the value without corrupting my Update Set XML.

Any help is appreciated.

Thanks in advance.

Regards,

Mahira

[jeremy_gardner]

Did you figure out an answer to this?  

My guess would be that the updates would use the domain of the file contained within the update set (if you're installing the update set as a user with permission to see that domain), and if no domain then would use your domain when installed the update set?  

But that's just a guess.

[richard-service]

Update sets cannot currently be moved from a domain separated instance to a non-domain separated instance and vice versa.   If anyone can figure this out, there is a lot of revenue in it for them because disentanglement is a huge problem for just about every MSP.

The underyling DB are in fact different between the two cases.   And it is a very easy way to corrupt your instance.   I actually had my user names all get rendered as sys_id's which is pretty awesome.   If you want to see an instance act all crazy and silly, go apply update sets from a non domain instance to a domain instance and just ignore the errors and commit them.   You'll have loads of fun.   Just make sure you are fine with z-booting that thing after your fun stops.