At the end of the installation, it may prompt you to upgrade the firmware. To continue this discussion, please ask a new question. Dell , Followers - Follow Mentions Products. Chris Dell. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks.
Dell , Followers Follow. Dell Technologies Latitude E The hardware wireless switch on the side of the laptop is already "on", confirmed by my WiFi being enabled and working.
Based upon this, I can't install any Bluetooth driver and can't seem to get past this point to even access Bluetooth settings Thanks in advance for any ideas.
Browse Community. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for. Search instead for. Did you mean:. Last reply by aadeel Solved. How to activate the bluetooth on Dell Latitude e How to activate the bluetooth on Dell Latitude e Solved! All forum topics Previous Topic Next Topic. Solution 1. Accepted Solutions. Community Accepted Solution. Replies PudgyOne 8 Krypton. I am a Dell user, just like you are. I'm using XP. So I checked BTtray and found several copies e. Thanks Bel. Achocobar 2 Bronze. Check and make a note of the driver installed on your system and re-install the bluetooth driver from the below steps accordingly.
If you are talking about the exe, I had originally removed this for a purpose however I have just recompiled it and included it in the zip if you re-download it. Inaccessible logs: Security. The AD account does not have any special permissions in the AD, as I only want this account to read data from the sccm. I tried setting the account as full administrator on sccm, as well as local administrator on the sccm server. Still the same error. There is a bug in the 1. The models are retrieved from an XML delivered by Lenovo so unfortunately I do not have control over this.
I presume you are talking about Windows 7 32 bit drivers in this instance as the X is listed in the tool for Windows Awesome tool. Just implemented in my dev environment. Just pick the models you want to deploy and then walk away. The script will not execute on the system. As the script is not digitally signed, you will need to either alter your execution policies or launch the script inside a PS session with the policies bypassed i.
I think I figured it out. Looks like if you have the Folders in MDT already created the way the script does them, the script will only create the missing folders but will not import the actual drivers. The script malfunctions. When I deleted this folder and reran the script, everything worked great. Looks like the script may need to be tweaked to check for those folders and continue with importing…? I think something else is going on there. The script does check for the presence of the folder structure when importing.
I have just purged my MDT environment and created the Windows 10 x64 folder to confirm, the import job completed without any issue. When I try to run this script for just MDT it will download the cab file and create the entry into the MDT share, but does not import the drivers. Any idea why this happens? Have you tried manually importing the drivers in PowerShell to test for any errors?. I found a problem with dirvers for Dell Precision name retrived from sccm As dell aparently calls it Dell Precision Mobile Workstation When you say you found a problem, are you having issues with the download etc?.
The model names come directly from the Dell XML. FYI Running without a proxy on a direct connection was failing when checking Lenovo models. Noticed the following error output:. Specify the UseBasicParsing parameter and try again. Turns out it just needed the UseBasicParsing parameter substituted in the script as seen in the global variables section per the error outpu.
All is well with the world. Hope that saves someone the research that it took on my end. Hi there — great tool! Is this normal? Previously the script was creating a PowerShell script in each of the bios package folders. In the latest release with modern bios management this is replaced by a script that works to download and dynamically identify the bios update.
EDIT: I found where the package was created! The drivers are packaged as a standard package for use with our MDM modern driver management post. You do have the option of picking Driver Package if you wish. Thank you so much for the fast reply. As a best practice, do you recommend choosing one of them? I see that I can still pick the standard driver package from a Task sequence but for an organization point of view I guess I should probably create the packages in the driver packages, instead of mixing application packages with driver packages….
My personal preference is to package the drivers into standard program packages. Our Modern Driver Management process works on the basis of the drivers being contained within standard packages.
Congrats on this amazing tool. Unfortunately I am experiencing an unusual behavior running it to get Lenovo drivers. The file sp Ahh, I get it. Some have a licence agreement selection and others have not. There were issues with some of the driver packages not following the silent extract paths and process, it is being corrected on a case by case basis at this stage.
Ah ok. For now I have altered the script so that it uses the Acer method 7zip to extract the content and so far it has worked for all models I selected. The model list and subsequent supported operating systems are fed through in an XML from Dell, so I have no direct control over the listings.
At present manually interrogating the XML only results in the following;. Thanks a lot for the quick response Maurice.
I guess I will have to do the win7 drivers manually. First off, great tool! Is there something different about the HP model request? Just wonder for troubleshooting purposes. If you are selecting the Windows 10 or as the OS, HP is the only manufacturer currently using this method.
If you select Windows 10 or previous OSes you should be able to select the other manufacturers. How often is the driver XML updated? Thank you, this tool is a great time saver! The Acer downloads are taken from a web scrape so they are real time and the Microsoft downloads are manually updated at the moment.
Is there any difference in your internet access policies between the two?. There is not. Both are exempted from filtering. Different content filter, but the same result. With regards to the MS information, we can download the file in a browser using DownloadLinks. Can you please mail me over the log [email protected] so I can see what is happening?. The script has been tested in Windows 10, R2 and with no issues. Still loving this tool, but am having an issue with downloading the device lists.
I was able to pull all but Microsoft a few weeks ago. I did a bit of troubleshooting for the MS issue. I cannot see the file with lower case letters. Could I be having an XML format issue or a filename issue? Nice tool, I really want to use it but I receive always the same error when the script tries to import the drivers. New-Item : Object reference not set to an instance of an object. Yes I have. The strange thing is, the driver packages are created and do contain the drivers.
With a previous version of your tool I received the same error but the driver packages were empty. I have just updated the script to allow for these. Ran into an issue with a few of the Dell models we use.
There is no error in the GUI, but it never downloads, extracts, and imports the drivers. Effected models are the Optiplex , Optiplex , and Optiplex I have found the issue, it applies to models with multiple sub-models, such as , M, AIO etc. I have just removed a wildcard on this line —.
Well Liked Process and Brain saver allowing more Coffee time, we have a total of 13 Dell models across 3 OS platforms using x86 and x64 on each this is going to same me whole bunch of time every quarter when we run updates against hardware. I will pass on this feedback though. Truly next level tool this, on have one problem when I put in my server name it keeps saying sccm server specified not found — I am an admin on the box and in configMgr.
I presume when you say it wont connect to your server you are running the script remotely?. This appears to be for different versions, like ATG and XFR, but the tool does not distinguish between these in the list. Also, I had 2 models which did not download the driver cabs E, E Next update in 30 seconds.. Unfortunately in some cases the model naming convention is not standardized, however I will add in exception rules where required. I am also working to add in another Dell XML feed for BIOS updates not currently listed in the tool and additional package checks, all of which will be in the next build in a couple of days.
I am excited about the prospects of this utility. I am testing it in my CM test environment which is running I am running into some issues and notice a few flaws in the UI of the tool.
Would you prefer an email communication vs posting my findings here? I am not sure if this is working or not. I had to force quit Powershell but the driver package does show up in ConfigMgr. I am not sure if this is normal or not.
Btw thanks for this tool, it will really help a lot. Please let me know the OS you had selected and I will run through this to see can I replicate the issue. Thanks for providing this tool. However, I am running into an issue when trying to use it. Site Server populates just fine. We have a physical firewall for the whole campus, so Windows Firewall is disabled.
I enabled PS Remoting, no change. So I was able to run it successfully on a different computer. Start-BitsTransfer : The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. Mana gement. You cannot call a method on a null-valued expression. I presume you are running the account as a different user on the machine?.
If so can you log on interactively on the machine and test the script?. That did it! We use standard credentials to log in with an admin login to run things as needed. Logging in as the admin account allowed everything to work, including reading the XMLs.
0コメント