SMS&MOM

ConfigMgr 2007: OSD Task Sequence Fails with "Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed"

Ever tried to do an OSD with System Center Configuration Manager 2007 and have it fail "Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed?"  If so then check out this tip from Frank Rojas on why this may happen and how you can fix it:

========

Issue:  When trying to perform an OSD Task Sequence using SCCM 2007, the deployment fails, usually after it has successfully formatted the drive, dropped the image on the PC, and scanned for drivers.

Looking at the SMSTS.log, the following error is logged:

Task sequence cannot continue after reboot because TS Manager is not configured to auto-start or GINA is not installed    TSManager
CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\engine.cxx,274)    TSManager
Fatal error is returned in check for reboot request of the action (Restart Computer).
Unspecified error (Error: 80004005; Source: Windows    TSManager
An error (0x80004005) is encountered in execution of the task sequence    TSManager

Cause:  This issue is caused because the "Setup windows and ConfigMgr" task has either been removed, disabled, or has been moved to the wrong place in the Task Sequence.

The "Setup windows and ConfigMgr" task performs several tasks that prepares the PC from going from WinPE to the Windows Setup, including modifying boot managers to boot to the correct partition. Once it finishes preparing the PC, this task then reboots the PC at the proper time to start Windows Setup or Mini-Setup. If this task is removed, it will cause the deployment to fail because the PC was not properly prepared.

Resolution: For these reasons, the "Setup windows and ConfigMgr" task should never be removed, disabled, or moved to another place other than the default in the Task Sequence. Moving it to another place in the Task Sequence may cause the PC not to be prepared or rebooted at the correct time, causing the deployment to fail.

The "Setup windows and ConfigMgr" task should also not be marked as Continue on Error because if this task does error out, the deployment will probably fail anyway.

Keywords: sccm2007 Operating System Deployment

========

Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: SMSTS error "Hash could not be matched for the downloaded content"

Here's an issue I hadn't seen before that was sent to me by Clifton Hughes, one of our top System Center Configuration Manager 2007 engineers at our Las Colinas site in Irving, Texas.  If you do any work with packages that contain localized file names then you'll want to be aware of this:

========

Issue: When deploying a software package in SCCM 2007 via a Task Sequence, and that package contains files with names containing extended ASCII characters, the Task Sequence may fail with an error code 80004005.  An example would be something like the Spanish word año where there's a tilde over the 'n.'

The following is an example excerpt from my SMSTS.LOG for a file name that includes extended ASCII characters:
Downloaded file from _http://smtp.contoso.com:80/SMS_DP_SMSPKGD$/CON00016/Speedup/Translations/Espa%C3%B1ol.txt to C:\_SMSTaskSequence\Packages\CON00016\Speedup/Translations/Español.txt

Note how the file is being renamed to Español.txt instead of the proper name espanol.txt with the tilde above the a.

The Task Sequence will fail with an Unspecified error 80004005 and the following error will also appear in the SMSTS.LOG:

Task sequence execution failed with error code 80004005

Cause:  These types of extended characters in the file names are not downloaded/named correctly and the file names will get created differently than the original files names, causing the hash mismatch error. This is a known issue in SCCM2007 and an update will be provided once it becomes available.

Resolution: For now, the workaround is to remove any files that have extended characters in their names from the package source and redistribute the package with out these files.

This problem can and will occur with a standalone Software Package if it is deployed using a Task Sequence, of if you are deploying the package as part of an Operating System Deployment via a Task Sequence. It does not seem to affect normal Software Package deployment as long as a Task Sequence is not used.

========

Thanks Clifton!

J.C. Hornbeck | Manageability Knowledge Engineer

OpsMgr 2007: Group disappears from groups list if used in Distributed Application

Here's another tip from Milan Jajal, this time on Operations Manager 2007:

========

Issue: Custom groups used in a Distributed Application may disappeared from the Groups list in the Authoring pane.

Note: Even though the custom group disappeared from the Groups list, if you do scoping on rules or monitors list, the group is listed if you select view all targets. That means the group is not getting deleted.  It's actually still present in the database but its disappearing from the Groups List view.

This applies to System Center Operations Manager 2007 RTM or Service Pack 1 (SP1).

Cause: This is a known issue. Microsoft is aware of the issue and working on a solution.  If you include any top level group (custom or built-in) in a distributed application then it may disappear from the Groups List.

Resolution: There are 2 possible workarounds for this issue:

1. Do not use Groups in Distributed Applications.

Since it is understood that this may not be a good option in many cases, the second workaround can also be used:

2. Use child groups (sub groups) in Distributed Applications. To do this, create a new Parent Group and a new Child group in that parent group. (In the properties of parent group, you should specify the subgroups to add the child group).  Then use that child group in Distributed Application.  Alternatively, you can also create a new Parent group and add the group which you have used in the Distributed Application under subgroups so it becomes child group.

========

Thanks Milan!

J.C. Hornbeck | Manageability Knowledge Engineer

OpsMgr 2007: Performance Reporting scale values may not plot as expected

We get a call on this every now and then so if you're not seeing what you expect to see with any of the performance reports in System Center Operations Manager 2007 then this may be what you're running into.  It's not that the data is incorrect, just that the scale values may not be what you're expecting. 

To give you an example, let's say we want to view a performance report for the time period from 1:00am to 4:00am.  When you view this report it may appear that the report does not show the correct times for the range we specified.  Based on our report, we would expect the report to plot our data using a starting value of 1:00am and an ending value of 4:00am, but when you view the report it's actually marked as 1:00am to 3:00am.  This gives the impression that we haven’t collected the data for the last one hour:

So what's going on?  The reason we see this is due to the timestamp of the aggregated data.  When you run a report for 1:00am to 4:00am this is actually 3 aggregation periods as shown below:

• 1:00am to 2:00am
• 2:00am to 3:00am
• 3:00am to 4:00am

Each of these periods would be time stamped in the DW as follows:

• 1:00am to 2:00am : Timestamp 1:00am
• 2:00am to 3:00am : Timestamp 2:00am
• 3:00am to 4:00am : Timestamp 3:00am

Because of that, this is what is plotted on the graph:

So the bottom line here is that while the graph isn't necessarily plotting what you might expect, it's working the way it is supposed to.

Hopefully this sheds a little light on why you're seeing what you're seeing, and you can rest assured that the report is not broken but instead is working exactly the way it was designed to work.

J.C. Hornbeck | Manageability Knowledge Engineer

MOM 2005: Event Error 25117 on MOM server if using DPM 2007 MP

We've been kind of ConfigMgr/SMS heavy lately so I thought maybe we'd do a couple posts on MOM/OpsMgr to try to even things out a little.  Today is a troubleshooting tip for MOM 2005 from Milan Jajal:

========

Issue: After importing the Data Protection Manager 2007 Management Pack for MOM 2005, you may not getlerted on DPM server problems and instead see errors relating to the DPM MP.  In the Application event log of MOM Server where DPM servers point as Management Servers, you will get below event:

Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: MOM Server
Event ID: 25117
Description: The following error details were returned during duplicate alert checking or insertion for Alert 'DPM Alert 3159: Recovery point creation failures'.
Details: Invalid Component 'Backup' in Rule 'DPM Alert 3159: Recovery point creation failures'
Verify the following:
-- The role name 'DPM Protected' is a valid class.
-- The class is related to a computer via a containment relationship.
-- The class has a primary key.
-- The component name 'Backup' is a valid attribute.
For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.

Cause: Error 25117 can occur if the attribute 'backup' is missing for the "DPM Protected" class in the database.  This can happen if you had previously imported the DPM 2006 MP and then upgraded to the DPM 2007 MP.  This is a known issue in DPM 2007 MP and will be addressed in later revisions.

Resolution: To resolve this issue follow the steps below:

Run the SQL queries below:

1. Select * from ClassDefinition where Name like 'DPM Protected'
2. Select * from ClassAttribute where ClassAttributeName='Backup'
3. Select * from relationshipDefinition where RelationshipTypeName ='Computer-DPM Protected'

    Note: Please note the value under column RelationshipTypeID

4. Select * from relationship where RelationshipTypeID=<'value'>
    Note: value is the ID obtained in 3rd query. Please ensure the value is enclosed within single quotes

If the problem is present you will find that for below query:

2. Select * from ClassAttribute where ClassAttributeName='Backup'

you will receive this message"

Result: No records returned

Normally we would expect some output for this query.

Next run the queries below to fix the problem:

update ClassAttribute set ClassAttributeName='Backup' where ClassAttributeID='91FBE7C0-929A-46A0-B8DA- 0D4E494FC68A'

and

update ClassAttribute set ClassAttributeName='Name' where ClassAttributeID='D18B4F2D-D168-489E-8605- EEE47D9BC3BA'

Then run this query:

Select * from ClassAttribute where ClassAttributeName='Backup'

Now this should give you the expected output which was not present earlier:

Result
:91FBE7C0-929A-46A0-B8DA-0D4E494FC68A EC27E193-8733-4126-86AD-18BFD8301A10
Backup 0 1 2004-09-16
21:18:03.860 2004-09-16 21:18:03.860 NULL Status
of Shadow Copy NULL NULL NULL NULL NULL

After above steps are taken, Error 25117 should no longer occur and your DPM 2007 should be monitored as expected.

========

Thanks Milan!

J.C. Hornbeck | Manageability Knowledge Engineer

New and Updated Knowledge Base articles for 9-28 through 10-4

We had one new and four updated Knowledge Base articles for the week - one on OpsMgr 2007 and four on MOM.  Links and titles are below:

========

Sys Center Ops Mgr 2007 SP1
958170 - Description of System Center Operations Manager 2007 Service Pack 1 support for Microsoft SQL Server 2008
Published - New

MOM Operations Mgr Base 2000 EN
825237 - Memory leak occurs after you install Microsoft Windows 2000 Server Service Pack 4
Published - Updated

MOM Operations Mgr Base 2000 EN
821266 - You receive incomplete information when the "Exchange 2000 - (SP1-Local System) Collect Public Folder Statistics" script runs
Published - Updated

MOM Operations Mgr Base 2000 EN
828782 - Microsoft Operations Manager 2000 Reports for Exchange 2000 and Exchange 5.5 Computer Groups Include Non-Exchange Servers
Published - Updated

MOM Ops Mgr Serv Ent Ed 2005 EN
889054 - You receive "Invalid Parameter (0x80041008)" error messages in the Microsoft Operations Manager Operator Console
Published - Updated

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: OSD PXE booting fails with error "No Boot Action for Device (x) found"

Here's another cool tip from Frank Rojas.  If you're trying to PXE boot and getting "No Boot Action for Device (x) found" errors then you'll want to check this out:

========

Issue: When attempting to PXE boot a PC using SCCM 2007 OSD, the PXE boot fails. Analyzing the SMSPXE.log while the PC tries to PXE boot shows the following error message as the PC attempts the PXE boot:

No Boot Action for Device (x) found

where x is a random number.

Cause: This issue can be caused by one of the following issues with SCCM2007:

1) An advertised Task Sequence to the PC has no Boot Image associated with it.

