Microsoft Zune Phone drivers

Hi guys,

I've already made thread in MS answers forum, but as this seems more of a packaging issue I would like to give it a shot here too.
This is what my problem is about:
Good day,

I am trying to implement Zune software (v 04.08.2345.00) into corporate network for users to connect their Nokia Lumia 800 phones to PC. Targeted OS - Windows XP SP3

So far I've successfully installed Zune on test pc with SCCM 2007 using MSI's with transform files (MS Application Error Reporting MSI, Mobile Device Updater MSI, wmfdist11-windowsxp-x86-enu.exe and Zune MSI ). If phone is connected it automaticly configures drivers and I can manage phone via PC, BUT that is only with Admin account.

If software is deployed and limited users connects his phone he is prompted for administrative rights. I would like to get to the point where I can install these drivers along with Zune MSI so limited users would'nt need any additional rigts to connect their phones.

I've tried to install manually drivers from %programfiles%\Zune\Drivers\Zune\ and %programfiles%\Zune\Drivers\ZuneBusEnum\ with DPinst.exe utility and they show up as installed, but when i log in with limited user admin rights are still promted.

After this is looked at logs and saw that Microsoft WinUsb Install-v1.0.exe and Microsoft User-Mode Driver Framework Install-v1.9-WinXP-Srv03.exe were installed at the time when phone is connected, but installing them manually before connecting phone doesn't help either.

I've also tried to use devcon.exe to install these drivers but I can't get it working either because I can't find the right HWID like from MS example.

Could someone point me to some direction how to install these drivers for Lumia 800 along with Zune MSI so limited users can use this?

Thank you in advance.
Taken from [url=http://answers.microsoft.com/en-us/zune/forum/zune_install-pc/how-to-install-zune-drivers-for-lumia800-with/4520f847-0d15-4497-8deb-33eb0a468826]MS Answers forums[/url]

Have anyone here had a hand on with installing drivers for Windows Phone's? TYIA
To sum this up, here's a some snapshots from the state where phone is installed and connected successfully.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: anonymous_9363 9 years ago
Red Belt
Check the MSI for properties that determine that the user is an administrator. The most common are 'IsAdmin' and 'Privileged'.
Posted by: Aivars_s 9 years ago
Senior Yellow Belt
If you ment MSI conditions they have nothing to do with right elevation. This is not triggered by MSI but by Windows. When phone is connected driver installation balloon appears as always and it recognizes device ID (showing it's name not "unknown device") so drivers are present, but for some reason they must initialize or something. I don't know the whole workflow of driver installation so I'm asking if somebody else may know this.

Posted by: Aivars_s 9 years ago
Senior Yellow Belt
Just an update with progress on this issue.
I've managed to install these two devices before phone is connected using:
devcon.exe install "Zune.inf" "USB\VID_045E&PID_04EC&MI_00"
devcon.exe install "WMZuneSerUSB.inf" "USB\VID_045E&PID_04EC&MI_01"

So after this devices appear in device manager even before phone is connected. But still I got prompt for admin. I guess that's because there are two HWID's per device with original install and I haven't figured out yet how to replicate that with devcon.

Will keep this update and also hoping for some suggestions :)
Posted by: bhagu_krish 8 years ago
Orange Belt

Hi Aivars_s,
Now, I am working with this application. Stucked with the same issue. Did you find any solution for this?


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