Jump to content
DeployCentral

WM-Martin

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

WM-Martin's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. I figured it was something as such. Perhaps a clarification on the upgrade steps might help with that for anyone else. I will take a look at that soon. I guess I will have to reinstall the client on any new endpoints I've imaged as well.
  2. Hello, Are I believe I have followed the steps to upgrade from v2 to v3, but I have yet to uninstall v2. I was kind of hoping to see images being done via v3, but it looks like they are still pulling from v2. Or at least the version information while imaging seems to indicate its still using v2. We are using WDS to enable PXE to pull the image, is there anything that needs to be done to WDS to make sure its pulling the right SmartPE or will it just automagically do that after I uninstall v2? I hope my question makes sense.
  3. I will make another attempt with the log cleared to see if I didn't screw something up in the process and give it another shot. If it fails again. I will open a ticket and submit the logs.
  4. That's what I did and it doesn't appear to have worked.
  5. Hi there, I am struggling to get the Lenovo Thinkbook 14s Yoga imaged. I created offline media with the available platform pack, but it cannot see the drive to image. It only sees my USB drive. Is there something I am missing here? I'm guessing it has something to do with Intel VMD. I've never worked with it before, but have seen that it can be a problem when imaging as Windows PE may not recognize it. I assumed thats what the platform pack would resolve. Thanks for any insight. EDIT: I got the driver working and can see the drive, but it would appear the drive is now Drive 1 instead of Drive 0. Any way to rectify this easily? Cheers!
  6. I would agree with the sentiments above. Thanks for the suggestion about VirtualHere, it worked well. I think that it would be nice to have the ability to create a single bootable ISO.
  7. Is there a way to configure the device renaming process to use the default WMI query of the serial name, but to cut it down to something like the last 4 digits and then include a prefix dependent on the machine type? For example: if it was a Lenovo T580 vs an HP 9480m to have one renamed to T580-ABC and the other named 9480-XYZ? Hopefully someone can help me out with this. Its not the end of the world, but because of this we aren't using the automatic domain join feature currently. Also I'm not sure, but I don't think the "use existing" name is currently working for us. I will try to test a bit more, but that would certainly help us with existing machines.
×
×
  • Create New...