Eric's profileiTrain Eric Ku BlogPhotosBlogListsMore Tools Help

Blog


    23 May

    Enabling Wireless Networking In Windows Server 2008

    By 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.
    22 February

    Installing Sharepoint on Windows Server 2008

    Since 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 & A

    1. 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:
    • Application Server
    • Complete
    • Web Front End
    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:
    • At least one server running Office SharePoint Server Search service in Index mode
    • An 'SSP Administration' Web Application
    • 2 databases in the farm's SQL server
    • Optionally, a server running the Excel Calculation Service
    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:
    • Index Server scale. There is a recommended maximum of 50 million items per Index Server (more information click here). Since you can only have 1 Index server per SSP. If you can more than 50 million items to index, you may need to split the load across multiple SSPs.
    • Privacy. Some parts of the organization may actually want to host their own My Sites, Profiles etc and the split is seen as a good thing.
    6. When to have multiple farms?
    Several scenarios where multiple farms make sense:
    • Physically separate data centres
    • Differing customisation approaches and polices
    • Differing support policies and SLAs
    • Development, staging and test environments
    21 December

    Hyper-V Best Practices

    1.       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

     
    29 November

    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.
    27 November

    Forms Authentication in SharePoint

    Explore several new features for authentication and authorization in Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services 3.0 that make it easier to develop and deploy solutions in Internet-facing and extranet environments. Here is the useful content from MSDN:
     
    http://msdn.microsoft.com/en-us/library/bb975136.aspx
    Introduction to Forms Authentication in SharePoint Products and Technologies
    Deciding to Use Forms Authentication
    Reviewing a Typical Scenario for Authentication
    Reviewing Changes to Authentication Terminology
    Setting Up Forms Authentication
    Granting Permissions to Create My Sites
     
    http://msdn.microsoft.com/en-us/library/bb975135.aspx
    Developing Custom Membership and Role Providers
    Applying the XML File for the Data Source
    Inheriting from the Membership and Role Base Classes
    Minimum Interfaces Required by MOSS and Windows SharePoint Services
    Registering the Custom Provider
    Debugging the Custom Provider
    Writing a Custom Forms Logon Page
    Using Web Services with a Site Protected by Forms Authentication
     
    http://msdn.microsoft.com/en-us/library/bb977430.aspx
    Introduction to Differences Between Forms Authentication and Windows Authentication
    Crawling Content
    Integrating with the 2007 Microsoft Office System
    Opening Documents in Internet Explorer
    Checking the "Sign me in automatically" Check Box at Logon
    Using an HttpModule During Authentication
    User Profile Imports
    Resolving Names
    Using an LDAP Provider
    Using the Microsoft Single Sign-On Service
    Conclusion
     

    Business Data Catalog tool for all SharePoint Developers and Administrators

    Do we really have to know XML coding to create an application defination for SharePoint Business Data Catalog? Here is the GUI tool can do it without coding XML. 
    BDC Meta Man is the first Business Data Catalog tool for all SharePoint Developers and Administrators interested in line of business data integration with SharePoint. Without writing a single line of code you can be viewing and searching across your business data through Microsoft Office SharePoint Server 2007 in minutes.
     
    So, what is the applicaiton defination? An application definition describes a database or web service. It includes connection settings, authentication mode, definitions of available entities, and other information. After you upload an application definition to the Business Data Catalog, you can use its entities in lists, web parts, search, user profiles and custom applications.
    09 November

    Getting UNDO functionality with Hyper-V Snapshots

    In Hyper-V, UNDO is not an available option on the virtual disk menu anymore, you now have snapshots. If you want the ability to protect your VHD from any changes getting merged you need to do this.

    Before you first power on a VM (the same point you would have enabled UNDO in Virtual Server), take a snapshot and call it something like UNDO DISCARD. This just makes your VHD effectively read only and all changes are written to a working AVHD file.

    Power on your VM and work away.  When you want to effectively “Turn OFF and Discard” all changes, then apply revert (under action menu) to the UNDO DISCARD snapshot and it is all gone…start a new test scenario. Just remember that if you made any changes to the VM settings, they are also discarded.

    27 October

    Quick Overview of Microsoft Hyper-V Server

    Microsoft Hyper-V Server 2008 is a free product available for download from Microsoft Download Center.
     
    It is important to note that the product does not require Host Server license. Each Windows guest Virtual Machine which is running on it requires a license, though. In comparison Windows Server 2008 standard edition Host Server License includes 1 Physical and 1 Virtual Machine license, the Enterprise edition – 1 Physical and 4 Virtual machines, and the datacenter edition – 1 Physical and unlimited VMs.
     
    Microsoft Hyper-V Server is a perfect choice for you, if you do not plan to use more than 4 CPUs on the host server, and more than 32 GB of memory. It also lacks some of the advance Virtualization features like Clustering and Quick Migration. In addition, it lacks most of the Server Roles which you are used to see on Server Core. Here is the list of Server Roles, available in Microsoft Hyper-V Server 2008:
     
    - BitLocker
    - BitLocker-RemoteAdminTool
    - Microsoft-Hyper-V
    - Microsoft-Windows-RemovableStorageManagementCore
    - MultipathIo
    - NetworkLoadBalancingHeadlessServer
    - SNMP-SC
    - TelnetClient
    - WindowsServerBackup
    Only the Microsoft Hyper-V role is installed by default.
     
    Hyper-V Server requires:
    - An x64-based CPU
    - Hardware-assisted virtualization (Intel VT or AMD-v)
    - Hardware Data Execution Protection (DEP)
     
    Find answers to frequently asked questions about Microsoft Hyper-V Server at http://www.microsoft.com/servers/hyper-v-server/faq.mspx 
    24 October

    Quick Overview of Microsoft Project Server

    Microsoft Office Project Server is a project management server solution made by Microsoft. It leverages Windows SharePoint Services as its foundation, and utilizes both a web interface and Microsoft Project as the client application.
     
    Microsoft extends the capabilities of Microsoft Project with Project Server and Web Access. Microsoft Project Server stores project information in a central database, protected from unauthorized access and corruption. A Project Administrator can control security defining users and access rights.
     
    The Project Center supports reports across an organization at the project level. Managers can drill down into project details.
    The project manager needs to communicate project plans and to distribute task assignments to team members. The assignment of tasks can be distributed to team member home pages in Web Access. They need to communicate status and changes to keep the project manager up to date. Project Server supports electronic communication over the web via Web Access.
     
    Resource workloads can be analyzed by project and by resource with the Resource Center, allowing organizations to forecast future resource requirements and make more efficient use of resources.
    23 October

    Microsoft Project User Group

    MPUG has been the User Group for Microsoft® Project for over ten years. MPUG connects project managers around the world, enabling them to collaborate and learn from each other to maximize their project’s success. With MPUG, users can get Project support relevant to their job from within their local community chapter and online. Companies, project managers and consultants all benefit from membership in the global MPUG community. Join MPUG at http://www.mpug.com/Pages/Home.aspx
    21 October

    Why are Project Managers Using Project Management Tools

    Microsoft Office Project gives you robust project management tools with the right blend of usability, power, and flexibility, so you can manage projects more efficiently and effectively. You can stay informed and control project work, schedules, and  finances; keep project teams aligned; and be more productive through integration with familiar Microsoft Office system programs, powerful reporting, guided planning, and flexible tools.

     

    Why Project Manager Use Microsoft Project?

     

    1. Effectively manage and understand project schedules

    2. Get productive quickly

    3. Leverage existing data

    4. Build professional charts and diagrams

    5. Effectively communicate information

    6. Gain greater control of resources and finances

    7. Quickly access the information you need

    8. Track projects according to your needs

    9. Customize Office Project 2007 to your needs10. Get Office Project 2007 online assistance when you need it

    12 April

    Microsoft Heroes Launch

    There was a very successful launch attended by 2500 people. Photo can check www.itrain.com.my