Brokered Request at while running Scripted OS install
TDLNZ
November 8th, 2009
Hi all,
Can anyone help me with this error
When I executed the scripted OS install on a client PC, it booted into WinPE, the agent connnected to the DS server, the client PC will sit there doing nothing Unless I choose to continue the job from the console. There is error on the job. Please see the attached screen. I have restarted the PEX services, reboot the DS server. it happen to every PC that I run the script. Please help. I want to install OS with anyone intervention
Thanks
Tony
KB Article
Hi Tony,
Is this issue across the board on all hardware, or has this issue just emerged recently for a particular model? There is an Altiris KB Article 26043 which looks like front runner for your issue.
Could it be that this computer has multiple drives (or a multi-USB card reader) which is preventing the F:\ Drive mapping? If so, follow the KB to move your F:\ mapping to something further down the alphabet. For example, I use M:\ for the deployment share.
Kind Regards,
Ian./
Ian Atkin
Senior Developer for the ICT Support Team,
Oxford University, UK
Delete and recreate the job
I had the exact same problem with one of my scripted OS install jobs. I have no idea what is causing this error, but deleting and recreating the job solved the problem for me.
Responce from other post
I posted a responce from my other post that you found but I will post it here for others having the issue.
When I was having this problem I believe I ended up just remaking the Unattended.txt file from scratch and cleaning it up. Try adding bits and pieces of your Unattended.txt a little at a time. I think that is what I ended up doing and in the end everything worked or maybe I forgot to do the part that was causing the problem. I did use the SOI to create Unattended.txt and when I was trying to fix the brokered request problem I re-did the unattended.txt file using as little as necisary in the file. When that worked I started adding peices little by little until everything ended up working anyways. So I am not sure exactly what I did to fix it, or I just missed something that I didn't need anyways.
@ Spazzzen Agreed -recreating
@ Spazzzen
Agreed -recreating the internal scripted OS install job might work if its gotten corrupted somehow. This error seems to be a general "can't find referenced resource" error. So, it need not be limited to drive mappings. If I'm gonna paraphrase KB articles, I guess I should so so accurately!!
Kind Regards,
Ian./
Ian Atkin
Senior Developer for the ICT Support Team,
Oxford University, UK
Not the job
I didn't mean recreate the whole job, just modify the unattended.txt file that the job is using. IE the section "Answer File Setup". I first put everything I needed in there, to remove outlook express, remove games, driver locations, display settings... a bunch of stuff to automatically configure the windows install. That is when I got the brokered request. So I went back and just put in the ProductID and a few other things just to see if it would get to windows. When that worked, I started adding things bit by bit in that section until everything I needed was working.
Would you like to reply?
Login or Register to post your comment.