Receiving System Error 1312 when KBE loads on target machine

Here again your favorite Random Dude.

Today's topic is about something a friend of mine came across. He installed the 2004 ADK on a machine, ran the Media Manager, created a KBE and then when trying to load that KBE on a target machine he got the following error:

System Error 1312 a specified logon session does not exist. it may already have been terminated

ERROR : Unable to mount KBOX share at \\sdaip\peinst, Attempt X

After talking with my friend I realized that he was running version 6.1 of the ADK. Now, this is not going to work as you might know KACE just added support for 2004 in version 7.2 and using version of the Media Manager ( you can get it here).

After that we upgraded his SDA to 7.2, and used the recommended Media Manager and it worked as expected.

See you in my next post!


  • well, this issue occurs usually if you do not have the right driver for your network card in the NIC. So it MAY be fixed by the latest ADK but more likely by adding the right driver to the KBE. - Nico_K 3 years ago
    • yeah we confirmed that the drivers were OK but it still didn't work. If we create another KBE with 1903 it did work just fine but as he wanted 2004 and with that KB in mind the final solution was just to update to 7.2 - RandomITdude24 3 years ago
  • I reported 2004 ADK not working with 7.2 to KACE. They confirmed with their dev team it was broken and needed to tether to my server to hotfix it. - YasnayaITscrub 3 years ago
    • yeah, the catch was that my friend was trying this on 6.1.... and KACE support said that it will only work with their new MediaManager - RandomITdude24 3 years ago
This post is locked
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