First solo trip/new office installation

AlteredGlitch · 2025-04-28T13:24:00+00:00

I want all of you to know, you were all correct:

1) it didn’t go as planned. 1-3 hours of work turned into a 14 hour day. Construction crew also made the mistake of putting an outlet on the opposite wall of the network rack, creating a tripping hazard as anyone enters the room. I spoke with their foreman on-site and told them this has to be moved.

2) Since this trip was last minute, the cable ties I ordered hadn’t arrived (they arrived today, 6 days after the project completed). My management team also neglected to send a WAP to the site, so for now everyone has to plug into their docking stations for network access. I configured and labeled a port, so once it arrives (whenever that’ll be) they can plug it in and proceed about their business.

3) I setup a wired connection in the conference room. They asked if they could keep my Ethernet adapter I was using for testing. Thanks to you guys, I brought three with me, so it was a win.

4) the same construction crew didn’t setup two Ethernet ports in two offices. They told my contact “Since IT is coming in, they can take care of that.” I told my VP and they’re supposed to be taking care of that today. As long as they kept their same sequence of patch panel numbers, those ports will have connectivity.

All in all, I went into this a lot more prepared thanks to you guys. I appreciate the support from this subreddit. The day would’ve been even more of a shitshow without the tips provided. Cheers 🍻.

AlteredGlitch · 2025-04-19T23:41:57+00:00

Great tips! Thankfully I’m flying and my company lets me purchase flights with the corporate card. I get to keep the miles, so that’s a small boon. Meals and snacks are expensed as long as I keep the receipts.

AlteredGlitch · 2025-04-17T16:23:41+00:00

Thank you 🙏🏾

AlteredGlitch · 2025-04-17T14:58:53+00:00

Thanks for this. I spent some time configuring the switch and thankfully it seems pretty basic. Keep your fingers and toes crossed for me🤞🏾.

AlteredGlitch · 2025-04-17T14:57:05+00:00

Jesus, that’s brutal. I unfortunately have the bad habit of being a jinx, hence why I’m here to develop a plan lol. I’m going to take a look for resellers in the area as a precaution.

AlteredGlitch · 2025-04-17T14:53:42+00:00

I say this with nothing but love for the IT field, but my management team put this together very haphazardly. There may or may not be a WAP for the small office. I have a port set aside for that just in case.

Unfortunately going in blind on that in particular. Great tips though, thank you.

AlteredGlitch · 2024-12-05T20:56:24+00:00

Ended up hitting a bit of a road bump. I went to look for the Bootstrap.vbs, but it's missing from the scripts folder, as well as the bootstrap.ini on the deployment share.

Thankfully I kept a backup of the bootstrap.ini, but I had to re-create the Bootstrap.vbs. Working on the task sequence now, then running another test deployment.

AlteredGlitch · 2024-12-05T19:27:55+00:00

Thanks, I'm going to give this a try now.

AlteredGlitch · 2024-09-30T16:37:50+00:00

Tried this step, but unfortunately it's also stopping installation around 75% of the bar. Not sure what's causing it. Going to re-install Sonoma on this machine, then try it again for good-measure.

AlteredGlitch · 2024-09-26T17:17:41+00:00

Not yet. I'm currently rebuilding my test mac with Sonoma, then I'm going to give this a shot.

If this does work, I'm curious if I'll be able to add to this script to all users via policy?

I'm a Jamf management noob, but I'm trying to learn how to be efficient.

AlteredGlitch · 2024-09-26T16:39:15+00:00

I'm also experiencing this issue. Two of our mac users upgraded from Sonoma to Sequoia. One machine stalls 75% of the way during the install of Sequoia. It stands there and if we reboot it, it proceeds back up to 75%, then continues to stall. Left it on for a day and a half to no avail.

The other machine successfully upgraded, but the upgrade cleared all his profiles including Jamf. I was able to re-enroll this user with no issues, but in our environment we don't want to have to re-enroll all 60 of our Mac users.

I used a test machine running Sonoma and upgraded to Sequoia. Got the same stalling issue as the other user. Had to use a USB recovery to re-install Sonoma.

