Archive

Posts Tagged ‘problem’

#Citrix #StoreFront Slowness, Join and Replication issue – check list!

Ok, I guess that you may have seen issue with StoreFront before… and it you have not then good for U!

But in the case that you have experience it here are a couple of things that you can do and hopefully it solves your issue with slow StoreFront console startup, server join issues or replication issues. Sometimes I’ve seen that the join, replication and slowness is ok and the process goes through. But then all of a sudden you get an error and the propagation fails… and this can be because of a timeout in the StoreFront process that you’ve initiated.

I already assume that you’ve checked the basic stuff.. that the servers can reach each other (ping server name and FQDN etc. and that there are no FW issues)….

You may have an issue because you/your server cannot reach the Internet, and some of the components of the product is signed with SSL certificates and StoreFront will try to perform a check whether the publishers certificate is ok or not. So if your servers are behind a proxy serevr that you usually configure in your browser to be able to connect from your companies internal network to the Internet then you should do the following.

1. Log on to your first StoreFront server and create a copy of the original aspnet.config file under C:\Windows\Microsoft.NET\Framework\v2.0.50727 (verify which framework version that your app is using in IIS and modify that appropriate aspnet.config file, more info about this change can also be found here and is for Web Interface but is also applicable to StoreFront)

2. Open Notepad as an Admin (if you have UAC of course enabled) and open the asp net.config file

Citrix_StoreFront_aspnet_config_file

It will have the content as described by the picture above,  add this line to it:  <generatePublisherEvidence enabled=”false”/>

Read more…

iOS 6.1 banned from corporate servers due to Exchange snafu – via @rspruijt

February 11, 2013 Leave a comment

Summary: iPads and iPhones running the newest version of iOS are being blocked in some enterprises because bugs are overloading corporate Exchange servers.

One of the benefits of Apple’s iOS devices such as the iPad and iPhone is that you can upgrade to the latest version as soon as it comes out. Being on the cutting edge is usually a good thing, but sometimes it can come back to bite you. If you are connecting to an Exchange server for mail and calendar services, the latest version of iOS has an unpleasant surprise in store for you.

Reports started surfacing in late January about excessive logging on Exchange servers caused by the upgrade to 6.1. A report on Microsoft Technet states:

I had a user upgrade to 6.1 and immediately after he finished, his phone/IPAD started causing excessive logging on the exchange server.  

I found the problem by using exmon and saw the CPU utilization in conjunction with high session count.

He shut down Outlook and the problem remained.  He turned off his iPad and the problem went away.  The only change he said he made that morning was upgrading to iOS 6.1.

This problem has been confirmed by many sources. Windows IT Pro’s Tony Redmond reports:

I’ve picked up a few other reports that cannot be publicly attributed at this point that also refer to excessive transaction log generation after iOS 6.1 devices are introduced into Exchange 2010 or Exchange 2007 environments. I assume the same is true for Exchange 2013 as the underlying cause is likely to be in Apple’s mail app code that calls ActiveSync…

Continue reading here!

//Richard

%d bloggers like this: