/build/static/layout/Breadcrumb_cap_w.png

updateing boot environments password

I updated my Samba password and re-downloaded the boot environment but when trying to use it i get a msg that the spcific network password is not correct - according tohttps://ikbox.pediatrichomeservice.com/locale/en_US.UTF-8/doc/wwhelp/wwhimpl/common/html/frameset.htm?context=K2000&file=t_BuildWindowsKBE.html&single=true


"If you change the Samba share password on the General Settings page, all Windows boot environments are automatically updated to use the new password."


the issue i am having is i just updated my boot environment fo rthe new Dell i7 AIL 7480 models (Kace SDA ver 8.0.194 - Win PE 2004 and A19 drivers) but when i attempt to image an older model AIO (i5) with the newer KBE it gives me an return code 4294967295 - when trying to apply the image.

on the new models there is no issue and when i was using teh old KBE on the older model the image had nto issue appling - no changes have been made to the image. I tried the steps to Apply UEFI Partitions - S:\ Captured that i found but that failed as well.


was hoping for some assistance eithre to allow the current KBE to work on the older models or get he older KBE updated with the current samba password.


Thanks


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Nico_K 1 year ago
Red Belt
0
Usually it works if you follow the procedure:
1. Update the password
2. Recache drivers

But I seen it a few times, and my workflow is from a time where it did not worked (and not implemented), which is the following:
1. update password
2. recache drivers
3. download the latest media manager
4. build a new KBE
5. test
6. if test worked well remove the old KBE
 
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