2) An advertised Task Sequence to the PC had a Boot Image associated with it, but the Boot Image originally associated with the Task Sequence has been removed or deleted.

Resolution: To fix the problem follow these steps:

1) Right click on the affected Task Sequence and choose Properties.

2) Click on the Advanced Tab.

3) Make sure that the option "Use a boot image:" is checked and that a Boot Image is selected.

Once you do this Operating System Deployment should work as expected.

========

Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer

New and Updated Knowledge Base articles for 9-21 through 9-27

We had five updated Knowledge Base articles for the week - two on ConfigMgr, two on OpsMgr and one on SMS.  Links and titles are below:

========

Sys Center Config Manager 2007 AL
955229 - You experience issues in the original release of System Center Configuration Manager 2007 after you upgrade some site databases to SQL Server 2008
Published - Updated

Sys Center Config Manager 2007 AL
955262 - You receive an error message when you click and then update the Drivers node in the Configuration Manager console of a Configuration Manager 2007 Service Pack 1 site that uses SQL Server 2008 for the site database
Published - Updated

Sys Center Ops Mgr 2007 SP1
954049 - Description of the hotfix rollup package for System Center Operations Manager 2007 Service Pack 1 and for System Center Essentials 2007 Service Pack 1: July 25, 2008
Published - Updated

