This would require a change in the pmimport file if warranted. Do your server admins not want it installed or is it not possible to install (your wording doesn't exactly clarify).

We had a similar request from our office in Germany; they use a software called ACT (not sure if it is the old Symantec ACT or something else; the vendor is SAGE software apparently). The default MS patches successfully stop the DB instance, but can't patch it due to the way it is installed, but they don't restart the services. So the users have to either reboot or maybe manually restart the SQL services. For now we are excluding machine with that app installed from the SQL patches until we find a work-around. Supposedly the vendor will develop a "wrapped" patch that can be deployed via SWD or manually...

Actually, the information I received wasn't clear either. All I know is these servers flagged for the SQL update, DS indicates that SQL Server 2005 is installed on these servers and NS is even erroring the update out. I googled the update and found that "MSP Error: 29565 SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete." I notified our Server Admins of this back at the beginning of October and received an email today stating "These servers are Backup Exec servers and have an instance of SQL 2005 that comes with the install for Backup Exec. Altiris is seeing this as a full version of 2005 which is not the case. The update cannot be applied to this "lite" version of SQL 2005. These servers will need to be excluded from the report for this update." I have seen a lot of goofy things over the last 3 years, but not this. My gut is that if it is flagging and erroring like this, then it can be applied. I wanted to get Altiris' opinion.

Hmm... according to this link from MS:http://www.microsoft.com/techn...bulletin/MS08-052.mspx, SQL 2005 Express is NOT affected. I'm guessing that is what is meant by SQL 'lite'.



That would mean that the pmimport is indeed incorrectly targeting the computers.

What happens if you manually run the patch .exe on one of these machines? Can you step through the wizard to get it updated, or does that fail too?

We've duplicated this issue and are working on a fix.



Thanks,



Andrew

Andrew, you're Kyle's hero, you know that?

I won't believe it until he updates his signature to acknowledge that fact...