I was excited when Labels were introduced to the K2/SDA. In using them, though, they have not been as useful as I initially expected. The problem is they are not "Smart". I would like to see a Smart Labeling ability added like what is available in the K1/SMA.

I know that the implementation would be a little different, as the SMA applies labels during inventory which the SDA doesn't do. A thought would be to make them saved searches instead of Smart Labels in the SMA since. Adding Advanced Search capabilities and then saving the searches so they can be used in the deployment sections. Kind of like SMA's Service Desk Custom Views where you save the advanced search on tickets to a view.

I know that labels can be brought over from the SMA but this is not an automated process. Even if this specific process was automated (and if a reader does, please upvote this post https://kace.uservoice.com/forums/82717-sda-k2000/suggestions/10320702-dynamic-updating-of-k1000-labels-in-k2000), I would still like to see the SDA have its own Smart Labeling ability.

Coming from WDS, there was an ability to respond to all devices, known or unknown, with different PXE boot policies:

Require users interaction pressing F12
ALWAYS CONTINUE PXE BOOT
Continue to PXE unless user presses ESC
Never PXE boot

I could then limit the response to a specific subnet/IP range. And because of it's rather reasonable price, I could easily spin up different WDS servers in different networks. I would really like to see the same with the K2.

In my own environment, when unboxing new equipment, we have a designated VLAN for staging and imaging devices. It would be very beneficial to have the K2 respond differently based on IP address range or even the K2 system NIC the request is coming from:

IP range 10.1.X.X Boot menu
IP range 10.5.X.X Setting defined KBE or system image installation
Traffic on K2 NIC 2 Image with System Image defined in settings

So many possibilities that would make imaging new machines possible without interaction and safely restricted from production networks (if configured properly).

I know there is hesitation to do something like this because, if not configured properly, it could cause serious problems by unintentionally imaging computers on the network. But this is a user configuration problem, not a KACE tool problem. By not offering this capability at all, it punishes and hinders everyone that is willing to configure it properly.

I upgraded from version 5 to 7.1.94 this week and imaged for the first time and was surprised and dismayed at the same time. I like the image progression bar addition but before you had an estimated time that it would take for the wim file to be copied from the host. I know roughly how long it takes from imaging many different PC's. The image progression bar sits a 0% the entire time that the wim is copying from the host. having a timer or another progression bar showing the progression/time remaining for copying the wim would be immensely helpful. Also adding a time remaining to the image progression bar would be helpful as well.

We have been having storage capacity and clutter issues with USMT scan states uploaded to our K2000. 90% of these have been migrated because the K2000 selects all profiles for migration by default and my peers will quite often zip through this without de-selecting profiles not needed. This will result in a lot of garbage data being captured as well as create duplicate local user accounts and profiles. This can form in to a very long list that takes up a lot of space that we have to manually clean up on each of our RSA(s).

Would it be possible to add the following features?
- Server Global setting or Task-Specific option to not auto-select profiles for migration when doing a manual deployment?
- Option to cleanup scanstates after X days paired with the ability to flag a capture for retention? E.G. automatically remove all scanstates that have been on the server longer then 45 days a long as they are not flagged for retention?

I Like the Sysprep Executor utility as it's fairly intuitive and user friendly when it's being ran prior to a capture, it however has a few barriers preventing me from using it.

• Custom Unattend answer file.

I have a few answer files created manually in WSIM as use a few settings that are not available in the Sysprep Creator menu, would it be possible to add an option to sysprep creator to select an unattend XML file instead of generating one via the menu options?

• Support for custom .bat,.cmd or .ps1 files prior to capture.

I have a script that I run before sysprep that performs the following tasks, not all of these are currently included within Sysprep executor. Would it be possible to add the ability to Sysprep Executor to run a custom script prior to running sysprep.exe so that I can automate the steps it does not natively cover?

• Close explorer.exe




• Verify bitlocker is off.

*Verify there is not a pending reboot

• Verify there is atleast 1 rearm remaining




• Verify VMWare tools is not installed.




• Verify the system is not a domain member.




• Reset McAfee's Agent GUID (A new one will be generated after next reboot, during the sysprep process)




• Remove windows Update Client ID's




• Stop the KACE agent (If installed) and remove the KUID (A new one will be generated after next reboot, during the sysprep process)




• Stop windows media player network sharing service and ensure it's startup is set to manual.




• Delete recent file history.




• Delete RDP connection history.




• Clear out Microsoft Office application MRU list




• Clear out types paths in windows explorer

The KACE SDA currently has no way to audit changes made to any imaging-related objects, including:

• KBEs


• System images


• Pre/Mid/Post install tasks


• Task Groups

Coupled with the "all or nothing" approach to permissions in the SDA, this creates an information gap that results in a security concern: how do you know what object or setting change was made, when it was made, and who made it?

Consider the worst case scenario: a disgruntled SDA Admin on their final day at the company adds a malicious script or application to a post-install task.

The risks that come with the current model:

1 - If you have more than one person in the image administration role, there is no way to prove accountability for this act of sabotage.

2 - If the change is not noticed immediately, there is no way to understand how far back it occurred and therefore no way to assess the true impact in terms of how many systems were imaged with the new configuration.

The KACE SMA has this functionality in the form of the Object History. Let's add it to the KACE SDA as well so that we can cover our security concerns there as well.

Basic configuration, such as system location or system contact, for SNMP is not available to the end user. Many SNMP monitoring tools pull this information and map devices using this information. This information can be provided in the /usr/local/etc/snmpd.conf however the end user can not edit this, so options might be to allow this information to be added in the konfig stage of the install or when going into the Security Settings/General Security Settings and putting a check mark in Enable SNMP Monitoring other fields can open (besides SNMP Community String) for syscontact and syslocation. Once saved this information can update the snmpd.conf file. Another option in this area would be to restart the snmpd service or after saving the box might request a reboot.