henselkp2001

I had this problem too. I had to import KB2670838 and then approve it as well as approve KB2834140 then IE 10 started to install properly. Your tips got me there. Thanks. I got the google apps is dropping support for IE9 message recently, and I was anxious to get IE 10 installed.

I think this interferes with https:--accounts.youtube.com/accounts/SetSID?... This affects my "manage this domain" button in Google Apps. Adding allow lines above the block with accounts.youtube.com fixed it. So the four lines together are: acl accounts dstdomain accounts.youtube.com http_access allow accounts CONNECT acl youtube dstdomain .youtube.com http_access deny youtube CONNECT

This looks really cool, but I am not sure exactly about the squid.conf thing. I am running Endian Community 2.5.1, so it is running squid, and I got to the right file, and I think the right place, but I am not quite sure how to format the text there or even if it is meant to be on two lines. I haven't edited this file before. The other changes were no problem for me. If possible, would you let me know if this is the right place (to your knowledge) and then do I just copy the 3 lines (including the comment) right there with just one space in between? Thanks so much. I have seen lots of people asking how to fix the https problem, but no one solving it except you.

"^https://www(\.google\..*)"->"https://nosslsearch\1" "(^http://[^/]*www\.google.*\?.*)"->"\1&safe=vss" "(^http://[^/]*bing.*\?.*)"->"\1&adlt=strict" "(^http://[^/]*yahoo.*\?.*)"->"\1&vm=r"

I am thinking that adding a pref in the middle will bypass that regex. Perhaps it should be more like blocking *.google.*/pref.* *.google.*safe=off.* *.google.*safe=medium.*

I got nosslsearch implemented in the urlregex file by adding the line "^https://www(.google.com.*$)"->"https://nosslsearch\1" and blocking encrypted.google.com Worked great on my Comsifter 8-DPro (dansguardian) filter. Karl

A modify URL regex filter "^https://www(.google.com.*$)"->"https://nosslsearch\1" and blocking encrypted.google.com fixed the ssl issue for me.

You can add a string-value named "ivsport" in HKEY_LOCAL_MACHINE/Software/iTALC Solutions/iTALC/parameters/. You can do the same for "isdport" (default 5800) although you probably won't need this. You could add those keys in an install script or GPO, etc.

Well, I looked around and found that the share on our backup file server (2nd target of our DFS) had a problem. I solved it with advice from a website that I will put in my next post. I will see if that helps in the future. The second target was disabled though, so I don't know why it should matter. Wish me luck. Merry Christmas!

I think that this is the problem that I am having on my domain as well. I am not positive that it is the problem, but it seems likely. We get the black screens for some users on some PC's. I never thought of the possibility that it could be a DFS issue. I will temporarily link all users to one server and see if that settles it. Thanks for the idea. I will try to remember to post back whether that fixes it for me. (In a few weeks)