
A popular question that seems to be floating on various blogs and message boards is related to why SCVMM integrates with Virtual Infrastructure by proxying requests through Virtual Center Web Service APIs as opposed to talking directly to ESX. There are several reasons for this and I'll go through them roughly in priority order to hopefully clarify some confusion.(
continue at source)

The normal procedure in System Center Operations Manager 2007 (SCOM) to remove agents, is to use the "Uninstall" task from the Agent-Managed Computer view in the Administration section of the Operations Console. This kicks off a decent MSI de-installation remotely and deletes any registry references and files on disk. If the machine is already decommissioned, you can use the "Delete" function from that same space, but due make sure that this agent will not be brought to live at any point in time (this will cause strange behavior). The internal grooming job will delete any references to this computer object from the Operational database, when it runs.
But what if anything goes wrong in this process? For instance; the Uninstall and/or Delete job seem to have worked fine and show a green end result, but looking at the Computers view in the Monitoring section, still shows the Computer but with a gray icon in front of it. You go back to the Agent-Managed Computers space, but cannot find the machine there, and the server itself does not have the agent installed anymore either.
(more)

Now that the Microsoft Deployment Toolkit 2008 is available, installing roles and features using the MDT integration in ConfigMgr2007 finally works, so you can enable all Windows Server 2008 roles and features, and you can even configure some of them know from the Task Sequence GUI. One caveat though is that when you want to install roles and features on a 64-bit windows installation it still doesn't work.
The reason for this is the fact that on 64-bit installations the task sequence process runs in 32 bit mode. Therefore WOW64 redirects system path references to \Windows\SysWOW64 instead \Windows\System32, and results to the problem that ServerManagerCmd.exe can't be found, because there is no copy of ServerManagerCmd.exe available in \SysWOW64.
This wasn't mentioned in the Open Issues and Work-Arounds in Microsoft Deployment Toolkit 2008 section of the MDT release notes which i looked at before starting my testing.
(more)

The Alert Forward Management Pack 3.0 by Ron Williams creates a console task that will allow you to forward the selected alert to an email recipient. To forward an alert, select the alert , and then click on "Forward Alert via Email" in the Actions pane of the Operations Manager console. If you are running the task from a console installed on a PC that also has Microsoft Office Outlook, then the task will open an email pre-populated with the information contained in the alert. If you do not have Outlook installed, then the email will be sent by SMTP.
Download the Alert Forward Management Pack 3.0

Given the recent support of Server 2008 with an OpsMgr 2007 agent.... (see
Announcing OpsMgr support for Windows Server 2008)
We need a good way to determine if all of our Server 2008 machines have the required hot-fixes.
We can do this by creating a Extended Class, and adding attributes to it from WMI queries. Sounds more complicated than it is. Let's get started:(
continue at source)

Roland Sanchez: In my particular part of the Microsoft organisation (the CTS testing lab), we install just about every OS, at every service pack level, on both major platforms. Because of this, I created a master template that is used to create dozens of task sequences where the only thing that changes is the OS. To pull this off, I made heavy use of the variables built into MDT2008 to branch my logic accordingly and create a framework in which future additions can simply get dropped into.(
continue at source)

A lot of people are curious to know what Microsoft's official support policy is regarding OpsMgr 2007 running on a virtual machine (VM) so Clive Eastwood, Senior Program Manager for Operations Manager, recently wrote up some guidance that should add a little clarity to the issue(
continue at source)

Emma Healey explains the new licensing rules and the exceptions granted under the new license terms for the System Center line of products from Microsoft(
continue at source)
Also available from Emma Healey:
Product Licensing High-Light - System Center Family Licensing

This hotfix contains fixes for issues that can occur, either after installation of Operations Manager 2007 SP1 or Essentials 2007 SP1 on Windows Server 2008, or after the operating system in-place upgrade from Windows Server 2003 to Windows Server 2008.
This hotfix should be applied to the following Operations Manager 2007 SP1 roles:
* RMS
* Management Server
* Gateway Server
* Web Console Server
* SCE Server
* Manually installed Agent (This hotfix should be applied directly to manually installed agents. Automatically deployed agents will appear in the Pending Management view to be approved for upgrade after installing this hotfix on the RMS/Management Server/Gateway server roles)
Microsoft System Center Operations Manager 2007 SP1 & System Center Essentials 2007 SP1 Windows Server 2008 Support Hotfix.

