New imaging issues
After having set up a system with all components that we need, we want to take an image of that system in order to later deploy it to other computers. Therefore the first step is to run the "Prepare for Image Capture" task.
We select our OS System (Windows Server 2003 R2) and Product key, we use no credentials since we don't really need it to rejoin the domain, and we reboot to Automation.
When we run it, the task immediately fails and when I check the Log Viewer the error I can see is
SecurityCache.CurrentIdentityMembership accessed without security context data set
Even when we insert a password (which password do we need? the Altiris user password?), as soon as we "Save Changes" at the task the password disappears and the task continues to fail.
Where are we wrong?
Thanks in advance
Comments
Hi, it sounds like you are
Hi,
it sounds like you are running the task in automation environment?
The correct order is the following:
The prepare for image capture task only works in production, never in automation or pxe!
1. Boot server to production
2. Prepare for image capture with boot to pxe after it
3. Capture image
4. Ready
Is this your procedure? Do you have the Deployment Agent Plugin installed on the affected system?
Regards
Hello and thank you for the
Hello and thank you for the reply. Some points:
- This would indeed be the procedure we want to follow, but we need to have a successful Prepare for Image Capture first :-)
- How do I know whether I am running in automation environment and how do I boot the server to production?
- What are the credential I need to rejoin the domain? Or do I not need them?
- We have the Deployment Solution Plug-in installed on the system, is it the same?
Regards
Hi, The procedure described
Hi,
The procedure described is the way to get the succesful image.
The production environment is the normal boot (normally hdd boot) of an operating system, i.e. just starting your system!
The automation environment is the preboot environment, often this is a WinPE booted by PXE Services. Do you have a working PXE-Environment?
So just build a job with three tasks:
1) Prepare for image capture (within this task boot to pxe)
2) Capture Image
3) Reboot to production
Prior to get this running you have to integrate the deploy.cab into NS. This is needed for getting the sysprep running on Systems below Windows Vista. Refer to following thread on how to do this: https://www-secure.symantec.com/connect/forums/capturing-windows-xp-image For 2003 it's the same procedure.
The credentials for joining domain are optional, but if you want you must provide credentials of an account which is allowed to join computers to your domain, i.e. an administrative account of your domain. The mentioned deployment solution plugin is the right one.
Regards
Update
1. I found out where to Reboot to production but this task failed as well
2. I went to "Job and Task Status" of the Computer resource and found out that my tasks have the Status "Waiting for the agent to get the task". Don't know if this rings a bell.
3. I have set up a job with the 3 tasks but I figured I would try the tasks one by one first, is that ok?
I'll integrate the deploy cab into NS asap.
At first you have to
At first you have to integrate the deploy.cab!
The Reboot to production only works in PreBoot Environment! So you can check this only while beeing in PreBoot.
One by one testing is in this case not the best way, because of the different needed environments.
When you have integrated the deploy.cab and the deployment solution plugin is correct installed it will work.
The prepare for image capture task does nothing else as a sysprep job on your system with all consequences.
Regards
The deploy.cab had already
The deploy.cab had already been deployed, I just redeployed it.
Unfortunately at the moment I can't even run a simple Restart task, as if the Agent doesn't fetch the tasks. The tasks are sitting there waiting with the Status I mentioned above and then eventually they fail :-S
Regards
Maybe you should have a look
Maybe you should have a look on you client server communication. Try to send an even simple job to the system. When this works we can have a look on the next steps.
Absolutely agree and will
Absolutely agree and will revert.
Hello, we solved our problem
Hello,
we solved our problem with the Agent (apparently we hadn't set up the correct IP after a reinstall) and proceeded with setting up our imaging job.
The strange thing is that the "Prepare for Image Capture" task doesn't seem to want to reboot to the PXE Environment, it tries to reboot to Production instead. If we manually intervene, we can stop it, reboot to PXE and Capture the Image normally. But this means that we can't run the 3-task Job (Prepare for image capture - Capture Image - Reboot to production), since the job will break off at the end of the Prepare for Image Capture task due to the unsuccessful reboot to PXE.
Can it have something to do with the Boot Sequence of the Machine (HP350ML-G6) we are capturing the image from? Currently the "LAN" option is last in the Boot Sequence.
Hi, nice to hear that. You
Hi,
nice to hear that.
You must change boot order to get network as first boot device!
Regards
Ok, we have done this. The
Ok, we have done this.
The timeout seems to be too long, we are currently trying to find out how to set it.
timeout is too long - for network boot?
Are the users complaining that it sits at a black screen too long when they reboot? Is that the timout your talking about?
Thomas Baird
Endpoint Management Specialist
Remember to give a thumbs-up to any post that is helpful.
It notifies readers of the forum that there's useful information in that thread.
Actually I was talking about
Actually I was talking about the timeout before the server we wanted to capture the image from switched from one component of its boot sequence to the other. Somehow our network admin solved this and now everything seems fine and we can capture images the way we want it.
Thank you for the help everyone!
Would you like to reply?
Login or Register to post your comment.