I want to do something like academy 240, holograms sharing. Since I don't have two hololens,I want to test that between unity editor and emulator. I try to do that using the latest MRTK, so some scripts are different.
I drag sharing prefab to hierachy form MRTK.
Then click Mixed Reality Toolkit->Sharing Service-> Launch Sharing Service and copy the IP address.
Paste the IP address to the Server Address of Sharing Stage(scripts attach to the sharing prefab)
Then, If I run in the unity editor, the SharingService shows message like:
SharingService: User VR at address 172.23.173.81 joined session DefaultSession
However, If I deploy this project to hololens emulator, nothing happened in SharingService. Does any other setting I need to do?
For Hololens device and Emulator, you need to put the IP of your machine (seems to be 192.168.1.86 in your case).
Related
We got users complaining that accessing remote client on Remote Desktop does not bring up anything. When I try logging in to its Azure AVD, it opens up with a black screen and disappears in a second.
A simple start and stop on Azure portal seems to have fixed the problem. A restart did not fix it though. But, I am not sure why it happened in the first place and couldn't find a reason for it. Could anyone offer some suggestions please?
I tried to reproduce same in my environment. I got same error.
To resolve this issue, try the below.
The reason of this issue is slow sign-in process A black screen will appear for a while, until the regular desktop appears.
When the back screen shows to return to the previous screen, press CTRL + ALT + END. This launches Task Manager you will see the Desktop right away after Task Manager is called like below:
Make sure to disable the Bitmap Caching on the Remote Desktop Protocol (RDP) client like below.
Persistent bitmap caching is the combination of memory caching and glyphs. It will be reused throughout client sessions and also provide a bigger amount of cache space, which will result in a black screen.
And try to adjust Display size of your remote host's display like below:
Now I am able to connect RDP without any issue like below.
I'm learning to use the open source version of OpenShift. I have downloaded the linux image and started it on a virtual machine (named VM1) on my PC, which runs Windows 7. On another VM (named VM2) I have installed another linux OS and configured the JBoss IDE to work with OpenShift. Then I have successfully created and hosted an app on my local OpenShift PaaS cloud. Here is where the problem starts:
On VM2 (the one running linux where I developed the app) I have no problem accessing my account webpage on OpenShift, viewing what apps I have created and testing them.
From any other PC on my network I can log in to the OpenShift web console and view my apps by simply entering the IP of VM1 (in my case 192.168.1.107). There I can see the URL to launch my app: http://localtest2-mydomain.openshift.local/ . But when I click on it, I get a message saying that the web page is not available. Again, if I use this link in VM2, it works like a charm.
I tried changing the system32\drivers\etc\hosts file so that and link ending in openshift.local will be sent to the IP address of VM1, but it doesn't work. Can anyone help me?
As far as I know, you can not use wildcards in your hosts file, you would need to specify the entire url in your hosts file for it to find it correctly. Give that a try and see if it helps.
I am trying to launch a remote performance and diagnostics session on my Surface RT machine in Visual Studio Express 2013 by selecting Debug -> Performance and Diagnostics. However, I get the following message:
Diagnostics session failed to start.
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named '192.168.11.43:4018 (< device name >)'. Connection request was rejected by the remote debugger. Ensure that the remote debugger is running in 'Windows Authentication' mode.
OK, fair enough, so I change the remote debugger to Windows Authentication mode, but no matter what I do I can't authenticate because my PC and tablet are on different domains (that is the way it seems anyway). The tablet is running Windows RT, of course, so it is impossible to change the domain. I have tried to start the remote debugger from the command line using the -u switch with the username and domain from my PC but that was no good either since the tablet can't authenticate it. I also tried to join the tablet's domain on my PC using the script from this answer but I don't get a successful return value (the return value is 5).
Most of the blogs I have come across say "just save yourself the trouble and switch to 'No Authentication' mode" which is what I did in the first place, but the diagnostics session refuses to run this way. What hoops do I have to jump through to get this to work?
Unfortunately I don't think you can get this to work on an RT. Our team has Pros for exactly this reason. Not being able to join a domain is the killer. :(
I now have my Windows Azure environment set up so that I can access my Worker Role with Remote Desktop. However, I'm not sure how to proceed at the moment. After much digging I found a web site that was offline but in Google's cache there was mention of attaching to the Worker Role running in the Azure Cloud from the Visual Studio debugger. But I only have Visual Developer (not studio) 2010 and I have searched all over and as far as I can see there is no such option to attach to a remote server. I am able to publish my project to the Azure Cloud without error and I have a "healthy" instance of my Worker Role showing as active and running.
I did connect with RDP through the Azure Management portal. The login worked fine and up came the remote desktop window. I searched through much of what I could find and was unable to find my Worker Role. I must have the wrong impression of RDP, because I had hoped to see the Worker Role's main display form when I logged in, just like I do when I debug it locally in the Cloud Emulator. But instead all I saw was a blank desktop with some base level server inspection and management routines. I even checked the Event Viewer for Application related messages and saw none.
So now I'm stuck wondering if my Worker Role is actually running or not, despite the seemingly positive status messages from the Management Portal, and I still want to attach to my Worker Role for debugging through Visual Developer, if it's possible, but I am unable to figure out how.
Anyone with experience in this area that can give me some solid tips on what to do next, please respond.
UPDATE: I believe my worker role may be running because I opened a command window and did a Netstat and saw it listening on the correct port. However, that may just be my Worker Role shell class that starts the custom EXE I have it launch as a spawned proces. I still haven't confirmed if my custom EXE is running yet.
UPDATE-2: Just ran TaskList from a command window and the custom EXE is listed.
UPDATE-3: Everything is working as I just ran a remote test of the service so that's not a problem. Still want to know how to attach to the Worker Role from Visual Developer 2010 for remote debugging, and if it's possible to see the custom EXE's display form like I do when doing local debugging in the Cloud Emulator.
-- roschler
There is a set of articles here which goes in length on how to set up for remote debugging in Azure:
http://blogs.u2u.be/peter/post/2011/06/21/Remote-debugging-an-Azure-Worker-role-using-Azure-Connect-Remote-desktop-and-the-remote-debugger.aspx
http://blogs.u2u.be/peter/post/2011/06/24/Remote-debugging-an-Azure-worker-role-using-Azure-Connect-remote-desktop-and-remote-debugger-part-2.aspx
http://blogs.u2u.be/peter/post/2011/06/26/Remote-debugging-a-Windows-Azure-Worker-Role-using-Azure-Connect-Remote-desktop-and-the-remote-debugger-part-3.aspx
The key takeaway is that you don't need to actually install Visual Studio on Azure, you only need to copy the Remote Debugger bits and then use Azure Connect to add your developer machine to the Virtual Network.
You can setup Remote Debugging with Visual Studio 2012
http://code.msdn.microsoft.com/Remote-Debugging-Windows-dedaaec9
When you say:
But instead all I saw was a blank desktop with some base level server inspection and management routines.
this is exactly what you get with an Azure VM. It's a basic OS install, plus the bare minimum of Azure stuff it needs to run and the code you've uploaded. There's no fancy monitoring or health checks available on the machine by default, you're expected to have provided those yourself to have them available without having to RDP into the machine to check on it.
RDP is very good for tracking down certain problems, like checking that a startup task will run, checking which directories items are installed in and just generally being nosey. If you need extra tools to track down a problem, you can just install them while you're connected to the server. For example I have RDPed into a server and installed the Microsoft Debugging Tools, to track down a memory issue.
I suppose you could remote into your VM, install Visual Studio there, and debug the process...
I also suppose it might be possible to enable remote debugging (not sure what's involved there, but such a thing exists, and it works over TCP) and debug from a local instance of Visual Studio.
To my knowledge, neither is commonly done.
Based on other answers, you would be better off writing a log file to a local storage. You can read the file from RDP if you reallyhace to. Keep in mind, debugging on Azure isn't really simple, and rightly so.
What I was thinking though was, maybe you could run the process using the user's credentials. I can't verify at the moment, but you have a better shot of seeing the ui when you rdp.
I have two PCs and I'm logged in both with same user id(have the administration rights). I have installed the service on both PCs. I'm getting a strange issue:
1. If I remove both PCs from network then starting the service makes application appear on both the PCs.
2. If both PCs are in network then One PC shows application while on other it does not appear. however, if I check the task manager, application is running fine.
I find out following things:
1. On PC where application appears, active desktop is "Default"
2. On PC where application does not appear, active desktop is "Screen-Saver". I checked that non of the screen-saver are active and running on this pc.
3. Now If I remove the PCs from network and re-connect then behaviour just got switched. I.e. where it was not working start appearing application but not on other PC.
Why one PC is in screen-saver mode while other in Default? Is this has to do with common login id? How can I work around this issue?
These two services are independent of each other. These service createprocess() which invokes a VB application.
Another question I have is that if I'm not in N/w and run the service then it VB GUI appears properly. If I use remote desktop to start the service, the service appears properly but the VB GUI does not appear :-(
The active desktop at this moment is 'winlogon'. I'm not able to make the VB GUI visible if I give lpdesktop = "WinSta0\Desktop" or "WinSta0\winlogon" or "WinSta0\screen-saver". Please note that I'm accessing the system where service is physically running through remote desktop.
Can someone let me know what I needs to do to make VB GUI appear remotely if I start the service remotely?