Welcome to TechNet Blogs Sign in | Join | Help

System Center 2007 and Virtualization

At the Microsoft Management Summit and TechEd this year we announced  System Center Essentials 2010, the next version of Essentials. We also started to talk about the new features, in particular how we’ve placed virtualization capabilities in Essentials, providing a single location for monitoring and managing virtual computers.

You don’t need to wait for Essentials 2010 though to get started with virtualization management in Essentials.

Essentials 2007 supports virtualization in the following ways:

  • Essentials server can run on a virtualized operating system, i.e. you don’t need a physical server for Essentials.
  • Managed computers can be virtual. The Essentials agent will monitor and manage your virtual computers the same as your physical computers.

If you have System Center Virtual Machine Manager (including Workgroup Edition) you can go one step further and not only monitor virtual computers, but also create and control (start/stop etc) virtual computers.

Instructions for configuring Essentials and VMM are now available on TechNet to help you get started.

http://technet.microsoft.com/en-us/library/dd759392.aspx 

If you’ve previously followed Pete Zerger’s instructions for configuring Essentials and VMM you’ll be pleased to know that there are updated MPs available that include reports for Virtualization.

With Essentials 2007 and VMM you will use 2 consoles, but when Essentials 2010 is released you will have a single console for monitoring and managing both your virtual and physical computers.

An Edge-ier Video on System Center Essentials 2010

David Mills and I hooked up with the TechNet Edge folks at TechEd 2009 and shot another video on System Center Essentials 2010.

http://edge.technet.com/Media/System-Center-Essentials-with-David-Mills-and-Dustin-Jones/

Posted by dustinj | 1 Comments

What's new for Microsoft System Center Essentials 2010?

Check out this video that we shot at TechEd 2009 for details on the next release of System Center Essentials.

http://www.msteched.com/online/view.aspx?tid=bf478844-4f77-4f92-9119-67eae225ecb5

Posted by dustinj | 1 Comments

Why are my Performance Graphs Empty in Essentials?

Have you wondered why some of the performance views and dashboards in the Monitoring Space don’t have any data to display, yet others do?

You can see an example of this by going to the Monitoring Space, expanding the Microsoft Windows Server folder and then expanding the Performance sub Folder.  

The "Disk Capacity", "Memory Utilization (Page File)" and "Processor Performance" dashboards all let you select performance counters for your servers and view pretty graphs. 

The "Disk Performance", "Disk Utilization", "Memory Utilization (Physical)" and "Network Adapter Utilization" don’t show a list of performance counters to select. Why is this, and how do we get a list of performance counters to display?

The performance counters available for display are controlled by rules in management packs. Not all of the rules responsible for data collection are enabled by default and this is why we don’t see a list of counters to select from in the views listed above.

To get a list of counters for these views we need to enable data collection by setting overrides on performance collection rules, and this is done in the Authoring Space.

Note: Enabling performance collection rules will increase the size of the Essentials database. If you are using SQL Server Express, collecting additional performance data may reduce the number of days of historical data available for reporting.

Let’s work through an example and enable data collection to populate the Windows Server Performance graphs we listed above.

For the Disk Performance dashboard view we will need to override the following rules:

  • Collection Rule for the Average Disk Queue Length
  • Collection Rule for Current Disk Queue Length
  • Collection Rule for Average Disk Seconds Per Read
  • Collection Rule for Average Disk Seconds Per Write

For the Disk Utilization dashboard view we will need to override the following rules:

  • Collection Rule for Disk Bytes Per Second
  • Collection Rule for Disk Reads Per Second
  • Collection Rule for Disk Writes Per Second

For the Memory Utilization (Physical) dashboard view we will need to override the following rules:

  • Memory Pool Paged Bytes
  • Memory Pool Non-paged Bytes

For the Network Adapter Utilization dashboard view we will need to override the following rules:

  • Network Adapter Bytes Received per Second
  • Network Adapter Bytes Sent per Second

 

To override a rule to enable performance data collection:

  1. Go to the Authoring Space
  2. Expand Management Pack Objects
  3. Select Rules
  4. Click Change Scope
  5. Click Clear All
  6. Type Windows Server in the “Look for” box
  7. Place a check mark next to all targets starting “Windows Server”
  8. Click OK
  9. Find the rule to Override
    You can either scroll through, or use the “Look for” functionality to filter the list.
    In this case, use one of the following words for each category: logical, memory, network
    You can only use one of the filter words at a time
  10. Select the rule, then from the Actions Menu, select Overrides -> Override the Rule -> For all objects of type: Windows Server 2003 Logical Disk
    For the Memory and Network rules the type will be slightly different
  11. Check the box in the Override Column next to Enabled.
  12. Click Apply
  13. The Effective Value for the Enabled Parameter will change from False to True
  14. Click OK

You will have noticed at Step 9 that for each rule there is a copy of the in the rule in the Windows Server 2000 Operating System and Windows Server 2003 Operating System Management Packs. If you want to enable collection for both Operating Systems you will need to override both copies of the rule.

As a general guide, the title of the graph in the dashboard view identifies the performance counter being collected. The rule to collect this counter will also have the counter name in it. You can use this information to find the rules that you need to enable for a particular graph.

Fix to enable Remote Assistance task on Vista and Windows Server 2008

As Dustin mentioned in the previous post, we recently released an update to the Microsoft.SystemCenter.Essentials.2007.mp. We have also released KB956890 which provides additional details.

This update resolves an issue where the Remote Assistance task fails to execute if the System Center Essentials console is running on Windows Vista or Windows Server 2008. Without the fix, attempting to run Remote Assistance results in the following error message:

Application: C:\Windows\pchealth\helpsctr\binaries\helpctr.exe

Parameters: -FromStartHelp –url hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/SCEUnsolicitedRCUI.htm -ExtraArgument NOVICECOMPUTER=<ComputerName>&NOVICEUSERID=

Error Message: The system cannot find the file specified

In Windows XP and Windows Server 2003, Remote Assistance is started from the Help and Support Center (helpctr.exe), while in Windows Vista and Windows Server 2008, Remote Assistance is started via msra.exe.

This update modifies the Remote Assistance task to call the correct command line based on the operating system that the Essentials console is running on.

You are recommended to install this update if you use the Essentials console on Windows Vista or Windows Server 2008 and want to use the Remote Assistance task.

When using Windows Server 2008, please ensure you have the Remote Assistance feature installed. The Remote Assistance feature is not installed by default, but you can use the Add Feature Wizard within Server Manager to enable it.

More information is available in KB956890.

This update is available from the Microsoft Download Center via the following link: http://www.microsoft.com/downloads/details.aspx?FamilyId=8F74CC26-5E0E-42F1-96CC-7AE064099190&displaylang=en

Management Packs for System Center Essentials

A management pack is a definition file (either with an .xml or .mp extension) that contains predefined monitoring settings that enable an agent to monitor a specific service or application in Operations Manager 2007 or Essentials 2007. These predefined settings include discovery information that allows Operations Manager and Essentials to automatically detect and begin monitoring services and applications, and a knowledge base that contains error and troubleshooting information, alerts, and reports to help you correct the problems detected in your environment.  You import a new or updated management pack into Essentials using the Management Pack Import Wizard (found in the Administration space in the Essentials console).

Almost all of the management packs developed for Operations Manager 2007 can also be used in Essentials 2007.  To help you identify these management packs, you can filter the System Center Pack catalog on Essentials:

http://technet.microsoft.com/en-us/sce/cc462787.aspx

One management pack that you might want to import into Essentials straight away is the updated Essentials 2007 management pack that resolves an issue that was preventing the Remote Assistance task from running on Windows Vista and Server 2008. You can download this management pack from this location:

http://www.microsoft.com/downloads/details.aspx?FamilyId=8F74CC26-5E0E-42F1-96CC-7AE064099190&amp;displaylang=en&displaylang=en

Posted by dustinj | 2 Comments

Announcing the System Center Essentials Technology Adoption Program

This announcement is to alert you that the next version of System Center Essentials Technology Adoption Program (TAP) is now accepting nominations.

Do you want to be part of making the next generation of the System Center Essentials product great?  If you are a responsible for managing the IT assets and services for a midsized business and have a passion for providing feedback, you could be a great candidate for our Technology Adoption Program (TAP).  We view our TAP program as one of the most important investments we make as a product team.  We are very selective in which customers we invite to participate and we intend is to partner very closely with you.  Our goal is to develop a mutually beneficial and long term relationship with you to enable building the next version of the System Center Essentials product that is designed to meet your needs to the best of our abilities.

For more information and to nominate yourself for the TAP please click this link.

Thank you!  The System Center Essentials Team.

Posted by dustinj | 3 Comments

Using the Remote Assistance task with Vista and Server 2008 computers

(thanks to Essentials team member Stephanie for this article!) 

If you've tried to use the Remote Assistance task in the Essentials Computer space to connect to a Vista or Windows Server 2008 computer, you've found that the task to initiate a Remote Assistance session does not work.  The task does not work because of a change in how Remote Assistance works in Vista and Server 2008.

In Windows XP and Server 2003, Remote Assistance was initated by using helpctr.exe.  In Vista and Server 2008, Remote Assistance is initated by using msra.exe.  helpctr.exe cannot be used to connect to Vista and Server 2008 computers.  msra.exe can be used to connect to XP, Server 2003, Vista and Server 2008 computers.  Also, msra.exe can only be executed on Vista and Server 2008 computers.

The Remote Assistance task in the Essentials computer space only uses helpctr.exe.  That said, you do not need to wait for a new management pack release to get this functionality.  Below are instructions on how to create your own task for Remote Assistance that will display in the Computer space and work with Vista and Server 2008.

In the Authoring space (the paper and pencil in the bottom of the wunderbar) expand Management Pack objects and right click on 'Tasks'.  Choose create a new task.  Choose Console Tasks\Command Line.  Click next. Name the task "Remote Assistance for Vista/Server 2008".  Chose a task target by clicking the Select... button and target "Windows Computer".  Chose next.  In the Application field, enter %SystemRoot%\system32\msra.exe.  In the parameters field, add:

/offerra $Target/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$ 

In the working directory, chose %SYSTEMROOT%\system32.  Uncheck the option to display output when the task is run.

Now from the Computers space, choosing a computer in a view such as All Computers, your task will appear in the available tasks lists next to the Remote Assistance task that uses helpctr.exe.  Note that this new Remote Assistance task will only work if you are using the Essentials console on a Vista or Server 2008 computer.

Posted by dustinj | 2 Comments

Want to receive emailed reports from Essentials?

Check out this blog post from Essentials MVP Bjorn Axell on how to use SQL Server Standard Edition or Enterprise Edition reporting services to scheduled Essentials reports to be delivered via subscriptions. 

http://advisec.wordpress.com/2008/08/13/would-you-like-to-be-able-to-schedule-reports-in-sce/

Posted by dustinj | 0 Comments

Moving from WSUS to System Center Essentials? Be sure to clean up your Group Policy settings!

If you used WSUS to keep your computers secure before upgrading to System Center Essentials, you probably used Group Policy to configure the Windows Update agent settings on the computers in your environment to connect to your WSUS server.  System Center Essentials, which includes WSUS technology, uses the same Group Policy settings to configure managed computers to connect to the Essentials server..  If you install Essentials, without removing these Windows Update settings from your existing Group Policies, you may notice this symptom in the Computer space of the Essentials console.

Computers will be listed, but their hardware inventory will be listed as unknown, and they will also show as 'Not yet contacted'.  This is because the Windows Update agent on that computer it not connecting to the Essentials server for updates and to submit inventory.

 

To correct this condition, check your Group Policy objects that are applicable to computers being managed by Essentials to see if the Windows Update are still configured configured (these settings are in 'Computer Configuration\Administrative Templates\Windows Components\Windows Update' in each GPO).  If you do find these, carefully consider whether they can be removed and if they are interfering with the same settings that are being applied by the the 'SCE Managed Computers (<essentials server name_MG>)' Group Policy Object.  This is the GPO that Essentials uses to configure the Windows Update agent on Essentials managed computers.  Once these settings are removed from other Group Policy objects, you should notice that your computers will start reporting inventory within a few hours (due to the Group Policy refresh interval of 2 hours plus a random 0-30 minutes).

Posted by dustinj | 1 Comments

Microsoft Updates and Windows Server Updates Services

System Center Essentials is built on top of Windows Server Updates Services (WSUS) technologies.  This allows Essentials to take advantage of the standardized Microsoft software updates technologies, content on Microsoft Update (MU), and deliver additional value by building on top of the WSUS platform.

However, it also means that System Center Essentials is sometimes affected by issues that affect WSUS and MU.  Over the last few weeks, two issues have been discovered that do affect Essentials.  Please read through the linked articles on this page to understand the issues and if you're affected.

Some Computer do not receive updates from the WSUS server

If you've deployed Office 2003 SP1 using Essentials, you may encounter this problem.

Consider the following situation. You use Microsoft Windows Server Update Services (WSUS) 3.0 to deploy software updates and hotfixes to computers that are in your organization. However, some computers do not receive updates from the WSUS server. This problem occurs if the computers have Microsoft Office 2003 or components of Office 2003 installed.

KB 954960 has been released  to address this issue and the WSUS team blogged about it here: http://blogs.technet.com/wsus/archive/2008/07/10/a-fix-for-client-server-synchronization-issues.aspx.

Millions of drivers, drivers for me...Millions of drivers, drivers for free..

If you've configured Essentials to synchronize driver content, you may not have noticed that many thousands of Realtek drivers were synchronized over the last week. Please see this article on the WSUS for the details http://blogs.technet.com/wsus/archive/2008/07/17/so-many-drivers.aspx.  Bottom line - the drivers are targetted at the right hardware, this is causing many, many instances of the driver to be distributed, and we're working on a long-term fix.

Posted by dustinj | 1 Comments

Essentials Team at TechEd US 2008!

We'll be at TechEd again this year with our demo packed sessions!  We'll also have a booth on the expo floor that you can drop by anytime to ask questions of the Essentials product team.

IT Conference MGT60-TLC Ask about Simplifying IT Management with Microsoft System Center Essentials
Session Day/Time: 6/11/2008 12:00PM-12:45PM
Room: Blue Theater 1
 
IT Conference MGT353 Supporting Your End-Users with Microsoft System Center Essentials 2007
Session Day/Time: 6/10/2008 3:00PM-4:15PM
Room: S310 E (ITPRO)

Check out our sessions and more at http://www.msteched.com!

Posted by dustinj | 0 Comments

Caching Microsoft Update content in System Center Essentials

A question came up in the Technet forums around content caching, and what variables exist to adjust it.   The footprint of cached content on the wSUS/SCE server take into consideration four variants:

  • Products (XP/2K3 as examples)
  • Classifications (Seciruty / Critical / Service packs)
  • Languages (EN, DE, JA, etc..)
  • Choosing to utilize Express files ( I will explain this one in more detail below)

SCE default configuration will bring in nearly 8GB of content; provided your needs stay within one language. 

...Now about Express files..

There are two ways that a package can install on your managed systems; Stand-alone, or Express.  For stand-alone, all the possible changes which can happen during that installation are contained in the package.  Let's say Foo.Dll is revising to 1.2, and Bar.Exe is revising to 1.3.  In this case, the old Foo.Dll and Bar.exe would be removed from the system, and the new ones applied.  This is the safest, and most common way patching happens.  However, it means that the entire package travels across the LAN/WAN when installation is necessary.

In the Express scenario, it may be that Workstation1 already had Foo.dll version 1.2, but not the latest version of Bar.dll.  It's neighbor, Workstation2 had just the opposite.  If the EXPRESS files were present, Workstation1 and 2 would ask the SCE/WSUS server for only the binary ranges it needed, and the acutal bytes which went across your LAN/WAN would be very close in footprint to the bytes which were needed to simply replace the specific files targeted. 

So, Express seems to be the winner here (almost).  In order to provide this optimization, the Update Services infrastructure needs to have fault tolerance.  Express packages will not work for 100% of the systems in need of patching.  Therefore, enabling express option means that the system will download the standalone version of an update as well as the Express version of that update.  Should it need to fall-back due to failure, the standalone version will be locally available.  Also, the express files are 2-4 times as large as the standalone packages. 

The tradeoff question is:  Should the optimization target ingress to the WSUS server at the cost of more LAN/WAN traffic, or the converse? 

Posted by TyofWA | 0 Comments

Determining which packages are "Needed" across your managed environment

Over the past six months, many within the System Center Essentials community provided feedback on the inability of SCE to show which updates and software are needed by managed systems.  Workarounds exist today for Microsoft Update content, but when it comes to locally-published content, or driver content obtained from a partner catalog the question remains unanswered. 

It is possible to call into the WSUS 3.0 APIs and obtain this information through the use of Powershell scripting using the steps below.

 

  1. Install PowerShell on your SCE server, or workstation running the SCE remote management console. 
  2. Copy the attached script, and save it as 'NeededContent.ps1'
  3. Launch the powershell console window 
  4. Sign the file, or set script execution to 'unrestricted' by running the following command:  Set-ExecutionPolicy UnRestricted  !! Note - It is important to understand the possible risks of running unsigned scripts.  More details at:  http://technet.microsoft.com/en-us/magazine/cc137728.aspx 
  5. Call the file from the powershell console window.  If it was located at d:\myscripts\ , the command would read:  PS > D:\myscripts\NeededContent.ps1

