IT BS thread

That's what I thought, but then i read this:

General
Cable Type: Video / audio adapter

That is what confused me

 

http://en.m.wikipedia.org/wiki/DisplayPort

I stand corrected, it looks like it does carry audio. If you try it, I would be interested in how it works.

 

Alright I guess I'll try it. Doesn't cost too much so it won't kill me if it doesn't work

 

By the way, it works for both audio and video.

It is set up as dual monitors with my laptop and my TV. And i just set the audio default to the TV so that all sounds come from the TV instead of the computer.

Works pretty well.

 

awesome. good to know the display port does audio as well.

 

Maybe you guys might have an idea on what to do here. I have a print server that I access through windows explorer by ip address, I then enter the username and password, find my printer and install. I also run a login script to map drives, I want to map a drive that points to the folder that the shared printers exist in, however I can't figure out how to do that. When mapping a drive it requires a folder, but when I browse the network the printers aren't in a folder.... so for now I just have it set to ipaddress\c$ so that it save the user account info, it would be great to map it to the shared devices. Any ideas?

 

My question is .. why?

Credentials should be automatically passed to the print server when connecting to install the printer or print a job. The desired printers should stay installed and connected unless the shared printer permissions change.

FWIW, A mapped drive connects to a data/disk resource which a printer is not.

 

I think he's installing the drivers locally. At least that's what I got from his request.

 

Correct

 

maybe I am misunderstanding... the point of a print server is to host queues and drivers. The first time you connect to a shared printer the drivers are pushed down to your local machine. This only needs to be done once per printer, hence why I am confused as to why a perpetual mapped drive is desired.

EDIT: understood that it would be convenient if you have tons of printers being installed by users regularly.
In that case you could create a shared folder on the print server with .LNK files for all the printer shares

 

Can you describe your environment? Do you run AD? Why not use one machine as the print server? Simplifies things.

 

This is true for server setups. But some shops want the drivers installed locally-which makes maintenance a real PITA.

 

print server was mentioned in the first post...

and drivers are ALWAYS installed locally even when connecting to a shared network printer. the difference is that they have to be managed locally if the print queue resides on the local machine instead of a print server.

this ^^^

 

I guess I am getting confused here but why not just connect to the printers that are on the print server ?

 

This is what I was thinking by how the question was asked.

 

No AD, but we connect to our local hospitals domain, since network printers are a user based setting, for each user that signs in I have to install their printer. Since I have a script anyway to map drives, it would save a few clicks for me if I could just browse to the printer, rather than search for it.

 

is the script that maps drives a vbscript? you can map printers with vbscript as well.

 

Nope, simple cmd script... Sounds like I need to learn vbscript.

 

There should be an easy way to do it via CMD also... not totally sure though.

 

I can get you some examples. We use vbscript at our office to map drives and printers based on AD groups. It really isn't too hard, especially when you have a template to go off of.