[BigFix-Announcements] BES Auto Notification: New Fixlets Published in Fixlet Site: 'Patches for Windows'

[autonotify at us.ibm.com]

Fixlet Site - 'Patches for Windows'
Current Version: 2484	Published: Fri, 22 Apr 2016 09:47:58  GMT

New Fixlets:
============

***************************************************************
Title: WARNING: Multiple Office Products Installed - Office XP
Severity: Important
Fixlet ID: 304
Fixlet Link: http://support.bigfix.com/cgi-bin/kbdirect.pl?id=129

Fixlet Description: The computers listed below have multiple Office XP products installed. This can cause Office updates to fail on computers using the Administrative deployment option. To see the names of detected Office XP products, define a new retrieved property using the following relevance expression: if (exists key whose (value "DisplayVersion" of it as string as version = "10" AND (character 1 of it = "9" AND (it = "0" OR it = "1") of character 2 of it AND (it = "11" OR it = "12" OR it = "13" OR it = "28" OR it = "15" OR it = "16" OR it = "17" OR it = "18" OR it = "19" OR it = "1A" OR it = "1B" OR it = "27" OR it = "29" OR it = "2A" OR it = "2B" OR it = "3A" OR it = "3B" OR it = "51" OR it = "54") of first 2 of following text of first 3 of it AND (preceding text of first "%7D" of it ends with "6000-11D3-8CFE-0050048383C9")) of name of it) of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of registry) then ((value "DisplayName" of it as string) of keys whose (value "DisplayVersion" of it as string as version = "10" AND (character 1 of it = "9" AND (it = "0" OR it = "1") of character 2 of it AND (it = "11" OR it = "12" OR it = "13" OR it = "28" OR it = "15" OR it = "16" OR it = "17" OR it = "18" OR it = "19" OR it = "1A" OR it = "1B" OR it = "27" OR it = "29" OR it = "2A" OR it = "2B" OR it = "3A" OR it = "3B" OR it = "51" OR it = "54") of first 2 of following text of first 3 of it AND (preceding text of first "%7D" of it ends with "6000-11D3-8CFE-0050048383C9")) of name of it) of key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of registry) else "<N/A>" To resolve this issue, do one of the following actions: 1. Reassign the computer to use the Local or Network deployment options. You can do this through the "Office XP Deployment Control -- Reassignment" task. 2. Uninstall unnecessary Office XP installations. This Fixlet message will no longer be relevant once there is only one Office XP Product remaining. 3. If there are applications wrongly identified as Office XP products by the retrieved property above, please contact enterprisesupport at bigfix.com for further assistance.

***************************************************************
Title: OFFICE: Office 2000 Deployment Control -- Initial Assignment
Severity: Critical
Fixlet ID: 28501
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: Microsoft Office 2000 is installed on the listed computers. In order to deploy security patches and updates for the Office 2000 installation on these computers, it will be necessary to choose a patch deployment method for each computer. The BigFix Enterprise Suite supports three deployment methods:  Administrative Installation: This installation method requires an administrative installation point for Office 2000. More information on Administrative Installations is available here. Network Installation: This installation method requires that a shared CD drive be available to each computer to be updated. Each Office installation updated through this method will need access to the shared CD drive in order to retrieve required files for updates. Local Installation: This installation method requires that each user have an Office 2000 CD available to them. The user will be prompted during the installation to insert the CD to complete the installation. To set the deployment method for other Office versions, please see the following Fixlet messages:   var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script4").innerHTML=Relevance('if (exists (fixlet 29501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 29501 of bes site whose (name of it equals "Enterprise Security")) ) else ("")');} else {document.getElementById("relTag2Script4").innerHTML=EvaluateRelevance('if (exists (fixlet 29501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it as string & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 29501 of bes site whose (name of it equals "Enterprise Security")) else "Fixlet unavailable"');}}catch(e){}  var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script16").innerHTML=Relevance('if (exists (fixlet 30501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 30501 of bes site whose (name of it equals "Enterprise Security")) ) else ("" as string)');} else {document.getElementById("relTag2Script16").innerHTML=EvaluateRelevance('if (exists (fixlet 30501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it as string & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 30501 of bes site whose (name of it equals "Enterprise Security")) else "Fixlet unavailable"');}}catch(e){} 