Microsoft has released several new management packs for Operations Manager 2007:
Windows Key Management Service for System Center OpsMgr 2007
The KMS MP monitors core Key Management Service offered by Windows Server 2008, Windows Server 2003 and Vista.
Exchange Server 2007 MP for SC Ops Mgr 2007
This management pack includes scripts and rules to effectively monitor Exchange 2007 and report on performance, availability, and reliability of its server roles.
Terminal Services MP for OpsMgr 2007
The Terminal Services Management Pack monitors the individual Terminal Services components on Windows Server 2000, 2003 and 2008.
Windows Server Operating System MP for OpsMgr 2007
The Windows Server Operating System Management Pack provides the fundamental monitoring basics for computers running the Windows 2000 Server, Windows Server 2003, and Windows Server 2008 Operating System.
Windows Server 2008 Application Server MP for OpsMgr 2007
The Windows Server 2008 Application Server Management Pack provides fundamental monitoring for the Application Server role of Windows Server 2008 Operating System.

Virtual Machine Manager (“VMM”) is a manager of Windows Virtual Machines (“VM”) and the Hosts (physical machines) on which the VMs reside. Depending on hardware configuration, a single Host can house several VMs. A large volume of the calls we receive at Microsoft are around installation and operation - the goal of this blog is to cover each.(
continue at source)

