BlueCurtain

Command Line Documentation

Recommended Posts

Hey!

I've had no luck finding any documentation on the command line tools. Using the HELP output I'm able to export computer lists, make packages, etc, but am wondering if there is anything else I'm able to do with it.

One thing I would really like is the ability to set the default policy for a computer when I create it's package. Even better would be the ability to create a policy, or clone a policy, from the command line.

I'm in the process of migrating roughly 150 remote computers from our current management system to the Emsisoft system and need several dozen policies to sort the computers into.

Otherwise, is there any possibility of giving the computers a nickname to better sort which ones are which? We typically have 2-3 computers to a group and I need to be able to tell which computers are in which group easily.

Thanks!

Share this post


Link to post
Share on other sites

Hi BlueCurtain,

We have a 'getting started' pdf available, downloadable from the EEC product page: https://www.emsisoft.com/en/software/enterprise/

https://dl.emsisoft.com/EmsisoftEnterpriseConsoleManual.pdf

The supported functionality of the cmdline is limited and does not replace the functionality available in the GUI.
We have no plans atm to implement new features.

Please stay tuned for news regarding EEC soon.

Thanks

 

Share this post


Link to post
Share on other sites

Hey Frank H,

Thank you for the link, I had found that document before but somehow missed the section about the command line (I thought it was strange it didn't have it).

I totally understand that it isn't meant to replace it, was just hoping I was missing some way to set the policy in the package so we don't have to do them manually. Ah well, that's just part of migrating systems, haha.

Thanks again!

Share this post


Link to post
Share on other sites

Hi BlueCurtain,

Roger that.

There is no need to include the policy in the package, as when EAM connects to EEC it will be assigned to the 'new computers' group and will receive those policies.

After the initial connect,  you can drag&drop the clients to any appropriate computergroup.

We also have a yet undocumented feature available where you can connect EAM to EEC from the cmdline on the client. You then first have to install EAM (can be done from cmdline too) and run another cmdline to connect it to EEC.

 

Cheers

Share this post


Link to post
Share on other sites

That makes sense. I was hoping I could make all the packages, then send them out through our existing system and have them automatically go into their own policy groups. Instead I'll just do them in batches and move them over from the New Computers section manually.

I did see the options for connecting them after the fact, I will most likely be taking advantage of that at some point and love that it's available. Our current system is a nightmare when something goes wrong during setup and we have to undo everything to try and get it to connect properly.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.