R Bond

Imaging some new Latitude 5420's from a USB stick. For naming, in the answer file, we call the SerialNumber from the BIOS then rename as needed. Noticed suddenly that post-imaging the computer name is pulling a leading "D" from somewhere. Thus, Service Tag/SerialNumber BBH45Q3 is DBBH45Q3. Checked the answer file on the stick and no reason sticks out. Checked the logs from one of the machines in question nothing sticks out. Tested on a Latitude 3410 and it works fine. Anyone run in to such a thing? Not HUGE issue provided I remember to remove that "D" when I'm renaming (we keep the Service Tag in the name), but awfully annoying. Thanks

Had a similar problem with our new Dell Latitude 5420's. Changed the storage. in the BIOS, from RAID to AHCI.

I've been imaging mostly with flash drives setup for office deployment. The image would work, answer file settings would work and a few of my app packs would install, but not all of them. I also, currently, haven't been able to deploy from console. Trying to get over to the site the server's on to test a little and rebuild my flash drives to see if/how things work and get back to support with what I find. Glad I'm not the only one.

I've heard from them. Thus far they checked my logs and didn't see an imaging event showing up in the logs. My server was a version or two behind, so I updated the server, rebuilt the answer file and deployment packages. Still having some issue so I want to get on-site, with the server, and try imaging on-site to eliminate the firewalls between where I am and where the server is. That where it stands for now.

So...got a new model laptop in the district. Latitude 5420. Downloaded the Platform Pack and rebuilt all of our deployment packages (console and USB). I have about 12 application packs as part of the deployment as well. I fire up a new 5420, jump in the BIOS and change from RAID to AHCI, reboot to USB drive. It will run through the imaging process, joins domain, installs a few of the application packages, but then just stops. Seems like it's the last part of the process (application packs). Always stops after the 4th (?) app pack. It seemed like maybe a chrome app pack issue, but I edited the .xml file and changed the position of the chrome installer (4th to 12th). Still stops installing after the same app pack. Then it will throw an Unrecognized USB device error continuously. I've tried 4 different flash drives and always does the same thing. I have the latest platform pack for the 5420 (I haven't tried these flash drives on another model yet, but I suddenly have 50 of these 5420's NIB to image asap), but also noticed when I run Windows Update (after imaging and after the app pack installs fail) there are a number of driver updates waiting. Any input would be appreciated. Apologize if I'm missing any important info.

Thank you Devon. After I posted this I wondered how often anyone frequented this forum and thought it may be a better idea to go through the proper support channel. Thanks Rick Bond

Question about the "Boot Media" option when creating a Deployment Package. I was assuming (hoping I guess) that creating a Boot Media Deployment Package to a USB drive would allow me to plug said USB drive into a newly unpackaged device (laptop in this instance), boot from that USB drive and the device would eventually (after a few minutes) pop up in the SD console and allow me to then deploy, from the server, from there. Is that not how it works? Looks like maybe said Boot Media (Flash Drive) will boot and start asking to pick an image and answer file and such, but from the client...

Looks like that was the case. Rebuilt from a 21H1 ISO and it seems good. Thanks very much. Rick

Been using SD for over a year now. A few times over that timeframe I've created new images (barebones Windows) to get up-to-date with Windows updates. Have had no problems deploying any of the builds. Last one was a 20H2 from like April and worked/works fine. I recently used the same ISO from that 20H2 build, built a new VM, got it all updated to 21H1. I rebuilt all the tasks, new answer file ... when I deploy it Windows is not activated when it's finished imaging. If I go in to the right screen and "troubleshoot" the issue, it activates on a digital license. I'm using the same MS key as my 20H2 image (which still works fine). It's a mild extra step, but I'd rather clean it up so it just activates. Any input would be much appreciated.

I honestly have no idea what version of SD we're running, but looking at the feature list I feel like we must have, at least, the lowest version necessary to use Message History. However any time I try to view the message history of a client it tells me it's not enabled and provides a link to buy software. Any assistance would be great! Thanks.

Thanks Jeff. I'll test another and if it happens again I put in a ticket.

Did anyone get anywhere with this issue? I'm now receiving the same message during image deployment and it appears the imaging process completes successfully after I click Ok.

That's exciting to hear such things may be coming up. We use Screenconnect onsite and the filtering options are fantastic and make things so much easier. Thanks for the quick response.

I show a lot of clients in the SD console that have updated driver packs available. Do I have to manually select them all to then push them all at once? No way to filter them based on ... well anything!? I feel like filters, in the console, would be a HUGE help.

Thanks very much. I'm changing some things around as I was maintaining two machines...won't get into why. Consolidating and will probably step through the OOBE, throw on the agent then image from console. Thanks again.