Standardizing on a single imaging suite for both Mac OS X and Windows was a big change for us; since we have roughly equal numbers of each that make up our pool of college-owned systems, a fully functional environment is equally critical for each of these platforms.
I am concerned that timely support for Mac OS X seems to be slipping, and this is only becoming more painful as Apple seems to be returning to a near-yearly OS release schedule. 10.7 was not supported in K2000 NetBoot until more than a year after its full release. 10.8 has been out in preview since February, in full release for 90 days, and there's no word on an ETA for K2000 support. Meanwhile, we're preparing to order some new Apple computers that almost certainly won't boot anything less than 10.8.x., and our newest MacBook Pros and Airs are highly unstable in the 10.7.5 NetBoot environment. This is actually a bigger deal than Windows 8 for us, because we can simply choose to hold off upgrading our images to Windows 8. With Mac OS X, once Apple has released a major new OS version, it's typically only a few months before they begin shipping new computers that require that new version. If we end up having to build and maintain a separate non-KACE imaging tool for NetBooting and imaging all Macs that are less than a year old (which represents the vast majority of our imaging work), it will become less and less clear why we are using the K2000 to image Macs at all.
If Dell KACE is not already enrolled in the Mac Developer Program, please do so. We're not expecting magic, but not even having an ETA for support for a Mac OS that has been available in the retail channel for 90 days (and in developer preview for 9 months) is really problematic.

Hello, there may be a few posts around this idea but they are lacking detail and mostly attack the changes in 3.5 when it comes to WIM's. I can see the merit's in what KACE has done in terms of "cleanliness" however, unfortunately 3.5 has been a step backwards in terms of functionality in regards to WIM's.

Reverting to the old method officially isn't going to happen, although we can all use the old method if we want, with just a few more steps. However rather than that, here's my suggestions on what needs to be changed post-3.5 to bring WIM imaging back up to par:

1) Allow multiple System Images to point to the same WIM file: I, as many do, don't have the available disk space to store multiple copies of the same WIM just for different image layouts.

2) Allow servicing of the WIM files: In 3.4 I would take the WIM, mount it, make changes, then commit and save the WIM back to the petemp\ImageStore folder. In 3.5 we have to re-capture the WIM every time which basically defeats the purpose of a WIM in the first place. A great feature would be to be able to make changes to the WIM without having to take it offline/out of the peinst\WIM folder.

3) Don't copy the WIM to the local machine before deploying. This wasn't necessary in 3.4 and certainly adds time to each deployment.

Thanks for reading my suggestions and hopefully some or all of them can be implemented.

Currently if a user updates the SDA (K2000) version, the Appliance Upgrade Log only has the date and time of the update. There is no way to see who started the process.

[Mon Jan 7 19:54:22 EST 2019] [notice] XXX Begin K2000 Server Update to 6.1.251 from 6.0.425
[Mon Jan 7 19:54:22 EST 2019] [notice] XXX===========================================================================
[Mon Jan 7 19:54:22 EST 2019] [notice] Removing backup 5.1.84backup.sql.0.gz
[Mon Jan 7 19:54:22 EST 2019] [notice] Removing old database backups
[Mon Jan 7 19:54:22 EST 2019] [notice] kboxupgrade:: NOTICE: Running kboxupgrade.php part 1
[Mon Jan 7 19:54:21 EST 2019] [notice] kboxupgrade:: NOTICE: Starting kbin upgrade process

I think I saw this listed on the itninja forums, but nothing was listed here that I could find. So adding it to make sure it is officially on the feature request list.

This would include driver support for Windows 8 and Server 2012 and an upgrade of the KBE to use Win PE 4.0 which I believe is required to install Windows 8 and Server 2012.

Would also like to make sure powershell is added to the KBE. I believe you already get that by adding the scripting package in PE 4.0 which is already added to get vbscript, but would need that verified.