Why can't I drag Remote App windows that can be merged? - azure

We are currently in the process of migrating from Azure RemoteApp to another RemoteApp deployment as the current version goes end of life soon. An issue has been raised in UAT whereby Windows cannot be dragged across the screen for more than a split second (only seems to occur in instances where the Window in question is primed to be merged with another Window).
Here are two such examples:
https://drive.google.com/open?id=0B1S4OHN3Sdfyck13UVFzT0c1eWM
https://drive.google.com/open?id=0B1S4OHN3SdfyOHg4WlJmVGdIQTQ
This problem seems to only occur when connecting to Remote Apps via Windows 7 (which is what our users use). When tested in Windows 10 and OSX there was no problem. We also tested this inside a Remote Desktop and it was working.
Our current live deployment doesn't have this issue (connecting to Windows Server 2012). The deployment with the problem is using Windows Server 2016 so we spun up a host server using Server 2012 and still had the same problem.
We have also tried modifiying settings in the connection file to eleviate the problem. These are some of the settings that didn't seem to help the problem when we changed them:
bitmapcachepersistenable
disable full window drag
disable menu anims
disable themes
enablesuperpan
Has anyone come across with problem or know how to fix it? I'm happy to answer any questions about our setup.

Related

Unable to run EXE's from network share

Before i begin let me inform you that I've already gone through other threads here regarding the same issue, none of them seems to have helped, therefore creating my own.
The issue started recently, by the very least i think it started happening 3 weeks ago. we have a custom build application that is deployed on our Network share, the exe is lightweight program, nothing too heavy.
The EXE can be ran manually or through our a shortcut but doesn't run either ways, a window about the same size as the app pops up and disappears immediately if you constantly double click on the exe.
All our Client computers are Windows 10 1909 build. All our servers are VMs running on a Hyper-V host and Windows Server 2019 latest version as well. only the Hyper-V Host is Server 2016 and the application runs fine on that server only.
Infact all other EXEs can be opened through the network share (not on the same server but on a VM) on that 2016 host but none of the exe's open on any other client computer or VM's.
The respective GPO to trust UNC paths is enabled and applied, there are no errors or warning whatsoever when launching any of the exe's, the files just don't open no matter how many times you click on it.
Any Ideas?

WinForms program is larger through Remote Desktop on Windows 2012 server compared to Windows 2003 server

Recently, we have switched our server that handles Remote Desktop connections from 2003 to 2012. When I run the same winForms program on each server, the one on 2012 appears to be larger. My workstation is Windows 10 and I put the resolution down to 1280 x 768 so I can see the screen at the top and the bottom on each RDP session on each server. On the 2003 server, the screen fits the desktop. On the 2012 server, the screen goes below the desktop and you can't see the bottom. It appears the controls such as the text boxes are just a little larger which is forcing the whole program to be larger.
I did check the "Change the size of text, apps, and other items" on Windows 10 desktop and it's set to 100% (Recommended). This doesn't seem to be the problem.
Does anyone have any ideas why the behavior would change between the two servers?
This is probably because 2012 does DPI-scaling (so the remote session tries to adjust the DPI to the same as it is on the client session): https://superuser.com/questions/830234/remote-desktop-into-windows-8-1-pc-with-high-dpi-scaling (also, I guess that you mean 2012R2 because DPI scaling only appears in RDP 8.1 which corresponds to 2012R2).
I have the same issue and I'm just blown away at the amount of money my organization has spent on RDS 2012 and it's been nothing but a complete nightmare. We have various types of Surfaces, desktops and monitors all of which require each user to have the ability to change the resolution and display settings on the actual terminal services end. We've tried everything on both the client and server side to correct this but displays are either too large for some users and too small for other users. Why doesn't Microsoft come out with a patch like there was for server 2008???? I understand the DPI scaling technology, and I will tell you it's horrible when you have multiple versions of the Microsoft Surface and other brand desktops (and yes we have installed the desktop experience on the server end).
Here's what I strongly recommend:
Abandon the whole terminal server 2012 configuration and go with individual virtual desktops. After this, install the display and resolution patch for each desktop which lets each user configure their own resolution and display settings. Not only will your users thank you but you'll thank yourself!!
We had this issue for about a week and I restarted our Windows Server 2012 on remote desktop and DPI is back to normal! :) I guess this must be some automatic Windows update that fixed this.

Windows Server 2012 Interactive Services Detection does not work

