Logo
programming4us
programming4us
programming4us
programming4us
 Home
programming4us
 XP
programming4us
 Windows Vista
programming4us
 Windows 7
programming4us
 Windows Azure
programming4us
 Windows Server
programming4us
 Windows Phone
 
Windows Server

Microsoft Systems Management Server 2003 : Migration Issues - Planning the Site Structure (part 2) - Running the Deployment Readiness Wizard

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
10/21/2011 5:30:01 PM

Running the Deployment Readiness Wizard

There’s quite a bit to consider before attempting to upgrade your SMS 2.0 site to SMS 2003. I’ve pointed out only a few of the concerns you must think about. However, Microsoft created a tool to help you determine whether your SMS 2.0 site is ready for an upgrade. You must run the Deployment Readiness Wizard (DRW) on the SMS 2.0 site server before you can run the upgrade.

As you can see in Table 1, this wizard runs a rather comprehensive series of tests on your SMS 2.0 site server. When it’s finished, it generates a list of the tests and whether they passed. As each test runs, it can either pass with flying colors or generate an error or warning message. A warning message doesn’t prevent the upgrade from occurring, but it does identify a potential issue that you might consider resolving before upgrading. An error message, on the other hand, does prevent the upgrade from occurring. You must resolve the issues that caused the error message before you can proceed with the upgrade.

Table 1. Deployment Readiness Wizard tests
TestFailure TypeDescription
Alpha processor clientsWarningVerifies that no alpha-based client operating systems exist in the SMS site.
IPX site boundariesWarningVerifies that no IPX site boundaries are configured.
Non-TCP/IP clientsWarningVerifies that all clients use TCP/IP.
NetWare server site systemsErrorVerifies that no site system servers are running Novell NetWare.
Secure client configurationWarningIdentifies those computers in the SMS site that are running Windows 2000 or later that have the SMS 2.0 client installed so that you can easily target those computers with the Advanced Client (which is more secure than the Legacy Client).
Pre–Windows 2000 SP2 site systemsWarningVerifies that all site systems are running Windows 2000 SP2 or later. SMS 2003 site systems require Windows 2000 SP2 or later.
Unsupported client operating systemsWarningVerifies that none of the clients assigned to the site are running an unsupported operating system.
Windows 98 FE clients without Internet Explorer 5WarningVerifies that all the clients running Windows 98, First Edition that are assigned to the site have Internet Explorer 5 or later installed.
FAT drive on site serverWarningVerifies that a FAT drive doesn’t exist on the site server.
Indirect child sites earlier than SMS 2.0 SP4WarningVerifies that all sites below the child sites of the site being tested are running SMS 2.0 SP4 or later.
Pre-SMS 2.0 SP4 sitesErrorVerifies that the site server being tested and all its child sites are running a version of SMS 2.0 SP4 or later.
SMS 1.2 clientsWarningVerifies that no SMS 1.2 clients are installed in the site.
Collation of temp database and SMS database should be the sameErrorVerifies that the collation of the temporary database and the SMS site database are the same.
Site database SQL Server version less than 7.0 SP3ErrorVerifies that the version of SQL Server used for the SMS site database is SQL Server 7.0 SP3 or later.
Backlogged inboxesWarningVerifies that the site server is processing critical inboxes in a timely fashion and doesn’t have any files older than one day. Review the test results for more information.
Distribution point has latest versions of packagesWarningVerifies that all distribution points in the site have the latest version of software distribution packages.
Duplicate client IDsWarningVerifies that the site doesn’t have any duplicate client IDs in its database.
Event to trap translatorErrorVerifies that the SNMP Event To Trap Translator client agent isn’t enabled on the site.
Hardware Inventory group mapWarningVerifies that the inventory definitions for the SMS 2.0 site have not been extended in a way that conflicts with the updated inventory definitions for SMS 2003 and that there are no incorrect NOIDMIF definitions that were created by SMS 2003 Beta 1, duplicate Group-Map table name entries, or GroupMap entries with missing tables.
Inactive clientsWarningVerifies that all the clients assigned to the site are communicating successfully with the site’s client access points (CAPs).
Logon Client Installation disabledErrorVerifies that SMS 2.0 Logon Client Installation has been disabled.
Logon Discovery disabledErrorVerifies that SMS 2.0 Logon Discovery has been disabled.
Logon points installed in hierarchyErrorVerifies that no logon points are currently installed in the hierarchy.
Packages SQL constraintErrorVerifies that there are no duplicate package IDs.
Multisite assigned clientsWarningVerifies that no clients are assigned to more than one SMS site.
SMSExec is runningErrorVerifies that SMS Executive is running on site systems such as the SMS site server and the CAPs.
SMSExec Service crashesWarningVerifies that no SMS Executive service crashes have happened on the site server within the last 30 days.
Site control file processing backlogErrorVerifies that site control file changes are being processed in a timely fashion.
Software Distribution: Uninstall registry key usageWarningVerifies that no SMS 2.0 programs use the Remove Software When It Is No Longer Advertised option, which uses the Uninstall registry key.
Software metering site systemsErrorVerifies that no software metering site systems are configured in the SMS hierarchy.

