ERROR: Unable to mount K2000 share at \\ \peinst
Hi,
I recently received a new laptop and needed to install it. It's a Latitude E7270.
I go in the K2000 to the driver feed, download the correct drivers for this type of laptop, Windows 7 (x64) and Windows 10 (x64).
I recache all drivers and create a new K2000 Boot Environment.
i boot into the K2000 Systems Deployment Menu and select the latest boot image I just created. I arrive at the Dell Kace Main Menu where I select a scripted installation.
After installing the OS (Windows 10 x64), it returns an error when trying to join the domain. I skip this step to solve this afterwards and Windows starts up. But no rivers at all are installed in Windows 10 x64. So, no network either. That's why I got the error when joining the domain.
But it worked in the Dell Main Menu when choosing the scripted installation.There he had the network drivers. But they are not installed into Windows.
Any idea why?
But now it starts:
I've copied the drivers manually to the drivers share on the Kace, into the "kbe_windows_x64" folder. And recreated a new boot environment.
Still no luck. Once in Windows, the drivers are not installed.
I removed all drivers from the driver feed and downloaded them again. I even removed all drivers manually from the share on the K2000 (see topic http://www.itninja.com/question/clear-k2000-driver-feed) and redownloaded them again.
for most of my laptops the drivers are successfully downloaded, for a few others I got the following errors:
Error: Unexpected status code when downloading package (503 ).
Error: cURL error while downloading package (transfer closed with 182120525 bytes remaining to read 18).
Error: cURL error while downloading package (Recv failure: Connection reset by peer 56).
This a new problem which I need to resolve later, since I have the drivers for my laptops I need to install urgently.
I recreate a new boot environment, PXE-boot a laptop, choose the latest image from the Systems Deployment Menu, but now I have the following error:
ERROR: Unable to mount K2000 share at \\\peinst
So no network drivers at all in this boot image?
I recache all the drivers, create again an new boot environment, boot the laptop, choose the latest image and now the screen turn black for a second and it returns back to the K2000 Systems Deployment Menu.
The more I try, the less progress I make. Back to the middle ages where I need to install Windows manually from a dvd?
Help me please!
I recently received a new laptop and needed to install it. It's a Latitude E7270.
I go in the K2000 to the driver feed, download the correct drivers for this type of laptop, Windows 7 (x64) and Windows 10 (x64).
I recache all drivers and create a new K2000 Boot Environment.
i boot into the K2000 Systems Deployment Menu and select the latest boot image I just created. I arrive at the Dell Kace Main Menu where I select a scripted installation.
After installing the OS (Windows 10 x64), it returns an error when trying to join the domain. I skip this step to solve this afterwards and Windows starts up. But no rivers at all are installed in Windows 10 x64. So, no network either. That's why I got the error when joining the domain.
But it worked in the Dell Main Menu when choosing the scripted installation.There he had the network drivers. But they are not installed into Windows.
Any idea why?
But now it starts:
I've copied the drivers manually to the drivers share on the Kace, into the "kbe_windows_x64" folder. And recreated a new boot environment.
Still no luck. Once in Windows, the drivers are not installed.
I removed all drivers from the driver feed and downloaded them again. I even removed all drivers manually from the share on the K2000 (see topic http://www.itninja.com/question/clear-k2000-driver-feed) and redownloaded them again.
for most of my laptops the drivers are successfully downloaded, for a few others I got the following errors:
Error: Unexpected status code when downloading package (503 ).
Error: cURL error while downloading package (transfer closed with 182120525 bytes remaining to read 18).
Error: cURL error while downloading package (Recv failure: Connection reset by peer 56).
This a new problem which I need to resolve later, since I have the drivers for my laptops I need to install urgently.
I recreate a new boot environment, PXE-boot a laptop, choose the latest image from the Systems Deployment Menu, but now I have the following error:
ERROR: Unable to mount K2000 share at \\\peinst
So no network drivers at all in this boot image?
I recache all the drivers, create again an new boot environment, boot the laptop, choose the latest image and now the screen turn black for a second and it returns back to the K2000 Systems Deployment Menu.
The more I try, the less progress I make. Back to the middle ages where I need to install Windows manually from a dvd?
Help me please!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
TheAustinDave
8 years ago
The KBE for the Windows 10 should be created with the native driver pack from KACE KBE Driver Pack PE10 form the support site. Should only have a single driver pack installed in the \drivers\kbe_windows_xXX directory or you will most likely have driver conflict and result with the same error message.
Be sure to also build the KBE with that driver pack using the Windows 10 ADK as the driver pack are matched to the KBE OS.
The error message with Connection reset by peer 56 is usually something related to the path that the download is using, check to make sure there isn't a WebFilter that is blocking the K2000 IP address as a delay in getting through the filter can cause this error.
https://support.software.dell.com/k2000-systems-deployment-appliance/kb/122974
David
Be sure to also build the KBE with that driver pack using the Windows 10 ADK as the driver pack are matched to the KBE OS.
The error message with Connection reset by peer 56 is usually something related to the path that the download is using, check to make sure there isn't a WebFilter that is blocking the K2000 IP address as a delay in getting through the filter can cause this error.
https://support.software.dell.com/k2000-systems-deployment-appliance/kb/122974
David
Posted by:
torgal
8 years ago
Ok, thanks. I'm looking into this right now.
But how do you explain when I'm in the K2000 Systems Deployment Menu and I choose a Client Environment the screen turns black and instead of continuing I return to the Systems Deployment Menu?
But how do you explain when I'm in the K2000 Systems Deployment Menu and I choose a Client Environment the screen turns black and instead of continuing I return to the Systems Deployment Menu?
Comments:
-
So the black-screen error occurs after selecting a KBE? Does it happen with all KBEs for one computer? Or for all computers on one KBE? - JasonEgg 8 years ago
Posted by:
torgal
8 years ago
Sorry for this late answer. I was on holiday... :)
I 've seen now that my boot images are around 450MB.
The latest ones however, are 125KB. That might explain why I cannot select a KBE.
But how can this be? When I create a new KBE I see the DOS windows for at least 10 minutes doing his stuff.
I 've seen now that my boot images are around 450MB.
The latest ones however, are 125KB. That might explain why I cannot select a KBE.
But how can this be? When I create a new KBE I see the DOS windows for at least 10 minutes doing his stuff.