Any Hope of Continuing to Use the K2000 with High Sierra/SSDs/APFS?
The newest Mac OS, High Sierra, converts an SSD into the new Apple APFS drive format, and there's no opting out.
In addition, the installer is not static, but is custom-built for each model of Mac, so you can't easily obtain a full High Sierra installer (so far, it's been impossible in my experience), which means you can't build a KBE using the APFS-aware High Sierra OS.
What this means is that you can no longer create an image of a High Sierra Mac using the K2000, unless it's a non-SSD and you have used a work-around to avoid file-system conversion to APFS. (You also can't use DeepFreeze any longer, if that's an issue for anyone here.)
What are Mac supporters going to do from this point on? Can we expect Quest to make the K2 work some how? Perhaps they already have, and I've just not found the answer? Do we move to a different solution?
Thanks for any feedback/suggestions!
/Kent
In addition, the installer is not static, but is custom-built for each model of Mac, so you can't easily obtain a full High Sierra installer (so far, it's been impossible in my experience), which means you can't build a KBE using the APFS-aware High Sierra OS.
What this means is that you can no longer create an image of a High Sierra Mac using the K2000, unless it's a non-SSD and you have used a work-around to avoid file-system conversion to APFS. (You also can't use DeepFreeze any longer, if that's an issue for anyone here.)
What are Mac supporters going to do from this point on? Can we expect Quest to make the K2 work some how? Perhaps they already have, and I've just not found the answer? Do we move to a different solution?
Thanks for any feedback/suggestions!
/Kent
3 Comments
[ + ] Show comments
-
Following these instructions I was able to adjust the version of our K2000 and successfully uploaded a new KBE (macOS 10.13.3). I was able to successfully boot from the KBE. But upon starting the "SDA Imaging Utility" I'm getting an error: APFS volume capture is not supported. I'm not concerned about capture, I simply want to deploy a macOS 10.13.3 system image (previously built). How can I get by this limitation? - skent 6 years ago
-
Has there been update from Quest support on K2000 supporting APFS? - fleminsa 6 years ago
-
There has been SILENCE from Quest about this topic other than to say, "keep using the old format; we don't support the new." I call BS!! We were sold this product because of it's 'rich Mac history' but it's about to become history (at our company) if they don't modernize and update the program to support modern-day features and applications. macOS High Sierra has been out for many months and has gone through several patches -- WHAT'S THE HOLD UP getting APFS support?!?! - skent 6 years ago
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
Channeler
6 years ago
I would say avoid using APFS, but you could try if you have a test system, and let us know if it works...
Posted by:
jnchaney
6 years ago
You can continue using the old file system structure. Have to erase/unmount and repartition the disk with the old format.
After creating the High Sierra KBE with the latest k2000 hotfix you also need to make a script to delete the APFS disk and re-partition the drive with JHFS+ then you can continue to use existing images or new ones. You can do this manually with disk utility and the partition tool but I find it easier to do with a script. FYI if you get a script error you may need to update the disk number in the script.
#!/bin/bash
diskutil unmountDisk /dev/disk0
diskutil partitionDisk /dev/disk0 GPT JHFS+ New 0b
If you try to just erase the disk in disk utility you will only see APFS format options. You actually have to delete the disk then go to the partition utility and create a JHFS+ partition. Sometimes after deleting the disk in disk utility, I have had to close and reopen the app for the unpartitioned disk to show back up as an unmounted drive.
Posted by:
Channeler
6 years ago
Top Answer
I have been able to create a KBE for High Sierra using the new media manger with available with the latest hotfix:
https://support.quest.com/kace-systems-deployment-appliance/kb/235057
"This release introduces macOS 10.13 (High Sierra) support for the SDA and RSA, but does not support the AFPS file system at this time. "
This implies it will be supported later in time.
We were able to capture and Deploy High Sierra successfully by skipping the AFPS system:
http://osxdaily.com/2017/10/17/how-skip-apfs-macos-high-sierra/
So I would say it's just a matter of developing the APFS module or code.
Comments:
-
Version of "K2000 Media Manager" with the 5.0.222 SDA = 5.0.16
Version of "SDA Media Manager" with the 5.0.1016 HotFix update = 5.0.1006
It still fails; but it fails with a different error this time.
An error occurred while building the NetBoot Image. - kentwest 6 years ago-
CREATE NETBOOT IMAGE VERSION 1.3
working directory is /Applications/SDA Media Manager.app/Contents/Resources/create_netboot_image
my name is ./create_netboot_image/make_netboot.sh
SRC is /Volumes/pc_apps/ISOs/Mac/OS/2018-HighSierra/Install macOS High Sierra.app
DEST is /var/folders/qg/fvysy6pj7y369__31x3s8dm40000gr/T/kace.ZFGLxK1E
source media is Mac OS X 10.13.2
local os is Mac OS X 10.13.2
targetImage is /var/folders/qg/fvysy6pj7y369__31x3s8dm40000gr/T/kace.ZFGLxK1E/netboot.sparseimage
calling create_image
VERSION = 10.13*
Boot volume name is Macintosh HD
SIU produced initial netboot image stored at /Volumes/Macintosh HD/Library/NetBoot/NetBootSP0/siuKaceNetBoot.nbi
Automator/SIU netboot image capture result is: 255
Error: Automator/SIU netboot image capture failed - kentwest 6 years ago-
That is 100% not related to high sierra, I suggest you to try 4 times, reboot and then try a couple of more attempts.
Also read:
http://www.itninja.com/question/error-using-k2000-media-manager-mac
And:
MAC Netboot fails to build and error with SIU 255 error (created in 2016 according to the website)
https://support.quest.com/kace-systems-deployment-appliance/kb/217593
Make sure your APP file is not damaged and try to use it in another Mac device - Channeler 6 years ago -
Channeler helped point me to a partial solution:
The "install macOS High Sierra" installer file *must* be in the /Applications folder. I had it in a different location when I was getting the failure above.
I've now successfully created and uploaded a High Sierra KBE; I have not yet tested it, nor do I yet know what it means that "APFS is not yet supported". I suspect it means I won't be able to image APFS-formatted machines. But maybe I can at least boot into the KBE. - kentwest 6 years ago -
Yes, it booted an existing High Sierra Mac to the new High Sierra KBE. W00t! Progress!
and the KBE's Disk Utility sees the non-SSD, non-APFS-formatted platter-drive. Tomorrow I'll try it on an SSD APFS-formatted machine. I expect it to see the drive as "unformatted". I'll know more tomorrow.
UPDATE: The KBE can not see the APFS-formatted SSD, just as we all suspected. - kentwest 6 years ago
