Search the Community
Showing results for tags 'hp'.
Found 3 results
I am having issues imaging newly acquired PCs in our office. The EliteOne 800G5 AiO, and the HP EliteBook 840 G6 Laptop. When deploying an image using WDS, the image seems to install without an issue, but when the PCs reboot to prepare for the sysprep/first boot phase, I receive an error on both the AiO, and Laptop. (see album link for pictures of screens and descriptions). It seems the laptop downloads a base image from HP using the HP Sure Recover feature in the BIOS, but the AiO does not. After disabling the HP Sure Recovery feature in BIOS on both the AiO and laptop, imaging works fine. I tested the same image and answer file on a HP EliteOne 800G4 (with HP Sure Recover enabled by default in BIOS) without any issues or errors. Has anyone else had issues imaging these model PCs without disabling HP Sure Recover? I cannot go into the BIOS for each individual PC to disable this as we move a lot of PCs through our lab. Any support on this will be greatly appreciated. Album for all screenshots and descriptions for each: https://imgur.com/a/rIpGeFF
I am able to image with no issues, and the driver pack is applied without issue. The problem is that we use HP Softpaq Download Manager (SDM) installed on each machine to verify that drivers are up to date. The most recent drivers are being installed in the driver pack, but SDM does not show the drivers as installed. How can I get it so that SDM shows that the drivers are installed?
We are running a trial of SmartDeploy, and have hit a snag. I'm testing with an HP Elitebook 8440w. After creating an image and deploying with either a Default.PPK that includes the specific model, or using just the model specific PPK, Windows 7 Pro 64 bit deploys fine for the most part. There are not any devices without drivers, most everything seems to work as it should, except Wireless. When I attempt to connect to a wireless network, I am told there are no connections available. I know there are definitely wireless networks present and visible. In fact, before deploying the image, this very notebook was connected to one of the networks. Even if I go ahead and manually put in the wireless info, no luck. Now, I've seen this problem before with HP computers. We've been using model specific images in the past few models. Basically when the image is built on one system, it works great, but when the image gets deployed to another system of the same model I got the same result as above. The fix from HP required us to rebuild the image from scratch, being sure to install the HP Software Framework, and the HP Connection Manager. Now, I've attempted to load those within the VMplayer image, but the packages require that HP hardware be detected. We also found in the past, that the packages appeared to need to be installed before Sysprep runs. Installing after the fact did not fix the problem on the HP images. Another thing I did was run the image setup from our OEM disc for Windows 7 from HP. I'm about to create a new vm from a Volume License disc to see if that is a factor.