Problem with new SDA Media Manager and RSA deployments.
I'm wondering if anyone else is experiencing this problem. Prior to using the new SDA Media Manager, when I would create a KBE and deploy an image from a remote location with its own RSA, I would only see system images deployable from that local RSA. Now, when I try to do that at a location with an RSA, I do confirm PXE boot with the local RSA's IP but when I get to the imaging menu, I see the images that are on our main SDA, and the images are deployed from the SDA.
I've been working with KACE tech support on this, and was told that if I put the IP of the SDA in the Server Configuration tab of the SDA Media Manager, it will always deploy from the SDA, and likewise if I enter the address of the RSA, it will deploy from the RSA. Conversely, selecting the "Use DHCP to find SDA" option should select the correct SDA or RSA depending on the DHCP scope, but that's not working. The old KACE Media Manager just seemed to "work" from any location with a single KBE. If I'm required to hard code the IP addresses of the RSA's to get it to work as it did would now require me to create and maintain four different KBE's; one for each of our RSA's.
Also, none of our DHCP servers/scopes or options have changed in the meantime.
Though we built a new Media Manager, the process to builda KBE has not changed, it has the exact same commands in the startnet.cmd file. This is usually something with DHCP. You can see what server the KBE is connected to by looking in the footer. Support provided you with a workaround to get things going.