Site quotas and locking can be applied via Central Admin but this will quickly prove to be time consumming in number of clicks if you have more than 5 Site Collections in each Web Applications, so use the custom STSADM command from Gary Lapointe so do so.
SharePoint Automation: Synchronizing Quota Settings via STSADM: “Synchronizing Quota Settings via STSADM”
This morning while having a “normal” second line support call with a user, she just mentioned something that she thought was a temporary or minor problem on her site :
– when adding a user to a site, she would click the Address Book icon to search for a name, and all name would just come up twice.
Obviously this translated in my language to be a more important problem as it meant that another domain has been added to Active Directory where all members of domain1 where also created in domain2, and Sharepoint just displayed the additional domain if there is a two-way trust between my Sharepoint domain.
Within just a few hours I could have dozens of people who would be added to a newly released site and who would call 1st line support asking why they can’t access the site although they are listed as user :-(
Bugger I thought! because any user who is added to a site using the additional AD Domain will not be recognised by the site SSO like that, the user will never know how to log in with a different AD domain and why would should they anyway.
My Active Directory obviously rejected the fault on Sharepoint that should “know what it’s doing” ..
Sharepoint can indeed add some rules to the display of users in the list, using STSADM commands (see links to “ninja”‘s blog). It all sounds good as I can do something like :
stsadm -o setproperty -pn peoplepicker-searchadcustomfilter -pv “(dc=mydomaintoinclude)” -url http://mywebapp
Only problem in my case is that this property “-searchadcustomfilter” is only available from Sharepoint 2007 SP1 onward. Well… . in a way I am glad as it will give more pressure to push management to approve an upgrade to SP1 and Infrastructure Update for WSS3 and MOSS2007. We should really on the upgrade wagon by now !
Come on, with all the pre-requisites steps, backups and testings that will be done and Microsoft Premier to support us if problem, why wait ?
Is there many organisation like mine who are still waiting for the train to pass ?
READ MORE ABOUT PeoplePicker Customisation with STSADM:
Have fun and knowledge with me.: Active Directory configuration on Sharepoint Server: “Peoplepicker: Stsadm property (Office SharePoint Server)”