Voila! It worked again for standard users. I opened command prompt to run as administrator, ran iisreset, then tried the test again. I was just about to fall asleep when I jumped up, grabbed my laptop, and logged back onto the server. I was frustrated, and it was late in the evening, so I put it aside. To my absolute surprise, they failed as before. I added authentic users to the group, and it automatically gave read & execute, list folder contents, read, as the correct permissions.įeeling pretty proud of myself, I ran the connectivty tests again. I checked permissions on that directory and found that the network administrator account had rights, but that authenticated users was missing. The test goes to the directory C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover and in particular to autodiscover.xml in that directory. Okay, that confirmed it was membership in the admin group. For grins, I changed the role on the new account to admin, tried the test again, and it worked.
So I created a new account, tried that, and it also failed when testing Outlook for RPC over HTTP. Hmm, I thought, maybe I don’t have the right credentials. Until I switched from the network admin account to a user account. What I found was that everything was working just fine. That was successful, albeit it very messy, and everthing seemed fine.īack to the connectivity tests. Some permission issues cleaned up most of the Default Web Site, but SharePoint had to be rebuilt. Before I tell you about that, let me give you some additional background about this server.Īccidentally, one of the users made a mistake trying to set up a new SharePoint web site, and as a result almost everything in Default Web Site and SharePoint got damaged from a little to completely dead.
I then ran some tests using so I could see what was happening. It was all users except those in admin group. It was then the pattern jumped out at me. The first thing I did was to get an authoritative list of those who had the problem.
None of these whack-at-it things worked, of course. Uninstalling and reinstalling Outlook (a lot of users running old XP machines and Office 2007).Making sure user name entered as domain\user.Our checklist to solve the problem included: Some users were being prompted for a password when using Outlook, but others were not.
0 kommentar(er)
