HP OfficeJet 6700 throught Remote Desktop in Windows Server 2008

i access a windows server 2008 machine via remote desktop i want to print to my local hp officejet 6700 printer i have my printer resources shared i have downloaded the OJ6700_Basicx64_1315.exe which says its for win server 2008 yet when trying to install it says my OS is not supported. is there any other driver i can use? any way to use a generic driver?

Yes, you can try to download the 990c driver and it should work. (Shane_R) has a post that gives you directions on how to download the alternate drivers. Here is a link that may assist you.
http://h30434.www3.hp.com/t5/Printer-All-in-One-Software-Drivers-e-g-Windows-8/How-to-Assign-Alterna...
Let me know if this helps, thanks.
**Click the KUDOS star on the left to say 'Thanks'**
Please mark a reply "ACCEPTED AS SOLUTION" if it solved your problem, so others can find it.

Similar Messages

Using drag and drop in remote desktop on windows server 2008

we running an application on windows server 2008 terminal services .. this application was support drag and drop functionality .. i understand that terminal services on windows 2008 is supported to drag and drop but is not happening !! even when i run remote desktop connection on this server the drag and the drop is not working !
i need to enable the drag and drop for windows 2008 terminal services ..
Thanks in advance

Hello Ayman,
If your requirement is to drag and drop files between local and remote sessions, Danny is right. Drag-and-drop feature is not supported in Windows Server 2008-based Terminal Server, which is a by-design behavior hard-coded in the current version of the Remote Desktop Protocol.
As a workaround, I recommend you to use copy-and-paste function instead of drag-and-drop. To enable the copy-and-paste between local and remote session, please enable the clipboard redirection in Windows Server 2008-based RDC. (In Windows Server 2003 environment, local drive redirection is needed.)
Hope it helps. Thanks.
Best Regards,
Lionel Chen

Can I use Remote Desktop Connection (windows server 2008) even if no user is logged in?

I'm configuring a Server, running Windows Server 2008, to be accessed remotely. Suppose no user is logged in in the server (if it was just turned
on, for instance). Can I use the "Remote Desktop Connection" feature to log in remotely in this case? Or is it always necessary to have a user locally logged in, to remotely log in to one of the users available?

If its a fresh installation, RDM might not work at first.
1. You need to check firewall and allow Remote Desktop. To be specific, communication to port 3389 TCP
2. Right click My Computer --> Properties --> Remote tab
Enable Remote Desktop
Allow connections to this computer
Click users and grant the permissions for the users. By default, Administrators do have the permission. An also, the users who are members of the 'Remote Desktop Users' security group also have the permission

Remote Desktop To Windows Server Very Slow

I have OS X 10.6 running on a MBP and a problem that seems to be growing worse over time. I am using Remote Desktop (both CoRD and Microsoft Remote Desktop) to gain access to remote servers. One is a Windows Server 2008, the others are Windows Server 2003. Initially all was fine, but over the last 2 months access to the W2K server has crawled to a halt. Now, when accessing the other servers I'm having the same issue. I have tried different clients for remote access, used different high speed Internet connections (FIOS, a private network) and the result is the same. Very, very slow connections.
I have also tried using a different login on the laptop to no avail.
I booted Windows on my MBP using Parralels Desktop and tried using Windows RDC to the same servers; that works fine. In fact, I can access the servers very quickly using my iPhone's Remote Access software using the same Internet connection (home WiFi) as my MacBook Pro.
So I can only assume it's an issue with OS X 10.6, since different devices using the same Internet connection can make a much faster connection. But I can't find any similar posts on the issue.
Any ideas are appreciated!

Hi Jason,
From the error message, it seems that take time to load the user configuration properly from the server and then the network connection was slow. Please refer to following article
and check if help you to troubleshoot slow logon.
Troubleshooting
Slow Logons
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Meanwhile, please refer to following thread and check if can help you.
Remote
Desktop Services has taken too long to load the user configuration from server Event ID 20499
Hope this helps.
Best regards,
Justin Gu

Web Access for Remote Desktop on Windows Server 2012

