I don't need IT, ipads fuck ralara every day (IT thread)

[halbarad]

Fuck this sccm PXE boot. Reinstalled WDS and PXE service point (WDS had a bunch of stuff configured and images set up and everything I was reading said that it shouldnt). Things were going well, everything seemed to install fine but then when testing get some annoying abortpxe.com error. Google shows a lot of fixes for that which I try and seems to fix it and instead I get some other error at the same stage. All seeming to ask for admin approval before the PXE download will continue, so I dig through a pile of more links and posts and can't find any solution to this nor any setting that I could possibly have put in place to require approval when trying to PXE boot an unknown computer.

Thinking about contacting some of the other schools in the area who have the same system and finding out how their's is set up to try to work out what else I'm missing.

[Liare]

abortpxe.com is very good to get Hal.

that means your service point is working, it's talking to to WDS and it's talking to the SCCM services and the database, it basically means everything is working EXCACTLY as designed.

you are just running it on a system with no task sequence assigned to it, dont forget that WDS is a peice of utter shite, so if you get a abortpxe.com boot on a system it will remember that for about 30 minutes, regardless of any changes you make in the console, unless you restart the WDS service.

do you want some decent links to "dummies guide to SCCM" type materials ?

though, in all honesty you should be telling your employer that you need some fucking certification, its dark magic, voodoo and human sacrifice rolled into one until you get some experience with it, it's incredibly newbie hostile.

configuring a slackware from the bottom up, compiling as you go is friendlier than SCCM, at least slackware has decent documentation accessible without knowing the secret rites and handshakes SCCM requires.

[halbarad]

abortpxe.com is very good to get Hal.

that means your service point is working, it's talking to to WDS and it's talking to the SCCM services and the database, it basically means everything is working EXCACTLY as designed.

you are just running it on a system with no task sequence assigned to it, dont forget that WDS is a peice of utter shite, so if you get a abortpxe.com boot on a system it will remember that for about 30 minutes, regardless of any changes you make in the console, unless you restart the WDS service.

That's what I'd read but it was trying to work past that to actually booting into winPE.

do you want some decent links to "dummies guide to SCCM" type materials ?

Would love them. Just got a photocopy of the SCCM teaching book thing for the certification (no idea where it came from).

though, in all honesty you should be telling your employer that you need some fucking certification, its dark magic, voodoo and human sacrifice rolled into one until you get some experience with it, it's incredibly newbie hostile.

I'd love to get more certifications but it's a little difficult at the minute to even get money to pay for the University degree I'm working on that they agreed to pay for. I'll still try to get some money out of them to do it if I can. There is only 2 of us in the place and the other person is currently working on fixing our GPOs to how they used to be (or at least sufficiently locked down).

[Liare]

to get it to boot to winPE you need to create a collection, advertise a task sequence to said collection, and make the system a member of that collection, and assuming above caveat about WDS being a bag of utter dicks, shake for 2 minutes and hey presto, PXE boot to WinPE!

it wont give you a PXE boot unless the system is a member of a collection with a boot enabled task sequence advertised to it.

i will dig around for some of links i tend to use, cant be bothered today, hope you dont mind that (and if you do, kindly take a hike off something really really tall)

also, dont your employer pay for your work related education ? it's pretty unreasonable to dump new responsibilities on people without up-skilling them, but then i live in the "socialist paradise" that is Scandinavia where that's the norm. (sorry if im rubbing it in here )

[halbarad]

to get it to boot to winPE you need to create a collection, advertise a task sequence to said collection, and make the system a member of that collection, and assuming above caveat about WDS being a bag of utter dicks, shake for 2 minutes and hey presto, PXE boot to WinPE!

it wont give you a PXE boot unless the system is a member of a collection with a boot enabled task sequence advertised to it.

Had that set up to Unknown Computers collection but wasn't quite working. I'll probably set up a collection for deploying images and add/remove PCs as needed.

i will dig around for some of links i tend to use, cant be bothered today, hope you dont mind that (and if you do, kindly take a hike off something really really tall)

I'm not back in work till Monday so it would just be some "light" reading for the weekend, I'm in no rush for it so take your time.

also, dont your employer pay for your work related education ? it's pretty unreasonable to dump new responsibilities on people without up-skilling them, but then i live in the "socialist paradise" that is Scandinavia where that's the norm. (sorry if im rubbing it in here )

To some degree they do, but budgets are limited and since I'm not a teacher the school generally prioritises them over us lowly support staff.

[Liare]

yea, but if the computer you picked to test with is previously known, it wont be a unknown computer now will it ?

