Connection closed session terminated.
Updated: 21 May 2010 | 6 comments
This issue has been solved. See solution.
Hi,
Im getting the above error when i boot a machine into windows pe and it is trying to connect to Altiris, any ideas?
Thanks
Dan
Discussion Filed Under:
Comments
Have you had the same
Have you had the same hardware boot using the same winpe image.
could be a network driver issue, run devcon to list the hardware and make sure the drivers are installed in the boot image
re: Connection...
Generally when you see that message, the network drivers are fine (as it is saying it connected just fine but is disconnecting). Does it reboot after this? My guess is that it checked into the console and found that it did not have anything to do (no jobs scheduled). If you did have a job scheduled, make sure that it is set to use the correct automation environment. If it doesn't think it needs to be in WinPE and you are in WinPE, it's going to reboot and try to get to whatever automation environment it is expecting. You might play around with that setting on the job if that is the case. Maybe change it to WinPE Auto instead of just Auto.
-B
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Yes it is just rebooting
Yes it is just rebooting after it goes into winpe, it picks up and ip address in there so i am assuming the network drivers are ok.
There doesnt seem to be any jobs scheduled for that machine and i cant see it in the DS until it has booted into the windows env and had the agent installed on it. Once it has had the agent installed from within the OS then i can see it in the DS to assign jobs to it.
Thanks for the replys
Dan
Initial Deployment
If there isn't any jobs assigned to it, that would explain why it reboots. If these are new machines that the console does not know about yet and you want them to stay in the automation environment so that you can schedule a job, you might set an initial wait job. This way, any new machines that boot to WinPE automation would be issued a wait job automatically, which would make the client show up in the DS console and allow you to schedule other jobs.
-B
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
That sounds perfect, i have
That sounds perfect, i have just created the Wait job in the DS ready to deploy to a machine.
How can i schedule the 'wait' job to a machine that isnt showing in the DS?
Initial Deployment
In the lower left quadrant there should be an "Initial Deployment". This is where you would schedule the job. This would automatically schedule the job to run on any machine that the DS console has never seen. You can do multiple jobs here (menu) if you want as well.
In our environment I have it set to ask the technician if they want to deploy the sysprep image or back the machine up. Once the machine is in DS it won't look at the Initial deployment anymore though, but at that point you can schedule the job from the console as the machine is known in DS, or you can delete the machine out of DS to allow for the Initial deployment job to take effect.
-B
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Would you like to reply?
Login or Register to post your comment.