Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Last week
  3. We use Symantec Endpoint Protection on everything. SEP hasn't been interfering with the wired desktop clients so far, but the laptops have a slightly different set of policies. I ran a couple more tests. First, I put the test laptop in the same SEP group as the successful clients. Next, I uninstalled SEP completely. Unfortunately, I got the "unable to create the ramdisk device" error each time again. I'll see if I can find another ProBook 450 to test on....
  4. Do you have any anti-virus or other security software running on the Probook? That would be the first thing I'd look to disable and re-try.
  5. Hello everyone, I have a test laptop, HP Probook 450 G3, running on Wifi, which I'm using to test deploying Windows 10 to clients on WiFi. Using a deployment package that was successful on HP Compaq Pro 6200/6300s, we're getting an error in the event logs during deployment: Log Name: Application Source: SmartDeploy Console/Client Service Date: 4/16/2019 2:48:46 PM Event ID: 0 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ------------------ Description: Exception: Unable to create the ramdisk device in the BCD. at Common.SmartDeploy.Managers.BootManager.#R6f() at Common.SmartDeploy.Managers.BootManager.ManageBootWim(Boolean manageBootFiles) The laptop never reboots or starts the deployment. As far as I can see, the contents of C:\SmartDeploy on that system are the same as on the successful ones. I figure it's either WiFi or something specific about that laptop model. SD Enterprise is on the latest version (2.0.3040). Does this ring any bells? -j
  6. Earlier
  7. Thank you. I will reference that article. I appreciate the help.
  8. Hi vlee14, Please refer to this: https://docs.microsoft.com/en-us/surface/ethernet-adapters-and-surface-device-deployment Based on this, your dock and dongle should work. You won't need to disable SecureBoot.
  9. Hello. Out of the box that was checked which I left alone. I've also disabled secure boot. Thank you.
  10. I am still a trial user. How do you connect a new computer in the field to the Console computer ? The new computer has no OS , just bare metal.
  11. Hi vlee13, I found that with using PXE boot, you still need to enable the "Enable boot from USB devices" option in the boot options list. Did you by chance do that?
  12. Hello, I just picked up a Microsoft Surface Pro 6 for a trial run. I'm attempting to image via PXE. BIOS has been changed and secure boot has been disabled. I'm still unable to boot to PXE because my thought is the USB dongle (3rd party) gets no network traffic/activity until the OS starts or finishes loading. Anyone have success with Surfaces and PXE minus a dock or MS specific dongle? Thank you.
  13. Thanks! Will do that when I'm back in the lab tomorrow.
  14. Adding some additional information "an error occurred while apply the image" happens when SmartDeploy starts applying image 2 of 2 and almost immediately cancels? Applying image 1 of 2 worked fine.
  15. Then please open a ticket and it will be sent to you that way.
  16. Cant download attachments in this forum.
  17. Please download, rename to .vbs, and run the attached script on one of the affected systems, and then email the file that's created to support@smartdeploy.com, detailing this issue. We'll need to dig into this beyond forum replies to investigate this. SmartDeploy_Support.txt
  18. Jeff, The driver packs for the 600 G3 and G4 called HPElitePro600-800-G3 or G4. This PC was SmartDeployed and so are the other ones as well. Wifi adapter driver:
  19. Alright well we can't re-produce that error ourselves. I'd file a ticket with Support. Hopefully it doesn't require shipping us a unit. I don't see an HP ProDesk 600 G4 platform pack, only a G3, as what's in your screenshot above. You deployed to a 600 G4, with the client install option? Or just installed the client? Can you share version information on the wireless adapter driver?
  20. I am on a 600 G4 device, but yes. It is occuring on those devices.
  21. I assume this is only happening on the HP ProDesk 600 G3 devices?
  22. I updated the server to 2.0.3040 and the client on my PC has been updated as well. I am still seeing the errors.
  23. I notice you're on version 2.0.3030. Would you mind updating your console, and watching to see if the issue persists after the clients update themselves to 2.0.3040?
  24. It appeared that the mps and the mps.xml file weren't in the Updates folder of the package they send. I confirmed that if they are, the /adminfile argument shouldn't be needed. I also discovered that I could not add the .mps.xml as an individual file to the Updates folder, getting an error about the path. I had to place the files into the Update folder, and then re-add the entire Visio installation folder back into the spk. (I have alerted the dev team to investigate this problem)
  25. Aaron, Glad it works in your case. This issue doesn't occur with all imported WDS images, but we have seen it come up quite a bit.
  26. Google search reveals that OSX imaging is dead: https://scriptingosx.com/2017/10/imaging-is-dead/
  27. If it helps. I am running SD on Server 2012 R2 and using Windows 10 1809 images without any issues. We've imaged almost 160 computers with this configuration.
  1. Load more activity
  • Create New...