SDA Deployment Information Field?

Hey everyone, I asked a question previously about how I can create a smart label that captures both newly added machines and re-imaged machines to complete post-imaging processes: https://www.itninja.com/question/smart-label-to-identify-new-and-reimaged-machines

Unfortunately, once I was able to deploy a machine using the SDA, I tried the inventory rule provided my Nico, but it wouldn't work. I couldn't even locate the k2000_deployment_info.conf. I also noticed that the SDA Deployment Information field under the machine inventory in the K1000. Is there something I need to enable on the SDA for this file or field(I'm assuming the field pulls from the .conf file)?

Thanks again!


4 Comments   [ + ] Show comments
  • The KACE SMA automatically retrieves information from that CONF file since version 10.

    The file is generated for every deployment made from the SDA, and saved at C:\ProgramData\Quest\KACE\

    If it's not there, something is preventing the SDA Engine from writing into that path. (AV or GPO policies modding folder permissions) - Channeler 1 year ago
  • Yeah I've got a machine just recently imaged, but no conf file. :( I don't know what could be stopping it from getting saved. There aren't any special GPO's or folder permissions being applied. It's so weird. - mytmouse 1 year ago
  • What are your KACE SDA and KACE SMA versions?
    If you explore that folder for CMD and list the contents of it with DIR, Do you see it? - Channeler 1 year ago
  • SMA - 10.1.99 (will be upgraded to 10.2.234 tomorrow)
    SDA - 7.2.97

    I viewed the directory in command prompt and the only CONF file that shows up is amp.conf. :( - mytmouse 1 year ago

Answers (1)

Posted by: Nico_K 1 year ago
Red Belt

at first:
What versions of the SDA and SMA do you use?
Which OS do you deploy? (as an example WiXP had another location)
Also check if you have a post install or a SMA script task which removes the file (some people suggest this since it contains valuable informations about the deployment env)
Verify that no restrictions to the location (c:\programdata\quest\kace) is in place (GPO, IDS/IPS, network wide antivirus) which could prevent this.
Did the deployment succeed completely or was it disrupted after the OS deployment itself?

I checked with SMA 10.2 and SDA 7.2 for a W10 deployment and can see the file (and therefore my CIR works here too)

  • We're currently on:
    SMA - 10.1.99 (will be upgraded to 10.2.234 tomorrow)
    SDA - 7.2.97

    Deploying a Windows 10 2004 scripted install. I checked our post install tasks and nothing seems like it should touch the directory or prevent access. Right now all it's running is:
    Win 10 activation
    Install the KACE Agent
    Apply KUID to agent
    Windows Updates
    Enable Bitlocker
    Some admin account password stuff

    This is probably the most vanilla scripted install I've seen. But I've got machines that came from an older org (we had to transfer appliances) and those machines don't have the CONF file either. - mytmouse 1 year ago
    • really strange. I suggest to open a SR with KACE to check what is going on here. - Nico_K 1 year ago
      • Thanks Nico! I think that's the move too. - mytmouse 1 year 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