You can actually do this, their filtering engine there uses a SQL query. If you use %val% for this example in the search it'll work
Yeah this is severely needed in situations such as ours, we're in a school with 2200 devices and students get their devices re-imaged fairly regularly... because.. well... students..
Being able to configure this would be outrageously useful.
Probably because when this was submitted ( the WIM format wasnt even close to supported.
All the same, block level imaging has its place and I can understand why he would still want it.
26 votesunder review · 4 comments · SMA (K1000) » Software Compliance · Flag idea as inappropriate… · Admin →
It would also be nice if this went into the KB Articles also, being able to categorize articles based on software title or other particular topics (not just the column which people never read).
Software library configurable into groups like 'drivers', 'creative software' etc? Got my vote!
Ahhh yes, I saw that one and thought, hey, why not, I could have my cake and eat it too. I think the invite is brilliant and would have given it one of my votes but I keep running out.
I'm all for answering questions publicly and I suppose with the ability to see eachothers contact details that should cover the gap. It'll be interesting to see if anyone else would like the feature back too though.
We are looking for an intuitive way to provide this capability. One method would be to support the exclusion of certain tags in search results (right now it is inclusive). Would love to hear any ideas members may have for a good way to do this (will likely need to be some method of tag filtering)
The new KNIT and K2 v3.4 will sort you out quite happily. See if you can also get a hold of the KBE Manipulator which allows you to upload your own ISO's and WIM boot media.
This allows quite near the flexability which I was requesting in this uservoice request. You will be able to use these tools to create a win pe environment which boots from the K2 with drivers and starts up a ghost console very easily.
Let us know how you go, if you need any help give me a buzz on app deploy or ITNinja username Roonerspism. We still run a multi pxe boot system here between wds and K2 but with the advent of these tools recently (my hats off to you Corey) we'll be looking to go pure K2.
I know where you're coming from though, we just did another 140 machine deployment ourselves with a 37gb image, and we'll be doing it again with 250 machines in a few weeks.
I may be a little off topic and turning this into more of a thread lol but:
Generally in our environment (while we dont use GHO images anymore and are WDS and WIM only now) we found that K-imaging was much slower than the bit-by-bit copy of ghost.
Granted the new versions of the manipulator are great and allow you to do some AMAZING stuff, people still gho imaging are doing so purely because its quick I believe (or maybe their policy requires it?). So I think the request by Ravi might be along the lines of 'let us bit-deploy a .gho with the K2'.
That being said, you can trivially add the ghost client into a winpe and upload that using the KBE Manipulator, so that might be a good middle man, as I mentioned, the thing is great.
Feel free to smack me down if I'm way off :)
Just as an idea for this in the mean time:
You could create a smart label called '(Software) Installed' (which detects if the software is installed) and if you install the software using a vbs to launch it you could create an sql query in the vbs to perform a count of the number of machines in the group (see below for an idea), then if the count hasnt reached your specified limit allow the installation, or if it has reached the limit stop the install.
You should edit this but in something like FlySpeed SQL it will give you a list of all your machine groups nd the number of machines in them.
MACHINE_LABEL_JT On LABEL.ID = MACHINE_LABEL_JT.LABEL_ID
group by LABEL.ID, LABEL.NAME
Just a quick heads up. If you assign each machine a user (add a user field to the asset and voila) you could control your scripted installs to specific users assigned to the machines by calling vbs files that instigate an sql query and query to ensure that the current user is the one that is set to it.
For instance, we use this method to, during imaging, set the local admin user to the assigned user, and on certain scripts to only (even though they can see them) run if the user fields match. Might help you work a solution for now.
Some way to authenticate users which allows different images would be nice, ie, everyone can get the BASE image, but only people who click authenticate and type AD credentials will get the TEACHER image.