K2000 "Breadcrumbs" From a Pre-Install Task to a Post-Install Task
05/23/2017 1416 views
I am working up some really cool scripting for custom post install tasks. So that I can choose what tasks I want to run for each job without logging into the K2000 and dragging the tasks off/on each and every time.
The only minor issue is currently my GUI used to pick the tasks to run is running as a Post Install task, it saves the breadcrumbs as registry values to the new image, then later when each install job gets run by the K2000 its checking if those registry values exist and running/not running based on the value.
The reason that is an issue is simply I cant pick my options as soon as I kick off the deployment, I have to babysit the image until the first post-install task runs that launches my GUI.
If I try to run it as a pre-install task, its running in the PBE thus the changes are not made to the new system.
I wondered however if maybe I can use the PBE as a go between, I think the PBE has the Y: as its disk or is it X: ?
If I re-do my GUI to say save a .INI file to the root of the PBE would that file still exist when I get to my post install tasks?
I just sort of need to verify the environment a bit so I know where to write the files, and if they are still present when coming back to the post install tasks.
There is usually a reboot somewhere in there, and I imagine that will cause loss of anything stored in the PBE, but maybe if my first Post-Install task is to read my PBE placeholder and then write that to the Registry of the new machine I can complete the chain of events.
Edit: Created myself a task to launch a cmd window at each phase of the install (Pre, Mid, Post) I can see X: is the PBE and Y: is the K2000
Looks like the K2000 can not be written to, access denied.
So I put a file in the X: home directory and will see if it is persistent, if not anybody have any ideas?
Edit2: Deployment I can see a T: and a C: - Looks like I can most likely save the file to the C: but not sure it may get over-written by the image there is no registry yet since windows is not installed and initialized, but there is access to the drive.
Now I wonder where this mysterious T: goes?
Answer Chosen by the Author
Please log in to answer
Using The T drive is a sticky situation as it is different for every RSA and does not reattach after reboot. An easier way is to use the X drive.
I have built an HTA that has all of our Software installers (On K1000), computer name,and Domain / OU choices. This dumps to a text file on the X drive (Ramdisk). Then as a mid task, Transfer the file or its contents to the C: drive. This way everything stays local.
Something like this:
Your Pretask dumps the file to "X:\Software.txt"
Then Midtask: copy "X:\Software.txt" "C:\Temp\" /Y
Answered 05/25/2017 by: Desktop Jockey