This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Would it be possible to have a LAB env synced with a production env with some way of automation?
So that you can have a lab that more or less reflects the production environment, except the clients of course.
I've been trying to find some good answers out there, but cant really find anyone that has written about it or tried it before.
Considering MECM is more or less a SQL DB, the things I've thought about is replication, or a Master/Slave, but i don´t know enough about it to say that is would be a valid option.
Or would the best option be using the build it export/import PS cmdlets, and building some kind of script to run which syncs these settings, and manually do the rest?
best regards,
You could possibly do this using the migration wizard, bt I'd never recommend that.
Depending on the exact requirements, using PowerShell and a DevOps approach would 100% be the path I would follow; i.e., I wouldn't sync settings, I'd only perform configuration using a script applying that first to the test environment and then the prod environment when it's ready to be productionized.
Powershell to the rescue!
I've got a base setup with PS that now "copies" an ADR and deploys it.
How usable it really will be in a real-world-scenario, remains to be seen, as the parameters which is required can differentiate alot between env.
But hey! it kinda works now, and maybe it can be useful for something, just gotta work out some kinks :)
Thanks for pointing in the right direction!