Hello I am going to use Azure Windows B1S instance. I have excel with macro which gets live values from web. Once I connected vm through Remote Desktop, and start excel and close. will excel run through without problem if I am closing Remote Desktop? and also will my excel connected to internet to get live values if I disconnected VM from my local pc?
thanks
If your application is a process, yes. After the window is closed, it will be continued and where it is connected when maintaining the previous state of the vm. Activate a pop-up that appears before closing that asks if you just want to close a window or suspend a vm. Select only to close.
Related
Basically I have a linux server, that I can connect to using ssh -i *pvKey* *user#host*.
When I'm connected I can open a java application, like I have. The linux server stays open 24/7 and I believe any application I open does the same. How do I reopen an open application if I close windows powershell.
Let's say I go to bed and close windows Powershell, I believe the java application will stay open during the night, which is what I want. How do I reopen that java program again after connecting to the server, so I can continue sending commands in the java application.
For more specific information: The java application I'm talking about is a minecraft server, which I want to leave on 24/7 (with some restarts obv). I want to be able to reopen the java program of the mc-server that has stayed open, so that I can send more commands and possibly restart the mc-server, without having to log into it in minecraft, stopping it, and reopening it in powershell.
This is the first time I try to work with a linux server and powershell, so please excuse my lack of knowledge.
Your remote shell automatically kills all processes that are running in the shell when you exit the shell.
I would probably use screen for this usecase.
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.
Currently I am running a jarfile from my CENTOS machine that takes parameters to make a connection to azure Windows VM using WINRM.
I get the sessionID of RDP and using psexec I execute my autoit script on the RDP sessionID (this assumes that I need to have already a RDP connection established).
psexec.exe -i 2 "C:\Program Files\AutoIt3\AutoIt3.exe" "C:\Users\admin\runNotepad.au3"
The script runs perfectly when I have a RDP session maximized/opened. If I minimize the RDP window some commands do not work, as for example the Send command.
How can I guarantee, taking my setup, that a session with GUI is opened and how can I bypass(if there is a way) the constraint of having the RDP window maximized in order to run the test?
I can also change my architecture if required (apart from the CENTOS machine).
Thanks
I connected two laptops using a cross-over cable. My IP Address is 192.168.1.1 and the other IP Address is 192.168.1.16. We both are able to ping each other and the reply is perfect. There is no loss of packets.
The problem is I shared a file and the other system is not able to open my IP Address using the run command. Even I am not able to open my Shared folder by giving in the run (\\192.168.1.1). A dialogue box with the message \\192.168.1.1, The Network Path was not found opens each time we try this.
But I am able to open his shared folder by giving in run command (\\192.168.1.16). I closed all the firewall services in my system. But still my system is not able to respond. Also we are not able to use remote desktop connection.
Can anyone please help me in solving this?
Additional Details: I use Windows XP and the other machine uses Windows 7. We both are in the same work group.
Here are some steps to solve your problem:
Did you set the static IP by yourself or that come automatically?
If yes then please go and set the IP manually
Then share the file and put the permission of that file to Maximum (If you believe your partner)
Then power down the firewall or antivirus for some moments (say 10 minutes)
Now try to connect using the \192.xxx.xxx.xxx method using the Run window
If the 5th step is not working, then try disabling and reenabling the LAN card, then try the 5th step again.
Hope that solved your problem.
Remote Desktop needs to be explicitly enabled. Right click on "My computer", go to properties and look at the remote settings tab.
I advice you to use Radio Access Point to connect both windows 7 and windowsXP. I think this is best choice of troubleshoting jaringan. why?
Because I already do anything to connect both Operating System but can't solve that problem.
I have a Windows application that exports to Excel using the Excel Object Module (programming module). It has worked fine on all Winodws versions except Windows Server 2008. It takes about 2 seconds to do anything in Excel, making the process take minutes or even hours to complete what normally takes a few seconds.
This happens when using Terminal Services or RemoteApp. I discovered that it only happens when you check the Printers checkbox under Local Resources when connecting via Remote Desktop. If you uncheck it the speed is normal.
However, I need my printers, so I can't just uncheck it.
Any ideas what is causing the slow down?
The MS Office apps do a lot of calculation in the background based on the default printer. When you connect from a remote Terminal Services session and import the Printers from your Local Resources, the Terminal Server really needs to have an appropriate driver for each printer you're connecting.
Thus, one solution to the speed issue would be to ensure that the server has the right drivers (and that they work as expected).