Re: Windows 7 crashed after sysprep
I like to use the HP Softpaq Download Manager: htp://www8.hp.com/us/en/ads/clientmanagement/drivers-bios.html?jumpid=va_r11260_go_clientmanagement_sdm#softpaq-download-mng Then I like to sort by Date...
View ArticleClik here to view.
Re: Windows 7 crashed after sysprep
It is definitely the latest from HP (Sep 6, 2011), but not sure if I select the correct one since there were at least 20 types of inf files.
View ArticleRe: PXE-E53: no boot filename received - when trying to PXE boot to upload a...
http://community.landesk.com/support/docs/DOC-1143 We just added another Cause and Resolution: CauseAnother service on the server is using port 67 ResolutionRun the "nestat -abn" command to find the...
View ArticleRe: PXE-E53: no boot filename received - when trying to PXE boot to upload a...
Unfortunately, I have nothing running on port 67 or neither the core server nor the PXE rep (should be netstat not nestat) Active Connections Proto Local Address Foreign Address State...
View ArticleInterl PRO 1000 driver for WinPE
The PXE boot Menu is hanging on IP. The network of Lenovo laptop is Intel PRO/1000 LAN Adapter Software but it doesn't have a vista version. i tried W7 it didn't work. I've tried to inject Vista driver...
View ArticleRe: Interl PRO 1000 driver for WinPE
What version and patch level of LANDESK are you on?
View ArticleRe: Windows 7 crashed after sysprep
When you run sysprep /generalize /oobe, you are "cleaning" the image of the driver, so it cant load the storage driver (even on the same machine). You can force sysprep to leave the drivers, but that...
View ArticleRe: Interl PRO 1000 driver for WinPE
Make sure when you add the NIC driver to the WinPE image you use the x86 version. And depending on which version of LANDesk you have, you may need the Windows 8 x86 driver. -Tracy
View ArticleRe: Windows 7 crashed after sysprep
Hello, I have been busy this morning so didn't get a chance to update this post. I found the issue. I included a bunch of AHCI drivers from different manufactures in the HII installation which...
View ArticleClik here to view.
Re: Windows 7 crashed after sysprep
Did any of these answers help? If so, please mark helpful or correct.
View ArticleClik here to view.
ImageX deployment with OSD Deployment
I am able to capture and image and deploy an image using ImageX but after the image is deployed we end up with 2 OS boot options. Is there a command that we need to add to the advance script so it will...
View ArticleRe: ImageX deployment with OSD Deployment
The multiple installs must be in the image you are using. You will most likely need to rebuild your image machine and make sure to use advanced options and format the drive before the OS install
View ArticleRe: Interl PRO 1000 driver for WinPE
Dave,i'm using LANDesk 9.0 SP2 (WinPE 2.0). Tracy,the issue i'm facing is that Lenovo doesn't provide windows vista driver for the network adapter i have.i tried to inject a driver from intel website...
View ArticleClik here to view.
Re: ImageX deployment with OSD Deployment
redrider1940 is right, it could be down to an issue with your source machine. I've also seen this from "clean" images. If you run bcdedit in Windows it will return details of the boot manager and...
View ArticleRe: Interl PRO 1000 driver for WinPE
ldm-lb, You can check what version of drivers you need here: http://community.landesk.com/support/docs/DOC-27542 The WinPE version you are on is not listed on the page, but subsequent versions are...
View ArticleRe: Interl PRO 1000 driver for WinPE
David, You are going to continue facing this problem by using something based on Windows PE 2.0. I would definitely recommend upgrading to at least LDMS 9.0 SP4. Ideally you should look to upgrade...
View ArticleRe: Losing drivers and partition sizing on OSD deployment
Well I tried doing the deployment using sysprep OOBE generalize and the partition problem went away. As well all the drivers remained intact except for video.
View ArticleRe: Interl PRO 1000 driver for WinPE
+1 to what David said. You are going to be in a work of hurt until you update your version of WinPE. -Tracy
View ArticleClik here to view.
Re: PXE-E53: no boot filename received - when trying to PXE boot to upload a...
If you don't have any service running that uses UDP port 67 then it means there are no PXE representatives installed in your client node neither in your core server (at least there should be one in the...
View ArticleRe: PXE-E53: no boot filename received - when trying to PXE boot to upload a...
I ended up installing the PXE rep on my Core Server, even though that is not suggested.
View Article