K2000 3.7 Patch
I saw the 3.7 available for download, but I'm not seeing very many questions about the new version around. I'm wondering if there just that aren't that many issues with this version, or if everyone is waiting? I'm patching one of K1000s this weekend, and was going to go ahead and do the K2000 as well. It's been a busy few months for me, and I haven't been paying much attention to the patches. Has anyone updated with any feedback?
0 Comments
[ + ] Show comments
Answers (2)
Answer Summary:
My update went smoothly. The only issue I had was the AIO drivers and the new directory. Perhaps if the "driver_feed_discovery_tool.vbs" can be made available prior to the upgrade it would help eliminate this, and we can check our machines prior to an upgrade. I was fortunate enough to have a test box that I updated, and then ran this vb script on all of my machines to verify the path. If it is made available prior to the upgrade maybe I'm overlooking it?
My update went smoothly. The only issue I had was the AIO drivers and the new directory. Perhaps if the "driver_feed_discovery_tool.vbs" can be made available prior to the upgrade it would help eliminate this, and we can check our machines prior to an upgrade. I was fortunate enough to have a test box that I updated, and then ran this vb script on all of my machines to verify the path. If it is made available prior to the upgrade maybe I'm overlooking it?
Please log in to answer
Posted by:
ISEKOLD
10 years ago
There is currently a bug with 3.7 where the model of computer is not identified properly.
"XPS 15,XPS-13-L321X, Dell Precision xxxx, 9030 AIO, Venue 11 Pro 7130/7130 MS/7139, E5250/5250, E5450/5450, and E5550/5550 systems are not identified properly by the copy_drivers.vbs script to inject drivers." - https://support.software.dell.com/kb/140378
In our environment we also noticed the issue with Optiplex 9010 AIO and Optiplex 9020 AIO as well. So I would not say this list is all inclusive.
If you have any of these models you may have issues with drivers after the update.
"XPS 15,XPS-13-L321X, Dell Precision xxxx, 9030 AIO, Venue 11 Pro 7130/7130 MS/7139, E5250/5250, E5450/5450, and E5550/5550 systems are not identified properly by the copy_drivers.vbs script to inject drivers." - https://support.software.dell.com/kb/140378
In our environment we also noticed the issue with Optiplex 9010 AIO and Optiplex 9020 AIO as well. So I would not say this list is all inclusive.
If you have any of these models you may have issues with drivers after the update.
Comments:
-
I'm glad you reminded me of that. After the last update I had to go and modify the path for all of my Lenovos.
I have the 9020 AIOs, and the 9030 AIOs as well. When I ran the driver feed discovery tool it showed "dell\windows_7_x64\AIO" for both. Even though the "Model reported by WMI" shows >Optiplex 9020 AIO< in the same vbscript. I'm testing now by creating the AIO directory. Hopefully this works. We have a ton of different models. - dugullett 10 years ago-
It should work. I did this to fix our 9030 AIOs as it showed up the same as it did for you (dell\windows_7_x64\AIO). I just told my team if we needed to build one of the other models (9010/9020) I would have to make a change first in the driver feed directory.
Unfortunately it will only work for one of the models as the drivers are different and they reference the same location. - ISEKOLD 10 years ago-
I created the AIO directory. It pulled the drivers for both the 9030, and the 9020. I don't really have the option of changing the drivers since we have so many. I guess that will work for now, but I'm wondering how many more problems I'll run into later? Our environment is too large for me to have one of every model that we have out there. So I may not know for a few months. I may just wait for 3.8. - dugullett 10 years ago
-
dugullett - Will having both sets in the same folder work? I have always read that you want the driver feed folder to be streamlined and not cluttered with mismatched drivers? I haven't done a whole lot with custom drivers so I could be wrong.
Also, if this is your only option, it might be your best option. - ISEKOLD 10 years ago -
It is my only option if I want to update. It seems to be working so far, but I'm still testing the machines. I'm fortunate to have a test K2000 that I can work out the majority of the kinks before I update my PROD box. - dugullett 10 years ago
-
This same bug was present in 3.6 as well. I had to submit a ticket to have a tech tether to my box and update the script. I wonder if 3.7 either doesn't replace the script in question (and you had the problem with 3.6 and just didn't realize) or it does replace it and re-introduces the problem. Here's the original article for 3.6: https://support.software.dell.com/k2000-systems-deployment-appliance/kb/122930 - BHC-Austin 10 years ago
-
Who knows, maybe we were experiencing issues and just never knew. This would explain why Dell support would like to tether to our k2000 box. Thank you for bringing this to my attention. - ISEKOLD 10 years ago
Posted by:
cserrins
10 years ago
3.7 is mainly a UI overhaul, bringing it to look like the K1. Mac multicast from the K2000 was also added, but that is the only new feature. Several bug fixes too according to the release notes on the same page as the download.
Comments:
-
Is there any change to what the techs would see on the imaging end? I generally have to document everything for them so that there's no confusion. If their process changed, or even looked different when imaging they would be calling me up.
I'm assuming if it did change I could just update one RSA still, and document it there? Then update the rest later? - dugullett 10 years ago
