Go 4 Sharepoint

Search:

Welcome: Guest!

Sharepoint Forum

Home » Forum » Sharepoint

Ask a question

RSS Feeds

NT Security Issues

Asked By: Noah Scott Date: Apr 13, 2010 Category: Sharepoint Views: 124

We are currently undertaking a SPS pilot and having trouble with assigning
security. I have my readers, authors and co-ordinators setup and can see it
all as it should be in Workspace Settings but SPS still does not recognise
the users. I know this is a bug but a restart did not cure the problem.

The following did:
I stopped the IIS Admin Service - This stopped the MS Exchange
Information Store, Sharepoint Portal Server and SMTP services.
I restarted all maually and it seems fine now. ( ???? Why didn't the restart
work ?)

Please tell me that SP1 fixes this issue - surely I don't have to do this
EVERY time I want to add a new user?

Tagged:nt security issues

8 Answers Found

Answer #1 Answered By: Alka Sarabhai Answered On: Apr 13, 2010

We've had the same problem & nope the sp1 does not fix it. We wrote an API
to restart SPS services & reboot the server (the latter works fine with our
set up). It's a pain alright, but we've advised clients to batch add users
and reboot the server evenings/weekends for minimal disruption.

Answer #2 Answered By: Eashan Nadkarni Answered On: Apr 13, 2010

There go my hopes about SP1!!

Looks like I will just have to batch add users after hours as you
suggested....

Is there a particular order in which the SPS services should be restarted to
ensure everything works okay?

Answer #3 Answered By: William Odom Answered On: Apr 13, 2010

If you restart the IIS Admin Service, all related services will
automatically be restarted as well.
That should do it.

If not:

IIS Admin Service
W3SVC
SMTP
NNTP
SharePoint Portal Server
Exchange Information Store

Answer #4 Answered By: Mia Scott Answered On: Apr 13, 2010

When I restarted IIS Admin the other services did not start automatically.

Thanks for the list of services...

Answer #5 Answered By: Kristian Chaney Answered On: Apr 13, 2010

You shouldn't be running Sharepoint portal on an Exchange box...

Answer #6 Answered By: Alicia Scott Answered On: Apr 13, 2010

I think you misread. She said the Exchange Info Store... that is part of SPS.
Although, in a lab, running it on an E2K standard box would be fine.

Answer #7 Answered By: Mike Lamb Answered On: Apr 13, 2010

One of the ways you may be able to avoid this is to assign permissions to groups
instead of users. Instead of adding users to SPS, add them to the appropriate
global group.It is not quite as convenient as dropping a user in, but it will
also make your portal run faster since it will have fewer permissions to spin
through each time someone tries to access a file or search request.

Answer #8 Answered By: Jose Scott Answered On: Apr 13, 2010

Does this have any effect on subscriptions? If I have a group (say
SPS-WS-AUTHORS) can each individual
in the group have different subscriptions?

Didn't find what you were looking for? Find more on NT Security Issues Or get search suggestion and latest updates.