Jump to content
DeployCentral

sking

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by sking

  1. Well I'll be. Under preliminary testing, that seems to have fixed the issue. What I have to figure out now, is how it to make it work with the rest of the models that we work with. In your testing with the M93, were you able to add other network drivers to the platform pack to work with other machines or was its success limited to being isolated to the single set of ethernet drivers?
  2. So, after getting Lenovo's new 4th generation based Intel machines, I'm having some issues getting the keyboard and mouse to work upon starting up SmartDeploy. I've created a new BOOT.WIM with a platform pack from the M73 as well as a custom pack built with the M73's USB 3.0 drivers in the WinPE section. The second pack, and BOOT.WIM work sporadically - an issue I cannot figure out. The first BOOT.WIM, built from the unaltered M73 platform pack for Windows Deployment Services, does not ever work. It boots properly, and the SmartDeploy screen comes up, but the keyboard and mouse are no longer detected and no longer work. I'm not able to get any kind of log file or see where the issue is. Is there a driver for the M73 that controls the USB hub that is missing or is there a reason why a basic HID device would fail in the WinPE environment?
  3. Yes. More often than not, the problem comes from the platform packs downloaded directly from the website.
  4. After deploying over a hundred computers, this is the problem that seems to crop up the most. I'll download the platform pack specified for the computer models, or I'll have to make one, and then, after deploying the imaged and reporting that it was done successfully, the computer in question will start to boot Windows, then get a blue screen and reboot. Unfortunately, there is no way to record this, as it happens too fast to either get a picture of or write down the error code. It seems to be related to platform packs, as when I make alterations to the pack in question or make a new pack, it sometimes will fix the issue. An important note about the new packs is that they rarely contain the same drivers. And sometimes I stuff different platform packs into one pack, without the model differentiation that is possible and recommended to set up. This is normally what works the best. It's just time consuming and doesn't always work. Is there anyone that can shed some light on why this happens in the first place or a fix for it? I assume it's because of a missing driver or something, but it shouldn't keep it from booting in the first place.
×
×
  • Create New...