LANDesk Management - updates

[pete_arnett-p40]

[font=arial]Headquarters has released an additional eight (8) system updates,[/font][font=arial](as of Mon a.m., 15Feb2010)[/font]
[font=arial]
To download and install the updates, just click on Start > Programs > LANDesk Management > Security Scan

A window will appear showing the progress of the "LANDesk Security and Patch Manager" and the window will automatically close when the updates have completed

Note: your count may vary, because when we did the Local Unit Security Software (LUSS) install, (Jan2010,) we did a "Security Scan" and installed system updates[/font]

[lajackson]

[font=arial]Headquarters has released an additional eight (8) system updates,[/font][font=arial](as of Mon a.m., 15Feb2010)[/font]

[font=Times New Roman]To download and install the updates, just click on Start > Programs > LANDesk Management > Security Scan

A window will appear showing the progress of the "LANDesk Security and Patch Manager" and the window will automatically close when the updates have completed

Note: your count may vary, because when we did the Local Unit Security Software (LUSS) install, (Jan2010,) we did a "Security Scan" and installed system updates
[/font]

Now that we have finished running all around the stake to get the LUSS software installed (well, we still have one to go), how often should we run around again to manually update everything?

Or how often should we tell the local clerk to do it for us?

[aebrown]

Now that we have finished running all around the stake to get the LUSS software installed (well, we still have one to go), how often should we run around again to manually update everything?

Or how often should we tell the local clerk to do it for us?

While I wouldn't disagree with Pete, I would wait for direction from CHQ before I would assume that there is some procedure we have to do on each computer at this point. I've heard no such directive, so I will treat Pete's post as only an interesting curiosity for now.

[techgy]

Now that we have finished running all around the stake to get the LUSS software installed (well, we still have one to go), how often should we run around again to manually update everything?

Or how often should we tell the local clerk to do it for us?

I was under the impression that the software would perform its own updates so that we don't have to circle the stake each month. Perhaps someone in the "know" from CHQ could address this and set us straight.

[lajackson]

I was under the impression that the software would perform its own updates so that we don't have to circle the stake each month. Perhaps someone in the "know" from CHQ could address this and set us straight.

I understand that is supposed to be true for those with high-speed connections. Those of us with lowly little phone lines probably do not even have the latest of whatever it is we have. [grin]

[pete_arnett-p40]

Talked with headquarter's staff today and they will be releasing a statement about doing patches very soon

Also, like in the FHCs, LANDesk software should perform its own updates so that we don't have to circle the stake each month

[russellhltn]

Also, like in the FHCs, LANDesk software should perform its own updates so that we don't have to circle the stake each month

Certainly if it's on broadband, it should. But I'll take a "I'll believe it when I see it" stance for dial-up users.

[pete_arnett-p40]

As of Tuesday a.m., 02Mar2010

Administrative (MLS) desktops - did a LANDesk security scan and there are no new updates

Family History Centers (FHC) desktops - did a LANDesk security scan and there are no new updates

Now we just need to wait for Microsoft's Patch Tuesday or another update to Adobe Reader

[russellhltn]

Now we just need to wait for Microsoft's Patch Tuesday or another update to Adobe Reader

That happened a couple of weeks ago. Last I checked, "current" is 9.3.1.

[pete_arnett-p40]

As of Saturday p.m., 13Mar2010

Administrative (MLS) desktops:

MS10-015: kb977165
Vulnerabilities in Windows kernel could allow elevation of privilege

MS10-016: kb975561
Vulnerability in Windows Movie Maker could allow remote code execution

and a Landesk deployment file 0_winxp_ENU.1268395212.0_winxp_ENU.1268395212.xmlz

---------------------------

Family History Centers (FHC) desktops:

MS10-016: kb975561
Vulnerability in Windows Movie Maker could allow remote code execution