hello,

 

i upgraded to 3.4 and since then my scripted installs now require a password to the driver share, it was reccomended that i download the win 7 sp1 waik, update my winpe to 3.1 and then upload a new KBE with the driver share password in it, now i cant get beyond a command prompt that just says winpeinit....

then:

X:\windows\system32\_

and a flashing cursor.

 

has anyone else experienced this?

 

 

Answer Summary:
i beleive i may have found it, our good old friend mcafee viruscan enterprise - it was blocking a part of the WAIK from working, if you blink you would miss it, i have disabled this and the boot environment process is going through without errors
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2

i beleive i may have found it, our good old friend mcafee viruscan enterprise - it was blocking a part of the WAIK from working, if you blink you would miss it, i have disabled this and the boot environment process is going through without errors, will confirm.

 

Answered 08/03/2012 by: trentderby
Blue Belt

  • confirmed, now booting into KBE with no issues, thanks for all your help, mcaffee users beware!
  • I have had nothing but bad luck with most of the major anti-virus vendors. Sometimes I wonder if the viruses wouldn't be easier to deal with, at least those are intentionally annoying. :)
  • We ran into problems with SEP grabbing files from the temp dir as the EXE installer decompressed them. I have a conspiracy theory that the AV's support the V's so they can stay in business.
Please log in to comment

Answers

1

Did you use the new driver pack when creating the new KBE?

https://downloads.kace.com/support/downloads/drivers/KBE_driver_pack-a08-r_k-arvy.zip

Answered 08/02/2012 by: dugullett
Red Belt

  • thanks, ill try that now.
  • When using the new driverpack, I would wipe out everything you have in kbe_windows_xXX, put in the new driverpack. Recache the drivers under Library|Drivers and then build a new kbe.

    Corey
    Lead L3 Enterprise Solutions Engineer, K2000
    If my response was helpful, please rate it!
Please log in to comment
1

Just to confirm, you have the 3.4 version of the K2000 installed on your KBox and you have the 3.4 version of media manager installed on a windows 7 machine?

Answered 08/02/2012 by: Ben M
Ninth Degree Black Belt

Please log in to comment
1

I beleive so, the media manager now has the K2000 Hostname on the left and the Host Login Password on the right - there is no help/about on the program.

 

im using

3.4.54256

k2000

Answered 08/02/2012 by: trentderby
Blue Belt

  • That sounds right. What type of machine is this failing on, what make and model? Have you tried another type of machine?
  • ill give that a try, i was trying on an old dell D430 - ill attempt on a dell E4310
    • Oh wow.... haven't seen on of those in a while. That would most likely be your answer.
  • have just tried it on a E4310 and its the same situation, just a blank dos window after it attempts wpeinit
    • Are you PXE booting to a RSA or directly to the K2000?

      Might want to take a look here.
      http://www.itninja.com/question/urgent-stuck-at-kbe-launching-deployment-client
  • ive just tried a reboot of the K2000, we dont use a RSA so im not sure if that would be an issue, we are booting direct to the K2000 - there is nothing sheduled on the machine either this is just to boot into the winpe environment to choose a scripted install to run.
  • If you create a CD/USB stick from your PXE boot does that work?
  • reboot no good, ill log a call with support and see what they come up with.
  • To find the version of media manager, you have to go to the app in Program Files or Program Files (x86) and get properties on the .exe, click on details. Right now, having the host login password is a sure sign that it is 3.4 Media Manager.
    The drivers you have in kbe_windows_xXX are significant.
    When did this problem begin? After the 3.4 update? The only difference between 3.3 KBE and 3.4 KBE is the password.
    The WAIK sp1 has no significance here, either should work.

    Corey
    Lead L3 Enterprise Solutions Engineer, K2000
    If my response was helpful, please rate it!
Please log in to comment
0

I beleive i may have found it, our good old friend mcafee viruscan enterprise was blocking an essential process during the creating of the boot environment, if you blink you miss it, but it was blocking part of the WAIK from installing - im just going to confirm this now.

 

Answered 08/03/2012 by: trentderby
Blue Belt

Please log in to comment
-2

steps i took:

 

downloaded the zip file

copied to driver share merging with existing folders

re-cached files

removed any existing kbe that was not working

recreated KBE

same issue occuring.

 

Answered 08/02/2012 by: trentderby
Blue Belt

  • This content is currently hidden from public view.
    Reason: Removed by user request
    For more information, visit our FAQ's.
Please log in to comment
Answer this question or Comment on this question for clarity

Share