I have one Stand alone windows VM in Azure means no Site to site or Express Route or P2S exists. So my question is how can I install the printer in the VM and print anything from that to my local printer?
Use the built-in Remote Desktop printer mapping - no drivers necessary since it will tunnel the print job through the RDP session back to your computer.
By the way, any infrastructure-related questions should be asked here instead -
https://superuser.com
Related
I want to be able to use a camera on an Azure Virtual Machine using Windows 10.
Camera feed can either come through on local machine or a feed from another machine. Either way I get the below error:
We can't find your camera, NoCamerasAreAttached.
Even though I have enabled both through the connection and enable USB Redirection in Windows 10. incl gpedit.msc
the easiest solution I discovered is that you can go to the settings of Remote desktop connection in the general tab, go to the connection setting and select your RDP file of azure VM:
Second, in the RDP setting go to the local resource and then go to the local device tab in setting and click on the 'more' button:
Enable both checkpoints inside the video catalog that include the webcam option:
goog luck! hope it saves your day!
#syedasadrazadevops
First of all, make sure you have enabled devices redirection in the Remote Desktop connection via MSTSC. And check if you have enabled USB Redirection in both sides of the client and VM via GPEDIT. For more details, Refer to this case.
A VM (virtual machine) has been provided for me to develop against (IIS) that is running Windows Server 2008. How can I determine the VM's publicly-facing URL? (that my users can hit with their web browser)
I am able to remote in to the VM via Remote Desktop. Also, this is an existing VM that has been around for some time (I am just new to using it).
Thank you in advance.
I think this is what you are looking for:
https://technet.microsoft.com/en-us/library/cc731692(v=ws.10).aspx
Essentially, you have to bind an IP (and/or port) for your IIS website. It's fairly straightforward.
I figured it out, there are two methods:
1) on the command line ping with "-a" like this: "ping -a 123.45.678.90"
2) on the command line run "ipconfig /all" and put the Host Name in front of the Primary DNS suffix.
I am working on a project and am attempting to run a FTP daemon on an azure vm running the Technical Preview 2. The Daemon reports that it is behind a NATed router, and as such I can not connect in via another means but the remote desktop connection. (I will be running other daemons on this server as well, and they also have this problem)
I need some way to access this router that my Azure server is behind to configure it to allow for the range of ports that i need to access.
The fine folks at MVA instructed me to ask here, so here I am.
I think you just need to open the port (endpoint setting in the portal) to the virtual machine, so check this article out.
Also, make sure the local firewall isn't blocking that ftp port... I'm pretty sure it's off by default.
I am trying to development a tool to deploy environment with hyper-v, I need to create VMs with template and install specified software in the VM.
But, as I am using the same template so I cannot communicate via IP/hostname, and then I find out I can connect the VM via RDP by giving the VM's name like
axMsRdpClient8NotSafeForScripting1.AdvancedSettings2.RDPPort = 2179;
axMsRdpClient8NotSafeForScripting1.AdvancedSettings7.PCB = vmIDTextBox.Text;
although, I cannot run exe file using the api "ITSRemoteProgram RemoteProgram"
Does anyone knows how to do it? As I have to do it automatically, I cannot use the GUI console. Any suggestions are very appreciated, thank you.
For Windows remote computers, you could use PsExec from Microsoft SysInternals tools:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
It's free, very lightweight, and does what you want :-).
For Linux, you could use SSH. (which is also available for Windows, but you would need a daemon running on the destination machine, such as FreeSSHd).
I am working on trying to get some linux Clearcase clients to work with our existing Windows infrastructure. All of the vobs and servers are stored on Windows machines.
Using an existing vob, I was able to create a tag in the linux region to refer to the vob, and then create a view on the linux client. This client was able to connect to the vob and pull the files in when I updated the config spec. However, while it can view files, it does not have permission to edit them.
The usernames match
linux: user1
windows: DOMAIN\user1
The Clearcase admin panel is set to "Use this domain to map UNIX user and group names" with DOMAIN selected.
However, the authentication does not appear to be working. From the unix client, if I run
credmap windowsServer
I get Nobody/Nobody for the remote username and group ID. If I run from the Windows server
credmap linuxClient
It times out and I get
credmap: Error: Unable to contact albd_server on host
Investigating further albd_list on unix shows that the albd server is running, and even finds the albd_server on the windows machine.
albd_server addr = 166.20.20.81, port= 371
albd_list 166.20.17.118
albd_server addr = 166.20.17.118, port= 371
Going in the opposite direction returns
albd_list 166.20.20.81
noname: Error: Unable to contact albd_server on host '166.20.20.81'
cannot contact albd
Ping works from the windows host to the linux host, and I am even connected to the linux host by SSH from the parent at the moment.
If anyone has any ideas on what to look for next, you'd be my hero :(
You get limited ClearCase functionality when you access a ClearCase server (running on Windows) from a Linux client. To learn more, read about CCFS.
I'd suggest you to consider migrating your VOB server to Linux. This way you get all ClearCase functionality, including dynamic views.
I confirm having Vob server on windows mean they won't be fully accessible from linux client, even though the official documentation from IBM describes the CCFS setting to follow.
(See "Configure UNIX or Linux clients to access Windows VOBs", which you must have seen)
In particular, I never managed to have a credential mapping fully working from Linux to windows (the other way works well).
And you need to make sure your view storage is accessible from Linux (see "Creating a view on a NAS device")
That leaves you with inter-environment solutions, like:
CCRC (ClearCase Remote Client, for CC7.x)
ClearTeam (for CC 8.x)
See "Feature Comparison Matrix for CCRC, CTE, CCWeb, Native ClearCase GUI and SCM Adapter".
This wound up being something stupid. There was a firewall running on the linux machine blocking the albd_server port.
This also did not resolve the credential mapping issues, but it at least let me eliminate one more potential cause. Thanks