|
|
||||||
|
#1
|
|
|
|
|
SBS 2008 includes Windows SharePoint Services 3.0 and one of the tasks that
needs to be performed is to change the default Central Administration Application Pool account. The following describes the process http://costas.cpstechgroup.com/2008/...-pool-account/ |
|
|
|
#2
|
|
|
|
|
Costas wrote:
>SBS 2008 includes Windows SharePoint Services 3.0 and one of the tasks >that needs to be performed is to change the default Central Administration >Application Pool account. Why? And are you sure this is the appropriate venue for this discussion? |
|
#3
|
|
|
|
|
I'm not sure I understand the 'Why' but if you are referring 'why the task
needs to be performed?' then it's because the task description indicates that this account has to be unique. As far as being the appropriate venue, I thought that some people could benefit from reading the post. It wasn't meant to be a subject for discussion. I apologize if I did something wrong. |
|
#4
|
|
|
|
|
Costas wrote:
>I'm not sure I understand the 'Why' but if you are referring 'why the task >needs to be performed?' then it's because the task description indicates >that this account has to be unique. The why was indeed why would you _need_ to mess with Sharepoint. If it's been deployed as part of SBS setup, you can expect it to be working without the need for manual tweaks. >As far as being the appropriate venue, I thought that some people could >benefit from reading the post. It wasn't meant to be a subject for >discussion. I apologize if I did something wrong. The point there was that SBS2008 is still in beta, and there are more appropriate venues to discuss issues with it (particularly, where MS staff will pick up comments). |
|
#5
|
|
|
|
|
Out of the box SharePoint, although it works, it still needs configuration.
The configuration steps that needs to be performed are the same as any other SharePoint installation, on a non-SBS environment. There are a couple of particulars to SBS when it comes to mail enabling libraries, but other than than the rest of the configuration steps are the same SBS or non-SBS environment. Do people go through these steps? My guess is most probably not, and that's the reason for the document. The reason for posting here (btw, I also posted the links to the SBS 2008 yesterday) was that there are a lot more people here that could have taken advantage of these documents. I didn't see it as 'issues', that the document would have provided solutions. The steps, especially with the SharePoint document, apply to every SharePoint installation, whether on SBS or Windows Server platform. |
|
#6
|
|
|
|
|
Hi Costas,
Thanks for the timely posting! Mike |
|
#7
|
|
|
|
|
You are welcome
|
|
|
| Similar Threads | |
| SharePoint Central Administration v3 Application pool stops I installed MOSS 2007 on windows 2008 R2 (RC1) which is a domain controller of my domain All went OK untill I added the share services. Now I keep getting: HTTP Error 503.... |
|
| Cannot backup portal Application with Central Administration. I am not able to back up portal applications through the Central Administration Site. SharePoint and SQL are on separate servers. The backup folder is on the SQL server. 15... |
|
| Cannot change application pool account Windows Server 2003, sp2 Sharepoint services 3.0 Using single server settings. I am trying to change the central admin account to a domain account. When I do that, if i try... |
|
| Central Administration application pool account should be unique Setup: wss3.0 sbs 2003; installed as per Microsoft whitepaper. Can I ignore this above message in the Central Administration? The website seems to be accessible OK. Although... |
|
|
All times are GMT. The time now is 02:19 AM. | Privacy Policy
|