Eric's profileiTrain Eric Ku BlogPhotosBlogListsMore  |  Tools Help |
iTrain Eric Ku Blog |
|||||
|
May 23 Enabling Wireless Networking In Windows Server 2008By default, Wireless Networking is disabled in Windows Server 2008. To Enable it, you have to install its required Feature. In fact, this is the beauty of Windows Server 2008. Most Features/Services are disabled by default, if you do not need it , keep it disabled, and at any time, if you ever needed any feature/service , all you have to do is to install its required feature or enable its service. February 22 Installing Sharepoint on Windows Server 2008Since Sharepoint is no longer included in Windows Server 2008, you have to install it yourself. The issue is this. If you try to install WSS 3.0 on Windows 2008, it will not install. It will tell you that you have to install SP1 and you will probably wonder how you can do that without first installing WSS 3.0. The answer is that you need to install the Windows Sharepoint Services 3.0 with SP1 installer that bundles Sharepoint 3.0 and SP1 together. download Windows SharePoint Services 3.0 with SP1. SharePoint Server Farm Q & A1. What is a SharePoint Farm?
In the context of SharePoint, the term 'farm' is used to describe a collection of one or more SharePoint servers and one or more SQL servers that come together to provide a set of basic SharePoint services bound together by a single Configuration Database in SQL. 2. What is the difference between an 'Application Server' and a 'WFE Server'?
When SharePoint is installed, you have to select one of three installation options, they are:
An 'Application Server' is a server that is capable of running any of the services apart from the Windows SharePoint Services Web Application service. A 'Web Front End' (sometimes called a WFE) is the opposite in that it can only run the Windows SharePoint Services Web Application service. 'Complete' means that the server can run any SharePoint service.
The problem with selecting anything other than 'Complete' is that it means if you ever change your mind about what services a server can run, you'll need to re-install SharePoint on that server. For that reason alone, I would always recommend that you choose 'Complete' unless you have a very good reason to do otherwise.
3. How should I design my web applications within my farm?
One of the rules about SharePoint farms is that every server that is running the Windows SharePoint Services Web Application service has to serve every web application in the farm. It is not possible to say "Server X serves Web Application X". This means that when you create a new web application in Central Administration, the Windows SharePoint Services Timer on each server that is running the Windows SharePoint Services Web Application service creates the necessary sites and application pools in IIS to serve the web application.
What about Central Administration?
The Central Administration web application is no exception to this rule in that the web application does exist on every web server. However, the Central Administration service only runs on a single server and it is that server that responds to Central Administration requests. This is why the Central Administration site is always bound to a server name rather than an NLB-enabled host header.
4. What is a farm's relationship with the SSP One of the optional components in a farm is a Shared Service Provider (SSP). SSPs are optional applications that use a combination of web applications and server services to provide several shared services. The key thing to note here is that the SSP does not run on any single server within the farm, there is no such thing as an 'SSP server'. The SSP is actually an application that requires the following:
Once an SSP is configured, its shared services can be provided to all of the web applications within the local farm. An SSP can also provide services to separate farms; this is called 'cross-farm Shared Services' and is very common in large deployments.
5. How many SSPs should I have in my farm?
Generally speaking it is best practice to have only one SSP per farm. It is possible to have multiple SSPs, but that configuration introduces a whole load of issues.
Each Web Application in your farm must get its Shared Services from a single SSP; it is not possible to pick and choose certain SSPs for certain shared services. Neither is it possible to say that a certain SSPs only provides certain services. The problem with this is that if you do have 2 SSPs, then you have 2 My Sites per user, 2 profiles per user, 2 sets of search indexes etc. Companies that do have this configuration, generally have to do a load of development work to keep the SSPs in sync with each other and make sure that user's are redirected to the correct SSP for their My Site.
There are only two common reasons for having multiple SSPs, they are:
6. When to have multiple farms?
Several scenarios where multiple farms make sense:
December 21 Hyper-V Best Practices1. Install Integration Services 2. Uninstall VMAdditions and Compact VHDs 3. Set Display for Best Performance 4. Configure Fixed-Size VHDs 5. Use SCSI Virtual Adapters for Data Drives 6. Allocate CPU Resources Based on Anticipated Usage 7. Consider Using Pass-Through Disks 8. Ensure File Share High Availability 9. Configure Domain Controllers to Optimize Performance Detail at Microsoft's Technet Blog: http://blogs.technet.com/vikasma/archive/2008/07/24/hyper-v-best-practices-quick-tips-2.aspx November 29 What is a Microsoft Product License "Virtual Key"'Virtual keys' are designed to be used when installing products that require activation in virtualized environments or on a hypervisor layer. The virtual key will allow you to change most virtual hardware configurations - such as memory or CPU - without requiring re-activation and will allow you to move instances of the product from one virtual environment to another without requiring re-activation.
For products like Windows Server 2008, Small Business Server 2008, two keys are provided. Both are 25 character keys. One is for installing the operating system in the physical operating system environment, and the other is for installing the operating system in a virtualized operating system environment. |
|
||||
|
|
|||||
Send a private message
Subscribe to RSS feed
Tell a friend
Add to My MSN
Add to your network
Sign up for alerts
|
|