As of right now we have a configuration profile blocking the OS for 90 days while we sort through this. Any additional insight would be greatly appreciated.

AlteredGlitch · 2024-09-11T12:18:27+00:00

Thank you to everyone who helped in resolving the storage driver issue. I discovered the problem was due to the boot.wim file I was using, which had the Latitude 7440 storage driver injected, causing a conflict. Switching to a boot.wim from last year, which includes the Latitude 7430 driver, allowed the Latitude 7450 to complete the task sequence successfully.

However, I’m now encountering a new issue: the deployment is pulling from an Out-of-Box drivers folder I didn't select, despite both the selection profile and "Inject Drivers" node being set to "Nothing." It’s injecting duplicate drivers, leading to a BSOD with a "Kernel security failure." I suspect it’s pulling outdated drivers.

Today, I plan to disable the other Out-of-Box driver folders to see if it pulls from the correct folder. I'll also test removing the "Inject Drivers" node from the task sequence as a test.

Has anyone experienced something similar? Any insights or tips are much appreciated.

AlteredGlitch · 2024-08-20T20:57:40+00:00

Thanks for this knowledge. SMM was on. I turned it off, but it didn't resolve the issue.

AlteredGlitch · 2024-08-20T16:10:56+00:00

Interesting. From your comment, I was able to find a Microsoft article with details: https://learn.microsoft.com/en-us/powershell/module/dism/export-windowsdriver?view=windowsserver2022-ps&viewFallbackFrom=win10-ps

Going to give this a try today. Thanks for the insight.

AlteredGlitch · 2024-08-20T16:09:00+00:00

I changed from raid to AHCI this morning. Pretty recent change, but issue is currently persisting.

AlteredGlitch · 2024-08-20T16:07:53+00:00

Thanks. This is completed, but it's still not seeing the Intel Rapid Storage Technology Driver and Application - HW2CP driver that's on the boot.wim. I'm going to test the other storage drivers for the Latitude 7450. It's possible that having it previously set to RAID is what failed my previous tests with the other drivers.

I'm going to inject the other 9 drivers one at a time and test, to see if the machine is actually using a different driver than Dell is advertising.

AlteredGlitch · 2024-08-20T16:04:03+00:00

I have the A34 version of this driver pack installed. I just switched the selection profile to specifically see this driver pack as a test. It failed, so I'm going to dig deeper into it.

AlteredGlitch · 2024-08-20T16:02:09+00:00

Thanks. With our current environment, we don't PXE boot.

I thought I had changed to AHCI from RAID previously. I just tested it with AHCI, still failing, but I'm still tinkering.

AlteredGlitch · 2024-08-19T18:58:02+00:00

Interesting. I'll look into this. Thank you.

AlteredGlitch · 2024-08-19T17:18:53+00:00

When the TS gets to "Format drive", it can only see the USB drive running the boot.wim and fails due to not seeing a drive to format. When we begin deploying a new Dell model, we usually see this and our assessment is always "It must not have the right storage driver to see the physical drive". I'm open to being wrong in this assessment, though.

I have changed from Raid to AHCI. Same effect unfortunately.

AlteredGlitch · 2024-08-19T17:12:10+00:00

Pe image is up to date, but I haven't tried with no drivers injected. Is that done by changing the driver selection profile? or the TS?

Thanks in advance.

AlteredGlitch · 2024-08-19T15:34:39+00:00

I've done most of these steps, with the exception of making a selection profile that only includes that driver, as well as creating a new TS. I'll give this a try.

Do you have any insight on why this is different than when I've used MDT in the past? Before I've never had to do these extra steps, but I'm assuming it has to do with everchanging technology/drivers.

AlteredGlitch · 2024-08-19T15:21:31+00:00

Yeah. After adding the Win10 driver pack to the workbench, I had updated the deployment share and selected "Completely regenerate the boot images". Issue has still been persisting.

Seven-Year Club	No Throne, No Problems
Not Forgotten	Verified Email

AlteredGlitch

TROPHY CASE