SCE Forum FAQs (For System Center Essentials 2010)

Discussion SCE Forum FAQs (For System Center Essentials 2010)

  • Thursday, May 06, 2010 3:32 AM
     
     

    Hi All,

    This thread contains the Frequently Asked Questions on System Center Essentials 2010. We consolidate them and post it here for your reference. If you have any further questions, please kindly start a new thread in that other community members, MVPs, and we can easily attend to your question and reply. Thanks for your understanding.

     

    You may also find Q1~Q5 for System Center Essentials here.

     

    Q6: How to monitor Exchange 2007 server in System Center Essentials 2010?

    Symptom:

    Essentials is only monitoring the Exchange 2007 server that exchange is installed on, but not the exchange server itself.

    Cause:

    Exchange 2007 monitoring is not enabled by default in System Center Essentials 2010.

     

    Resolution:

    1.    Go to the Object Discoveries node located under Authoring in the Operations console.

     

    2.    In the Look for field, type Exchange 2007 Server Role and click Enter. A list of Exchange 2007 Server Role Discoveries appears. You need to enable Server Role Discoveries of the following discoveries for most environments:

     

                Exchange 2007 CCR Node Role Discovery

                Exchange 2007 CAS Role Discovery

                Exchange 2007 Hub Transport Role Discovery

                Exchange 2007 Edge Role Discovery

     

    If you don't see the "Look for:" box above the list of discoveries, press Ctrl+F to display it. If you have a clustered Exchange Server, or Exchange Unified Messaging please refer to the Management Pack Guide for additional discoveries to enable.

     

    3.    To enable the discoveries, right click on each of the Discoveries and select Overrides\Enable the Object Discovery\for all objects of type Exchange 2007 Discovery Helper.

     

     

     

    Q7: A task may return a "Success" code when it actually failed in System Center Essentials 2010.

    Symptom:

    A task may return a "Success" code when it actually failed in System Center Essentials 2010. For example, the Logical Disk Degragmentation Task returns a "Success" status even the details of the task says the following:

     

    "Defrag failed (disk: C:; computer: computername.domainname.com). Return code: 10."

     

    Cause:

    Running tasks is a two-step process:

     

    1. Submit the task to the Health Service and start the task requested

    2. Review the task output

     

    Currently, the task status is based on only the first step of the process. As long as the task is submitted and the executable to run was started, the task is returned as being "Successful". i.e. Essentials reports back "I ran the task".

     

    This definitely causes confusion for people since most people assume that the Task status is based on the return code.

     

    Resolution:

    None.

     

     

     

    Q8: "A reboot is required to begin installation" when installing Microsoft System Center Essentials 2010.

    Symptom:

    When installing Microsoft System Center Essentials 2010, you receive the following error message even after the server reboots several times: 

     

    "A reboot is required to begin installation"

     

    Resolution:

    1.    Click Start -> Run, then type regedit, press Enter.

     

    2.    Check HKLM\SYSTEM\CurentControlSet\Control\SessionManager for the key PendingFileRenameOperations. Backup the key, then delete it.

     

    3.    Re-launch setup.

     

     

    Q9: Cannot specify properties to new virtual machine in System Center Essentials 2010.

    Symptom:

    When you use the "Import a virtual machine" wizard in System Center Essentials 2010 and select a VHD, the specify properties are not imported to the new virtual machine. All properties are XXXXX and Change Properties doesn't do anything.

     

    Resolution

    Prior to importing a virtual machine in System Center Essentials 2010, you must designate a physical server capable of supporting virtual machines as the host server.

     

    To designate a host server:

    1.    In the Essentials console, click Computers, click Computer Groups, and then click All Windows Servers.

     

    2.    In the Tasks pane, click Designate a Host.

     

    3.    On the Select a computer to use as a host page, select a computer from the provided list that has sufficient resources to be used as a host server for Virtualization Management, and then click Select to continue.

     

    4.    On the Provide account credentials page, specify an account that has administrative privileges on the selected computer, and then click OK to continue.

     

    5.    A dialog box appears notifying you that the process of designating a host computer might require the computer to be shut down and be restarted. Click Yes to continue.

     

    6.    A progress bar appears while Essentials designates the selected server as a host. Clear the check box if you do not want to view the new host after closing the wizard. When the wizard has completed and the selected computer has been successfully designated as a host, click Close.

     

     

     

    Q10: Error 0x80070661 when deploying a x64 MSI package to x86 computers in System Center Essentials 2010.

    Symptom:

    When deploying a x64 MSI package to both x64 computers and x86 computers in System Center Essentials 2010, the x86 computers report an Windows Installer error because the MSI file is for the wrong Platform (error code: 0x80070661)

     

    Cause:

    This is a limitation in System Center Essentials 2010.

     

    MSI files that are approved to a group of computers will be downloaded and attempt to be installed on all computers in the group. If the MSI can only be installed on x64 computers, then x86 computers will still attempt to install the package but report an error.

    Resolution:

    To workaround this limitation we recommend only approving x64 specific MSI packages to groups containing only x64 computers.