Re: Delete Aged Software Metering Summary Data...maximum days

Tech-Archive recommends: Fix windows errors by optimizing your registry

Steve Thompson wrote:
It is interesting... I'm seeing some inconsistency in our sites, I chose a different SMS site for this test and received the same error prompt (max 255 days). The only thing I believe that is different, the site I chose yesterday had been upgraded from SMS 2.0 to SMS 2003. The one I chose today, was a brand new SMS 2003 install. Go figure.

Steve
"Mcrawford" <Mcrawford@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:FFBD8FC6-F64B-466E-8E28-6E12AAB1F999@xxxxxxxxxxxxxxxx
Interesting...I wonder if the limit on SP2 was 370, and it was lowered with
SP3.

If you enter 371 do you get the error saying it must be between 2 and 370?
The instructor even pointed this out to us. We must have been on SP 2 when he
showed this to us.

I would like to keep 1 year worth, but it's not that big of a deal. I can
live with 255 days.

Thanks!

"Steve Thompson" wrote:

"Mcrawford" <Mcrawford@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B7EB5897-0D30-4869-80E9-26AB205D66FC@xxxxxxxxxxxxxxxx
I recenlty took an SMS class and remember the trainer stating the Delete
Aged
Software Metering Summary Data task could be set to a max of 370 days, and
I
remember making this change in our class simulation.

I'm back in the office and tried changing our max to 370 and I get a
dialog
box that states I must enter an integer between 2 and 255. Why is this? I
am
running SMS 2003 with SP3.

We started off in class running SP2, but then upgraded to SP3, so I'm not
sure at what point we changed the max to 370.

Is there anythign I can do to increase it to more than 255 days?
Probably not if that is what the error is giving you, how much do you really
need?

I just tried this on our site (set to 180 days), it would allow me to enter
370 days. We're running SMS 2003 Sp2.

Steve





It's all new to me, except for this upgrade thingy, it wouldn't be the first feature where they have taken over old settings if it was upgraded. That's not even an sms only approach, I have seen the server os folks do the same.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx
.

Relevant Pages

  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... Upgrading from SMS 2.0 to SMS 2003 ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Create an upgrade schedule for all 50 secondaries ...
    (microsoft.public.sms.admin)
  • Re: Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... Upgrading from SMS 2.0 to SMS 2003 ... A site upgrade from SMS 2.0 to SMS 2003 may not succeed if SQL ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ... Setup the secondaries boundaries and configure the site settings ...
    (microsoft.public.sms.admin)
  • Re: Upgrade Questons
    ... So just to confirm when should I upgrade to sql 2000 sp3. ... upgraded my sms 2.0 primary site to sms 2003 (configuring using standard ... so anyway we have a sms 2.0 primary site with 2 secondary sites hanging off ...
    (microsoft.public.sms.setup)
  • Re: SP2 Client upgrades
    ... Development SMS with SP2 successfully, however, in my readings, such as in the 'SMS 2003 SP2 Upgrade Checklist', I was under the impression that the clients do not automatically upgrade. ... With this information I prepared a package and found during my testings of my upgrade package push to one test client, ...
    (microsoft.public.sms.admin)
  • Need guidance on SMS 2.0 to 2003 Upgrade approach
    ... We are belatedly upgrading from SMS 2.0 to SMS 2003. ... the Primary Site Server hardware as it is old and under spec. ... secondary sites as some of them are throwing errors under SMS 2.0. ... Upgrade secondary sites OR consolidate (by re-homing clients via Site ...
    (microsoft.public.sms.admin)