KBE Manipulator won't fill in Password field
Just finished updating to 3.5, and updated to the latest KBE Manipulator. Now every time I try to build a KBE, it won't fill in the password field and errors out. If I fill in the password field manually in the media manager (without exiting the KBEM) and click Start Upload it will appear to work fine, but the boot environment won't map Y: to \\k2\peinst.
Any thoughts?
Answers (4)
I can confirm that the newest KBEM appears to be working now. However, while the KBE successfully loads, there is an error that appears immediately before WinPE initializes. It looks like there is a syntax issue in the commands to build it, but again this does not cripple the KBE. Here is the error:
'[DHCP]' is not recognized as an internal or external command, operable program or batch file.
'static' is not recognized as an internal or external command, operable program or batch file.
Comments:
-
Are you uploading winpe 3.1 windows 7 or winpe4.0 windows 8? I had that happen when I created my Boot Env for windows 8 pe 4.0 but not in winpe3.1 - SMal.tmcc 11 years ago
-
Windows 7, nothing different than how I previously uploaded. From the format of the .ini I posted below I am just assuming that maybe Corey has a syntax error in some of the fields?? Not a big deal though cuz it does progress and load the KBE. - nheyne 11 years ago
-
What version of kbem are you using? 3.4.9.2 is the newest version.
Can you post your startnet.cmd commands, replacing your password with password? - cserrins 11 years ago-
Looks like the first two lines may be the culprit:
[DHCP]
static= @echo > %TMP%\kbox-ip-address
@echo Copyright (c) 2013 Dell Inc.
@echo.
@echo *** Initializing WinPE and network devices
wpeinit
wpeutil InitializeNetwork
wpeutil DisableFirewall
@echo.
@echo *** Waiting for network devices to settle
@ksleep 5
@echo.
@echo *** Checking if this is a UFD boot and an image is prepped for deployment
@for %%i in (Z Y X W V U T S R Q P O N M L K J I H G F E D C) do @if exist "%%i:\kace\deploy.bat" set UFDPATH=%%i:
@if defined UFDPATH (
@echo.
@echo *** Deploying image from UFD at %UFDPATH%
@set KBOX_IP=127.0.0.1
start /wait %UFDPATH%\kace\deploy.bat
@echo.
@echo *** Rebooting
wpeutil Reboot
)
@echo.
@echo *** Locating K2000 IP address from DHCP option 66 or 244
kgetdhcp 66 > %TMP%\kbox-ip-address
if errorlevel 1 kgetdhcp 244 > %TMP%\kbox-ip-address
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to determine server IP address from DHCP
@echo WARNING: Using hardcoded IP address as fallback
)
set /p KBOX_IP=<%TMP%\kbox-ip-address
@if "%KBOX_IP%"=="no data" (
@echo.
@echo ERROR: Unable to determine server IP address
exit /b 1
)
@if "%KBOX_IP%."=="." (
@echo.
@echo ERROR: Unable to determine server IP address
exit /b 1
)
set /p KBOX_IP=<%TMP%\kbox-ip-address
@echo.
@echo *** Getting client MAC address
cscript /nologo kprintmac.vbs > %TMP%\mac
set /p MAC_ADDRESS=<%TMP%\mac
@echo.
@echo *** Mounting the install shares
@echo off
net use Y: \\%KBOX_IP%\peinst /user:%KBOX_IP%\www "password"
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\peinst
exit /b 1
)
@echo off
net use T: \\%KBOX_IP%\petemp /user:%KBOX_IP%\www "password"
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\petemp
exit /b 1
)
@echo.
@echo *** Performing local startup
@if exist Y:\hta\startup.bat (
start /wait Y:\hta\startup.bat
)
@echo.
@echo *** Launching deployment client
@if exist Y:\hta\deploy.hta (
mshta Y:\hta\deploy.hta
) - nheyne 11 years ago
-
Please use the check for updates to go to version 3.4.9.3, I was writing the static IP to startnet.cmd directly instead of to the startnet.ini file. ooops, apologies. - cserrins 11 years ago
-
Looks like it's going to work, thanks Corey! I will build more KBEs tomorrow and report any difficulties, but it looks fine at the moment. - nheyne 11 years ago
KBEM has been updated to work with 3.5. Please use the "Check for Updates" app to download the latest version; 3.4.9.3. This version fixes the issue with the password, with MM not closing, and also with mapping the drives when using 3.5 MM, and fixed where I was writing static ip addresses to startnet.cmd instead of to startnet.ini (which I broke in 3.4.9.2).
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!
Comments:
-
Thanks Corey - SMal.tmcc 11 years ago
-
The KBE uploads correctly, however I am still having the issue of being prompted for credentials when it maps to Y. I looked in startnet.cmd and there is no username/password for those lines. - nheyne 11 years ago
-
ah ok I will check the test I uploaded to see if pw is there or not - SMal.tmcc 11 years ago
-
I see what you mean now. it does not put the local kbox user credentials in.
3.4 startnet
@echo.
@echo *** Mounting the install shares
@echo off
net use Y: \\%KBOX_IP%\peinst /user:%KBOX_IP%\www "kacepassword"
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\peinst
exit /b 1
)
@echo off
net use T: \\%KBOX_IP%\petemp /user:%KBOX_IP%\www "kacepassword"
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\petemp
exit /b 1
)
net use t: /delete
net use t: \\10.16.19.152\images$ Password /user:dr-acad\k2000
net use w: \\10.16.19.152\images$ Password /user:dr-acad\k2000
3.5 startnet
@echo.
@echo *** Mounting the install shares
net use Y: \\%KBOX_IP%\peinst
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\peinst
exit /b 1
)
net use T: \\%KBOX_IP%\petemp
@if errorlevel 1 (
@echo.
@echo ERROR: Unable to mount shares at \\%KBOX_IP%\petemp
exit /b 1
)
net use t: /delete
net use t: \\10.16.19.152\images$ Password /user:dr-acad\k2000
net use w: \\10.16.19.152\images$ Password /user:dr-acad\k2000 - SMal.tmcc 11 years ago
I'm working on a fix for this now. Seems you found the fix to make it upload and this does work. You mention that it isn't mapping to Y:, is it mapping to t:?
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it!
Comments:
-
Just tried, nope. In my support ticket, I also mention that when the mapping fails and prompts for credentials, using "admin" as the username does not work, however using "k2\admin" does. Support had me verify which user was mapping, and instead of admin it was using "www". Hope that helps in some way :) - nheyne 11 years ago
-
So no drives map. Does k2\www work?
This is helpful as I'm working on an update now and have 3.5 MM working, but would want to address this issue at the same time.
Thanks,
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it! - cserrins 11 years ago-
Yes k2\www works, in fact it works better because it will proceed to fully load into the KACE Menu, whereas when I use k2\admin the command completes successfully but won't proceed any further and I am left at the command prompt screen. - nheyne 11 years ago
-
Make sure you are using the latest version of kbem because I added k2\www as the username quite awhile ago.
Corey
Lead L3 Enterprise Solutions Engineer, K2000
If my response was helpful, please rate it! - cserrins 11 years ago -
I found out that the issue of the not-filled-password helps you with the username problem while mapping the net drives:
1. Config your BE with KBEM as you desire and hit "Create KBE"
2. Media Manager starts, wait till all fields are filled
3. Now go to your TEMP-Directory e.g. "C:\Users\MyUser\AppData\Local\Temp\"
4. You should see a folder "kbe_man" there, dive in
5. Edit "startnet.cmd" with a text editor like Notepad
6. Find the "net use Y:" and "net use T:" commands and provide the proper username and password for your K2000
7. Save the startnet.cmd and go back to Media Manager
8. CHECK IF THE CHOSEN ARCHITECTURE IS CORRECT since the passing over of the x64-flag does not seem to work either
8. Fill in your Samba-password and now start the upload - chrpetri 11 years ago-
This will work, but I'm confused as I've had the username/password for net use in startnet.cmd since 3.4 was introduced. What version of kbem are you using? - cserrins 11 years ago
-
Hi Corey, im using KBEM 3.4.8.0 with DELL Media Manager 3.5.7324.0
Best regards,
Christian - chrpetri 11 years ago
-
Can you see if you have an old version of Media Manager installed as well? There was one in program files\kace I believe. - cserrins 11 years ago
Here is what I am seeing now. The startnet.ini file in the kbe_man folder at TEMP has this content:
[MAP]
key=
key=@echo.
key=@echo *** Mounting the install shares
key=net use Y: \\%KBOX_IP%\peinst
key=@if errorlevel 1 (
key= @echo.
key= @echo ERROR: Unable to mount shares at \\%KBOX_IP%\peinst
key= exit /b 1
key=)
key=
key=net use T: \\%KBOX_IP%\petemp
key=@if errorlevel 1 (
key= @echo.
key= @echo ERROR: Unable to mount shares at \\%KBOX_IP%\petemp
key= exit /b 1
key=)
key=
[MAP3.4]
key=
key=@echo.
key=@echo *** Mounting the install shares
key=@echo off
key=net use Y: \\%KBOX_IP%\peinst /user:%KBOX_IP%\www "$password"
key=@if errorlevel 1 (
key= @echo.
key= @echo ERROR: Unable to mount shares at \\%KBOX_IP%\peinst
key= exit /b 1
key=)
key=
key=@echo off
key=net use T: \\%KBOX_IP%\petemp /user:%KBOX_IP%\www "$password"
key=@if errorlevel 1 (
key= @echo.
key= @echo ERROR: Unable to mount shares at \\%KBOX_IP%\petemp
key= exit /b 1
key=)
key=
But, the startnet.cmd file is missing the second part where the credentials are included. I have not found a way to edit this file prior to uploading though, since now the newest KBEM doesn't halt at the same spot as the workaround posted earlier.