System Center Configuration Manager 2007 Operating System Deployment has the ability to migrate the time zone from the source operating system to the destination operating system. This is done by using the Migrate time zone option in the Capture Windows Settings step of the task sequence.
Unfortunately, MDT Lite Touch Deployment does not offer the same functionality. So I created a User Exit script (GetCurrentTimeZoneExit.vbs) to query the source OS time zone and set the MDT time zone variable(s).
The Deployment Guys : Setting MDT Time Zone Variables from the Source OS Time Zone
After 13 years of consulting, I joined the UA team in Redmond last August as a technical writer focusing on management pack authoring. My initial focus is a new version of the Management Pack Authoring Guide which will provide background concepts, processes, and specific walkthrough examples on creating management packs for Operations Manager 2007.
BWren's Management Space : Management Pack Authoring Guide v2
We are excited to announce that two important new server management capabilities will be available through purchasing Server Management Suite Enterprise (SMSE) and Server Management Suite Datacenter (SMSD) licenses.
- System Center Service Manager will be a new component of SMSE & SMSD when it is released in the first half of calendar 2010. Service Manager will allow you to improve datacenter service availability and performance by integrating incident and problem management with operational tools—all aimed at simplifying your processes, reducing downtime, and improving the reliability of your datacenter environment. When Service Manager becomes generally available, customers licensed for the SMSE or SMSD will receive the Service Manager Server ML as part of their active Software Assurance coverage.
- Opalis was acquired by Microsoft in December 2009 and Opalis software will be granted to any new or existing SMSE or SMSD license with active Software Assurance coverage as of December 10, 2009. Opalis delivers IT process automation capabilities, including task orchestration across systems, standardization of processes, automation of repetitive tasks, and integrates with System Center and many third-party tools.
Nexus SC: The System Center Team Blog : Server Management Suites: New Capabilities and Price Change
Today we are announcing the opening of the Technology Adoption Program nominations for the next release of System Center Configuration Manager.
The Technology Adoption Program is designed to provide a consistent experience for Microsoft customers to obtain real-world customer feedback on Microsoft pre-release products.
Nexus SC: The System Center Team Blog : The Next wave of Client Management begins now……
As you may or may not know, we’re running a poll to show community thoughts about Microsoft moving the OpsMgr 2007 Management Pack catalog to their new PinPoint technology. As we noted before, the thoughts have been mixed, and our poll so far is reflecting that.
Here’s a quick sampling so far:
|What do you think of the new OpsMgr 2007 Management Pack catalog on PinPoint? (feel free to leave comments)
|Love it! Great move Microsoft!
|Could be useful. I'll wait and see how it works out.
|What the–?? Who did this?
|I hate it! Put it back!
And, the number one comments is:
Sorting by release date is not available anymore which is a big pain. And the categories filter is not that intuitive.
So, while the poll numbers suggest that this wasn’t a great move in the minds of those who relied on the old catalog, I think it also suggests (through the comments) that Microsoft could provide some immediate improvement just by adding a sorting mechanism by release date.
Do you feel the same? Drop out and participate in the poll:
Here's a unique issue I came across the other day that I thought you might like hearing about. In this case, we were unable to connect to a ConfigMgr 2007 Secondary Site server from Tools => Service Manager unless we were using a domain admin account.
The Configuration Manager Support Team Blog : Solution: Unable to connect to a ConfigMgr 2007 Secondary Site server from Tools => Service Manager unless you use a domain admin account
I spent awhile trying to get my ConfigMgr environment to collect HBA WWNs and with help from my co-worker Jason Sandys, a great doc he referred me to (Discovering Fibre Channel Topology through WMI) and various other sources I finally got it working. Here’s the process. As always, follow these steps at your own risk.
Extend System Center Configuration Manager 2007 to Collect Fibre Channel HBA Information » Ross’ Cogitations
Microsoft released a new version of ACT, version 5.5. This version changed the database schema which prevents configuring the ACT database from the ACT Connector administrator console. If you upgrade an existing ACT installation to 5.5 which has already been configured in the ACT connector, no additional steps are required.
Using this documented workaround ACT 5.5 is supported by Microsoft with the System Center Configuration Manager 2007 ACT Connector.
The Configuration Manager Support Team Blog : Support for ACT 5.5 with the ACT Connector
Do you use the Windows Server Print Server role in your environment? Are you using the either of the print server management packs for OpsMgr 2007? Do you use the print management console? If you answered yes to any of these questions then we would greatly appreciate your input to help form the future manageability plans for the print server role. Head over to the OpsMgr public Connect site and fill out the "Print Server Management Survey".
System Center Operations Manager : The Windows Server Print Server role team is looking for your input
So you have a solid understanding of Service Manager 2010 Beta 2, installed the necessary components into your virtual lab, and have also installed the Service Manager DW to get the full breadth of the product.
In this posting we’ll cover the final component: Register with Service Manager DW.
vNext: Service Manager 2010 – DW Registration « System Center Spartan