Hello,
i've a Windows Server 2012 without a domain. So i installed the remote desktop session host, the remote desktop license server and the remote desktop gateway as a server role only. All is working fine. Without a domain, no management tools for remote
desktop are available. So i configure the remote desktop via the registry. I define (via registry) some remoteapps, too. All values are copied from a running Windows Server 2008 R2. So the remoteapps are runing.
Now i want to use the new Microsoft Remote Desktop client for Android. To use a remoteapp i must define a remote resource. To define a remote resource i need a url to the web access for remote desktop. So i installed the web access. But if i login to the
web access, i don't see any remoteapp. What's wrong? I've set the ShowInTSWA to 1. What must i do to access an existing remoteapp via web access?
Martin

Hi Martin,
Server 2012 RD Web Access is designed to retrieve published RemoteApps and Desktops from a Server 2012 RD Connection Broker and/or a Server 2008 R2 RD Session Host server. From your description it doesn't appear that you are using either of the above.
I know it is a more complicated set up, but you should consider having a domain, creating a RDS deployment, etc., so that you can use the full featureset as it was intended. You can do it all on a single server if needed. For Server 2012
there is a hotfix that needs to be applied to permit RD Connection Broker to work on the same server instance as active directory.
-TP

MacBook with OS X and remote desktop to Windows server

I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server. It is easy to do so with a Windows PC with Windows XP. However this necessitates carrying a Windows machine while travelling. I like the MacBook Pro I have and would like to use it for remote access. I do not want to install Windows on the MAC even though I can do it with my MacBook Pro.
Any thoughts? Or are there sittes addressing this issue?
Thanks in advance.
Raj

"I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server."
Please search the discussions before posting. Questions regarding ARD controlling Windows computers have been asked and answered dozens of times.
Install VNC server software on the Windows server and control with ARD, or just use Microsoft's own Remote Desktop Connection for Mac.

OS 10.6.3 and Remote Desktop for windows server, PDF Printer problem

We are using Remote desktop for mac by windows in the office to work on a remote windows server, On the server we are using a business software (Mamut) for sale. In OS 10.5 we are using the PDF Printer to transfer PDF (invoice) from the business software (Mamut) 'Mamut is seeing the PDF printer as any other printer' to the desk top of your mac, so we can attach the PDF to a mail before we send it out to a customer, but in OS 10.6 the PDF printer is removed! So we need a different way of transfer the PDF from the windows server to the mac desk top.
So now I am wondering if any one has a suggestion on how to fix this! if not we can't upgrade to OS 10.6, and that would be a shame!

The thing is that in Mamut, we hit print, and because we us the PDF printer as Printer for Remote desk top, it pup up on the desk top of the mac, as a PDF. But in OS 10.6 there isn't any PDF printer to install, so then we have to make a PDF on the windows server and move it from the server to the mac, by mounting the HD from the Mac to the remote desk top, so it become edible in from the server. I think this is cumbersome.

How to allow more than two users on remote desktop on windows server 2012 foundation?

i have a dell server power edge T300 with windows server 2012 foundation. I am unable to connect more than two remote desktop at once.

Hi,
Add to Brain, you cannot have more than 15 user accounts in Windows Server 2012 Foundation.
In order to access a hosted application, such as Microsoft® Office, a license for Windows Server 2012 Remote Desktop Services is required for each user account (not to exceed 15 user
accounts) that directly or indirectly uses RD Gateway to host a graphical user interface, including using Remote Desktop Connection (RDC) client. When using Remote Desktop Services, you may not install or use Remote Desktop Connection Broker or Remote
Desktop Virtualization Host role services. For more information about Remote Desktop CALs , see http://go.microsoft.com/fwlink/?LinkId=140238.
http://technet.microsoft.com/en-us/library/jj679892.aspx
Hope this helps.
Jeremy Wu
TechNet Community Support

Problem Connecting more than 3 Remote destops to windows server 2008 R2 standard

Sir,
We have bought widows2008r2 standard server with 5 cal & 8 remote desktop License from M/s Mukesh Info Serve.
As there office is closed at Hyderabad we request you to resolve this issue at the Earliest.
Thanking you
K.N.Ramesh