Important Note: The Administrative Installation and Network Installation will each require that the relevant installation media be shared through a null session share. If you are using either installation method, you must familiarize yourself with the instructions below prior to deploying Office Fixlet messages.

***************************************************************
Title: OFFICE: Office 2000 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 28502

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office 2000. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office 2000 is installed on a client computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. This is the option currently being used on the listed computers. For computers that do not have administrative installation point for Office 2000, you may apply Office 2000 patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office 2000 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 28503
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: The listed computers are configured to update Office 2000 through a network shared Office 2000 CD. Instructions on how to create a null session share are included below. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options: If Office 2000 is installed on a reporting computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office 2000, you may apply Office 2000 patches silently by providing the affected computers with network access to the appropriate Office CD. This is the option currently used on the listed computers. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office 2000 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 28504

Fixlet Description: The listed computers are currently configured to use a local Office CD to update Office 2000. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office 2000 is installed on a reporting computer through an administrative install, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office 2000, you may apply Office 2000 patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation. This is the option currently being used on reporting computer.

***************************************************************
Title: OFFICE: Office 2000 Administrative Installation Point Reassignment
Severity: <Unspecified>
Fixlet ID: 28505

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office 2000. If the network address of one of your administrative installation points has changed, you can use this action button to update the network address used by computers which use that administrative installation point.

***************************************************************
Title: OFFICE: Office XP Deployment Control -- Initial Assignment
Severity: Critical
Fixlet ID: 29501
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: Microsoft Office XP is installed on the listed computers. In order to deploy security patches and updates for the Office XP installation on these computers, it will be necessary to choose a patch deployment method for each computer. The BigFix Enterprise Suite supports three deployment methods:  Administrative Installation: This installation method requires an administrative installation point for Office XP. More information on Administrative Installations is available here. Network Installation: This installation method requires that a shared CD drive be available to each computer to be updated. Each Office installation updated through this method will need access to the shared CD drive in order to retrieve required files for updates. Local Installation: This installation method requires that each user have an Office XP CD available to them. The user will be prompted during the installation to insert the CD to complete the installation. To set the deployment method for other Office versions, please see the following Fixlet messages:   var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script5").innerHTML=Relevance('if (exists (fixlet 28501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 28501 of bes site whose (name of it equals "Enterprise Security")) ) else ("")');} else {document.getElementById("relTag2Script5").innerHTML=EvaluateRelevance('if (exists (fixlet 28501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it as string & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 28501 of bes site whose (name of it equals "Enterprise Security")) else "Fixlet unavailable"');}}catch(e){}  var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script16").innerHTML=Relevance('if (exists (fixlet 30501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 30501 of bes site whose (name of it equals "Enterprise Security")) ) else ("")');} else {document.getElementById("relTag2Script16").innerHTML=EvaluateRelevance('if (exists (fixlet 30501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it as string & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 30501 of bes site whose (name of it equals "Enterprise Security")) else "Fixlet unavailable"');}}catch(e){} 

Important Note: The Administrative Installation and Network Installation will each require that the relevant installation media be shared through a null session share. If you are using either installation method, you must familiarize yourself with the instructions below prior to deploying Office Fixlet messages.

***************************************************************
Title: OFFICE: Office XP Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 29502

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office XP. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office XP is installed on a client computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. This is the option currently being used on the listed computers. For computers that do not have administrative installation point for Office XP, you may apply Office XP patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office XP Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 29503
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: The listed computers are configured to update Office XP through a network shared Office XP CD. Instructions on how to create a null session share are included below. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office XP is installed on a reporting computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office XP, you may apply Office XP patches silently by providing the affected computers with network access to the appropriate Office CD. This is the option currently used on the listed computers. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office XP Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 29504

Fixlet Description: The listed computers are currently configured to use a local Office CD to update Office XP. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office XP is installed on a reporting computer through an administrative install, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office XP, you may apply Office XP patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation. This is the option currently being used on reporting computers.

***************************************************************
Title: OFFICE: Office XP Administrative Installation Point Reassignment
Severity: <Unspecified>
Fixlet ID: 29505

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office XP. If the network address of one of your administrative installation points has changed, you can use this action button to update the network address used by computers which use that administrative installation point.

