K2000 3.5.80613 issues. Resolve them or upgrade to 3.6
Hi,
I'm having some issues with ever since we've upgraded to 3.5.80613. Most of the scripted installs failed, drivers arent installed. I've followed instructions from support and recreated the PE with different drivers. Deleted all dell driver feed drivers and downloaded them again. For the HP nodes i recreated the driver structure and uploaded all drivers again.
But from all nodes i only have one dell model system that deploy's without any issue. I've been trying to debug the issue but haven't reached a point that i could understand or fix the problems. Some of the driver issues seem to be random.
Before the upgrade to 3.5.80613 everything was working just great!
I'm no longer at the point that i want to wait for support to help me out, so i would like to ask you for advice.
Does anyone have these issues with 3.5.80613? Did you resolve them? Or should i start looking at a upgrade to 3.6.
I don't have a testbox, so i'm going in blind. We are deploying systems just as scripted installs, not as an image. Does 3.6 install drivers from the feeds and other vendor drivers without any problems?
The known cmd/batch issues with the postinstall tasks i can resolve. Problems deploying drivers are a real pain to get working once you've hit a bump in the road.
Answers (2)
With the K2 3.6 the task scheduler will show you which task has been failed.
This let troubleshoot it more easy.
I suggest to update in that case.
Comments:
-
Agreed - you get a more in depth progress of each task and audit logs with the update. It may help... - jegolf 10 years ago
Thanks for your input. I've decided to upgrade. And resolved most of the issues within a couple of hours. Big fan of the new engine!
Had some issues with a few Postinstall routines that i've offloaded to the K1 box as a workaround.
Comments:
-
if you have a K1000 this is the best way. I would always keep the installations tight. Every installation and most needed scripts should be done by the K1000 as this is the job for a K1000 ;)
I only install the agent, set the name, (join domain is also useful) and start a new inventory that the K1000 puts the client into the right smart label - Nico_K 10 years ago