Here is a native tool to troubleshoot Windows accounts lock out:
http://www.microsoft.com/downloads/details.aspx?FamilyId=7AF2E69C-91F3-4E63-8629-B999ADDE0B9E&displaylang=en
You can find a DC where account was locked, as well as you can to search all Event logs from all DCs:
EventCombMT.exe. Gathers specific events from event logs of several different machines to one central location.
LockoutStatus.exe. Determines all the domain controllers that are involved in a lockout of a user in order to assist in gathering the logs.
Wednesday, May 12, 2010
Thursday, May 6, 2010
Monday, May 3, 2010
Sharepoint errors 5552 and 7888
To remove repetitive errors on the MOSS 2007, set a valid domain account for the web applications.
here is someone who had similar issue in the past: http://vspug.com/rlangley/2007/10/10/failure-trying-to-sync/
In meantime trying out this free and gret app: http://spi.codeplex.com/
It helps to decypher GUIS in the event viewer. I could see that these errors are coming MySite and SSP sites.
here is someone who had similar issue in the past: http://vspug.com/rlangley/2007/10/10/failure-trying-to-sync/
In meantime trying out this free and gret app: http://spi.codeplex.com/
It helps to decypher GUIS in the event viewer. I could see that these errors are coming MySite and SSP sites.
Tuesday, March 9, 2010
Alerts in Sharepoint MOSS 2007
We have several complaints from users that they do not receive alerts. The log shows that alerts subscription are ok, but they are security trimmed. Looks strange because users actully can see the files in this document library. Logs looks like:
02/23/2010 09:10:55.88 OWSTIMER.EXE (0x04F0) 0x03C8 Windows SharePoint Services Timer 95lg Verbose Alertsjob results for immediate delivery: 334 prematches, 54 passed filtering, 24 of 54 passed security trimming, 24 final after rollup
02/23/2010 09:10:56.36 OWSTIMER.EXE (0x04F0) 0x03C8 Windows SharePoint Services Timer 95l5 Verbose AlertsJob processed 24 immediate notifications in 24 digests, sent 24 emails, failed to send 0 emails
I opened a call at Microsoft, but they could not get more data on why this security trimming is happening. They start claiming that nested AD groups are not supported by Sharepoint. Indeed the users that are included to nested AD groups were trimmed. They provided few links, but mentioned that Technet article is not released for public. After a while I discovered that alerts started to work normally even with nested AD groups. In meantime I changed account under which timer job is working from local to Domain. I can not recall any other change, may be except refreshing security on the library in question. So that must be it, timer job account must be domain in order to send alerts even to users of nested Active Direcotry groups. In any case let me give you MS provided links here:
http://blogs.msdn.com/joelo/archive/2007/06/29/sharepoint-groups-permissions-site-security-and-depreciated-site-groups.aspx - Explains the problem & a work around is provided
http://social.msdn.microsoft.com/Forums/en/sharepointworkflow/thread/65e5dfc7-626b-47f0-bf56-b58a08219db7
http://hermansberghem.blogspot.com/2008/04/windows-security-groups-vs-sharepoint.html - # 3 is Important
http://objectmix.com/sharepoint/731902-add-active-directory-user-group-sharepoint-user-group.html - It talks about work around as well
02/23/2010 09:10:55.88 OWSTIMER.EXE (0x04F0) 0x03C8 Windows SharePoint Services Timer 95lg Verbose Alertsjob results for immediate delivery: 334 prematches, 54 passed filtering, 24 of 54 passed security trimming, 24 final after rollup
02/23/2010 09:10:56.36 OWSTIMER.EXE (0x04F0) 0x03C8 Windows SharePoint Services Timer 95l5 Verbose AlertsJob processed 24 immediate notifications in 24 digests, sent 24 emails, failed to send 0 emails
I opened a call at Microsoft, but they could not get more data on why this security trimming is happening. They start claiming that nested AD groups are not supported by Sharepoint. Indeed the users that are included to nested AD groups were trimmed. They provided few links, but mentioned that Technet article is not released for public. After a while I discovered that alerts started to work normally even with nested AD groups. In meantime I changed account under which timer job is working from local to Domain. I can not recall any other change, may be except refreshing security on the library in question. So that must be it, timer job account must be domain in order to send alerts even to users of nested Active Direcotry groups. In any case let me give you MS provided links here:
http://blogs.msdn.com/joelo/archive/2007/06/29/sharepoint-groups-permissions-site-security-and-depreciated-site-groups.aspx - Explains the problem & a work around is provided
http://social.msdn.microsoft.com/Forums/en/sharepointworkflow/thread/65e5dfc7-626b-47f0-bf56-b58a08219db7
http://hermansberghem.blogspot.com/2008/04/windows-security-groups-vs-sharepoint.html - # 3 is Important
http://objectmix.com/sharepoint/731902-add-active-directory-user-group-sharepoint-user-group.html - It talks about work around as well
Tuesday, February 2, 2010
disable LDAPS/SSL weak ciphers
Disable weak ciphers in Windows 2003 DC LDAPS protocol on a domain controllers:
you may follow the tip from http://www.curtis-lamasters.com/2008/06/21/windows-iis-ssl-restrict-weak-ciphers/
you may follow the tip from http://www.curtis-lamasters.com/2008/06/21/windows-iis-ssl-restrict-weak-ciphers/
Wednesday, January 20, 2010
Linux from USB
A reminder - there is a great tool UNETBOOTIN that allows to create USB bootable for many distros - Ubuntu, Suse, FreeBSD, etc.
Subscribe to:
Posts (Atom)