I'm tring to connect to printers that are on a Windows 2003 Server. They are
Dell 1710 and 1815n printers. I have even went to makeing sure to load the
drivers on the vista machine by going to file and server properties. The
drivers are installed localy on the vista machine. When I try to connect to
them I see them fine through the network I see them fine. I then click
connect and it ask me if I want to install the drivers and I choose yes. Then
it says Connecting to "the printer" on "the computer". It then hangs on here
the green bar goes accross but never finishes. I have left it up over night.
Any thoughts on how to diagnosis this more. i have looked in the event logs
and nothen is written there. Thanks Josh

There's this window I noticed on my machine...kind of obscure to tell you the
truth. Says something about user interactive mode. When you click on the
button to take you there it shows the printer's control panel or whatever
requires your attention. I believe Dell printers are offspring from Lexmark
and mine is a Lexmark so I can say that this is probably your case as well.

Anyone know anything about this user interactive mode?


"Josh" wrote:

I'm tring to connect to printers that are on a Windows 2003 Server. They are
Dell 1710 and 1815n printers. I have even went to makeing sure to load the
drivers on the vista machine by going to file and server properties. The
drivers are installed localy on the vista machine. When I try to connect to
them I see them fine through the network I see them fine. I then click
connect and it ask me if I want to install the drivers and I choose yes. Then
it says Connecting to "the printer" on "the computer". It then hangs on here
the green bar goes accross but never finishes. I have left it up over night.
Any thoughts on how to diagnosis this more. i have looked in the event logs
and nothen is written there. Thanks Josh

I believe you mean the Interactive Services Detection service. Session 0,
the console session, is basically gone. When one logs on now it is in
session 1. Some printers throw dialog to session 0. Drivers that do this
normally have a problem in Terminal Service scenarios since the dialog goes
to the wrong session. UI0Detect.exe monitors the session 0 desktop and any
application sending to session 0 will prompt to bring the user to the
session 0 space to respond to the prompt.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"DavidIQ" wrote in message
...
There's this window I noticed on my machine...kind of obscure to tell you
the
truth. Says something about user interactive mode. When you click on the
button to take you there it shows the printer's control panel or whatever
requires your attention. I believe Dell printers are offspring from
Lexmark
and mine is a Lexmark so I can say that this is probably your case as
well.

Anyone know anything about this user interactive mode?


"Josh" wrote:

I'm tring to connect to printers that are on a Windows 2003 Server. They
are
Dell 1710 and 1815n printers. I have even went to makeing sure to load
the
drivers on the vista machine by going to file and server properties. The
drivers are installed localy on the vista machine. When I try to connect
to
them I see them fine through the network I see them fine. I then click
connect and it ask me if I want to install the drivers and I choose yes.
Then
it says Connecting to "the printer" on "the computer". It then hangs on
here
the green bar goes accross but never finishes. I have left it up over
night.
Any thoughts on how to diagnosis this more. i have looked in the event
logs
and nothen is written there. Thanks Josh

That's EXACTLY right. I do have a problem with this though. The dialog box
that informs you of this window shows up on my desktop PC which has Aero on.
My laptop doesn't have Aero on and does NOT show this dialog box to take you
to the Interactive Services screen and I'm SURE it's got to be there since
it's the same printer that I installed on the desktop and thus should be the
same installation behavior. Any way to manually access this "Session 0" you
speak of? Thanks!

-David


"Alan Morris [MSFT]" wrote:

I believe you mean the Interactive Services Detection service. Session 0,
the console session, is basically gone. When one logs on now it is in
session 1. Some printers throw dialog to session 0. Drivers that do this
normally have a problem in Terminal Service scenarios since the dialog goes
to the wrong session. UI0Detect.exe monitors the session 0 desktop and any
application sending to session 0 will prompt to bring the user to the
session 0 space to respond to the prompt.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

I'll check around but no promises since it's not a printer function.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"DavidIQ" wrote in message
...
That's EXACTLY right. I do have a problem with this though. The dialog
box
that informs you of this window shows up on my desktop PC which has Aero
on.
My laptop doesn't have Aero on and does NOT show this dialog box to take
you
to the Interactive Services screen and I'm SURE it's got to be there since
it's the same printer that I installed on the desktop and thus should be
the
same installation behavior. Any way to manually access this "Session 0"
you
speak of? Thanks!

-David


"Alan Morris [MSFT]" wrote:

I believe you mean the Interactive Services Detection service. Session
0,
the console session, is basically gone. When one logs on now it is in
session 1. Some printers throw dialog to session 0. Drivers that do
this
normally have a problem in Terminal Service scenarios since the dialog
goes
to the wrong session. UI0Detect.exe monitors the session 0 desktop and
any
application sending to session 0 will prompt to bring the user to the
session 0 space to respond to the prompt.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

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


"Alan Morris [MSFT]" wrote:

I'll check around but no promises since it's not a printer function.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

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.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"DavidIQ" wrote in message
...
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


"Alan Morris [MSFT]" wrote:

I'll check around but no promises since it's not a printer function.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

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.




--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Alan Morris [MSFT]" wrote in message
...
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.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

"DavidIQ" wrote in message
...
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


"Alan Morris [MSFT]" wrote:

I'll check around but no promises since it's not a printer function.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto