We would like to be able to netboot a Mac across subnets (we have 39 academic subnets on campus, out of about 107 total subnets) without having to issue a bless command on each Mac or having to have an RSA on each subnet. We have a 10.5 server running DeployStudio that handles this just fine, but I'd like to be able to use KBOX for all of our imaging (Windows imaging on KBOX is much nicer than using Ghost).

Regulate access to various functionality based on user roles and permissions. This would include granular access to capabilities such as:

- Logon to KBE
- Access to specific production images
- Server/workstation roles
- Samba share access
- Differentiate between access to deploy images, and access to log into connected machines as an admin.

It would be beneficial to be able to leverage the label feature in the K1 at time of system deployment.

If i'm rebuilding a computer the Kbox should rename the computer correctly based on the information in the K1000. The old scripts are klunky. Maybe just a simple database/SOAP query to the K1000 for basic naming.

Please allow the ability to customise the email sent from Charlie Root (K2000). At the moment it doesn't seem to be configurable. We want to change its 'from' address, and the display name 'Charlie root' to something more meaningful. And make that email alert more configurable, like how often its sent, what to put in 'subject', etc.

1. Modify 'from' address
2. Modify Display Name
3. Turn on/off email notifications
4. Schedule charlie root emails (weekends, etc)

I just found out that you can not restore the K2000 database even though you can backup the K2000 database. I want to be able to have all my settings if there is a catastrophic failure with my server or just need to refresh the hardware. I have to recreate all my labels, users, Ldap authentication, all my general settings, date time settings, relink all of my RSAs and K1000.

Some of our sites are on low bandwidth data connections. Trying to sync multiple RSAs takes days as the syncs do not happen concurrently. As these tasks queue up, I am unable to do other K2000 tasks, such as driver feed updates, upload images, or recaching of drivers. If we could have a window for replication similar to the K1000 replication to network shares, this would improve efficiency in our environment and ensure our RSAs are more up-to-date.

It would be very beneficial to have the K2000 be able to slipstream MS patches similar to nlite/RT7lite with all current patches. Right now a Windows 7 sp1 Scripted install has 170 patches pending from MS.
I see our K1000 as a maintainer of machines not an initial configuratior.

Add Dell Diagnostics or memory testing to the KPE recovery options.

With Apple's transition to macOS HIgh Sierra and their new APFS file system protocol, I would like to see native support for APFS when creating a Mac KBE netboot. As Apple recommends moving to APFS with High Sierra, it is not good practice to continue hobbling along with the older file system format.

If we deploy an RSA to each location, why can't I use it as a K1000 replication point? Doesn't it make sense to use the RSA for this purpose as well as K2000 tasks?

The idea is to have the same process for the Imaging that the scripted installation. Then the image captured will be stored in the media Library and not in the deployment image tab. To create an image deployment job, we will select the image in a dropdown list.

It would be more practical to link tasks (pre-install, mid-install, post-install) to a deployment rather than an image. We are several people to deploy the same image but we use different pre and post-install tasks... If each person changes the tasks for each deployment of the same image we risk to have conflicts...
Actually we duplicate the image to have different tasks but it's not a good solution because the same wim stored many times on the K2000 Appliance.
Another solution would be to just duplicate a link on the wim file and not the entire wim.

It would be nice if the K2000 would also manage Windows Updates (like the K1000) to deploy them automatically as postinstallation Task.

It would be nice to have the ability to "hide" certain images or scripted installs from within the KBE environment. We have images that only get used once or twice a year and our list of images is almost 100 so if you could "hide" them from the list our technicians wouldn't be able to select the old images.