To simplify Application Virtualization Server management, the App-V team is excited to make available a RC version of our App-V 4.5 System Center Operations Manager 2007 Management Pack (OpsMgr 2007 MP). It has just been posted over on the Microsoft Connect site (
http://connect.microsoft.com). This OpsMgr 2007 MP only supports version 4.5 servers; it does not support previous SoftGrid server versions and MOM 2005.

The growing needs of today’s workforce demand that IT become more agile in how it provides access to desktop and device resources such as applications and corporate data. As a result, IT organizations struggle to provide the computing flexibility required by the modern workforce while balancing organizational requirements of compliance, security and reliability. System Center desktop solutions enable IT to empower users by streamlining the connection of any authorized user to the applications or resources they need—regardless of their location or connectivity. System Center achieves this by managing the delivery of traditional, virtual application, mobile, streamed and virtual desktop infrastructure, providing both secure access and the consistent, optimized performance that today’s users expect.
System Center Solution: Managing the Dynamic Desktop

J.C. Hornbeck: I get asked this every once in a while and since I couldn't find it mentioned anywhere I thought it might be a good idea to post it here. Under certain circumstances it may be necessary to install the OpsMgr 32-bit agent on a 64-bit operating system to monitor a 32-bit application. This is a supported configuration but the 32-bit agent must be installed manually and both the 32-bit and 64-bit OpsMgr agent cannot be installed simultaneously.
It may also be necessary to install the OpsMgr 32-bit agent on a supported 64-bit operating system for management pack monitoring of some 32-bit applications together with some 64-bit applications which do not support 64-bit agent monitoring via their management pack. One such application is System Center Configuration Manager 2007. See the System Center Configuration Manager 2007 management pack release notes for Operations Manager 2007.(
continue at source)

Rod Trent: As referenced in the
Overview of SMS/Intel SCS migration to SCCM SP1 blog post, Intel has developed a utility to easy the migration of vPro Client that have been activated on SMS/SCS to SCCM SP1.
The Production version of the Intel SCS to SCCM Migration Utility has been released and will be available for downloaded from the following location shortly:
http://softwarecommunity.intel.com/articles/eng/3898.htm
A User Guide on how to use the migration utility has been included in the download.

Jeff from the Configuration Manager Writers blog: Before beginning the upgrade process to Configuration Manager 2007 SP1, the Windows AIK 1.0 should be uninstalled from the SMS Provider computer for the site to allow SP1 Setup to install Windows AIK 1.1 to support SP1 OSD WIM images.
If the Windows AIK 1.0 is not uninstalled prior to beginning SP1 Setup, and a PXE service point is installed in the site running the Windows Deployment Services (WDS) Server service, the upgrade might fail and result in an unexpected restart and post-upgrade SMS Executive service crashes.
The following information has been added to the documentation libary for Configuration Manager 2007, but we won't be able to publish it to the Web until we refresh the documentation libary when Configuration Manager 2007 R2 is released. In the meantime, I'm making this post to give you the information that you need to successfully upgrade Configuration Manager 2007 sites to SP1 and troubleshoot an issue that you might encounter.(
continue at source)

This management pack provides several script-based monitors for shares, files and folders, offering something for most any scenario. The MP also includes custom object classes for discovered objects, and an impressive diagram view. The accompanying MP Guide is also quite detailed.
You can download the File System Management Pack for System Center Operations Manager 2007 at
http://www.systemcenterusergroup.com/files/folders/contest/entry121.aspx

With the Remote Maintenance Mode Scheduler you can schedule Powershell maintenance mode scripts for computers or groups of computers in OpsMgr 2007 (System Center Operations Manager 2007) through a simple graphical user interface, rather than using the task scheduler directly. The tool also supports scheduling of scripts on any remote computer with the OpsMgr UI components installed.
You can download the Remote Maintenance Mode Scheduler for System Center Operations Manager 2007 at
http://www.systemcenterusergroup.com/files/folders/contest/entry120.aspx

A key security feature of SCMDM is the ability to wipe a device remotely. Often time is of the essence, so it is important to know if a wipe was successful or not. Here we will discuss how remote wipe works and how to troubleshoot it. (
continue at source)

Steve Rachui: A common step in imaging is to use the 'Apply Network Settings' task sequence item to configure joining a system to the domain.
There are two options for supplying a username to use in the join - supply username in the Domain\User format or use a variable. In this task sequence step, the Domain\User option expects a domain name that is 15 characters or less - anything more will result in an error exclamation marker. Provided the total domain name is no more than 15 characters you can use either NetBios or FQDN names. With FQDN names longer than 15 characters it is still possible to configure this task sequence step but you must use a variable as shown above. When you choose to use a variable there must be a preceding step in the task sequence that sets the value of this variable. The screenshot below shows the task sequence order and then step where we set the value of our variable, domacct.

Rod Trent: We’ve dealt with AV exclusions for SMS and ConfigMgr for a long time, so having information about recommended exclusion practices for OpsMgr 2007 is definitely welcome.
While not officially documented, the OpsMgr teams recommends the following(
continue at source)

Steve Rachui: I've seen the question several times now about whether ConfigMgr supports setting OpsMgr agents into maintenance mode during software deployment. The answer is mixed.
Notice that the text says that setting this option in ConfigMgr will result in any alerts being suppressed for the duration of the program. When you set these options ConfigMgr WILL stop alert generation ON THE AGENT by simply pausing the health service. However, there is nothing done to suppress the alerts that may be seen from the various other components that may be interacting with the agent, such as the health service watcher. We are aware that there needs to be improvement in this area and are anticipating some changes in how this performs so that, when selected, all components will be placed in maintenance mode.

When people that are new to Microsoft System Center Configuration Manager 2007, start playing around with the product in a test lab, they often want to start with a simple OS deployment setup. But if you are new to the product and wants to deploy Windows XP, getting started could be a bit challenging. This article (not sure how many parts it will contain yetJ), will be a guide through the basic steps, that needs to be configured in order to successful deploy Microsoft Windows XP Professional with Service Pack 3 and Windows Vista Enterprise with Service Pack 1.
Ronni Pedersen published two articles already on how to set up Configuration Manager 2007. The first article details how to prepare Active Directory and how to configure Windows Server 2008 for hosting the Site Server role. The second article details how to install and configure the Microsoft SQL Server 2005, Windows Server Update Service (WSUS) and finally System Center Configuration Manager 2007. In the next article (not published yet) he will detail how to configure the Site Settings and install new site roles.
Introduction to Configuration Manager 2007 %u2013 Part 1
Introduction to Configuration Manager 2007 %u2013 Part 2

Jeff Gilbert: I'm updating the official documentation for this right now, but since there seems to be a lot of confusion about this process, I figured I'd post here as well. This way the information will be 'out there' before the next documentation update to the Web (planned for when Configuration Manager 2007 R2 RTM's).
First off, you can only do this with the Asset Intelligence feature included in Configuration Manager 2007 SP1 so if you are not running that stop reading and go upgrade your site!
Anyway, the quick intro to this is that by using the Asset Intelligence License Import Wizard included in ConfigMgr SP1, you can import both Microsoft and non-Microsoft software license information into the site database to help in inventorying the licensed software in use in your enterprise. You can then use Asset Intelligence reports to compare what you have versus what you paid for. Pretty handy. (
continue at source)

System Center Virtual User Group Weblog: Congratulations to our second category winner, for the Command-line or Web-based Tools category, Vicent de Vries, who submitted the SDK Connector Tool for System Center Operations Manager 2007.
You can download the SDK Connector Tool for System Center Operations Manager 2007 at
http://www.systemcenterusergroup.com/files/folders/contest/entry117.aspx

System Center Virtual User Group Weblog: Congratulations to our first category winner, for the SCCM Configuration Pack category, is Jason Scheffelmaer, who submitted an SCCM Roles Wizard. While not technically a Configuration Pack, his solutions goes far beyond being a simple script, and as such, Jason was declared the winner for this category.
You can download the SCCM Roles Wizard at
http://www.systemcenterusergroup.com/files/folders/contest/entry114.aspx

The work that needs to be done in the Configuration manager 2007 admin console is often spread out amongst different team members. Not all of these team members require access to the full admin console. Most environments do configure the permission set in a somewhat restrictive member so that team members only have the permission they need, but what is often forgotten is building a custom minimal admin console with just access to the features people need.
This shouldn't be done from a security point of view, the additional security this brings is neglectable, but more from a usability point of view. It makes the admin console easier to use, and avoids access denied errors, or empty detail panes because someone clicks on a heading in the admin console for which he doesn't have permission.(
continue at source)

Steve Rachui: Every OSD administrator knows the feeling of configuring a complex (or even simple) OSD Deployment, testing and releasing - only to have the deployment fail. At failure, OSD will begin a countdown to reboot and, on restart, the logs are often lost and we administrators are left wondering what went wrong. To find out we have to start the deployment again and spend time waiting for the failure. Wouldn't it be cool if we had a way to automate forcing OSD to collect logs when it fails before exiting? Good news! :)
I have spent some time recently working on just how to do that and we have two examples - both use the same approach but one is for generic task sequences (those sent through advertisements,etc) and the other is for OSD deployments. Lets start with the generic one, explain the needed steps and the show how we incorporate that into OSD.(
continue at source)

As you may of may not know, Virtual Machine Manager 2007 was only available as part of available as part of SMSE (System Center Server Management Suite Enterprise). Good news: Virtual Machine Manager 2008 will be available for purchase separately as well.
The System Center blog mentions: one thing that’s new with the release of VMM 2008, is that we’ll be making it available to customers and partners as a standalone product; VMM 2007 was only available as part of the SMSE. While the feedback from customers on the synergy of the products in the SMSE has been exciting over the last 8 months, we also wanted to offer customers the choice of VMM 2008 standalone as well, as we do with the other products in the System Center family including Configuration Manager 2007, Operations Manager 2007 and Data Protection Manager 2007. (
continue at source)

Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate
Issue
When the Configuration Manager 2007 operating system deployment feature is used to deploy a Vista SP1 image, a new boot configuration data (BCD) store is created using the BCD template. Configuration Manager 2007 explicitly creates the Boot Manger and Operating System objects from the BCD template, but allows the Resume object to be created implicitly by Windows Vista when it goes through mini-setup. Vista SP1 correctly generates the Resume object during mini-setup but the associated Resume settings objects are not generated. Because there are no Resume settings objects, hibernate functionality does not work.(
continue at source)

Satya Vel: If you are like me and just itching to try and install OpsMgr 2007 DB and Reporting on Longhorn and cannot wait till SQL 2008 to install SQL on Longhorn as they do not support SQL 2005 on Longhorn you can try my HACK!! Yes, this is NOT supported by the OpsMgr team and our test manager will probably kill me for posting this on the web but what the heck that why there are blogs. These steps are a culmination of things Stephanie and Melissa on our test team and I have tried to get it to work. So here it goes…(
continue at source)

The Service Level Dashboard for Operations Manager 2007 is a new Solution Accelerator that addresses IT Service Managers’ need for near real time, end-to-end reporting of the performance and availability of their line-of-business (LOB) applications. The accelerator provides a unique view of a business application from the user’s point of view by simulating user interactions with the business application and reporting on the experience. A small number of agents are deployed in the enterprise network to provide an accurate sampling of all the different conditions under which the business application operates. The data is then collected and interpreted.
Results are displayed in a single Web-based user interface, providing both top-level and drill-down views. The top level view reports the Service Level Agreement (SLA) status (compliant or non-compliant) of every application being monitored. The detailed views reveal component-level information that can help administrators investigate the possible causes of noncompliance reported at the top level.
You can read more
here and you can also watch a video overview
here.
Download Service Level Dashboard Management Pack for System Center Operations Manager 2007

Have you ever wanted to create email notifications for Alerts based on Alert Descriptions? This cannot be done using the E-mail Notification Channel and Subscriptions settings.
This can be done however with the use of the Notification Command Channel with uses a vbscript that sends an email based on the information in the Alert Description. All the logic and sending of the emails is done by a script.(
continue at source)

An important aspect of virtualization is the actual management: as an administrator, you want to have a single console for managing all your virtual machines and hosts. With software such as VMware’s VirtualCenter, you can manage a complete ESX environment and add a ton of extra features (such as DRS, HA, intelligent placement, templates, etc). Microsoft’s answer to the management question is System Center Virtual Machine Manager (also known as VMM).
This piece of software is your one-stop shop to all your Virtual Server 2005 R2 (and in the 2008 release) Hyper-V hosts and even your VI3 infrastructure. VMware’s VirtualCenter can be added and so ESX hosts can be managed from within VMM. Virtual Machine Manager 2008 provides most VirtualCenter Server functionality including VMotion. More complex tasks such as adding hosts to an ESX cluster must be done using VirtualCenter itself.
It is also tightly integrated with other System Center products (such as integration with System Center Operations Manager 2007) and PowerShell. A very interesting feature is Performance and Resource Optimization (or PRO). PRO is a feature of VMM which can dynamically respond to failure scenarios or poorly configured components that are identified in hardware, operating systems or applications. VMM 2008 also integrates with the new clustering support in Windows Server 2008 to allow for fault-tolerant and cluster aware virtual machines to be created. It leverages the much talked about Quick Migration technique.
In this article, we will install and explore the basics of System Center Virtual Machine Manager 2008. (
continue at source)

Kristian F. Thomsen: When ConfigMgr is configured in Mixed mode and client computers are re-imaged/re-installed; by default a new ConfigMgr computer object is created and the “old” computer object will become “Obsolete”. Well, this is by design, but it might become a problem. If the client has many direct collection memberships, these direct memberships will not be preserved when a new computer object is created. Therefore, these have to be re-created.
When ConfigMgr is configured in “Native Mode”, the client identity is automatically migrated since we are using certificates.
Well, with ConfigMgr, this problem can be handled. However, it is a manually process. In the “Site properties” dialog, on the “Advanced” tab, there is a section called “Conflicting records”. From here it can be configured how ConfigMgr should handle conflicting records. That is, clients with duplicate hardware Id’s.(
continue at source)

This management pack monitors ISA Server 2006 and includes monitors and rules to track the performance, availability, and reliability of ISA Server 2006 components. With detailed alert information, you can quickly identify and troubleshoot ISA Server 2006 issues, minimizing time-to-resolution when problems occur. You can collect and analyze performance trends and metrics, and obtain performance information that allows you to manage bottlenecks, identify capacity requirements, and proactively manage your ISA 2006 deployment to resolve issues before problems occur.
Download Microsoft Internet Security and Acceleration Server 2006 Management Pack for OpsMgr 2007

Describes how the Microsoft System Center Operations Manager 2007 (OpsMgr 2007) was implemented to improve Microsoft IT's infrastructure management service offerings. OpsMgr 2007 provides a centralized monitoring infrastructure with increased reliability and granular rights delegation. By implementing OpsMgr 2007, Microsoft IT improved operational efficiency and reduced the cost of IT lifecycle investments.
Download Implementing System Center Operations Manager 2007 at Microsoft

The Release Candidate of ConfigMgr 2007 R2 has been posted to the Microsoft Connect site today.
BTW: R2 requires a ConfigMgr 2007 environment already running on SP1.
What does R2 add to ConfigMgr 2007? Here’s some new features:
# Application Virtualization management support
# Forefront Client Security Integration
# SQL Reporting Services Reporting - Allows you to report on Configuration Manager activity using SQL Reporting Services
# Client Status Reporting - Provides a set of tools and Configuration Manager 2007 reports to assess the status of client computers, sometimes referred to as "client health." Clients that show a change in activity patterns might need administrative intervention.
# Operating System Deployment Enhancements
* Unknown computer support
In Configuration Manager 2007 R2, you can deploy operating systems to computers using a PXE service point without first adding the computer to the Configuration Manager database.
* Multicast deployment
Previously, all operating system deployments used unicast. Multicast can make more efficient use of network bandwidth when deploying large images to several computers at the same time.
* Running command lines in task sequences with credentials other than the local system account.
(
continue at source)

Richard Smith: I get quite a few emails from people asking if there is a help file that details all of the scripts that are supplied with Microsoft Deployment Toolkit (MDT). The scripts form the engine of a deployment and can also help you to develop a framework for scripts that you need to create for your own tasks. The MDT documentation (installed in \Program Files\Microsoft Deployment Toolkit\Documentation) is a good place to start - but I also point people to the online MDT Reference - which lists the following information for each script supplied:
* Name. Specifies the name of the script.
* Description. Provides a description of the purpose of the script and any pertinent information regarding script customisation.
* Input. Indicates the files used for input to the script.
* Output. Indicates the files created or modified by the script.
* References. Indicates other scripts or configuration files that are referenced by the script.
* Location. Indicates the folder where the script can be found. In the information for the location, the following variables are used:
o program_files. This variable points to the location of the Program Files folder on the computer where Microsoft Deployment is installed.
o distribution. This variable points to the location of the Distribution folder for the deployment point.
o platform. This variable is a placeholder for the operating system platform (x86 or x64).
* Use. Provides the command line and options that can be specified.
* Arguments and description. Indicate the valid arguments to be specified for the script and a brief description of what each argument means.
* Properties. The properties referenced by the script.
You will find each MDT script breakdown at
http://technet.microsoft.com/en-us/library/bb979605(TechNet.10).aspx

Diane Prescott, Product Manager, System Center: Hello – I wanted to provide a quick update on some changes we have coming regarding the System Center Server Management Suite Enterprise (SMSE) and System Center Virtual Machine Manager (VMM) later this year. In Q4 of 2008, we’re excited to be providing customers with additional value and functionality in the SMSE by releasing the next version of our VMM software, VMM 2008. One thing that’s new with the release of VMM 2008, is that we’ll be making it available to customers and partners as a standalone product; VMM 2007 was only available as part of the SMSE. While the feedback from customers on the synergy of the products in the SMSE has been exciting over the last 8 months, we also wanted to offer customers the choice of VMM 2008 standalone as well, as we do with the other products in the System Center family including Configuration Manager 2007, Operations Manager 2007 and Data Protection Manager 2007.
As far as how we’ll offer VMM 2008 standalone in Q4 of 2008, it will follow the licensing model set forward by the SMSE. It will be sold as a per-device enterprise server management license (ML) and will include rights to the management server. Because we’ll be selling the VMM 2008 enterprise server ML on a per-device basis, which makes sense in the context of virtualization, we’ll be targeting a price which will be approximately 10-15% less than the SMSE at that time it’s generally available. Additionally, because of the new value and functionality being added to the various System Center offerings over the next year, including VMM, Operations Manager and Configuration Manager, we will be implementing a price increase to the SMSE of approximately 10-15% in the same time frame. We’re still working on the specifics regarding the pricing and licensing of VMM 2008 and the SMSE and we’ll have further details to share in early August.(
continue at source)

Richard Trusson: In this post I am going to talk about a BitLocker solution that myself, Richard Smith and others from Avanade/Accenture - Chris Bird, Jonathan Goulding, Chris Urwin and Steven Westwell - put together for a customer. I should point out that enabling and applying BitLocker via OSD on SMS 2003 SP3 is not supported. So think carefully before implementing this in your environment.(
continue at source)

Have you ever wanted to pause the task sequence in MDT 2008 or ConfigMgr 2007 for a few seconds while something catches up...? I had a requirement to do this recently where I ran a
task to close and cancel the Windows Sidebar at the start of the State Restore phase of the task sequencer and then turn the Windows Sidebar back on again at the end of the State Restore phase - I was doing this as the Windows Sidebar can sometimes get in the way of some customisation scripts and you can also see peculiar VB messages when 2007 Office System updates are applied. When the Windows Sidebar is turned back on, there is a couple of seconds before the Sidebar actually appears - yet my task for turning on the Sidebar had returned and the task sequence had moved on...it made be think that there may be other situations where a slight delay in returning to the task sequence may be useful - sure you could add sleep commands to the scripts that your running as commands - but that doesn't help with the tasks that are not scripted - so here is an MDT based script that will pause the task sequence for a specified number of seconds (specified on the command line)
(
continue at source)

SBS 2008 and EBS 2008, previously known by their respective codenames of Cougar and Centro, are important because they are based on the all new server technologies that include Windows Server 2008 and Exchange Server 2007. Additionally, both products use System Center Essentials as a primary management platform and require 64-bit CPUs. SBS 2008 is a single-server solution for up to 75 desktops, with an optional second SQL server, which can run a 32-bit OS.
System Center Essentials 2007 SP1 is installed automatically on the first server that is built, the Management Server. The Essentials EBS instance is modified from a default Essentials by adding management packs for Exchange 2007, Forefront Server Security (for Exchange 2007), and Forefront TMG (former codename ISA Server Nitrogen). There is also an EBS management pack that we’ll take a closer look at in a moment. Essentials agents are automatically deployed to the Security and Messaging servers, and the Essentials product features are pre-configured during the EBS install. (
continue at source)

"What You Write Is Not Necessarily What You Get"
Abstract
OpsMgr 2007 has a fairly substantial library of discovery module types and monitor types that ship with it. Even with that library, it seems that the single most important extensibility point in OpsMgr today is the ability to use custom scripts to perform discovery and monitoring tasks. As I've developed scripts for OpsMgr, I have learned a great deal about how OpsMgr processes scripts. This article describes some important concepts regarding how scripts are processed by OpsMgr. (
continue at source)

Susana Guedes: There are different methods you can use to deploy an operating system image using Configuration Manager 2007 [2]:
* PXE Initiated Operating System Deployments
* Bootable Media Initiated Operating System Deployments
* Stand-alone Media Initiated Operating System Deployments
* Side by Side Operating System Deployments
* Configuration Manager 2007 Initiated Operating System Deployments
In this post I will talk about PXE Initiated Operating System Deployments. (
continue at source)

Version 2.0 of the Multi-Host Ping Management Pack is now available for download
HERE. The completely rewritten MP includes:
* Updated monitoring logic and a fully parameterized Multi-host Ping Rule with 6 overridable parameters that allows the user to specify a number of options, including a comma-separated list of IP addresses, NetBIOS and FQDN host names to be tested for ICMP echo (Ping) connectivity.
* Six overridable parameters are now exposed individually, much like in MS and commercial MPs .
* The ability to generate custom performance data allowing ping reponse time (in ms) to be automatically displayed in the included performance view.
(
continue at source)

The Microsoft Deployment Toolkit (MTD) Wizard Editor is a simple .NET application designed to assist with the process of editing the wizard XML manifest files used by the Microsoft Deployment Toolkit. While it does not presently help much with the authoring of each wizard pane's content, it does simplify the more tedious parts of editing the XML manifest and the HTML embedded within each wizard pane.
Features available in the current release:
- Editing. The Wizard Editor can open an wizard, add and remove panes, change and preview a pane's HTML, and change a pane's settings.
- Testing. The Wizard Editor can execute a wizard, simulating the environment in which it would normally be used.
http://www.codeplex.com/MDTWizardEditor

If you are using Microsoft Internet Security and Acceleration (ISA) Server with the Internet-based client management feature of Microsoft System Center Configuration Manager 2007, configuring SSL to SSL bridging provides a high level of security for Internet traffic. In this scenario, connections from Configuration Manager Internet-based clients are authenticated and terminated at the ISA Server, inspected, and then new SSL connections are made to the Configuration Manager Internet-based site system servers.
The alternative configuration for SSL-to-SSL bridging is to use SSL tunneling with ISA server publishing, which is a less secure option because the SSL traffic from the Internet clients is forwarded to the Configuration Manager Internet-based site system servers without termination, so it cannot be pre-authenticated or inspected for malicious content. (
continue)

Kenny Buntinx: Got this one from Brett Flag - OSD team Microsoft :
SCCM defines a driver as an INF file plus its associated content. When a driver is first imported we do a check to see if the exact same driver (e.g. same INF file and content) has already been imported at the site and prevent it from being imported. However, if there are any differences then the metadata is read from the INF file (including name, manufacturer, supported operating systems, etc.) and a new driver object is created.
It is not uncommon for hardware vendors to package different INF files for each operating system they support in the same directory. When this happens, SCCM will create a driver object for each INF file but it is smart enough to only keep a single copy of the content. Since the default name of a driver comes from the supported hardware list in the INF file, each of these driver objects will likely get the same default name even though they support different operating systems (to see if this is the case, check out “Applicability” tab on the Driver’s preview pane).(
continue at source)

Wes Miller: Over the next few months I'm planning to cover Windows Deployment Services (WDS), which is available for Windows Server 2003 and is built into Windows Server 2008. WDS can be a very important component in your deployment infra-structure, so I want to make sure you have a good foundation for the discussion.
This first column will drill into the architecture of the Pre-boot eXecution Environment (PXE; pronounced pixie), the history of Remote Installation Services (RIS), as well as other PXE-related technologies used at Microsoft.(
continue at source)

**We're looking for beta testers for the Dell Deployment Toolkit for ConfigMgr. If you're interested in testing this (and giving us some valuable feedback), send me an email (greg_ramsey@dell.com).
With this free toolkit, you'll be able to leverage Dell-specific task sequences within the ConfigMgr Task Sequence Editor to configure Array Controllers, BIOS, and more! Read more about the DTK.
"The integration of Microsoft® System Center Configuration Manager 2007 and the Dell OpenManage™ Deployment Toolkit helps simplify this process by providing easy-to-use graphical tools for the deployment of Dell™ PowerEdge™ servers."(
continue at source)

System Center Operations Manager 2007 (OpsMgr) has given administrators access to Windows PowerShell, a powerful new scripting language for automating tasks. Released to the public in November 2006, it has been downloaded more than two million times since then.
Marco Shaw: In this article, I am going to talk about Windows PowerShell® and discuss how it applies to Operations Manager. I'll cover some of the common tasks that Windows PowerShell can help you accomplish in a far easier and more automated manner, and refer you to some Web sites that provide useful scripts and explanations. I've gathered insights and blog posts from many of the experts using Windows PowerShell today.
Although Microsoft has started releasing the Community Technology Preview (CTP) versions of Windows PowerShell 2.0, these versions are not production-ready, have not been tested with OpsMgr, and should not be installed on a production system.(
continue at source)

Cliff Hobbs: The ConfigMgr Doc Team write some great content and plenty of it. But I have a SERIOUS problem with the way Microsoft organise content on their site.
For starters they are STILL suffering the issue whereby they have some content in the Product Pages and other/ different content in the TechNet side of the house (for example I’m currently speaking to Microsoft about why the SMS 2003 SP3 content is different and not up-to-date on the Product Page Vs TechNet, when the Product Pages to me is the obvious place people will look first).
Then there’s the whole Documentation Library search facility. It’s good that you can limit your search to just TechNet, Microsoft.com or Live search. However, to me this isn’t granular enough. When I search TechNet I want the ability to be able to search JUST parts of TechNet such as the Doc Library and NOT have results returned for forum threads and other places on TechNet.
Speaking to Jeff Gilbert from the Doc Team he sent me the information below (thanks Jeff), which some of you might found useful.(
continue at source)

Kenny Buntinx: This post and subsequent posts will be a step by step on how to build a base XP SP3 image in SCCM. I will be outlining not necessarily pointing out every click. Hopefully others will find this helpful. This assumes an understanding of SCCM and uses what is refereed to as a “Thin Image Strategy”.(
continue at source)

Ronni Pedersen: Living in a non-english speaking country like Denmark, I often have to deal with deploying English versions of Windows XP and/or Windows Vista, with other Regional Settings, Keyboard Settings, Time Zones etc.
In the past I've created a VBScript to modify the sysprep.inf or the unattend.xml, after laying down the image on the client. The values were configured with Collection Variables or Computer Variables. The script collected the value during deployment, and replaced the value in the sysprep.inf or unattend.xml file before restarting into mini setup. (
continue at source)