Hi,
Please let us know if you have configured the RD Session host role, RD licensing server role, install the RDS CALs and properly configured the roles. If not, you can only have two concurrent
administrative remote sessions.
Thanks.
Jeremy Wu
TechNet Community Support

Routing and Remote Access Logs (Windows Server 2008 R2)

Hi,
I have a Windows 2008 R2 server running Routing and Remote access and users are using PPTP VPN's to connect to our network.
I have been asked to find logs for the following for connections in to our server
Username used for connection
Computer Name
IP Address used by computer connecting
Start/End time of VPN session
Date
Encryption used
I found an article stating to enable RRAS logs you need to run the following command
To enable RAS logs run command “netsh ras set tracing * enabled” and found a series of logs created in this location C:\Windows\tracing
None appear to contain the information I am looking for and was wondering if I was doing this correctly and if not how I am meant to extract this information?
If you require any more details just let me know.
Kind Regards
David

Hi,
I can’t sure which article you have read, but fur the 2008R2 the RAS to enable the log and the debug log in the KB is descried like this, I recommend you to try the KB
mentioned method.
To configure RRAS to enable logging
1. Start Server Manager. Click Start, click Administrative Tools, and then click Server Manager.
2. In the navigation tree, expand Roles, and then expand Network Policy and Access Services.
3. Right-click Routing and Remote Access, and then click Properties.
4. On the Logging tab, select Log errors only, Log errors and warnings, or Log all events, depending on how much information you want to capture.
5. Click OK to save your changes.
The related KB:
RRAS: Logging should be enabled on the RRAS server
http://technet.microsoft.com/zh-cn/library/ee922651(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server 2008: Add Links to Desktop

Hello,
Does anyone know if it is possible to add hyperlinks to videos or documents to client's desktops on Windows Server 2008? I am trying to use a similar functionality to Active Desktop which allows desktop wallpaper to be .html files.
Thanks

Yes, create an IE shortcut for the hyperlink and simple shortcut for the documents, with GPP it's easy with GPO. (Adding
shortcuts on desktop using Group Policy Preferences in Windows 8 and Windows 8.1) (wrote for windows 8, but the same gpo can be applyed to 2008R2)
Regards, Philippe
Don't forget to mark as answer or vote as
helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

To install Remote Desktop Services User CAL on Windows Server 2008 R2 Enterprise Edition with SP1

Dear Sir,
Presently we have installed Windows Server 2008 R2 Enterprise Edition with SP 1. And now i would like to install Remote Desktop Services User CAL on this server. I have 25 digit product key of Windows Server
2008 R2 Remote Desktop Services User CAL (20). Downloaded this product key from our MSDN Subscriptions.
Kindly suggest me how to install (CAL server with product key that i have) and configure remote desktop services on my above existing server also how to point other server with my CAL server.
Thanks

Hi,
1. Install Remote Desktop Session Host and Remote Desktop Licensing Role Services using Server Manager.
2. Open RD Licensing Manager (licmgr.exe), Activate your server, then install your license
3. In RD Session Host Configuration (tsconfig.msc), set the Licensing mode to Per User and Specify your RD Licensing server name (itself). If you want you may configure these two settings via group policy setting instead. The path of the
group policy settings is Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
4. You may point other RDSH servers to your RD Licensing server using RD Session Host Configuration or via group policy as mentioned above.
5. Optionally you may consider installing other Remote Desktop Role Services such as RD Gateway, RD Web Access, RD Connection Broker, etc.
-TP

How to recognize if application is installed using "Install Application on Remote Desktop" option on Windows Server 2008 R2

How to recognize if application is installed using "Install application on remote desktop..." option in Control Panel in Windows Server 2008 R2?
Basically, as administrator, I can't say if the user installed application using "Install application on remote desktop..." in Control Panel or he just installed it by clicking the .msi executable. I can't find anything that makes any difference.
I could not find anything in the registry. I am quite confused.
Thanks,
Aleksandar9