Additional notes -

  • You will need to execute the script in the context of a WSUS administrator, or WSUS reporter role. 
  • The script allows for the display of Microsoft Update content as well, but it will take considerably longer to execute due to the large volume of updates. 
  • The script will filter out packages which are declined.

Hope this helps! 
/Ty

 

Posted by TyofWA | 1 Comments
Attachment(s): NeededContent.ps1

System Center Essentials team at MMS 2008!

If you're attending the Microsoft Management Summit this week in Las Vegas, be sure to stop by the Essentials booth on expo floor, or catch us at one of the many sessions we are hosting this week.

 

SU32 Ask the Experts Panel
Wednesday, April 30 4:00 PM - 5:15 PM, Titian 2201B 
Speaker(s): Rod Trent
Track(s): Community
Session Type(s): Breakout
Products(s): Community, Configuration Manager 2007, Data Protection Manager, Essentials, Operations Manager 2007, Service Manager, SoftGrid / Application Virtualization, Virtual Machine Manager, Windows Client, Windows Server

This session continues to be one of the most popular at MMS each year, where you can ask a panel of industry experts your burning systems management questions. As in previous year’s, any and all questions are acceptable, as you try to stump the carefully crafted expert panel. Get help with your biggest technical issues back home or find out more about upcoming product releases. Rod Trent, owner of myITforum.com, the largest internet systems management community, will moderate the session.

SY17 Microsoft System Center Remote Operations Manager 2007: Deployment and Configuration
Wednesday, April 30 4:00 PM - 5:15 PM, Murano 3201A 
Speaker(s): Dustin Jones, John Joyner
Track(s): Systems Management
Session Type(s): Breakout
Products(s): Essentials, Remote Operations Manager

Learn how Microsoft partners can move from a break-fix to an annuity-based IT support business! Remote Operations Manager 2007 is a new platform which Microsoft partners can use in conjunction with System Center Essentials 2007 to provide proactive remote IT management for their small and midsize business customers. This session will also cover in detail the process of deploying and configuring this solution as well as using it to provide great deep remote IT management for Microsoft products.

SY18 Architectural Overview of System Center Essentials 2007
Tuesday, April 29 11:45 AM - 1:00 PM, Murano 3201A 
Speaker(s): David Mills
Track(s): Systems Management
Session Type(s): Breakout
Products(s): Essentials, Security, WSUS

Essentials 2007 is a new unified management solution designed for midsize businesses with 50-500 PCs. Get an overview of Essentials 2007 and understand how it enables IT professionals in midsize organizations to proactively manage their IT environment with increased efficiency. Essentials 2007 helps you keep your systems up-to-date with tools that accelerate problem resolution and enable automation of system updates and data collection.

SY19 Supporting Your End-Users with Microsoft System Center Essentials 2007
Tuesday, April 29 4:00 PM - 5:15 PM, Murano 3201A 
Speaker(s): Dustin Jones, David Mills
Track(s): Systems Management
Session Type(s): Breakout
Products(s): Essentials

In this session, you will learn how you can use System Center Essentials 2007 to more effectively support your end-users in a mid-size business (50-500 PCs)by deploying, monitoring and troubleshooting mission-critical applications, services and operating systems in your IT environment. We will walk through deployment of Office 2007 and demonstrate how to use Essentials 2007 to effectively manage business critical applications. We will then demonstrate Essentials 2007 desktop management capabilities which support the Windows Vista operating system.

SY20 System Center Essentials 2007: What's New in SP1?
Thursday, May 1 10:15 AM - 11:30 AM, Murano 3201A 
Speaker(s): Campbell Gunn, Dustin Jones
Track(s): Systems Management
Session Type(s): Breakout
Products(s): Essentials

Essentials 2007 is a new unified management solution designed for midsize businesses with 50-500 PCs. In this session you will get an overview of updates being delivered in SP1 to improve the installation and configuration process and provide compatibility with Windows Server 2008. We will also describe and demonstrate new features such as configuring workgroup-joined computers for management and managing Windows Server 2008.

YY20 Introduction to System Center Essentials 2007
Track(s): Systems Management
Session Type(s): Hands-On Lab
Products(s): Essentials, Windows Client, Windows Server

In this lab you will walk through the installation, configuration and use of System Center Essentials 2007. System Center Essentials is a systems management product designed for medium sized businesses and this lab will demonstrate some of the key capabilities of Essentials 2007 including managing computers, software and hardware inventory, software deployment, update management and monitoring
 

 

 http://www.mms-2008.com

Posted by dustinj | 0 Comments
More Posts Next page »
 
Page view tracker