Sys Center Ops Mgr 2007 SP1
953141 - Support for running System Center Operations Manager 2007 Service Pack 1 and System Center Essentials 2007 Service Pack 1 on a Windows Server 2008-based computer
Published - Updated

Sys Mgmt Server 2.0 SP2 EN
306521 - SMS Service Manager may not connect
Published - Updated

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

Windows Server 2008 Hyper-V is now supported for Configuration Manager 2007 RTM and SP1

After posting about our support for SQL Server 2008 I got some questions about Hyper-V support so here you go:

"Support will be provided for client management, site server roles, and the administrator console running within a Hyper-V environment.   There are no hot fixes required for the release to support configuration scenario.  This applies to customers running Windows Server 2008 with Hyper-V RTM installed."

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: SQL Server 2008 is now officially supported

I don't think I saw anything about this but since the hotfixes have gone public I might as well give it a little pub here.  With the release of the hotfixes below, SQL Server 2008 is now supported on System Center Configuration Manager 2007 RTM (the released version) and SP1 (the Service Pack 1 version).  In order to upgrade a site-server database to SQL 2008 there are 2 hotfixes required:

• ConfigMgr 2007 RTM customers must apply hotfix KB955229
• ConfigMgr 2007 SP1 customers must apply hotfix KB955262

