Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

1
Company network, new drive, Windows PXE/image, BitLocker on drive boot but not network boot
Post Flair (click to view more posts with a particular flair)
Post Body

Hi y'all - this doesn't make much sense to me, and it's fickle to search for, so I figured I'd ask in here instead.

I reinstalled a bunch of company computers today (after switching their old drives for new ones), and they will only boot completely into Windows if I leave the NIC as primary boot device, which makes PXE run for a bit and then move onto the Windows installation. If instead the drive is set as primary, BitLocker comes up and demands to be unlocked (which I can't do because that's another department and I couldn't be bothered to involve them).

Lots of other machines have been reinstalled in the same way, and BitLocker is not a problem there (the drive can be chosen as primary without issue).

Does this sound like a known problem of some sort to any of you? The machines are some years old, so maybe something ran out somehow? Only, they work fine via the PXE "detour", so it's not like they've been tossed off of the company network completely. They work completely fine - as long as they're not booted from the drive...

Any tips? :)

Author
Account Strength
100%
Account Age
12 years
Verified Email
Yes
Verified Flair
No
Total Karma
220,162
Link Karma
17,034
Comment Karma
202,853
Profile updated: 1 day ago
Posts updated: 9 months ago

Subreddit

Post Details

We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
6 years ago