i have multiple collections configured to handle OS installations because i let the users do it themselves when they request it (and provide a reasonable cause for it), each collection handle a single task sequence, with only the unknown computers one handling everything (and that's only accessible if you come from the IT subnet, bitches!) and i then add the systems as required, old computer entries are marked as obsolete when the re-installation is done so there's no fuzz beyond adding it to a collection.

i have to get around to do some powershell scriptlets that people can just execute at some point, but right now the only person fucking with SCCM is me, and i prefer the console despite its incredible level of shittiness.

you're making all the rookie mistakes here, dont worry about it and feel free to ask in this topic, i know most of that product by now and can almost make the fucker dance when i want it to, and many of the other crybaby posters know it almost as well or better.

[halbarad]

Got it set up to deploy to a specific collection for image deployment. Discovered that there is a tiny window when I have to hit F12 again to boot into winPE. Once I get into it and try to run a task sequence it's stopping due to not being able to access the resources on the DP but everything is set up correctly. All the relevant packages and the image are on the right DP and checking the folders shows them in the right place and definitely shared.

[Itiken]

i gave up on PXE booting / Biilding on SCCM ages ago.
Pushing out gold / pre-installed images via WDS is faster and more reliable in my place, then you simply deploy department specific software on top of it with SCCM.
Makes life so much easier.

Regarding that error though, it's saying, i think, that the machine is connecting ok but the GUID is not recognised.
Is your task / build / deploy sequence advertised on the "unknown computer" collection?

[Lana Torrin]

Got it set up to deploy to a specific collection for image deployment and I'm not getting the abortpxe error. Getting something else instead.

Going to test it on another machine as well to see if happens there as well.

WDS? Isn't that the standard waiting for approval message? Did you try approving it on the WDS server and hitting F12?

[halbarad]

Just edited my post with the updated details. I can get into winPE now but it's not running task sequences as its claiming resources aren't available.

[Fachiri]

Fuck troubleshooting iPads and all other iOS devices. That is all.

[halbarad]

I love finding random documentation that no one seems to know about. Found a random word file named capturing and deploying images, hidden a few levels deep in our admin share that I recently got access to. Turns out they used wds for image deployment and not sccm. Might have to go with that as it's a bit easier to use (at least from the deployment side) but I'm not sure what the configuration side is like.

[Liare]

you're halfway there Halbarad, cheer up. the hard part is done now.

one or more of your task sequence packages are not deployed properly, go trough them and make sure their status is correct, its located under "package status" note that even if your package has no contents (some of my software packages has no content, there are several cases where the build in "run command" is not sufficient, such as chaining specific commands together) it can and will whine about that, also keep in mind that Windows PE is severely limited, i typically reboot out of it as soon as i can simply because the full OS can be managed as part of the task sequence, and is functionally identical both in terms of what you see and what you can do.

be sure to enable command line support see the image.


(yes, there's a box missing, no i dont want to let it show since it tells you where i work, and i dont want that info to float about)

that will give you a command line inside Windows PE when you press F8, and access to all the tasty tasty logfiles that generates, helping any and all troubleshooting. (get Trace32 from the SMS/SCCM toolkit, it will make reading those so much simpler)

once configured, a SCCM based image deployment is less annoying to manage than a WDS based one, but you have to get used to the idiocy inherent in SCCM for it to really "work"

[Snake]

Got a weird outlook issue that I'm stumped on.

We are on a exchange 2010 Outlook 07 environment. I have a user that whenever he goes home and uses the VPN he gets the need password prompt in outlook which is fairly normal. However the issue is that it doesn't give him the dropdown to enter his domain credentials, he just gets Insert "Smart Card" and "APNS certificate". The weird thing is that when he is on the domain network it works properly with credential pass-through.



Ideas?

[Lana Torrin]

Just edited my post with the updated details. I can get into winPE now but it's not running task sequences as its claiming resources aren't available.

Remember its not on the domain, so you need to make it an open share.. Or add domain details to your script..

WDS was a bitch to get working the first time I tried it but once its up and you have a working unattended file its awesome.

[Liare]

Just edited my post with the updated details. I can get into winPE now but it's not running task sequences as its claiming resources aren't available.

Remember its not on the domain, so you need to make it an open share.. Or add domain details to your script..

WDS was a bitch to get working the first time I tried it but once its up and you have a working unattended file its awesome.

and this is why WDS is utter shite.

this is how the pro's roll it.

why are there multiple network settings options ? because it's a single task sequence to handle both lappies and desktops on our public facing n0tw0rk, and regular workstations and desktops go into seperate OUs. (and yes, we have permission from VMWare to use their player that way)

why am i using separated tasks instead of loading everything into a TS variable and executing it from there ? because that's confusing as fuck when somebody not initiated into the darker arts view it.

[EntroX]

so a dell r620 i installed like 2 weeks ago needs a new dual-port card for our iSCSI environment (it seems the broadcom that came with it is acting up) and i had to go replace it on friday, a co-worker of mine said he was going to be around the area we do our colo in so he said he could do it (he's in charge of networking and telephony) so yay n1 i dont have to drive downtown.

he calls me on friday that the server wont come out from the rack but its OK cos he's going on saturday to finish the cabling for our 8th rack and is bringing someone and they can take the server out.

they failed to take it out

[halbarad]

I decided to set up WDS to deploy the images, we've already got all the files and just needed to spend a bit of time configuring WDS itself (which didn't take long thankfully). It was also kind of decided for me since the Network Manager and the other technician we have don't really know much about SCCM (and really don't want the other technician messing on with it).

I'll set up a small test environment to try and get SCCM working like this and then sometime in the next holidays I'll go live with it.

Thanks for all the help guys and I'd appreciate any SCCM guide links you have as we are still using it to deploy software.

[Liare]

daww..

people not using it like it's supposed to be used makes me a saaad panda.

i was a bit busy at work to dig trough links for you, will do later Hal.

[halbarad]

daww..

people not using it like it's supposed to be used makes me a saaad panda.

i was a bit busy at work to dig trough links for you, will do later Hal.

I'd love to use it like this but I don't trust the other technician to not screw something up (he's generally out in primary schools fixing small problems they have and not touching anything important) and the network manager tries not to do too much with it since he is more familiar with other systems we've used in the past.