The Offline Virtual Machine Servicing Tool helps organizations maintain virtual machines that are stored offline in a Microsoft® System Center Virtual Machine Manager library. While stored, virtual machines do not receive operating system updates. The tool provides a way to keep offline virtual machines up-to-date so that bringing a virtual machine online does not introduce vulnerabilities into the organization’s IT infrastructure.
The Offline Virtual Machine Servicing Tool helps organizations maintain virtual machines that are stored offline in a Microsoft® System Center Virtual Machine Manager library. While stored, virtual machines do not receive operating system updates. The tool provides a way to keep offline virtual machines up-to-date so that bringing a virtual machine online does not introduce vulnerabilities into the organization’s IT infrastructure.
Download Offline Virtual Machine Servicing Tool

With Microsoft® Office Visio® 2007 Professional the user now has the ability to connect data to diagrams and use data graphics to make the visualization more meaningful and impactful. The Microsoft® System Center Operations Manager 2007 and Microsoft® System Center Configuration Manager 2007 solution for Office Visio 2007 Pro helps you visualize your key reports. Using the solutions framework which utilizes an easy to configure web server component provided for your environment you can now easily connect data from OpsManager and ConfigManager in Visio 2007 Pro.
Download the Visio add in and the web server component to connect and generate datasets to connect to your existing diagrams or auto generate your diagrams for your infrastructure monitoring needs. See your data from OpsManager and ConfigManager live in Visio diagrams today by downloading this valuable Visio Add-in free.
Download Microsoft Office Visio 2007 Pro SCOM & SCCM Add-In's

