| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 10 months |
| seen | Dec 15 '11 at 16:18 | |
| stats | profile views | 3 |
|
Apr 15 |
awarded | Popular Question |
|
Mar 17 |
awarded | Popular Question |
|
Dec 1 |
revised |
Outlook Distribution List and WSS 3 "Outlook 2010 parlance" |
|
Dec 1 |
asked | Outlook Distribution List and WSS 3 |
|
Nov 30 |
comment |
Does Sharepoint offer live editing? Thanks! I appreciate your help and links. |
|
Nov 30 |
accepted | Does Sharepoint offer live editing? |
|
Nov 30 |
asked | Does Sharepoint offer live editing? |
|
Jul 19 |
accepted | Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance |
|
Jul 18 |
comment |
Alternate Access Mappings make me cry Ribbon menu? This is WSS 3...? :-) |
|
Jul 18 |
comment |
Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance @Jesus -- Thank you much for commenting here, too! Thanks for the link. I am having a production meeting this morning and will bring up the options. |
|
Jul 17 |
awarded | Commentator |
|
Jul 17 |
comment |
Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance Hmmm... In the second link re: upgrading from Express to full SQL, there are two follow-up questions: 1. Does the full SQL install need to be newer than 2005? (I have licenses for 05, but not any others). 2. Maybe this is something different about Express 2008, but in WSS 3, the database is on a different server address entirely. \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query vs. \\servername\Sharepoint. I don't see how the author accounted for Sharepoint looking for the DBs in the old location? |
|
Jul 17 |
awarded | Scholar |
|
Jul 17 |
comment |
Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance I just checked and it looks like we have an Open License for Server 2008. Since this is an ESXi server, we could deploy a 2008 Server configuration with Sharepoint 2010 Essentials. Hmmmmmmm.... |
|
Jul 17 |
accepted | Alternate Access Mappings make me cry |
|
Jul 17 |
comment |
Alternate Access Mappings make me cry Yes, they work. I did see some errors in the Event Log re: an older sharepoint URL that is no longer is use. The errors are not continuous. Rather they logged for about 1.5 hours and stopped ... I am wondering if there is an Outlook client out there trying access over this older URL.... |
|
Jul 17 |
comment |
Alternate Access Mappings make me cry So as far at the Zones go, Default is servername. Internet is the 987 site. 443 is in the Intranet site. This configuration seems to work in that Search still functions and Outlooks outside of the LAN don't complain about inaccessible URLs. I do need to lock down the 80 site more to my liking, however and I've not re-tested outgoing email for alerts. I'll do that shortly and update. |
|
Jul 17 |
comment |
Alternate Access Mappings make me cry First, I am sorry if I implied that you didn't read my post. I was unsure of the timing between my edit and your comment. I think that the way things are configured now is what you're suggesting. I didn't install Sharepoint so I don't know how things were set up in the beginning but I imagine that the first site was 80/NTLM. In essence, I've gone back to that original configuration, extended the original site twice using different ports. The original site is: servername. Extended1 is sharepoint.domain.com:443. Extended2 is sharepoint.domain.com:987. |
|
Jul 16 |
comment |
Tutorial to move WSS 3.0 DBs from Windows Internal to SQL 2005 Instance Thanks. My anxiety over the whole procedure leads me to this question: Is it more troublesome to upgrade or to stay in WSS 3 and move the DBs into SQL 05? Keep in mind that we're going to do all of this on one server. -- Oh, this might be a wrinkle. We're running Windows Server 2003. |
|
Jul 16 |
comment |
Alternate Access Mappings make me cry Not sure if you happened to read the edit above, but I have three IIS instances of the site now. One for port 80, one for 443, and one for 987. The users are all currently using 987 from outside of the LAN. I'd prefer not to have to reset them all up again, but will if I have to. -- Should I restrict the 80 instance as you suggest? -- Goal here is to keep search running and to prevent send/receive errors in Outlook. |