Hi,
Thank you for your posting in Windows Server Forum.
Please make sure that you are using category view of control panel-programs to check the application. And in addition to “install application on Remote Desktop server” user can also use command line also.
change user /install
change user /execute
change user /query
“The first time you run the application, it searches the home directory for its .ini files. If the .ini files are not found in the home directory, but are found in the system directory, Terminal Services copies the .ini files to the home directory, ensuring
that each user has a unique copy of the application .ini files. Each user should have a unique copy of the .ini files for an application. This prevents instances where different users might have incompatible application configurations.” (Quoted formthis
article).
Hope it helps!
Thanks,
Dharmesh

Windows Server 2008 R2 Remote Desktop - The requested session access is denied

Hi, I have been using Windows Server 2008 R2 since it was released, and have 100 servers up and running. I configured Allow Remote Desktop on all of them and have been able to connect to them and manage them via RDP since then. I also have two servers configured as Remote Desktop Services.
That was up until yesterday. Yesterday afternoon I started getting the The requested session access is denied. I managed all Terminal services via Group Policy and have three users entered.
I am connecting to the servers via Windows XP SP3 and Windows 7. Both clients have been updated to the latest Remote Desktop Services client.
I have been searching for the answer, and I am not finding it.
I have also tried KB954369 without any success.
Thanks,
Brian

Ok, from my trials and tribulations and discussions with Microsoft I have identified the following;
Assumptions;
A. My terminal server is in domain widget
B. All the users are in domain contoso
1. I had the Terminal Server configurured with a specific Login, which would launch a specific application only and not give them any desktop functions. Wiht this configured this way, I get the error I wrote about.
2. If I turn the specific login off, then I can login normally and perform the functions as Administrator that I need/want to do.
3. Microsoft said to configure the Terminal Server with Single Sign-on. I did as instructed and went thru all the steps, however because my terminal server is in domain widget, the users get prompted twice each time for login. Once on the website, and then again as the application launches. Microsoft said that the users needed to Remote Desktop Client 7.x or the self-signed certificate that I have has to be included in the domain contoso certificate authority so that they will not be prompted for the second sign-on.
4. Conclusions - I need to have a chat with our enterprise security team about including the self-signed certificate in the contoso certificate authority. I need to also work on my RDWeb website so that it meets our company standard look.
Here are the links that Microsoft provided;
http://technet.microsoft.com/en-us/library/cc772108(WS.10).aspx
Enable RDC Client Single Sign-On for Remote Desktop Services
http://technet.microsoft.com/en-us/library/cc742808.aspx
Blogs -
http://blogs.msdn.com/rds/archive/2007/04/19/how-to-enable-single-sign-on-for-my-terminal-server-connections.aspx
http://blogs.msdn.com/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
http://blogs.msdn.com/rds/archive/2009/06/05/publishing-in-windows-server-2008-r2.aspx
http://blogs.technet.com/pfe-ireland/archive/2008/09/05/windows-server-2008-terminal-services-presentation-virtualisation-and-windows-xp-clients.aspx
I hope this help you in your troubleshooting.
Brian

Novell login not available with remote desktop on windows 7

Installed Novell Client 2 SP3 for Windows Server 2012 on my terminal server. When I log in from Windows XP to that terminal server I am getting an option to login with Novell Client. On Windows 7 however I only can logon to the server. What am I missing here?

