Details required :. Cancel Submit. In reply to divrdrew's post on October 22, I finally figued it out after four days and many hours on the phone with Microsoft. Microsoft claimed that it was related to my router settings, but I didn't believe it since the remote computer saw my iPhone just fine when it was connected locally. After simply playing around, here's what I found On the remote system, when you try to add a 'local' printer, there's a drop down menu with a list of local ports that your remote system sees.
Some of those will be on the remote system, but others will be on your local system. Make a note of the ones that are seen on your local system. Next, on your local system, in the settings for your functioning printer Printer Properties, Ports Tab , there's a tick box that says "Enable Printer Pooling. Here, you need to tick the box that your remote system is seeing in my case, it's COM3 , but make sure that your exisitng port remains checked as well in my case, an IP port for my wireless router.
Basically what you're doing is on your local system, you are pooling your exising printer setup with a port that can be seen by your remote system. Then, on the remote system, install the printer drivers but don't select a port. Then go into Printers and add a printer. Select 'local' setup for that and when asked for the port, use the port you checked in the previous step on your local system in my case, I selected COM3 on my local system.
Select your printer from the list. Also make sure of course that the boxes are ticked to allow local resources in the remote session. Office Office Exchange Server. Not an IT pro? Learn More. Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.
Archived Forums. Windows 7 Networking. Sign in to vote. The printer is connected via ethernet cable, using standard pscript drivers and runs perfectly for local printing. The exact same pscript drivers are installed on the server. Printer sharing obviously enabled in Advanced Sharing Options. The video communication tool Teams saw a huge increase in users, as did the reporting tool PowerBi. Obviously, those that already started deploying are putting the new DaaS offering to good use.
Is it possible to react to the current pandemic and get WVD up and running now? Based on our experience, deploying Windows Virtual Desktop is something that certainly takes a bit of planning, time and consideration when building. Unfortunately, the current circumstances make this quite difficult. One factor that prevents the swift deployment of Windows Virtual Desktop is that the cloud-based Azure Active Directory handles the permissions your users have.
Companies that already had Azure Active Directory in place are therefore best placed to react immediately to the situation.
0コメント