You are not logged in.


[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2014-07-19 04:06:53

Registered: 2010-06-27


We are supporting a some commercial and some not-for-profit installations of Deploy Studio. Where possible, we try to reuse NetBoot Sets and some basic images.

Any chance of giving us a way to export workflows so that we might be able to do something similar with those? Also, in the case of images, some of the metadata gets lost when we do that. At the risk of being charged with heresy, one wonders if maybe a copy that info might be put into the resource fork for the image, or elsewhere, so that it could come along for the ride when one takes the image to a different system?

I would think that many multi-site schools and businesses, might find this a useful feature too.

This isn't a high priority request, as we are working around it now. But, if you get a chance...


#2 2014-10-14 19:44:40

From: Salt Lake City, UT
Registered: 2013-01-28

Re: Portability

It is actually very easy to "export" workflows.
In DeployStudio Admin, click "WORKFLOWS", in the Identifier column, you will see a string of letters, numbers, and dashes - This is a UUID.
Now, go to {DeployStudio Repository}/Databases/Workflows, find the plist with that UUID as the name, copy the plist to wherever you want.

FYI - this is how I managed almost identical DeployStudio repositories at over 20 schools.


Board footer

Powered by FluxBB