I am running Windows Server 2012 R2 and I am running the program FireDeamon to run my game services, but upon clicking the pop-up message it'll just either bring me to a blue or black screen. I already tried setting the value in the registry to: HKLM\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices=0 and rebooting the machine but this did not work, I even tried it twice.
So is there an clear and working solution for this issue? If not, could someone please provide me with a good working alternative for FireDeamon.

Copy website feature in visual studio 2010 is not working because my local pc code is under source control

This is my first time posting a question in StackOverflow. Pls forgive me if I made any mistake.
The condition is such: I have codes inside my laptop that is under source control by a TFS (Team Foundation Server) server in the company and I have a web server which I upload the codes so that user can browse the pages. So there are 3 main items here: the TFS server, my laptop and the web server.
When I try to check in/out between my laptop and TFS server using Visual Studio, no problem.
When I try to use "Copy Web Site" feature in Visual Studio to upload my laptop's code to the web server, no problem too.
However, when I try to use "Copy Web Site" feature in Visual Studio to DOWNLOAD the web server's code into my laptop, then it will says the job is completed, but in actual fact, it has not done anything because the fact is laptop's code is under source control and it cannot overwrite it.
The only solution is I have to "check out" the local laptop's code before I can successfully DOWNLOAD from web server into my laptop. This is very troublesome and annoying if I have many files to DOWNLOAD. Is there another solution to this problem?
Another question is, is there any better way to configure the relationship of these 3 items?
Sorry for such a long question.
I cannot post any images because I don't have the "10 reputation" rights required by stackoverflow.
Thanks
The easiest answer is to use a local workspace, but unfortunately local workspaces aren't an option unless you're using both Visual Studio 2012 and TFS 2012.
The basic problem here is that when you use a server workspace, files are read-only on your file system until you explicitly check them out of source control. Local workspaces don't have that necessity.
The bigger question here is why you want to grab files from the web server. You're using source control. If people are making changes to the code directly in the web server without going through source control, that is a huge problem that should be addressed immediately.

Debugger can't connect when starting local azure project

Ok, first of; here's what I did:
Install AZURE tools
Reboot
Start Visual Studio - new Azure project
Add web role (asp.net MVC 4 beta web role)
Hit F5 (debug)
It starts up the storage emulator and the compute emulator and starts to load in runtimes, and then I get a popup saying that the debugger couldn't connect.
Then after some googeling I'm suggested to try to run the application without running the debugger to see if I can acces the application. When I do I get this:
So I figure that IIS does not have permissions to access some file/directory. So I go to IIS and look up the application pool running the app, and it tells me that the identity in use is NetworkService, then I go give NetworkService full permissions to the entirety of the folder IIS has set for the application (which also happens to be the path to the project dir). Still I get the same error. Now I'm more or less out of ideas, but I try one last thing, which is to also give IUSR full permissions to the same dir, but this did not help either.
How can I go about resolving this problem? I haven't tried actually launching my project to Azure yet, cause if I can't even get it to work in development I don't see much point. Any and all help would be appreciated.
I ran into the same error today after uninstalling .NET 4.5/Visual Studio 11 Dev Preview, then installing ASP.NET MVC 4 Beta (this is before Feb 29th when the updated VS 2011 Preview drops).
Since I uninstalled .net 4.5, you just need to do an "aspnet_regiis -i" to ensure the .net framework (4.0) is set up with IIS 7.x this worked for me.
Edit: This will work if you uninstall/then manually install Visual Studio 2012 RTM as well.
I had a similar error yesterday. For me the problem was that the output of the build was empty in the target folder.
I tried to answer a similar question https://stackoverflow.com/a/9411422/182371:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log
file for the error messages. Mode details at
https://stackoverflow.com/a/8432621/182371
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0', right
click --> Explore.... Make sure that this folder is not empty and
contains all the files required to start a web project successfully.
As for the Access Denied error:
it could be just an IIS default setting to disable browsing. To resolve that, just navigate to that web site in IIS, find Directory Browsing icon, and press Enable. You will at least see the files inside that directory.
Also try not only 127.0.0.1:81, buta specific document inside that folder, like 127.0.0.1:81/Default.aspx
Take into account the fact that there's sometimes some mess with the ports. You see that in the error message it's port 82, but in your browser it's port 81. So make sure you're using the right port. Or, even better, in your service definition try to use some non-standard port for this to avoid remapping.
I've met the same issue. In the end, I had to reinstall IIS 7.
I got this exact same error and tried a re-install of IIS and the Azure SDK - nothing worked.
Eventually tracked it down to the "IIS URL Rewrite Module 2". I went to the Control Panel and chose Repair and it resolved it. If you have a section in your web.config then this might be the cause.
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk when upgraded from 2011.

Resources