/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Problem with new SDA Media Manager and RSA deployments.

02/19/2020 158 views

Hello all,

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.

1 Comment   [ + ] Show comment

Comments

  • The KBEs will query the DHCP,

    If the DHCP has no Option 66, they will fallback to the main SDA.

    If the IP supplied by the DHCP is not responding to Pings (from the KBE), the KBS will fallback to the main SDA.

    From the KBE you could run kgetdhcp 66, Open CMD and run kgetdhcp 66, from KBE's troubleshooting tools. It should print the RSA IP.

    It sounds like you have a rogue DHCP over there, OR you are using KBEs designed to always look for the SDA IP. (static KBEs, they will ignore the DHCP values).
    • Cool, thanks... I'll give that a go.

All Answers

0

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.

Answered 02/19/2020 by: cserrins
Red Belt

  • Yes, they did, but my question was if anyone else experienced the same problem after switching to the new SDA Media Manager. I detailed that according to the IP I'm booting from the RSA with PXE, but the menu is showing me images on the SDA. I don't recall doing anything different with the old Media Manager, and of course I'm unable to use it with the new version of the SDA.
    A workaround is not the same as having it work as intended.
 
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