The following are requirements when using a SQL Server 2008 database:

ConfigMgr 2007 RTM

If you're running the original, RTM version of Configuration Manager, then you must first install Configuration Manager 2007 using SQL Server 2005, then install hotfix KB955229, then upgrade the site databases to SQL Server 2008.  The hotfix referenced must be installed on the following servers:

• Primary site servers that are using SQL Server 2008 to host the database
• Secondary site servers that report to primary sites that are using SQL Server 2008 to host the database
• Servers that have the Configuration Manager 2007 console installed and connected to a site that uses SQL Server 2008 to host the database
• Servers that host a remote SMS provider

ConfigMgr 2007 SP1

If you're running the Service Pack 1 version of Configuration Manager 2007 then you should apply hotfix KB955262 prior to upgrading SQL Server to the 2008 version. Apply this hotfix on the following servers:

• Primary site servers that are using SQL Server 2008 to host the database
• Servers that have the Configuration Manager console installed and that connect to a site that uses SQL Server 2008 to host the database
• Servers that host a remote Systems Management Server (SMS) provider

I should also make it clear that while this is in fact supported, official documentation may not be posted for a little while.  As soon as it goes live I'll make sure to mention it here.

For more information see the corresponding Knowledge Base articles above.

J.C. Hornbeck | Manageability Knowledge Engineer

OpsMgr 2007: How to install and configure an RMS on a Windows Server 2008 cluster

Ever wonder what's needed to setup and configure an RMS on a Win2K8 cluster?  If so then check out the doc that Arnab Mitra was kind enough to put together for us:

========

How to Configure/Setup RMS on a Windows 2008 Cluster.

1. On each RMS cluster node, ensure that the domain Operations Manager Administrators security group has been added to the local administrators group and that the Cluster service account is a member of the domain Operations Manager Administrators security group.

Note: Having the Cluster service account in the Operations Manager Administrators group is necessary for creating the clustered configuration of RMS.

2. Ensure that each cluster node meets the prerequisites for the Management Server and User Interface components:

a. .NET Framework version 3.0 components (Add it from the Features Wizard)

3. Add the SDK and Config service accounts to the Local Administrators group on each node of the RMS cluster.

4. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights.

----------

Cluster preparation:

1. In Failover Cluster Management, right click ‘Services and Applications’ and select ‘Configure a Service or Application’.

2. Click next and select ‘Other Server’.

3. Click next and enter the network name for the clustered RMS

4. Click next and select an available storage for cluster group and click next through remainder of wizard.

----------

Install the RMS on the First Node

1. Log on to the cluster node that will be the primary owning node for the RMS with administrative rights

2. Ensure that the RMS cluster group is owned by the node that you are logged onto

Proceed with the regular installation wizard

3. On the Completing the System Center Operations Manager 2007 Setup Wizard page, clear the Start the Console checkbox and ensure that the Backup Encryption Key checkbox is selected, then click Finish. The Encryption Key Backup or Restore Wizard will now launch.

Important: Even though the Operations Console has been installed, do not launch the console at this point.

Note If setup fails, it provides you with a value to search on and a link to open the setup log.

4. On the Introduction page of the Encryption Key Backup or Restore Wizard click Next.

5. On the Backup or Restore page select Backup the Encryption Key radio button and click Next.

6. On the Provide a Location page specify a valid path and filename for the encryption key and click Next.

Important: It is critical that the location provided for backing up the encryption key be accessible by all nodes in the cluster.

7. On the Provide a Password page, enter a password to secure the encryption key backup file and click Next to start the backup process.

8. You should now see the Secure Storage Backup Complete page, click Finish.

