That's great! Thanks. Also...will the error we're all (or most) getting
when adding a network printer the old fashioned way (i.e. browse to the
printer via Network places, right-click on printer and connect) be fixed in
the final version of Vista? Seems a bit obscure to have to add a network
printer as a local printer. Thanks.
-David
> I'll check around but no promises since it's not a printer function.
I found someone to ask about the UI0detect service. Is it running on the
laptop? I'd verify this first then try the driver installation again.
The Add Printer Wizard will detect if you are on a managed network or an
unmanaged. A managed network is basically one that has an Active Directory.
Unmanaged is the one in your home or small business (but I'll bet there's a
number of IT pro out there who will take offense to this description). On a
managed network, the default search finds printers that have the same
location string as the one you are currently attached. If no one has ever
filled this information in then the default location is empty (I guess this
managed network is not really that managed- no offense) and the search will
only find published printers with no location field. At this point the
user needs to Click Not in the list to get to the point where they can type
in the print server name
On an unmanaged network, the default search finds printers that are hung off
TCP/IP addresses, that are shared, that are Bluetooth, and that are Web
Services Devices.
This is configurable in gpedit.msc
We fixed the bogus connection problems when a printer has been renamed. As
well as a few other issues. Vista will not support connecting to print
server devices that appear as a \\machinename unless they support Samba 3.0.
One will be able to connect to them as a local printer using
\\machinename\printersharename.
When you are using Server 2003, the driver installed there should be the one
that is downloaded to Vista (x86 to x86). You should not be required to
install the driver locally (unless Dell requires this).
Let me know if the UI detection service is running on the laptop.

Signature
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
> That's great! Thanks. Also...will the error we're all (or most) getting
> when adding a network printer the old fashioned way (i.e. browse to the
[quoted text clipped - 6 lines]
>
>> I'll check around but no promises since it's not a printer function.
Alan Morris [MSFT] - 31 Oct 2006 20:05 GMT
from the dev on this
The service should start only when the session 0 window is up.
The troubleshooting steps are as followed:
· Repro
· If no instances of ui0detect.exe run (taskmgr), sc start ui0detect
· If the user dialog shows up then, it means that the hook dll doesn't
work
· If it still doesn't, then I'd question whether the S0 dialog is
really present.

Signature
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
>I found someone to ask about the UI0detect service. Is it running on the
>laptop? I'd verify this first then try the driver installation again.
[quoted text clipped - 39 lines]
>>
>>> I'll check around but no promises since it's not a printer function.