Chrome Surpassing Safari and Opera as the Browser of Choice on Apple macs

Image is Courtesy of: www.WebDevelopersNotes.com

Chrome vs Opera vs Safari : Browser Battle

Google's Chrome was released on several years ago and has managed to gain dramatic share in usage,. Although Google also supported Firefox, it seems it's abandoning Firefox and developing Chrome as the competitor of choice to Internet Explorer. Internet Explorer I believe will not be surpassed by Chrome. I find Chrome to a good browser and I use it daily on almost all of my computers but it does not have support for many of the things I need it for. 
For example, I connect to many networking devices and other appliances used in information technology as part of the infrastructure for managing or containing important information system. 


There are many who like and appreciate the "simple and clean interface" but that's all illusion of what a browser today is used for.  I personally dislike not having a menu-bar and no option to add one either. For average web usage such for browsing for videos, music, shopping or social networking, it works well. It lacks the support from developers to enable it to do as much as Internet explorer can. It's a browser, it's not a viable option in many cases to be a front-end application. 

Configure Idle and Disconnect Timeout Settings in XenApp 6.x

Configure Idle and Disconnect Timeout Settings in XenApp 6.x and XenApp Fundamentals

Configuring idle and disconnect timeout settings in XenApp 6.x and XenApp Fundamentals is crucial for optimizing resource management and enhancing security. These settings determine how long a user session can remain idle before it is automatically disconnected, thereby freeing up system resources for other users. To configure these settings, administrators can access the Citrix App Center, navigate to the desired application server, and specify the appropriate timeout values under the session management settings. By fine-tuning these parameters, organizations can ensure a balance between user convenience and system efficiency. In addition to a better user experience, implementing strict timeout policies can help mitigate potential security risks by reducing the window of opportunity for unauthorized access to idle sessions.

XenApp 6.5 for Windows Server 2008 R2

The session limits applied using the ICA listener configuration utility only affect connections to a XenApp server. The session limits settings in a user policy only apply to XenDesktop.

•  Click the Start menu, select All Programs, Citrix, Administration Tools, and then click on ICA Listener Configuration.
• Select the ICA-TCP listener and click the Edit option.  
• On the Session Limits tab, configure the disconnected sessions timeout in the drop-down menu in the End Disconnected Session section.

    
  

  

  
  

  
  

  
  

  

  
  

  
  

  Click Okay and Close.

  
  

  These options control how long a user session can stay inactive before disconnecting automatically and releasing system resources for other users. Administrators can set them up by logging into the Citrix App Center, selecting the correct application server, and going to the session management settings. From there, they can adjust the timeout numbers accordingly. Organizations can guarantee a balance between system efficiency and user convenience by adjusting these characteristics. Strict timeout rules can also lessen the window of opportunity for illegal access to idle sessions, which helps reduce possible security threats.  Setting up idle and disconnect timeouts in XenApp 6.x and XenApp Fundamentals is essential to improving security and resource management.

  
  
  
  
  

Disable Session Reliability in XenApp 6

Disable Session Reliability in XenApp 6

Disable Session Reliability in XenApp 6. One of the requirements of published apps in Citrix is to limit the user to a single instance of a published application. In Xenapp 6, the checkbox in the published application properties that states limit the user to one session does not seem to do the trick by itself and often brings about errors. Users receive errors like "the server has reached the maximum number of connections" and others of similar effect.

So what everyone does is uncheck the box and find what is different about Xenapp 6 or even worse think there is a larger problem with their Xenapp 6 installation. The solution is simple enough. Limiting session for a user to one per app can be accomplished using a policy. Create a new computer policy for the farm and disable session reliability. Once session reliability is turned off, check the box in application properties to permit only one instance of the published app .

The time provider NtpClient is configured to acquire time

If your geting the following error in your system log do the following.
On your root level PDC emulator domain controller run the command at a command prompt:
net time /setsntp:ntp2.usno.navy.mil /set /y
Then restart the time service.
On all child domain controllers that are the PDC emulator for the domain run the following command:
net time \\ROOT-DC-name /set
Change ROOT-DC-name to your root level domain controller name running the PDC emulator.
Then restart the time service.
Check your system log. You will see confirmations that the local time service is now syncing with the time source.