----------

Install the Secondary Management Servers

In this procedure you will install secondary management servers on all other nodes in the cluster. These servers are secondary Management Servers until this process is complete, at which time they will be able to host the Root Management Server.

1. Log on to each remaining cluster node with the Operations Manager Administrator account.

2. Follow the Install RMS procedures to install the Management Server and User Interface components on each of the other nodes in the Management Group.

----------

Prepare the RMS Cluster Resources

1. In Failover Cluster Management, Right click the RMS server name under ‘Services and Applications’ and select ‘Add a resource -> 4-Generic Service’.

2. From list of services select ‘OpsMgr Health Service’ and click ‘next’ through rest of wizard.

3. Right click newly created resource, choose Properties and enable ‘Use Network Name for computer name’ and add dependencies for the shared disk and network name.

4. Repeat steps 2 and 3 for Config Service and SDK Service.

----------

Create the Virtual RMS

1. Log on to each secondary Management Server computer with an account that is a member of the Administrators group.

2. At a command prompt on each secondary Management Server, type cd <path to Operations Manager installation directory> and then press ENTER.

3. To restore the key to each secondary Management Server, type the following, where <fileshare> is a share accessible by all cluster nodes:

SecureStorageBackup.exe Restore \\<fileshare>\<filename>.bin

Note: You must provide the same password that you entered to encrypt the file on the RMS node.

4. On the SQL server that hosts the OperationsManager database, open the SQL Server Management Studio tool, open the Databases folder and select the OperationsManager database. Right-click to open the context sensitive menu and select Tasks, Back Up to initiate a backup. On the Back Up Database - OperationsManager page, ensure that the Backup type value is set to Full, give the Backup set an appropriate name, and set the Backup set will expire value to a date in the distant future. In the Destination box, for the Back up to value, select Disk and add an appropriate disk location to hold the backup, if one is not already present, and then click OK.

Important: When you run the ManagementServerConfigTool to create the RMS cluster, you are advised to back up the OperationsManager database because irrecoverable damage can be done by creating the RMS cluster.

Note: The OperationsManager database should already be running in the Full Recovery model. For more information, see SQL Server 2005 Books Online.

5. On the RMS server, open a command prompt, type cd <path to Operations Manager installation directory> and then press ENTER.

6. To instantiate the RMS cluster group as a cluster, type the following, where G is the disk resource that is allocated to the cluster group that is being used to create this virtual Root Management Server and where <VirtualServerNetbiosName> is the network name resource allocated to the same cluster group:

ManagementServerConfigTool.exe InstallCluster /vs:<VirtualServerNetbiosName> /Disk:G

The value you enter for <VirtualServerNetbiosName> must be the value that appears in the Name text box located in the Parameters tab of the Properties dialog box for the network name resource.

If InstallCluster runs successfully, the InstallCluster action will return ‘InstallCluster performed successfully’

Note: ManagmentServerConfigTool.exe InstallCluster will install the RMS as a clustered service on every available node in the cluster.

7. In the Cluster Administrator, right click the RMSClusterGroup to open the context menu and select Bring Online. This will bring all the RMSClusterGroup services online

----------

At this point you can test a failover and it should work fine.

========

Thanks Arnab!

J.C. Hornbeck | Manageability Knowledge Engineer

OpsMgr 2007: Updated BizTalk Server Management Pack for Operations Manager

Looks like the updated MP for Biztalk is now live in the catalog.  We're now at version 6.0.6411.0 and changes include:

• Addressed an issue where discovery was not fully working when host instances had multiple parent hosts.
• Addressed an issue where discovery was not fully working on systems using a locale other than US-English.
• Removed the dependency on the base BizTalk management packs from the Microsoft BizTalk 2006 R2 RFID Management Pack.

You can download the updated Management Pack from the catalog here.

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: How to automatically apply a client hotfix as part of a client push or client installation

Ever wish you could automatically install hotfixes or updates when doing the client installation?  Thanks to this tip by Frank Rojas and Jason Adams now you can:

========

When applying a Configuration Manager 2007 or SMS 2003 client hotfix, the hotfix is not automatically applied when:

1) Using client push.

2) When installing the client using CCMSetup.exe from the Client directory in the SCCM/SMS directory (even if copied to the local client PC).

3) When the client installation is part of a Package, and the Package Source points to CCMSetup,exe in the Client directory in the SCCM/SMS directory.