Microsoft System Center Mobile Device Manager 2008 Management Pack for Operations Manager 2007 provides proactive monitoring of your Microsoft System Center Mobile Device Manager 2008 environment. This management pack includes:
* Detection and monitoring of all MDM servers and dependent services
* The alert-driven state
* Performance and backlog monitoring and configuration
Before you install the MDM management pack, read the MDM Management Pack Guide document. The guide includes instructions that you need to correctly deploy, configure and use the management pack
Download Microsoft System Center Mobile Device Manager 2008 Management Pack for SC Operations Manager 2007

A number of customers have been having problems deploying the native mode certificates with Active Directory Certificate Services in Windows Server 2008, not least because the Web enrollment pages no longer allow you to request a certificate for the local computer store. The same issue applies if you’ve installed KB 922706 on a Windows Server 2003 CA, in order to update the Web enrollment pages for Windows Vista clients and Windows Server 2008 clients.
I’ve also recently heard from the forums that the new Windows Server 2008 v3 certificate templates seem to cause problems with native mode, and I’ve reproduced this myself. For example, if you deploy a site server signing certificate with a v3 template, the validation for the certificate succeeds on the Site Mode tab, but SMS_POLICY_PROVIDER returns error status message 5115 when it tries to sign the policies instead of the success status message 5116. I also haven’t had any success with v3 templates for site systems running on Windows Server 2008, or clients running Vista or Windows Server 2008.(
continue at source)

Stefan Schörling: If you are running application installs within your Task Sequence and you are running SP1 of Configuration Manager you will bump into a 90 second delay between every application. So if you have 200 applications in your task sequence the deployment will take allot of time. Microsoft is currently working on a fix for this until then you can get around it by using the RTM Client instead of the SP1 client binaries in your Apply Client - Task Sequence Step. (
continue at source)

Kerrie Meyler: When you first install Operations Manager 2007, you may be a bit overwhelmed with all the information that is available to you (if you could figure out what it is and how to find it!), and the fact that you have to forget most of the things you learned if you had MOM 2005. However, there is training available, several books are out - I may be a bit biased, but System Center Operations Manager 2007 Unleashed is the best one available, and there are also numerous utilities and software available for OpsMgr 2007, some of which is at no charge. (
continue at source)