Search results for query: *

In reality, you shouldn't need to extend the web app to get it working with SSL. All you really need to do is add the cert to IIS, and add the https:// entry for your site into Alternate Address Mappings

Open Port 80/443 Configure DNS (both internal and external) to be what you want Configure Alternate Address Mappings in SharePoint Central Admin (Operations tab) Add host header in IIS if just adding AAM doesn't work That should be about it

SP wouldn't "break", as the local users & groups would still be there and access would still be allowed via them. However, yes everywhere 'webserver/johnsmith' was located, it would need to be changed to 'activedirectorydomain/johnsmith'. There are some tools that would make this a little...

It is a security issue in FireFox. FireFox will not pass NTLM authentication automatically. In IE, there are options to fix this. Add the site to your "Trusted Sites" list and make sure the security options for this zone have "Automatic log on with current user name and password" selected...

As long as you are using the Embedded edition and not SQL Express you should be fine. SQL Express has a 4GB database limitation, but embedded edition does not. However, you will not be able to use SQL Client tools to manage the DB A few helpful links on Embedded edition...

That pretty much what we are doing right now. We backup all our sites to disk every night via STSADM and do a file level backup of the app server. We also run a SQL backup of all the SP databases. You are covering all your bases at that point, and like you said - better to be safe than sorry.

Also, forgot the 1 place on the server where you would want to backup would be the "12 hive" c:\program files\common files\microsoft share\ web server extensions\12\ This is where all of your templates and images etc are stored

All of SharePoint is stored in your SQL database. The STSADM backup you run pulls the data out of SQL and dumps it to file. If all you are doing is backing up your SP server, you are only getting a true backup once a week (when your STSADM runs). On the SP server itself, you have your...

This might be a pain, but would probably work.. Create a folder for each associate and trim the permissions on that folder so that only the user and admins have access to it. When they go into the document library, they will only see their folder and be able to upload to it. The admins /...

If you are a site owner, you can add the items on to the quick launch bar manually. It is possible that they were removed, or when the list was created, the option to include on QL was not checked. Site Actions - Site Settings Quick Launch (under look and feel column) If you are not a site...

There are a few options available. Microsoft has free SharePoint training. Users can either download their own, or you can deploy to SP http://office.microsoft.com/en-us/sharepointserver/HA102488011033.aspx Also, there is a great end user book out there called "The SharePoint Shepherd’s...

The best way in this situation is to build AD groups for Sites A, B, & C. If you have Site A Users, Site B Users, and Site C Users, you can just add the individual AD groups to the sites they need access to

See -- http://support.microsoft.com/kb/923896

There is no way to do this out of the box. You may want to look at the 3rd party tool DeliverPoint to accomplish this (http://www.deliverpoint.com)

Check the host-header in IIS for the SP site. You can add the entry that you added as an alternate address mapping in here and have it look at port 80 without interfering with the default website

Use SharePoint alternate Address mappings in Central admin. Then create a DNS entry on your DNS server and it should work without issue.

Are you using MOSS or WSS? If you are using MOSS, look into the content query web part. If you are using WSS, you may be SOL out of the box. Bamboo Software has a list roll-up web part that you can purchase to use for this purpose. See --...

Also, look at SharePoints alternate address mappings if you are publishing it with a different DNS name for external access.

It is hard to go wrong with any of these 3 in my opinion. I was impressed greatly by the Cashel solution at the SharePoint conference Cashel ecKnowledge http://www.casahl.com/Solutions/SharePointSolutions.html Quest http://www.quest.com/sharepoint/ Avepoint http://www.avepoint.com/

The only work around I have found is to create a group owner group in SP and add the domain group to that. Then make the SP group owner