SharePoint would handle this nicely out of the box if this was a simple list, since lists have item level permissions built in, but not the case with forms. So I finally figured out this out of the box solution.

• In the Form Library Settings set Require content approval for submitted items to Yes. This is found under Versioning  Settings.
• Create a new Permission Level called Form Submitter. This custom role should be able to Add Items and View Items. Now give the group of users that will be submitting forms in the form library, this level of permissions on the library and give your admin contribute rights or higher.

Since your submitter doesn’t have rights to approve the form only themselves and the admin will be able to see it. The admin just has to make sure that they don’t approve the form.

What I ended up doing is creating a work flow that the admin can kick off to move the form to an archive folder that only the admin has rights to once the form has been completed.

Most the forums pointed to re crawling your site, deleting old databases, etc… and while this may work for some it didn’t work for us. Our real problem is we weren’t defining Members for each site, we were just assigning advanced permissions for each site. To set a group as Members of a site do the following.

• On your team site, go to Site Actions and then Site Settings
• In the first column under User and Permissions, click on People and Groups
• From the Settings menu choose Set Up Groups
• Set the Members of this Site option and click ok.

Your search will have to run a re-crawl at this point for it to pick up on your membership list. If that doesn’t work try doing a full crawl, but be careful to do this during non-peak hours.

I recommend the following

• Make sure WebClient is started ont he Server
• Run all XP updates + IE Updates
• Reboot

I think the fix is most likely burried in an IE 8 update.

We decided to go with SharePoint Groups to manage our group permission in Sharepoint. Granted AD would have given us a one stop shop for all of our permissions, but we felt it was better to go with SharePoint Groups.

• SharePoint Groups will allow us to delegate managing the groups to committee chairs, project leaders, etc… This is one less thing that Information Systems will have to manage. We can set the site up, make the base group and let the site lead take it from there.
• SharePoint Groups are viewable by SharePoint. This means we can use a Web Part to show the membership of a site on the site. This is really useful for project and committee sites, when it’s nice to have a team director right there. Granted we could have wrote a web part to do this our bought one, but it’s built in to SharePoint.

So that’s are take and we are sticking to it, till we change our minds.

Finally what I did is set my Admin Color Scheme on production sites to blue for my admin user and to Gray on development sites. This has helped alot to keep them straight with an easy glance at the colors.

Barracuda Networks

• These guys are top notch. I call in my problem or submit it online and I usually have a call back within 5 to 10 minutes top. They remote in and fix my solution, within minutes.

SAP

• I had several questions regarding Crystal Server Enterprise so I called them in. SAP proceeded to then spend 12 days verifying if I had a valid support contract (I had to email old PO’s, etc… to prove I had support.). Once that was cleared up, the representative referred me to the community network for help. One of the reasons, I called my problems in is because my community network ID no longer worked, despite resetting the password numerous times. I finally got my ID reset and finally had to email SAP support again because the support portal isn’t easy to navigate. Who would have thought a “help ticket” or “support request” would be buried several pages in and called a “message”.  I think it would be better to use standard industry lingo. At least the support people sent me a 23 page PDF file on how to submit a “message”. I’m not joking, 23 pages. I’m sure if a customer has frequent problems with SAP they become familiar with the whole process, but for us who only call in a request every year or two, this is a big pain.

In the end.

Kudos + mad props to Barracuda

and SAP, you need to keep working at it.

To fix this change the setting in login to your SharePoint back end and goto The “Shared Services Administration” and click on “My Site Settings”.

Change the Default reader group to your AD SharePoint Group.

This doesn’t casecade to all your current mysites. Each one now has to be tweaked. I’m looking for a fast way to do this but no luck yet.

• In finder goto Go->Connect to Server
• In the server address, paste in the url of the library you want to map to
• Click “connect”
• Enter in your domain, username and password.

It should mount the folder on your desktop. I expected to be able to drag and drop right into the mount, but that is not the case.

I ended up downloading free program call muCommander. This program will let you bridge your local file system (left hand column) and then browse the remote file system (right hand column). Now navigate to the correct place in your SharePoint library and in your file system and you can drag and drop using muCommander.