Microsoft Y2K  
Microsoft
 This static CD-based web site is representative of the www.microsoft.com/y2k site as of October 15, 1999.

Microsoft Year 2000 Readiness Disclosure & Resource Center
System Mgmt Server 1.2 (Italian) - Win NT

Product Summary
Product: System Mgmt Server
Version: 1.2
Category: Compliant*
Operating System: Win NT
Language: Italian Release Date: 13 Sep 1996
Operational Range: 01 Jan 1980 - 31 Dec 2035
Prerequisites: Systems Management Server 1.2 Service Pack 4
Product Dependencies: Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5
Clock Dependencies: System Clock
Last Updated: 26 Jul 1999
Product Details

 

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customersÆ Year 2000 efforts, Microsoft intends to maintain Systems Management Server 1.2 Service Pack 4 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.

Systems Management Server 1.2 through Service Pack 3 is Compliant#.

The acceptable deviation:

When trying to inventory software users are unable to create a query with the user interface for files with a date stamp in the year 2000. Note: Any date prior to 1/1/2000 or after 12/31/2000 works properly. This issue can be worked around by importing a Package Definition File (PDF) which already contains an inventory rule rather than creating the rule in the user interface. Service Pack 4 resolves this issue.

Microsoft Systems Management Server version 1.2 Service Pack 4 is a prerequisite and is assumed for the information described below.

Systems Management Server 1.2 Service Pack 4 is available from:

ftp://ftp.microsoft.com/Softlib/MSLFILES/SMS12SP4.EXE

Service pack 4 fixes known issues with Systems Management Server 1.2 as indicated by the information below. Microsoft SMS 1.2 can use earlier versions of SQL Server, however SMS is dependent on SQL 6.5 for its Year 2000 test information. The Systems Management Server Installer, freely available as a web download for all version 1.2 customers, is also compliant from version 2.0.64 onwards. The current version at http://www.microsoft.com/smsmgmt/downloads/install.asp

is compliant and older versions can be seamlessly upgraded to this version as needed.

Systems Management Server Architecture

Subsystem

Component

Microsoft's Testing Summary

Sites

Personal Computer Properties

Workstation Status

- Last Hardware scan

- Last Software scan

For both Last HW and SW scan

Before Year 2000 - Works properly

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" HW and SW scan for the respective client will not get updated properly on the server until the client's clock is past the Last HW and SW scan already represented on the server. Resetting the clientÆs clock to the correct time solves this problem until the next century.

 

Operating System

- Install Date

Operating Systems installed before the Year 2000 are represented properly in the SMS Admin User Interface before and after the Year 2000.

Operating Systems installed after the Year 2000 are represented correctly.

Operating Systems installed on 2/29/2000 are represented correctly

 

File

Properties

Site Properties

- Last report GMT

- Last report Local

Before Year 2000 - Works properly.

Site servers whose BIOS clocks rollover from 1999 to 2000, works properly.

Site servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" report GMT and Local will not get updated until the server's clock is ahead of the Last report GMT and Local already represented on the server. Resetting the server's clock to the correct time solves this problem.

 

Inventory

Hardware Inventory Frequency

- Every N Days

Software Inventory Frequency

- Every N Days

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, inventory will not occur until the client's clock is at the last HW or SW inventory + N days. This functionality is all on the client in the SMS.INI. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, updating the inventory frequency functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the update of the site properties will not occur until the site's date is past the last time the site control file was updated before the BIOS rollover error. Resetting the server's clock to the correct time solves this problem.

 

Clients

PCM Polling Interval,

- Every N Minutes

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover properly from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the interval works properly but offers from the server are slated to begin after a certain date. The client's clock is well in the past and therefore offers will not appear in the client's PCM User Interface. Resetting the clients' clock to the correct time solves this problem.

 

Account

Service account

- Last Valid Password Created

Represented properly.

If the site server's clock rolls-over to 1980 the account will not expire for an extra 20 Years and changing it through the SMS Admin User Interface is not possible until the systems date is past the last update for the site control file.

 

Outbox

- Schedule

If the server's BIOS clock works properly:

1999 rolling over to 2000 works properly.

2/29/2000 poses no problems.


If the server's BIOS clock does not rollover to the Year 2000, but reverts to 1980, whichever day of the week in 1980 the clock reverts to, and subsequent days, is the schedule the Outbox Schedule will follow. Regardless of this, the mechanism, which initiates the sending of information from this site server will not launch, because it views this as an "old" request to send.

 

Execute Queries

- Query results (Header bar)

Dates before Year 2000 - Works properly

Dates after Year 2000 -Works properly

 

Execute query with the following

- is

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is not

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is on or after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- is on or before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Define Query result Formats

Properties ( Identification)

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Machines with last activity

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are listed in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Jobs

File

"Jobs" Window

Dates are listed properly and sorted in correct chronological order.

 

New

Run Command on Workstation

Details

Send Phase

- Only if Not previously

sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Even if Previously Sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Run Workstation Command

- Offer after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clock rolls-over from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not occur until the site's date and time matches that for the job.

 

- Mandatory after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs become mandatory properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the mandatory job is launched.

Regarding Servers

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, this has no effect on the clients except the offer after and job schedule dates will prevent jobs from being launched or reaching the clients.

 

- Expires after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs expire properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not expire until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the job expires.

Regarding Servers

Before Year 2000 û Works properly.

Servers whose BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, job will not truly expire until the expiration date is reached on the server.

 

Job Schedule

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the job will not go active until the scheduled date.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, the old jobs now happen in the future

 

View

- All details

Dates are listed in correct chronological order.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Packages

File

Properties

Inventory

- Package Properties

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Alerts

New

- Alert query

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Events

File

Properties

Event Detail

- Time:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the old events now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SNMP Traps

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the traps now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SQL Server Messages

Event Display

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Database

Manager

Edit

Merge History For Selected PCs

Works properly.

 

Machines

Duplicate machines

- Last hardware scan

Regarding Clients

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, performs properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000, the last hardware scan is time stamped with the same time stamp of the first hardware scan. Resetting the client's clock to the correct time solves this problem for the next hardware scans.

Regarding Servers

Before Year 2000 - Works properly.

For servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

For servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, this has no effect.

 

Tools

Delete Collected files

Select by date

Select Cut-Off Date

- No Activity Since: (m/d/y)

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, it is the clientsÆ clock which time stamps this.

 

- Select by number of inactive

days

- Minimum inactive days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, does not function properly. Resetting the system clock solves this.

Package Control Manager

Log File

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, perform properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000 accurately report the inaccurate date(s).

 

Return to Search Screen

Legend of Symbols:
* The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
# The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product.
+ The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

If after reviewing this information you have additional questions related to this product, click here.

 

YEAR 2000 READINESS DISCLOSURE

ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.

ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.


 

Friday, August 6, 1999
1999 Microsoft Corporation. All rights reserved. Terms of use.

This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.