k2000 system image deployment issues and order of operations
My work currently has the k2000 appliance, version 3.5.8. I am trying to set up a system image deployment. I can capture the image no problem, and then I can distribute the image. The problem is the install tasks are not running when they seem like they should or drivers are not installing.
What I am trying to do is have an image that has certain customizations on it, such as GPO, BUT it needs to be a base image that works for a number of different models. So it needs to install drivers after the image is complete. Then I need it to put in dns info in case for some reason, the info is missing. Then join an active directory domain and finally, run updates.
What happens is that the image deploys, then before it reboots out of the KBE, it looks to run driver install, then the post install tasks. All while in the kbe. Then it restarts and the image is there, but no drivers or anything else.
I have the driver feed box checked and the other tasks are set in the post installation field. I have tried this with both a K image and a WIM.
I have little documentation and so am really trying to wing things. So, if anyone has a good guide for a step by step set up of a system image deployment, or can tell me why drivers are not installing and other tasks are not running when I feel they should be, let me know. Any info is appreciated.
Answers (10)
I would recommend using the RunOnceEx Converter postinstall task, it takes all of your postinstalls out of the KBE and runs them on first bootup into Windows. They seem to be much more reliable that way. As for the drivers specifically, do any of them get installed? We have seen one or two always be missing, and we have to use a postinstall to apply them.
No, nothing seems to get installed other than the basic windows drivers that occur on installation. What is this Runonceex? I am guessing I have to create a script for that, as I don't see it under postinstall?
Edit: found a manual and it says that system images must be deployed to like machines. I wanted to use 1 system image for multiple models. Doesn't seem like it will work. Unless this has changed from Jan 2012 date on the manual I found.
For WIM images, you will need to Sysprep the machine 1st and capture for redeployment. Sysprep will generalize the system and remove all drivers and such and make it Vanilla. In the K2000, you need to download drivers for each of the systems and OS you deploy. If you are an all Dell shop, they have made this quite easy for you.
Go to the Library Module > View Available Driver Feed Packages > Search for your models in the top right > Check the box to the left of the Make/Model > Choose Action > Download and Install Packages.
In the top right where it says Currently: Idle - it should change to downloading x package. If you are downloading multiple packages, wait for it to say Idle again. Then go to Library Manage Drivers > Recache All drivers.
When you go back and redeploy your WIM, make sure you check the Driver Feed box like you did. Now it should go ahead and deploy new drivers for you.
To tell if it is, it should show a dos screen and show the drivers being installed while in KBE. Typically I see 90-150 drivers get installed.
If you need more clarification, please let me know.
Sysprep is old hat. Done that more than I ever wanted. So that part is covered. The manual I found though said that driver feed isn't available with system images, sounds like it needs to be built into the image and that the image, optiplex 790 for example, can only be applied to other 790s.
I DO get the screen showing drivers being installed, but they end up not being there once the machine boots into windows.
Comments:
-
That may be an old manual/help file since Driver Feed IS supported in 3.5. The main thing is to make sure you have downloaded drivers into the feed, as spinuzer mentioned, from the Driver Feed tab. - BHC-Austin 10 years ago
Well, the driver feed is working for our scripted installs. I would assume both methods of install work the same, but then again, maybe not. But the drivers do appear to install while in KBE, but when booting windows for the first time, they are not there.
You can use the driver feed with System Images now - you just need to make sure it is enabled in the System Image Detail:
Yep, I have that box checked. It acts like it installs, but once it boots to windows, there are no drivers.
Make sure that you do not have "persistalldeviceinstalls = true" in your sysprep file. If you have this setting set to true will interfere with driver feed.
<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep">
<PersistAllDeviceInstalls>false</PersistAllDeviceInstalls>
</component>
When I look at the xml feed of my answer file, I have nothing at all for persistalldeviceinstalls.
Now, when I upload my image, I already have it syspreped with my answer file. Does kace apply 1 of its own when pushing the image to the client?
Maybe I need to add the line in and make it false?
Comments:
-
What flags are you using when you sysprep? Are you using /generalize /oobe ? - Chrysis 10 years ago
/generalize /oobe /shutdown.
I found part of the issue. I was booting into windows after sysprep before capturing. Now, I cap the image after sysprep but before booting windows.
However, a new issue crops up. I can only use the image 1 time. Regardless of machine. It is only good for 1 use and then on the second time, things get stuck on "setup is starting services".