Options to manage a group of Win10 PCs separate from the rest of the company.

We have a new group joining us. 40-50 PCs. These PCs are from the old location that we didn't manage with KACE.

As the old Windows PCs will be getting replaced but we still need to run a full inventory on them. I would like to use our KACE SMA for this process.
This needs to be a temp setup that I can roll back away from after all the old PCs have been replaced.

My first thought was to setup an Organization just for this new group. The problem with that is that I don't have my current SMA setup for Organizations.
I am not opposed to setting up Organizations but just need to know how to roll back from doing so.

I then was trying to think if I could create a label or something that would not run any of my automation that all Windows workstation PCs get.
This also started looking like a hard this to work out.

Ok, here comes the best part. I only have until the end of June 2019 to work this out.

Any thoughts, ideas or even shots in the dark are welcome at this point. Thanks

2 Comments   [ + ] Show comments
  • User a Device Smart Label, and use IP range as the criteria... that way machines within that range will or will not be part of your existing tasks...

    You might need to modify your existing device smart labels, to exclude devices within that IP range as well... - Channeler 3 years ago
  • @Channeler
    You think this would be better and just as safe as the Organizations setup? - DLCurtis 3 years ago
    • If you don't want to obtain an ORGs license and stay there, then yes.

      The thing is when you go ORGS Enabled, the Database mutates in a way there's no going back.

      (unless you have some backups pre-ORG Era, and restore a new KACE with them... loosing all your data\progress). - Channeler 3 years ago

Answers (2)

Answer Summary:
Posted by: SMal.tmcc 3 years ago
Red Belt

Top Answer

Call support and tell them you want a multi org license and setup orgs for this.

You can keep them in separate orgs and just use a org for the old machines inventory, then they will not get anything done to them accidentally with Kace.  Bring new machines into the working org.  Once you convert to multi org the only way to really go back is from the last single org backup you made.  Even if you go multi org you can have just one org.  The thing to be careful about it what org is your default, any machine that does not meet the org filter rules goes there.  Having multi orgs is nice because you can have an org just for testing when you need it. 

This would be quick and also you do not have to worry if a smart label is correct so you do not mess with those when running MI's or scripts.  also if you have any CIR to gather info it would not effect those

Posted by: chucksteel 3 years ago
Red Belt

If a multi-Org setup isn't an option:

  1. Install the KACE Agent
  2. Immediately disable the Quest KACE One Agent
  3. Run "c:\program files (x86)\Quest\KACE\runkbot.exe" 4 0

The machines should upload their data to the appliance, but not actually check-in (so no other tasks will run on the device). 

  • I will give you this. You are creative but that is not something that I would like to relay to 4 IT staff and have done correctly at 3+ remote sites.

    Thanks for the general info on the reporting habits of the agent. This will come in handy down the road. - DLCurtis 3 years ago
    • Well, at the very least I would package it in a zip file with a batch script and tell them to unzip and run the script. - chucksteel 3 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