Failed to Get Client Identity During ISO Boots - PXE Boots Work Fine

[BzowK]

Hey Guys -

In our environment, OSD Task Sequences are usually run in the PC Lab by booting to PXE. Even though the PC Lab is 10 feet away from me and on the same local network, they are on a different subnet which is the only one set up for PXE booting. When starting here recently, I was told that to run OSD outside of the PC lab I'd have to boot to ISO. Fine with me.

The Issue

The problem is that every time I try to boot to ISO, I get errors and the process fails right before I can even see a list of Task Sequences. I'm using the same boot image that's on PXE, though. We do use SSL and re-created the ISO again this morning using the correct cert and password but no change. Below is a clip from the smsts.log.

I've searched online, but so far haven't found a solution that works. This issue has been going on since I started which was a couple of months ago. I've tried different systems including ones fresh out of the box which haven't ever been on the network here.

Known Solutions That Didn't Work

Here are the solutions I've found online plus a couple of things I tried plus their results when I tried them:

- BIOS Time / Date is Incorrect - I verified that they were correct plus was able to boot the same system via PXE without changing anything and it worked

- Check IIS Logs - I checked them on the Primary as well as the local DP. Didn't see any issues. Restarted both last night anyways. Still have issue

- Tried creating ISO using Default Boot Image instead of custom one. Same result with each. Both pull IP info

- Attempted booting to ISO when connected to the subnet where PXE works - Same result

Any Ideas? Thanks!

[anyweb]

that's one day off, was it taken today ?