djaquays <[email protected]> wrote:
> Mostly, that MS RDP for Mac ignores the authentication level:i:0 option
> in an RDP file and there's no GUI equivalent to force legacy
> authentication.
Microsoft's Network Level Authentication (NLA) feature is supported in
Windows Server 2008 and later terminal servers, and supported by
Remote Desktop Connection (MSTSC) 6.x and later terminal clients.
Windows XP did not ship with a MSTSC 6.x terminal client, but it is
available optionally through Windows Update.
The NLA authentication is essentially requiring that valid Windows
user account credentials for the Windows Server machine must be
provided /before/ the RDP-level terminal session connection is even
attempted or permitted. If the Windows user credentials you're logged
in with on the client workstation do not already satisfy this
requirement, the NLA-aware MSTSC clients will prompt you for valid NLA
credentials before even attempting to open the terminal session.
In other words, NLA doesn't directly have anything to do with whom you
will become authenticated as within the terminal session, or whether
you'll reconnect to some other already-running terminal session; it's
a new default mechanism which requires Windows credentials for
authorizing you to create an RDP connection to the Windows Server
machine "at all."
Unfortunately Windows Server 2008 and later don't permit you to turn
NLA completely off. You can configure the Windows Server to always
require NLA, which means pre-MSTSC 6.x terminal clients will be unable
to connect. Or you can configure the Windows Server to "not require
NLA" ("Allow connections from computers running any version or Remote
Desktop"), but this still means Windows Server will use NLA if the
workstation's MSTSC client supports NLA.
The only option which has been available to "disable NLA" even when a
Windows Server 2008 or later terminal server and a MSTSC 6.x or later
terminal client are involved is to configure the
"enablecredsspsupport:i:0" setting in the MSTSC client's .RDP file
(e.g. default.rdp in the My Documents folder), in addition to
configuring the terminal server to "not require NLA."
Once you have "Allow connections from computers running any version or
Remote Desktop" set on the Windows Server, and
"enablecredsspsupport:i:0" set in the MSTSC client, now you're back to
the Windows XP & Windows Server 2003 behavior where an RDP terminal
connection can be established without first having to supply NLA
credentials, and the first thing the MSTSC client user will experience
is the full normal credential provider-based login experience just
like you see at the physical console of the terminal server.
Note that if you do leave NLA enabled and supply NLA credentials
during the MSTSC connection attempt, after successfully using those
credentials to authorize creation of the RDP connection, the MSTSC
client will /also/ default to using the NLA credentials as default
credentials to attempt logging on with within the terminal session
itself. In other words, if you successfully supply NLA credentials,
by default you also become logged in on the terminal session and go
straight to the desktop of the Windows user account specified in the
NLA credentials. So even though "NLA credentials" and "whom I will
logon as within the terminal session" are two separate things, by
default the MSTSC client tries to use the same credentials for both.
But it's not that the NLA credentials "must" be used for logging in on
the terminal session; that's simply the default behavior. If you
leave NLA enabled on the Server 2008 or later terminal server, after
NLA credentials are successfully used to authorize creation of an RDP
connection, if you wanted to instead be prompted within the terminal
session with the normal credential provider login experience, enable
the "Always prompt for password" on the Windows Server 2008 or later
terminal server.
(On the Server 2008 or later machine, under "Administrative Tools"
find the "Remote Desktop Services" group and launch the "Remote
Desktop Session Host Configuration" console. Highlight/select the
"RDP-Tcp" connection, right-click and select "Properties". On the "Log
On Settings" tab elect "Always prompt for password".)
That sounds like probably the scenario which fits best for the "I have
a Macintosh-based client which doesn't allow enablecredsspsupport:i:0
/ authentication level:i:0." You would leave NLA enabled on the
Server 2012 machine, but enable "Always prompt for password" in the
RPC-Tcp connection properties on the Server 2012 machine. Such that
after NLA authentication was performed and Windows allowed creation of
the terminal session, instead of immediately also attempting to login
within the terminal session as the Windows account specified in the
NLA credentials, Windows will instead present the normal interactive
credential provider login experience to allow the user to specify whom
they want to login as.
Finally, note that everything described above applies even to a
Windows Server and Windows client workstation that do /not/ have the
Novell Client for Windows installed. The same mechanisms remain in
effect even once the Novell Client is installed; the presence of the
Novell Client just changes what credential providers would be used or
presented within the terminal session once the terminal session was
allowed to be created. The fact that NLA is required by default and
requires valid Windows credentials in order to authorize an RDP
connection is still the same, regardless of whether the Novell Client
is present or not.
Alan Adams
Novell Client CPR Group
[email protected]
Novell
Making IT Work As One
www.novell.com
Upgrade to OES Community
http://www.novell.com/communities/co.../upgradetooes/

HP OfficeJet 6700 throught Remote Desktop in Windows Server 2008

Similar Messages

Maybe you are looking for