Looks like this might be possible, https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/boot-windows-to-audit-mode-or-oobe
Oh, and use 126.96.36.199 as the multicast address and set the appropriate number of hops.
The NORM protocol supports IGMP, you must enable igmp snooping on the switch to git it to route traffic.
The CSV files accepts 3 criteria, IP Address, MAC Address (with colons), and Host Name (optional), so this request is already fulfilled.
The reason this is not supported is because there are often times when capturing images or adding other items to the appliance that those processes fail because the appliance can't expand the size fast enough to capture images,etc when needed. You should be able to run thin provisioned just fine, but if there is a failure, that is the first thing to be looked at and multiple attempts should be made to accomplish whatever task is being tested. The only issue you will have is when calling into support with an issue related to this type of situation, because they know if thin provisioned errors tend to happen.
You can use PE5 for both Scripted Installs, better yet PE10.
If the issue is because of the error that pops up twice for Windows 7 SI in pe4 or higher, then just add on this as a preinstall task; http://www.itninja.com/blog/view/windows-7-scripted-install-error-in-winpe4-and-winpe5
70 votesunder review · 3 comments · SDA (K2000) » Feature Enhancements · Flag idea as inappropriate… · Admin →
Seems like a decent idea, but you can just duplicate an image with similar results.
Researching ways to integrate the ITNinja community, and this may be one of the big draws. We’ll look into it.
The article is still relevant and following it will allow the surface 4 drivers to be injected.
139 votesunder review · 11 comments · SDA (K2000) » Feature Enhancements · Flag idea as inappropriate… · Admin →
Please see this article as to why you currently are unable to import the database:
This is part of a long-term vision in the roadmap towards restoring a machine’s identity on the K1000 when rebuilt from the K2000, with incremental progress being made in each release.
While this is being planned, you can use get/set computername to accomplish this. http://www.itninja.com/blog/view/get-set-computername
outlines a current way to do this.
However, the change I would make is using kbe manipulator to add odbc to kbe instead of installing it each time on the fly.
There is a post on ITNinja that outlines doing this, but can't find the post right now, I'll update when I find it.
The get/set computername script now looks at the host_name field on the K2, check out the readme.
Look for an updated version of Get/Set ComputerName in the next coming weeks that will have this feature.
You could technically enter the computername in the host section of inventory, then use kbem to upload a kbe with odbc in it, and query the db for the host name of said computer...
We’re looking at this after we get more K1000 synchronization built into the K2000.
35 votesunder review · 4 comments · SDA (K2000) » Feature Enhancements · Flag idea as inappropriate… · Admin →
or what if the user deploying was logged by the k2 boot actions? That would probably be easier to tackle initially
12 votesunder review · 2 comments · SDA (K2000) » Feature Enhancements · Flag idea as inappropriate… · Admin →
Depending on the application you want to use, I personally store them on petemp, which is accessible via /opt/kace/petemp in netboot environment. Most applications will run.
@carlos use KBE_Manipulator for a GUI to upload custom boot images.
3.4 will have an add-on toolkit called Kace Native Imaging, so you can capture/deploy .wim files for faster mass deployments.
I can't say the stuff you eluded to in the 2nd paragraph ;) or how ghost is a portable app.
Why not deploy the ghost image, and then without rebooting capture with Kimage, or .wim with 3.4?
This will be possible with KBE Manipulator, an add-on to 3.4. You can add DCCTK to your KBE along with ODBC drivers, you just need dcctk installed on the same machine you are using to build a kbe with waik, media manager, and kbe manipulator.
We agree! This is great feature and the team is working diligently to get it into a future release. Stay tuned for more details.Corey shared this idea ·
Great idea. Can folks also provide links to other vendors’ tools?
Josh, if you are using the latest version of kbem, there is a bug, please click on "Add Feature" and select the .iso from that window, that should work, I'm coding a fix.
Have you all tried KBE Manipulator to upload these? You can get it from this page:
This unfortunately would require the K2 to have similar functionality to the K1. If there is software that needs to be up-to-date on your endpoints, you would likely be better served with the advanced features of the K1 instead.
The Adobe installs in particular require a distribution license agreement, so I doubt any of those could be done.
IE has a wizard to create a custom install, so this would be different for each company.
changing the background in kbe would be another user configuration that could go along with this if approved.