***************************************************************
Title: OFFICE: Office 2003 Deployment Control -- Initial Assignment
Severity: Critical
Fixlet ID: 30501
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: Microsoft Office 2003 is installed on the listed computers. In order to deploy security patches and updates for the Office 2003 installation on these computers, it will be necessary to choose a patch deployment method for each computer. The BigFix Enterprise Suite supports three deployment methods:  Administrative Installation: This installation method requires an administrative installation point for Office 2003. More information on Administrative Installations is available here. Network Installation: This installation method requires that a shared CD drive be available to each computer to be updated. Each Office installation updated through this method will need access to the shared CD drive in order to retrieve required files for updates. Local Installation: This installation method requires that each user have an Office 2003 CD available to them. The user will be prompted during the installation to insert the CD to complete the installation. To set the deployment method for other Office versions, please see the following Fixlet messages:   var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script5").innerHTML=Relevance('if (exists (fixlet 28501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 28501 of bes site whose (name of it equals "Enterprise Security")) ) else (html "" as string)');} else {document.getElementById("relTag2Script5").innerHTML=EvaluateRelevance('if (exists (fixlet 28501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 28501 of bes site whose (name of it equals "Enterprise Security")) else html "Fixlet unavailable"');}}catch(e){}  var isEvansOrLater = '' == 'True'?true:false; try{if (isEvansOrLater) {document.getElementById("relTag2Script4").innerHTML=Relevance('if (exists (fixlet 29501 of bes site whose (name of it equals "Enterprise Security"))) then ( ((format "" + link of it as string + applicable computer count of it as string ) as string) of (fixlet 29501 of bes site whose (name of it equals "Enterprise Security")) ) else ("" as string)');} else {document.getElementById("relTag2Script4").innerHTML=EvaluateRelevance('if (exists (fixlet 29501 of bes site whose (name of it equals "Enterprise Security"))) then (link of it as string & " (" & applicable computer count of it as string & " relevant computers)") of (fixlet 29501 of bes site whose (name of it equals "Enterprise Security")) else "Fixlet unavailable"');}}catch(e){} 

Important Note: The Administrative Installation and Network Installation will each require that the relevant installation media be shared through a null session share. If you are using either installation method, you must familiarize yourself with the instructions below prior to deploying Office Fixlet messages.

***************************************************************
Title: OFFICE: Office 2003 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 30502

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office 2003. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office 2003 is installed on a client computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. This is the option currently being used on the listed computers. For computers that do not have administrative installation point for Office 2003, you may apply Office 2003 patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office 2003 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 30503
Fixlet Link: http://support.bigfix.com/bes/misc/null_session_share.html

Fixlet Description: The listed computers are configured to update Office 2003 through a network shared Office 2003 CD. Instructions on how to create a null session share are included below. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office 2003 is installed on a reporting computer through an administrative installation point, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office 2003, you may apply Office 2003 patches silently by providing the affected computers with network access to the appropriate Office CD. This is the option currently used on the listed computers. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation.

***************************************************************
Title: OFFICE: Office 2003 Deployment Control -- Reassignment
Severity: <Unspecified>
Fixlet ID: 30504

Fixlet Description: The listed computers are currently configured to use a local Office CD to update Office 2003. If you want to reassign the deployment type for the computers below, you can use these action buttons to do so. There are three options:  If Office 2003 is installed on a reporting computer through an administrative install, you should use our administrative install Fixlet messages to apply all patches. For computers that do not have administrative installations of Office 2003, you may apply Office 2003 patches silently by providing the affected computers with network access to the appropriate Office CD. For computers that can not use either of the previous two options, you may choose to run the normal installation process -- this will require that a local user insert the appropriate Office CD in order to complete the installation. This is the option currently being used on reporting computers.

***************************************************************
Title: OFFICE: Office 2003 Administrative Installation Point Reassignment
Severity: <Unspecified>
Fixlet ID: 30505

Fixlet Description: The listed computers are currently configured to use an administrative installation point to update Office 2003. If the network address of one of your administrative installation points has changed, you can use this action button to update the network address used by computers which use that administrative installation point.