No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

A method to settle the problem that we open the virtual machine via TC and login in the WI but the speed is too slow

Publication Date:  2012-11-12 Views:  41 Downloads:  0
Issue Description
Version: V100R002C00SPC200.
If there isn’t any user login in the WI for a long time, then once there is a user want to login in the WI of the virtual machine via the TC, he/she must wait a long time (more than one minute) before the register interface, and after enter in the account/password, it must take more than 5 seconds to display the desktop group; once the user isn’t the first one to login in the WI, he/she may open the WI fast.
Alarm Information
None
Handling Process
1. Login in the WI virtual machine, “start” -> “run” -> “open” and enter the “%SystemRoot%\system32\inetsrv\iis.msc”, then confirm. Confirm whether the version of the “.NET Framework” is v2.0.5.0727 at the corresponding “website” attributes.


2. Backup the following configuration file: “c:\Windows\Microsoft.NET\Framework\v2.0.50727\ASPNET.CONFIG”, then open this file via the text, the content is as followed:
<?xml version="1.0" encoding="UTF-8" ?>
<configuration>
    <runtime>
        <legacyUnhandledExceptionPolicy enabled="false" />
        <legacyImpersonationPolicy enabled="true"/>
        <alwaysFlowImpersonationPolicy enabled="false"/>
        <SymbolReadingPolicy enabled="1" />
    </runtime>
</configuration>

Add the following content in the configuration file:
<generatePublisherEvidence enabled="false"/>

The content after modified is as followed:
<?xml version="1.0" encoding="UTF-8" ?>
<configuration>
    <runtime>
        <legacyUnhandledExceptionPolicy enabled="false" />
        <legacyImpersonationPolicy enabled="true"/>
        <alwaysFlowImpersonationPolicy enabled="false"/>
        <SymbolReadingPolicy enabled="1" />
        <generatePublisherEvidence enabled="false"/>
    </runtime>
</configuration>

Save and close the “ASPNET.CONFIG” configuration file, and then restart the IIS service.
3. For testing, the speed of opening the WI via TC is fast, and we display the desktop group fast.
4. There has integrated with fixes to settle this problem in the version of R002C01SPC100, R002C00SPC202 and the above versions.

Root Cause
While opening the WI, it will call the “asp.net” program in the IIS, and when we run the “” program for the first time, it will connect to the external network to validate the digital certificate, once the server can’t connect to the external network, this validating process won’t complete until the “timeout”. The “asp.net” will resident in the memory, then subsequent users don’t need to validate the digital certificate, if there isn’t any request for a long time, the “asp.net” in the memory will be recovered.
Suggestions
None

END