Should be in the administrator's guide in the first link of the last post.
In STS 1.0 the libs are stored in the DB - the actual files that are uploaded are stored as individual files on disk.
In the latest version (Windows Sharepoint Services)...everything is stored in the database.
Documentation for Sharepoint Team Services
http://www.microsoft.com/sharepoint/previous/default.asp
Support Link
http://support.microsoft.com/default.aspx?scid=fh;EN-US;spts
Deployment Guide
http://www.microsoft.com/technet/prodtechnol/sppt/sharepnt/spdepgdp.mspx
It is not a separate...
If you don't want to upgrade to Windows 2003 you can run the original version of sharepoint (sharepoint 1.0 or sharepoint team services). It is on the frontpage CD starting with frontpage 2002 I believe. It worked well for me.
Make sure the server is pointing to itself as the primary DNS server. I would also suggest that you verify that all the appropriate SRV records were created during installation.
If you want to prevent it from running altogether you can disable it from the registry via scripting or group policy. Let me know if this is what you want to do and I can get you the details.
Also, you can use a sniffer or firewall prodcut to see what the network utilization is for IM traffic...
Hi cplbaum2,
What DNS server are the workstations using? Internal or external? Do you have basic connectvity to the DNS server - ping? NOTE: Most organization's\ISP's block ICMP traffic so pinging may not work. What about UDP traffic...is it getting blocked by a local firewall? Definitely...
Hi czarj,
Run gpedit.msc from the run prompt and navigate to User Configuration, Adminstrative Templates, Control Panel, Display. There are several options here to disable display tabs and prevent access so users cannot change the default background image. I don't think there is any policy...
The best way would be to use login scripts or Active Directory group policies but you can also do this:
Choose "Local Printer" instead of "Network Printer" when you run the wizard (uncheck automatically detect) and then choose "Create New Port" (TCP\IP Port). Now, enter the IP address of the...
Hi FroggyJ,
I encountered this same problem today. Here is how I fixed it.
Check your DHCP log on the DHCP server. By default it is in c:\winnt\system32\dhcp. You should see log names like "DhcpSrvLog-Sun.log". Open up the one from the day you were having the issue (if it was within the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.