Portal Administrator



  • 1. Need update on the "Change Location" feature/bug
    I've been reading the posts on the Change Location issues and would like to know if anyone has an update or solution. I'm running SPS 2003, and the site has multiple areas. I just want to move a list from one area to another, but whenever I Change Location and then go back into the list it still has Home as the default location. I've tried the suggestion to deselect the Home checkbox in the site/area list, and that doesn't work. It seems silly to me that such a fundamental requirement -- moving content around on a portal site -- is so confusing. Thanks, GRT
  • 2. Contacts List Issues
    In contact list, there is a button called "Import Contacts". When I click it, a message box pops up: "Either there is no default mail client or the current mail client cannto fulfill the messaging request. Please run Microsoft Office Outlook and set it as the default mail client." I have office 2003 installed. What's wrong with this? Also, how can I make MS Office Outlook as the default mail client? Thanks a lot.
  • 3. Tried changing the account sharepoint uses
    I now get this error trying to access any page Service Unavailable Any ideas?
  • 4. SPS audience create/edit/compile give error
    audiencejob.exe giving event 0 .NET runtime error. in the diag log I see errors about sql sp, and 07/06/04 13:38:32:844 UNK 00000000 00001764 SqlError: 'Could not find stored procedure 'dbo.Orgle_job_UpdateLastTouch '.' Source: '.Net SqlClient Data Provider' Number: 2812 State: 62 Class: 16 Procedure: '' LineNumber: 0 Server: 07/06/04 13:39:09:844 UNK 00000000 00001764 AudienceOM : _GetADMemberShipRecursive encounter error. path=LDAP://CN=Productivity Group,CN=Users,DC=corp,DC=rmic,DC=com; Error is: Unknown error (0x80005000) lots of the latter error... seems to correlate to after adding an exchange group to AD. (though that is speculation) suggestions?

Portal Administrator

Postby Usman » Sun, 12 Dec 2004 16:36:27 GMT

Dear All

We have setup a SPS portal, and have run into an issue. We setup Sharepoint, 
on our test domain called ABC. The user setting up SPS on the machine had a 
login name called "TEST". We then created a subsite within SPS when we were 
logged in as "TEST". The objective we wanted to achieve was that we setup 
the portal and the relevant subsites using this "test" login, but then once 
the structure is there, we wanted to remove access of "Test" from the sub 
sites. We can remove "Test" from the main portal level access area, and also 
from each of the sub sites. On doing so, access to the main portal is 
finished, but we can still access the sub sites by typing the complete url 
in the window (e.g. if we created a site call XYZ on our machine, we can 
type http://<machine_name>/sites/XYZ) and the user can view the sub site 
completely, even though we cannot access the main portal anymore.

Please help!!!

Re: Portal Administrator

Postby ewyong » Tue, 14 Dec 2004 13:13:00 GMT

Try refreshing the window that you said you can still access. I guess the 
site must have been cache in the PC that you are using.

Re: Portal Administrator

Postby Bill English [MVP] » Tue, 14 Dec 2004 13:18:14 GMT

Well, I suspect that either 1)  Test is a member of the local admin's 
group - though I'm not sure why Test couldn't make it into the portal, if 
that was the case, or 2) Test is a member of a site group that has access to 
the site, or 3) you're not logged on as Test, though you might think you 

Just thinking out loud.............


Bill English

Similar Threads:

1.Portal Administrators

Hi, and happy new year to all,

I have an urgent question; my client has noticed that members of the "Domain
Admins" group on Active Directory have "Administrator" privileges on the
Sharepoint portal although they are not added to the users list on the
Portal (not even as Readers). My client is not happy about that.

Does anyone know how to stop "Domain Admins" from being "Administrators" on
the portal?



2.Restricting Portal Administrator Access

Dear All,
           We have SharePoint Portal Server deployed. I want to
restrict the Portal Administrator access to some of the sites,
documents, document library, etc.
Is there any way I can restrict the access of Portal administrator to
some of the specific sites or document library?

3.How to block local administrators from being Portal administrators?

Easy, don't put the server in the domain with your 'rogue' administrators,
leave it standalone and create the account locally. You might also want to
consider AD account creation mode and creating a separate doamin, that will
make it easier for users to provision their own account.

There will be no other solution, if a user is a local admin of a machine
then they could undo and setting you put on to lock them out. I *think* you
could remove doamin admins from the local admins group on that machine,
although Ive no idea of the consequences.

Steven Collier

SharePoint Portal Server MVP

Raymond W. Six < XXXX@XXXXX.COM > wrote:
> The environment:
> For our evaluation, we're running SharePoint Portal Server
> beta-2 with the "Technical Refresh" on Windows 2003
> Enterprise Server (eval).
> The question:
> How do I block local administrators on the portal server
> from being administrators within the portal site?
> I saw something on one of the screens indicating that
> local administrators are automatically site administrators
> too.  But, I haven't been able to find any way to disable
> this security hole.
> The issue:
> We're thinking about running Portal server to
> communication with business partners and such.  But, if we
> can't lock-out various domain admin accounts and service
> accounts on our domain from being used in the Portal site,
> then we'll have to dump Portal server and use another
> product.
> Please don't give me the "stock" Microsoft answer to
> require SSL on the site.  We're going to do that also.
> However, that doesn't fix (or in anyway address) the issue
> with local administrator's being portal administrators.
> The consequences:
> This is a very, very, very basic security requirement.
> Until we find a way to block such accounts, It's just way
> too big of a security hole.  The guys at corporate, and
> their outside security auditors will have my head if we
> implement anything with a hole like this in it.

4.local administrators are sharepoint administrators

Now I work for a company as a tier 3 support person.  I have because of this
domain admin rights.  By default domain admins are put in the local
administrators group on each server.  this means that most of my colleagues
for whom I am trying to set up sharepoint portal server are also doing the
same thing and can all administer sharepoint.

I realise that we may be unusual but this does present difficulties.

Is there any way around this at all ??


5.Site Administrator Vs Site Collection Administrator

Can any one plz clarify the difference between the Site Administrator and the 
Site Collection Administrator in sharepoint portal server environment. I am a 
bit confused in the two. My webpart asks for authentication if the user is 
not the Site Collection Administrator. Else it works fine. Can anyone help me 
in this?



6. SPS security: Domain administrator is site administrator?

7. Server local administrator vs SharePoint Administrator Group

8. SharePoint administrator - local machine administrator

Return to sharepoint


Who is online

Users browsing this forum: No registered users and 3 guest