KACE Product Support Question
Big task - Kace K2000 - Deploy two windows-partitions with separate post-installationtasks
it seems that I got a really big client-installation-requirement and -task for the Kace K2000 appliance. I didn’t find a solution with google for my specific task. Maybe someone’s got some tips and ideas. Sorry for my very basic english.
We are using clients with two windows-partitions because of software-requirements. Partition 1 is a windows-7-x86-partition and partition 2 is a windows-7-x64-partition. The clients have the windows-boot-menue to choose which partition should be booted. Both partitions are specific pre-configured-images with sysprep.
The task is not really simple. We want use the K2000 appliance to install a client with the two in the overview described windows-partitions, configure the boot-menue and do post-installation-tasks for each partition. That’s where the problem starts. We want to do automated post-installation-tasks on both partitions.
What we got working:
We captured both partitions with sysprep at the same time from a masterclient with the k2000-KBE. Deploying this image is working fine. K2000 has successfully deployed both partitions. Also we got a post-installation-task working to edit the boot-menue-sequence and do a reboot to start from partition 2, normally it would start from partition 1. Here is where the problem really starts.
After booting from partition 2 we want to continue the post-installation-tasks from the k2000 but it doesn’t work, ofcourse. So we are looking for a solution to move the post-installation tasks from partition 1 to partition 2 and continue the final-tasks.
Maybe there is a windows-directory on partition 1 from the k2000-deployment which could be moved to partition 2 or some other solutions.
I really hope for some tips and ideas, maybe a solution.
Answer Chosen by the Author
Kace sets triggers to start the post from local drive and sequence the other post tasks. If you copy the tasks prior to triggering them (first task) you will have trigger system intact so it will be the same point on both drives. If you check restart after the first task, both should start at the next post task.
the xml 371 starting at the local calls