it is possible to disable a Juniper SSL browsing tool bar for a specific URL - refer to http://kb.juniper.net/InfoCenter/index?page=content&id=KB25387&actp=search&viewlocale=en_US&searchid=1343729631134
Upload a patch package and use internal URL rather than external in the filter.
Search This Blog
Tuesday, July 31, 2012
Monday, July 30, 2012
Adobe Flash player autoupdate and Bluecoat
Review the following advice on exception policy for Flash autoupdate:
https://kb.bluecoat.com/index?page=content&id=FAQ1791&actp=RSS
https://kb.bluecoat.com/index?page=content&id=FAQ1791&actp=RSS
Thursday, July 19, 2012
CentOS 5 life cycle
CentOS 5 (RHEL5) will be safe to use until 2017: refer to upstream life cycle info: https://access.redhat.com/support/policy/updates/errata/
Wednesday, July 4, 2012
Autocomplete search in MOSS 2010
http://weblogs.asp.net/jan/archive/2009/07/02/sharepoint-search-as-you-type-with-jquery.aspx
to query People change scope to "People" and modify the query string to add "*"
to query People change scope to "People" and modify the query string to add "*"
Friday, June 8, 2012
Thursday, June 7, 2012
Cisco IP Phone Owner ID is greyed out in CM
If owner ID is greyed out in Call Manager (8.6), check if you have extension mobility enabled - scroll little bit lower on the same page. Uncheck it then set owner ID.
Friday, June 1, 2012
Junkmail GPO in Outlook
http://www.effectusdigital.com/outlook-junk-mail-filter-through-group-policy/
as explained above, do not forget registry JunkMailImportLists otherwise it will not work...
update from http://forums.msexchange.org/m_1800545996/printable.htm:
We got an update from Microsoft -- they say that the best option is:
New-TransportRule -Name ' Flag internal email domains as not junk and set SCL to minus 1' -Comments ' Flag internal email domains as not junk and set SCL to minus 1' -Priority '0' -Enabled $true -FromAddressContainsWords 'domain1.com','domain2.com' -SetSCL '-1'
The reason why email from our own internal domains is being flagged as junk is because the emails are being send un-authenticated and are not really "people" with AD accounts. They are 3rd party internal applications that cannot send/use authenticated senders.
So "white-listing" internal un-authenticated email seems to be the option to go with until we can replace this legacy software or find ways to convert them to authenticated senders.
as explained above, do not forget registry JunkMailImportLists otherwise it will not work...
update from http://forums.msexchange.org/m_1800545996/printable.htm:
We got an update from Microsoft -- they say that the best option is:
New-TransportRule -Name ' Flag internal email domains as not junk and set SCL to minus 1' -Comments ' Flag internal email domains as not junk and set SCL to minus 1' -Priority '0' -Enabled $true -FromAddressContainsWords 'domain1.com','domain2.com' -SetSCL '-1'
The reason why email from our own internal domains is being flagged as junk is because the emails are being send un-authenticated and are not really "people" with AD accounts. They are 3rd party internal applications that cannot send/use authenticated senders.
So "white-listing" internal un-authenticated email seems to be the option to go with until we can replace this legacy software or find ways to convert them to authenticated senders.
Subscribe to:
Posts (Atom)