DalekSec Posted November 16, 2015 Posted November 16, 2015 Current state = Pulling my hair our Need to get a task sequence working to start imaging old staff laptops. I have done the following: Captured an image off a quick built laptop and made a task sequence around it Created new boot image with various network drivers for the laptop. PXE is switched on as we were imaging the new staff laptops over the summer (no problems there once we sorted it) Distributed EVERYTHING Doesn't boot into PXE says policy can't be found Any ideas what it could be?
Steve21 Posted November 16, 2015 Posted November 16, 2015 Did you deploy the Task Sequence to any machines? (e.g. All systems) And make it available to use? (not required obviously ) Steve
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 Yes I have, I deployed it to all 'Unknown Computers' But I can't see how this is the problem as the laptop doesn't reach the stage where I can choose a task sequence
supawat1 Posted November 16, 2015 Posted November 16, 2015 Have you "Clear Required PXE Deployments" by right click on All Unknown Computers Collections?
jamin100 Posted November 16, 2015 Posted November 16, 2015 Drivers missing from the boot image? Edit: ignore. Just read you've added drivers
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 Have you "Clear Required PXE Deployments" by right click on All Unknown Computers Collections? Just did it, no luck still. Plus all the PXE deployments are not labelled as 'Required' just 'Available' as we have a few different sequences
Steve21 Posted November 16, 2015 Posted November 16, 2015 Yes I have, I deployed it to all 'Unknown Computers' But I can't see how this is the problem as the laptop doesn't reach the stage where I can choose a task sequence We've had it before where they were deleted from AD, but SCCM has their account in it still, and as nothing is assigned to it it errors out. What's the state of the laptops in regards to AD/SCCM accounts etc? Is it in both or deleted in both? Steve 1
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 We've had it before where they were deleted from AD, but SCCM has their account in it still, and as nothing is assigned to it it errors out. What's the state of the laptops in regards to AD/SCCM accounts etc? Is it in both or deleted in both? Steve Yepp checked these swell. Its an old of domain laptop. I've had various looks in SCCM and even renamed the laptop to see if I could find it easier. Just checked AD its not in there either...
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 Going down the 'Create everything from scratch' route. Even though the Task sequence was brand new. The boot image was a copy of another wim, which I forgot about... So hopefully a brand new shiny wim will do the trick!
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 Still not working grrrrrrrrrrrrrrrrr!!!!!!!! Did notice the OS Installer wasn't setup right, have corrected it. still....not...working *Hits head on desk*
Steve21 Posted November 16, 2015 Posted November 16, 2015 Narrow this down a bit then, is it only this laptop that isn't working, or haven't you ever used OS deployments? Is it before you even get into the PXE boot? As in at the PXE boot/command line etc? Do you have multicast on, if not is the pxe boot on the same vlan as the SCCM server? Did you change the DHCP options for where it points to PXE boot from? Just trying to find out more infos Steve
supawat1 Posted November 16, 2015 Posted November 16, 2015 Can I see a screenshot of when it's doing PXE boot?
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 Narrow this down a bit then, is it only this laptop that isn't working, or haven't you ever used OS deployments? We used it over the summer for our new desktops and laptops. worked fine once setup Is it before you even get into the PXE boot? As in at the PXE boot/command line etc? Yes (see screenshot) Do you have multicast on, if not is the pxe boot on the same vlan as the SCCM server? It does detect the server but gets no further, we have very few vlans Did you change the DHCP options for where it points to PXE boot from? No that I am aware of
JoHimself Posted November 16, 2015 Posted November 16, 2015 What does smspxe.log say? Are there any status messages on the SCCM server? Can you add the machine back into SCCM manually? My thinking here is that if you can't add it back the machine might still have some remnants lurking around in the database somewhere. 1
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 What does smspxe.log say? I haven't checked, need to remind myself how to access these logs! Are there any status messages on the SCCM server? None Can you add the machine back into SCCM manually? The HDD I am using in the laptop has never been on the domain. But the rest of the laptop might of been at one time.
DalekSec Posted November 16, 2015 Author Posted November 16, 2015 IT'S WORKING!!!!!!!!!!!!! I think @JoHimself might be right in an aspect even though I have a new HDD in the laptop obviously the NIC is the same as is still assigned to the old laptop somewhere in SCCM.. Deleted the laptop once I found out which one it was and BOOM!!!!!!!!!!!!!!!!!!!!
supawat1 Posted November 16, 2015 Posted November 16, 2015 Have you got these options on your DHCP? option 066 = your Distribution Point /PXE IP Address option 067 = SMSBoot\x64\wdsnbp.com Within your WDS server, check whether PXE response to all client computers (known and unknown) is tick
Norphy Posted November 16, 2015 Posted November 16, 2015 Have you got these options on your DHCP? option 066 = your Distribution Point /PXE IP Address option 067 = SMSBoot\x64\wdsnbp.com Within your WDS server, check whether PXE response to all client computers (known and unknown) is tick You really, really, really should not be setting those unless your PXE Enabled DP is sitting on the same server as your DHCP server. If you've got a flat network, the WDS server will automagically get detected on boot. If you have VLANS, you need to set IP helpers to point to the PXE enabled DP. 1
ITGuyWestMidlands Posted November 16, 2015 Posted November 16, 2015 We had this on a couple of laptops. Must be an issue in their firmware. The dhcp options are OK as a temporary fix
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now