/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Do the K1000 and K2000 servers require AD objects for themselves?

01/06/2016 540 views
In order to function properly, are AD objects required for the Kace servers?

Both my K1000 and K2000 AD objects disappeared from AD sometime around 12/31/15. I know they were there because I built an RSA with a name that made it appear alphabetically next to the K1K and K2K AD objects. I deleted the RSA to create a better name for the remote site. Our Accounts team sees the log of me deleting the RSA object and they see logs of other two Kace objects existing a couple weeks before that, but there is no log of the K1K or K2K AD objects being deleted. They're still investigating. In the meantime, I'm checking on the necessity of these objects. 

Thanks
0 Comments   [ + ] Show comments

Comments


All Answers

1
Hi,

about the K2000: It does not participate to the domain so the only real objects that it needs is the A record in the DNS
about the K1000: if you have not activated the single sign on feature the only real object needed is, like for the K2000 the DNS A record.
Otherwise if you activated the SSO and the K1000 it is no more joined to the domain you need to unjoin it and rejoin it.
 Kind regards,
Marco - StockTrader
Answered 01/06/2016 by: StockTrader
Red Belt

  • I would also agree that you really just need a DNS record, we use SSO but there are no AD objects for our K1, so "joining" the domain is really a misnomer, it's just setting up LDAP in the K1.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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