Was thinking about this. Could you prompt the user for a domain admin name and password to pass to the netdom renamecomputer command?

I need to completely reinstall from scratch and then dreadfully migrate all images, just to have the same product

This is actually a "simple" process. It takes 20 minutes to install Theopenem and migrating the images is as simple as copying from one folder and pasting into another. Also, it is not the same product. CloneDeploy is discontinued.

Are all CD users supposed to figure this one out on their own?

I have provided free support on these forums for anyone that needed help migrating the images. If you search these forums you would find that info out.

"expands". How did you expand the project by removing support for Linux hosting environments and providing less detailed documentation?

Theopenem provides a significant amount of new features over CloneDeploy. If you don't use those features, that doesn't make the statement false. There is a bug with Mono on Linux that I opened up a ticket on Github in 2019, that they still have not resolved. That removes the ability to install on Linux.
https://github.com/mono/mono/issues/13298

By axing CloneDeploy you demonstrated that you don't focus on long-term stability in this project

It's actually the complete opposite. Every decision I've made was done to keep the components of CloneDeploy alive. CloneDeploy(Previously CrucibleWDS) has been around for 12 years. I would argue that already suggests long-term stability. By moving the components of CloneDeploy into Theopenem, I am now contractually obligated to keep developing the software while I have paying customers. These changes ensure that I will keep the development of Theopenem moving forward.

Offering scripts for migrating CD installations to theopenem. Un-break your upgrade path.

Implement proper Linux server support.

Ensure a stable upgrade path between versions, favorably in the form of continious integration via Docker images.

Upgrade scripts are unlikely to be offered, as I suggested earlier, migration is very "simple"
Linux / Docker support is not happening:

1.) Very few of my users actually installed on Linux or Docker
2.) The Mono bug I mentioned earlier, still is not resolved after 3 years, suggesting that it never will be
3.) CloneDeploy used to be offered on Windows, Linux, FreeNAS, and Docker. The end result was, that it removed my ability to provide bug fixes / new features because I spent all of my time fighting to keep it working across many platforms. I just don't have that kind of time any more. Now I focus my energy providing what the majority of my users want.

Thanks. I'll look into it.

@theopenem_admin
LOL - I hear you on not being able to stand Apple.

Thanks you for the heads up.. although it would be nice to have one platform that supports both.

But I completely understand.

@grimtooth said in Quick Group Add // Module progress:

I was wondering if there will be a way to quickly import or add a list of machines into a custom group? For example import from a text file or similar. If a function exists, I apologize.

There is no feature to do this, you must manually add them to the group, or you could use a dynamic group to do it automatically if there is a naming convention that could be used.

Another thing is, can we have a progress meter of some sort, similar to the imaging progress %, but for modules? Even better if it shows the progress for each machines during software/command deployments if it is pending, ongoing or failed.

I can look into adding something in the next release.

@cycy thanks, I will take a look at it

@theopenem_admin Followed the process in the Universal Image video. https://www.youtube.com/watch?v=ZmMzStsFnEI. Going to try again, just in case I missed something.

@theopenem_admin Thanks for considering my ideas! My thought on the remote access link on the computer page is so if there is something you need to do manually in mass(IE: a computer lab) you could just remote in and out of them easily. I get your point of view though, it opens a can of worms as to what everyone wants on that page.

Strange, it seems to working fine for me, tested with multiple emails. I'll look into it some more.

Thanks, I'll look into it.

You would need to create a new image profile for these machines and add the argument to the image profile kernel arguments.

custom_hard_drives=/dev/sdb

or whatever the drive is

Then when you image those machines, select that profile.

This is now available in 1.5.0.

This is now fixed in 1.5.0.

This is now available in 1.5.0.

This is now available in 1.5.0.

This is now available in 1.5.0.

This is now available in 1.5.0.

This is now available in 1.5.0.

This is now available in 1.5.0.

Looks like I accidentally sent the unassigned flag, so it's only returning results for modules that are unassigned. I've attached the fix if you want it. Just download this dll and overwrite the existing one located at

C:\Program Files\Theopenem\Toems-UI\bin

Toems-FrontEnd.dll