Does petemp (and/or other shares) get automounted during pre- and post-installation tasks?
What K2000 shares, if any, are automatically mounted during the pre-installation and post-installation task phases, and where, on both the Mac and PC?
If I store data on the petemp share during the pre-installation task, will it still be there waiting for me during the post-installation task?
Is there a better way to preserve data over the reboot/imaging stage?
Do I need to manually delete my stored data on this share after imaging so it doesn't clutter the share, or is that an automatic process?
Is this info officially documented anywhere?
Thanks!
If I store data on the petemp share during the pre-installation task, will it still be there waiting for me during the post-installation task?
Is there a better way to preserve data over the reboot/imaging stage?
Do I need to manually delete my stored data on this share after imaging so it doesn't clutter the share, or is that an automatic process?
Is this info officially documented anywhere?
Thanks!
0 Comments
[ + ] Show comments
Answers (1)
Answer Summary:
Please log in to answer
Posted by:
TheAustinDave
7 years ago
Top Answer
The K2000 does create some samba shares that it mounts during the pre-installation process, these are Y: and T: drives. Each contain information on the tasks, Y: drive contains the actual pre-installation tasks which are run to condition the drive before installing an OS. MAC OSx has a similar location, once the OS is installed on the system the post tasks are written to a temporary directory to run.
There are no samba shares connected for post tasks as these all run from the information on the target system. Any temporary data (get/set computer name as an example) is saved to the RamDrive (X:). Once the install is completed the kcleanup will remove the temporary files used for the deployment.
David
Comments:
-
Thanks, David.
This is a partial answer, but I still don't know what shares are mounted, or where (other than the drive letters, which only works in Windows), nor where any of this is officially documented.
If I understand your answer, these shares are only mounted in the pre-installation task phase, and not in the post-installation task phase (which explains the failure of my test attempt prior to getting your response).
You mention a RAM drive, X:; that sounds interesting. But again, a google for "kace k2000 ram drive x:" turns up a lot of nothing. Is there any official documentation on these shares?
Thanks! - kentwest 7 years ago-
There is nothing that really explains the process of how the KBE is loaded. The files are loaded from either the PXE boot or USB to a RamDrive created on the system. That allows the ability to access the physical hard drive and prepare it to deploy and image. - TheAustinDave 7 years ago
-
From experimenting...
When the Mac is booted into the KBE, the PETEMP and PEINST are automatically mounted on /opt/kace/petemp and /opt/kace/peinst respectively. You can see these mounts by opening a Terminal window and using the command "mount".
This /opt directory is not on the local hard drive; it's on the network boot drive (the K2000), so you don't have to worry about it disappearing during a partition/erase procedure on the local drive. But it is not remounted after the deployment of an image, so if you want access to them post-deploy, you'll have to manually mount them. - kentwest 7 years ago