4) As part of the Setup Windows and ConfigMgr task in an SCCM 2007 OSD Task Sequence.

Since the hotfix is not installed as part of the initial ConfigMgr or SMS client install, the hotfix then needs to be applied separately.

Under some circumstances, installing the hotfix separate from the initial client install may lead to issues. For example, during an SCCM2007 OSD Task Sequence, installing the hotfix via an Install Software task may cause the SMS Agent Host service to be temporarily disabled. The Task Sequence may then fail because it detects that the SMS Agent Host service is not running. The SMS Agent Host service is needed by the Task Sequence for any tasks run after the Setup windows and ConfigMgr task.

So what's the solution?  The solution is to apply any ConfigMgr or SMS client hotfixes during the initial client installation. To do this without having to run any additional installations follow these steps:

1) On the SCCM/SMS site server, create a folder called ClientPatch in the following directory:

SCCM 2007:
<drive_letter>:\Program Files\Microsoft Configuration Manager\Client

SMS 2003 or SCCM 2007 upgraded from SMS 2003:
<drive_letter>:\SMS\Client

Please note that the above two locations assumes the default install location for SCCM/SMS.

2) Locate the MSP file that corresponds with the hotfix. Usually the hotfix MSP is located in the following directory:

SCCM 2007:
<drive_letter>:\Program Files\Microsoft Configuration Manager\Client\i386\hotfix\KBxxxxxx

SMS 2003 or SCCM 2007 upgraded from SMS 2003:
<drive_letter>:\SMS\Client\i386\hotfix\KBxxxxxx

Please note that the above two locations assumes the default install location for SCCM/SMS.

3) Copy (do not move) the MSP file from step 2 into the ClientPatch folder created in step 1.

4) If the client installation is part of a Package, make sure to update any Distribution Points that contain the Package.

The hotfix should now be installed automatically during the initial SCCM/SMS client installation.

========

Thanks guys!

J.C. Hornbeck | Manageability Knowledge Engineer

ConfigMgr 2007: OSD deployments to 'Unknown' Computers

Have you ever wanted to use deploy operating systems to computers using a PXE service point without first adding the computer to the Configuration Manager database?  Well now with Configuration Manager 2007 R2 you can and the famous Steve Rachui shows you how.  Over on his blog he just posted a couple great articles on OSD deployments to 'Unknown' Computers including an Overview here and a How It Works here.

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer

New and Updated Knowledge Base articles for 9-14 through 9-20

We had seven new Knowledge Base articles for the week: Two on SMS 2003, one on MOM 2005, one on System Center ConfigMgr 2007 and three on System Center Operations Manager 2007.  The links and titles are below:

========

Sys Mgmt Svr Ent Ed 2003 EN
838891 - You may receive status message ID 4963 or 5436 in the Systems Management Server 2003 or Configuration Manager 2007 Administrator Console when you try to install a new management point
Published - Updated
EN-US

Sys Mgmt Svr Ent Ed 2003 EN
886092 - You receive status message "ID=5436" when you reset the passwords for Systems Management Server connection accounts during a site reset in Systems Management Server 2003
Published - Updated
EN-US

MOM Ops Mgr Serv Ent Ed 2005 EN
883348 - Cannot use the push installation method to install the Microsoft Operations Manager 2005 agent on domain controllers in untrusted domains
Published - Updated
EN-US

Sys Center Operation Mgr 2007 EN
956444 - Error message when you try to run a Service Level Dashboard report after you install Service Level Dashboard Management Pack for System Center Operations Manager 2007: "EXECUTE permission is denied on SL_Dashboard_DashboardGroupGet"
Published - New
EN-US

Sys Center Operation Mgr 2007 EN
956423 - The connection settings for connectors in tiered management groups are configured incorrectly after the OpsMgr SDK Service restarts in a System Center Operations Manager 2007 SP1 environment
Published - Updated
EN-US

Sys Center Config Mnger 2007 AL
955955 - A task sequence that contains many packages may take longer to run after you install System Center Configuration Manager 2007 Service Pack 1 or hotfix 949225
Published - Updated
EN-US

Sys Center Ops Mgr 2007 SP1
956471 - Health Service problems occur when an active Root Management Server is targeted as an agent from other Management Groups
Published - New
EN-US

========

Enjoy!

J.C. Hornbeck | Manageability Knowledge Engineer