Microsoft webbrowser FEATURE_BROWSER_EMULATION in RDP application - webbrowser-control

I have an application that has an embedded Microsoft webbrowser ActiveX control. On the server where the application is installed - it runs fine (runs quickly, runs scripts) within the application. The application is exposed via RDP for users to run - the Microsoft webbrowser ActiveX control page does not work properly (hangs for a long time - finally displays script error message - scripts don't work) when it is run using an RDP session.
When directly accessed from any computer, the webpage that is contained in the ActiveX control runs fine.
The application.exe files are in these registry folders with the appropriate decimal value (11001):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
I'm thinking that there is something more that I need to do to either force the version emulation or permit scripts.
Server is 2012R2 64-bit OS


Make sure client browsers are supporting ActiveX
Set sufficient permissions for clients Explained Here
Change Security Layer and User Authentication to a hexadecimal 0 in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp
You can do this via Regedit
Reboot the server


I found that Internet Explorer on the server was pointing to an old proxy server that was likely finally removed from service. I updated the proxy server to the one that is used by the clients and it works fine.

Related

"Single instance application": Multiple instances in Windows 2008 terminal server environment

I have a small VB.NET application to handles a custom URL protocol. It is set up in Visual Studio with the option to "Make single instance application". This has worked for hundreds of installations, but a recent customer is using Windows Terminal Server 2008, and it is launching multiple copies of the application. It does not seem to sense that it is already running for a specific user. BTW -
Multiple users can run it without problems in different sessions.
Is there some sort of setting on the Windows Terminal server that could cause this?
We have installed the application using install mode, and with the administrator ID.
Any ideas would be appreciated.

Unable to reach Windows server: "Please wait for the Local Session Manager"

When connecting to our Windows Server 2008 R2 desktop via MS Rdp tool (latest version), occasionally the connection is closing after displaying "Please wait for the Local Session Manager". The result is that I am unable to get into Windows desktop.
Searching the web gives me a hotfix from Microsoft (https://support.microsoft.com/nl-nl/help/2661001/-please-wait-for-local-session-manager-message-remains-for-several-minutes-when-you-disconnect-from-a-computer-that-is-running-windows-server-2008-or-windows-server-2008-r2-during-the-logon-process) which doesn't seem to be downloadable any more.
Also the tip to delete some "usrclass.dat" files did not work (
https://discussions.citrix.com/topic/291092-please-wait-for-the-local-session-manager/?p=1624478) because the files can't be deleted since they're "in use".
Only solution is to reboot Windows, but that's highly impractical for a production web server.
Windows is running virtually on VMWare's Vsphere.

Deleting usrclass.dat DID the trick here. But of course you have to delete this file logged in with admin-account...

Coldfusion COM not registered

First time ever using ColdFusion.
We have a website that uses ColdFusion 9 on our live server. It calls a COM DLL to encrypt certain things. The code on our live server works fine.
Since I may be taking over the project I installed ColdFusion 10 Developer edition on my local machine and copied all the source code and DLL's down to my local machine for testing.
I am getting an error that it can't instantiate the COM object because it is not registered but I KNOW it is registered because the DLL works on other parts of our website that are still in Classic ASP and will run on my local machine. I actually wrote a ASP script inside the the ColdFusion test site on my machine to test the DLL and everything works fine so it IS registered (via regsvr32.exe).
The ColdFusion page was done by an outside company that we are going to be breaking ties with and I don't have the password to their ColdFusion control panel even though it is on one of our servers. I wanted to look at their settings. Is there some setting that I need to set in the control panel on my machine? If there is I haven't found it yet.
Any ideas?
EDIT:
Here is the code:
<cfscript>
objEnc = CreateObject("com", "mycom.myclass");
</cfscript>
Also, I am running the 32-bit version of CF on a Windows 7 Pro 64-bit OS.
EDIT:
Another edit just for some more info:
The Windows 2008R2 server that it runs successfully on is a 64-bit server. So OS shouldn't have anything to do with it.
Should I try to find Version 9 developer edition on adobe's site and see if it works since it matches the CF version on the server? Haven't been able to find that yet and now Adobe just released 11.

After downgrading my local machine to ColdFusion 9 I can now access the COM DLL perfectly. Which is probably for the best since our server is running CF9. My testing will be with same version. Thanks for all you guy's input.
Randy

Use WebDav in Sharepoint 2010

I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.

Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.

If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.

make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)

Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager

This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.

Ways of Authentication against a Windows Server in C# for a Client Application

I have windows server 2003 machine as a part of our network. I have created an administrator user on it.
Now this server system has a shared folder.
I am writing a C# application which will copy some files a local system to that shared folder in the windows server 2003 machine.
I have coded the file transfer code, it works fine if I authenticate the client machines using windows explorer to copy file into the shared folder on the server.
However If I don't authenticate using windows explorer my code gives Access Denied Error.
I want C# cope piece which can authenticate my file transfer application without entering the creds on windows explorer each time. The windows server has normal windows authentication.
Please help!!
Edit-
The server does not have an AD, please note that Iam authenticating against an AD, I just want to create an Authenticated windows session to the machine.

You need to use impersonation.
The following KB article has some good information on using impersonation from .NET:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306158
A quick Google search turns up the following example (based on the same idea):
http://www.codeproject.com/KB/cs/cpimpersonation1.aspx