Mapped Network Drive: An unexpected network error has occurred.

After applying a security hardening policy through a GPO on the servers in our environment we were
not able to access the mapped network drive on CIFS filer.
I was able to map the drive  but when I try to access the mapped drive I get an error "An unexpected network error occurred".


Resolution: Some GPO settings were blocking this as the Netapp filer was supporting only NTLM
protocol authentication.
The policies should be set as below.
1) Network Client Digital sign Network communication always : Disabled
2) Lan Manager Authentication Level: Send NTLM response only
3) Minimum session security for NTLM session based (including secure RPC) Clients : No minimum
4) Minimum session security for NTLM session based (including secure RPC) Server : No minimum

Multi Monitor Configuration Settings in Citrix Xenapp 4.5

In one of our Citrix Farms, Users were facing an issue with a Particular Published Application where they want to work on Multi Monitors and this application was behaving erratically  with Dual Monitors.

That’s when I resolved the issue with the below settings in our environment with reference to a particular Citrix Document CTX115637.

1)   Open Farm server Properties and set the display settings as per the screenshot below.

è Deselect “ Use Farm Setings”

è Set Max memory usage to 8192 KB (max which you can set)

è Degardation the colour depth first

è Deselect the notify user option

       2)  Adjust Window’s SessionPoolSize parameter as needed to accommodate increased LVB

           memory requirements. SessionPoolSize parameter is held in a DWORD value named

           SessionPoolSize in the system registry.

            HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

            It is expressed in MB. Default SessionPoolSize for x86 systems is either 16MB or 32MB

           depending upon how much memory your system is configured with. Default SessionPoolSize

           for x64 systems is 64MB 

3)      Calculating the DWORD DefaultHooks Value

è To change the behavior from the default, choose the hooks you want enabled and add them together, remember to use decimal mode when entering the value in the registry, or first convert to HEX.

è Setting a value of zero is the same as disabling MMHook

è For our case this value comes to 40959.

For more information and kindly refer http://support.citrix.com/article/CTX115637