PXE "Problem", Missing Things in the main console & maybe a bug?

[huberj]

Hi anyweb,

 

first of all i would like to congratulate to those fantastic guides - according to them i have been running a whole sccm2007 structure and were easily able to migrate to the new 2012 version..everything is running fine so far, but i have 2 little "problems" and hope you could help with fixing them.

 

all of my clients are set to pxe-boot as first and hdd-boot as second boot option in bios - so i am sure that i can always deploy operating systems.

 

when i compare the old 2007 version to the new 2012 i realized the following differences

 

2007: my clients always connected to wds - when there was an anouncement for them, they loaded it(pxeboot.com) and if not the continued with booting the installed windows(abortpxe.com)

 

2012: the clients need a lot of time to boot if there is no os-deployment for them - after that (about 1,5 minutes) they are continuing with booting the windows but there is no abortpxe.com loaded. thats annoying for the users to wait that long time (and most of them dont know, that they can abort that wds-search by pressing esc)

all of the files (abortpxe.com, pxeboot.com, pxeboot.n12 and so on) are listed in the right directories. Is there any setting that the clients are booting faster and load that abortpxe.com file?

 

my seccond "problem" is that i am missing "Systemstatus - Deplyomentstatus" (I hope this is the right translation for that, because i only have the german values, but i have a picture systemstatus.png of that part i am missing ). i liked that feature, because it showed depoyment problems especially in tasksequences, so i were able in all of my cases to fix the problem with the silent parameters i am using for my deployments. was that feature kicked out by microsoft, or do i only need glasses because i just dont found it?

 

 

last but not least another small problem i could fix with a workarround - but this is not very satisfying

depending on the whole environment i am working in, i have to set the dns-servers manually during the os-tasksequence, because the dns-servers my clients are getting through dhcp are not the same than those from my trusted-domain where the sccm is running.

when i am using the part "apply network settings" and add my dns-servers there, they dont work for windows 7 (not in sccm2007 and not in 2012) - i tested it on 2007 with XP (working) and win7 (not working) and hoped that this will be fixed in 2012 - but it dont seems to be fixed :/

do you think is this possible? i think that feature is not that difficult to understand, so i dont think that i made anything wrong? only when i am using a command line with a netsh-command the dns servers were set right.

 

thanks for helping

 

 

[si124]

Sorry, did you solve the problem?

2012: the clients need a lot of time to boot if there is no os-deployment for them - after that (about 1,5 minutes) they are continuing with booting the windows but there is no abortpxe.com loaded. thats annoying for the users to wait that long time (and most of them dont know, that they can abort that wds-search by pressing esc)

all of the files (abortpxe.com, pxeboot.com, pxeboot.n12 and so on) are listed in the right directories. Is there any setting that the clients are booting faster and load that abortpxe.com file?

 

I have exact the same problem!

[huberj]

hey si124

 

sorry for answering that late.

i "solved" that problem by creating an EMPTY!! dummy-tasksequence.

 

that ts is announced to a system group containing every known computer (clients & servers) in my network with the setting "ALWAYS execute the program"

with that ts the systems are starting faster, because they "abort" the pxe-boot-request after about 10-15 seconds

 

its not beautiful, but it works because the clients are getting that announcement every time they boot (which is much faster) - but there are no instructions in that ts, so the client has nothing to execute and continues with booting from the hard disk