To run the DRW, complete the following steps:

1.
On the SMS 2.0 site server, navigate to the SMSSetup\Bin\I386 folder on the SMS 2003 product CD and run DRW.exe. The Welcome page is displayed, as shown in Figure 1.
Figure 1. DRW Welcome page.
2.
Click Next to display the Site Selection page, shown in Figure 2.
Figure 2. DRW Site Selection page.
3.
Select Analyze This Primary Site if you’re running the DRW on the SMS 2.0 primary site you’re upgrading or select Analyze One Or More Direct Child Secondary Sites if you want to run DRW against an SMS 2.0 secondary site associated with this primary site. If you select the latter option and click Next, the Secondary Sites page is displayed, as shown in Figure 3. Select the site or sites that you want to analyze and then click Next.
Figure 3. DRW Secondary Sites page.
4.
Click Next to display the Tests page, shown in Figure 4. Select the tests that you want to run and then click Next. Unless you’re truly confident about the state of your SMS 2.0 site, I recommend running all the tests.
Figure 4. DRW Tests page.
5.
On the Completing the Systems Management Server 2003 Deployment Readiness Wizard page, shown in Figure 5, click Finish.
Figure 5. Completing the Systems Management Server 2003 Deployment Readiness Wizard page.
6.
When the wizard has completed running the tests, click Details on the Progress And Results Summary page shown in Figure 6 to see the results of each test.
Figure 6. DRW Progress And Results Summary page.

When you click Details, the Test Results page is displayed, as shown in Figure 7. In this page, click View Report to display a report that lists and describes each test that ran or select a test from the list and click Details to display information specific to that test. Click Close when you’re finished.

Figure 7. DRW Test Results page.

Notice the More Information button on the Progress And Results Summary page. Clicking this button takes you to the SMS 2003 Deployment Readiness Wizard Procedures for Resolving Test Failures Web page, shown in Figure 8, hosted on TechNet. This document outlines each test in more detail and includes steps you can take to resolve the warnings and errors that might be generated. You can download a printable version of this document either from TechNet or from the SMS Web site.

Figure 8. SMS 2003 Deployment Readiness Wizard Procedures for Resolving Test Failures Web page.
Other -----------------
- Managing Microsoft Windows Server 2003 Disk Storage : Implementing RAID
- Managing Microsoft Windows Server 2003 Disk Storage : Maintaining Disk Storage Volumes
- Securing Windows Server 2008 R2 : DirectAccess
- SharePoint 2010 Search : Setting Up the Crawler - Crawling Metadata
- SharePoint 2010 Search : Setting Up the Crawler - Crawler Impact Rules & Crawler Scheduling
- Securing Windows Server 2008 R2 : Active Directory Recycle Bin
- Securing Windows Server 2008 R2 : NPS & NAP
- Microsoft Dynamics AX 2009 : The MorphX Tools - Unit Test Tool (part 2)
- Microsoft Dynamics AX 2009 : The MorphX Tools - Unit Test Tool (part 1) - Test Cases
- Active Directory Domain Services 2008 : Manage Active Directory Domain Services Data - Move a Group Object
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
 Windows Vista
programming4us
 Windows 7
programming4us
 Windows Azure
programming4us
 Windows Server