KACE Product Support Question
K1000 v.7 Provisioning looks to wrong FQDN
12/14/2016 1094 views
I've just installed a new virtual instance of the K1000, version 7.x, and am tinkering with it before moving our ver 6.x data to it.
In setting it up, I accidentally configured the Control Panel / Network Settings / Domain to "acu.local" rather than to "acu.edu".
Later, as I tried a Provisioning test, it failed with this message:
process (//k1box.acu.local/client/agent_provisioning/windows_platform/agent_msi_provision.bat k1b0x.acu.local client ampagent-7.0.763-x86.msi k1box.acu.edu) could not be launched: 2 The system cannot find the file specified.
Of course the file can't be found, because "k1box.acu.local" is not resolvable.
So I went back to Control Panel / Network Settings / Domain, and changed that setting to "acu.edu", and then rebooted the K1 (not just restarted the services), but still, whenever I try my provisioning test, I get the same error.
From where is the "k1box.acu.local" coming from now?
I checked Control Panel / Security Settings / Samba / Enable File Sharing, and it has a help-tip that says, "(File sharing is currently enabled at \\k1box\client\. Log in as the admin user to \\k1box\clientdrop\ to add files to the file share.)"
Again, my question: From where is the "k1box.acu.local" coming from now, when as far as I can tell it should either just be "k1box" or "k1box.acu.edu"?