locked
Un-Install Software called WinZip RRS feed

  • Question

  • How and where I can create a package to uninstall a software called WinZip from all the clients machines running on windows 2000 and Prof. using SCE 2007. Please note I did not use SCE 2007 to install WinZip on all the machine but I want to use SCE 2007 to uninstall it.

     

    Thanks

     

    Tuesday, June 10, 2008 8:21 PM

Answers

  • Hi,

    For the verification error, please use the following steps to verify your certificats:


    To verify that the SSL certificate has been configured on the WSUS website:
    1. Open IIS Manager on the Essentials server

    2. Navigate to Web Sites\WSUS Administration

    3. Right click on the WSUS Administration web site and select Properties

    4. Select the Directory Security tab

    5. In the Secure Communications section, click on View Certificate.

    6. On the Details tab of the certificate, the “Issuer”property should be the name of the System Center Essentials server. The “Thumbprint” property should match what is in the SSLCertHash value in HKLM\Software\Microsoft\System Center Essentials\1.0\PolicySettings. This can be used to compare with the Thumbprint of the certificate on the client machine to verify that they are the same.

    To verify that the Code Signing certificate has been created on the System Center Essentials server, verify that the “WSUS Publishers Self-signed” certificate exists under WSUS\Certificates in the Local Computer certificate store. To do this:

    1. Go to Start - Run - mmc.exe

    2. When the MMC console opens, select File - Add/Remove Snap-in, then click on Add.

    3. In the list of snap-ins, select “Certificates” and click on Add.

    4. Select “Computer account” and click on Next, then select “Local Computer” and click on Finish.

    5. Close the Snap-ins list and click Ok on the Add/Remove snap-in window.

    6. In the Certificate console, expand the Certificates (Local Computer) tree and verify that the “WSUS Publishers
    Self-signed” certificate exists under WSUS\Certificates.

    7. On the Details tab of the certificate, the “Issuer” property should be “WSUS Publishers Self-signed”. The “Thumbprint” property should match what is in the WSSUCodeSigningCertHash value in HKLM\Software\Microsoft\System Center Essentials\1.0\PolicySettings. This can be used to compare with the Thumbprint of the certificate on the client machine to verify that they are the same.


    To verify that the Code Signing certificate has been configured on the Essentials server and on client computers, use the Certificates MMC console to verify that it exists under Trusted Root Certification Authorities, Trusted Publishers, and Third-Party Root Certification Authorities in the Local Computer certificate store. To do this:

    1. Go to Start - Run - mmc.exe

    2. When the MMC console opens, select File - Add/Remove Snap-in, then click on Add.

    3. In the list of snap-ins, select “Certificates” and click on Add.

    4. Select “Computer account” and click on Next, then select “Local Computer” and click on Finish.

    5. Close the Snap-ins list and click Ok on the Add/Remove snap-in window

    6. In the Certificate console, expand the Certificates (Local Computer) tree and verify that the following certificate is listed under Trusted Root Certification Authorities\Certificates, Trusted Publishers and Third-Party Root Certification Authorities:

    Issued To:WSUS Publishers Self-signed
    Issued By:WSUS Publishers Self-signed
    Intended Purpose :<All>


    7. Verify that the Thumbprint properties on the above certificate matches the thumbprint on the “WSUS Publishers Self-signed” certificate under WSUS\Certificates in the certificate store on the Essentials server.

    --------------------
    Regards,
    Eric Zhang



    Thursday, June 19, 2008 9:38 AM

All replies

  • If its a windows installer package, then you can deploy it first to all clients and once all clients have reported sucess, you can proceede to uninstall it. If it is not a windows installer package, then you can write a script such as in vbs to uninstall and deploy the script together with wscript.exe as a package. Once all clients report success, check the software deployment report to see if Winzip is not installed.

    Wednesday, June 11, 2008 10:06 AM
  • How can I tell if it's a windows installer package? Why would I deploy it bcuz all the clients have installed it already and I want to uninstall it.

     

    Wednesday, June 11, 2008 8:11 PM
  • Hi,

    You can only deletet the software that deployed by

    SCE.Administrators can use the System Center Essentials 2007 console to uninstall previously deployed software from managed computers. For packages that use MSI-based installations, the removal parameters can be specified on the Installation table in the package’s properties, and the package can be approved for uninstall.

    Packages that use .exe files for the installation must be removed by creating a new Software Package that contains the files and parameters necessary for the uninstall.

    I think the solutions that provided by Paulm187 are available.

    --------------------
    Regards,
    Eric Zhang



    Thursday, June 12, 2008 7:26 AM
  • where I can find this Paulm187 solution?

    I tired creating a software package and got this error message:

     

    "Verification of the file signature failed for file"

    Thursday, June 12, 2008 6:47 PM
  • Is Winzip a Windows installer package ( .msi) or install shield etc with .exe ?

    Friday, June 13, 2008 9:46 AM
  • Hi,

    For the verification error, please use the following steps to verify your certificats:


    To verify that the SSL certificate has been configured on the WSUS website:
    1. Open IIS Manager on the Essentials server

    2. Navigate to Web Sites\WSUS Administration

    3. Right click on the WSUS Administration web site and select Properties

    4. Select the Directory Security tab

    5. In the Secure Communications section, click on View Certificate.

    6. On the Details tab of the certificate, the “Issuer”property should be the name of the System Center Essentials server. The “Thumbprint” property should match what is in the SSLCertHash value in HKLM\Software\Microsoft\System Center Essentials\1.0\PolicySettings. This can be used to compare with the Thumbprint of the certificate on the client machine to verify that they are the same.

    To verify that the Code Signing certificate has been created on the System Center Essentials server, verify that the “WSUS Publishers Self-signed” certificate exists under WSUS\Certificates in the Local Computer certificate store. To do this:

    1. Go to Start - Run - mmc.exe

    2. When the MMC console opens, select File - Add/Remove Snap-in, then click on Add.

    3. In the list of snap-ins, select “Certificates” and click on Add.

    4. Select “Computer account” and click on Next, then select “Local Computer” and click on Finish.

    5. Close the Snap-ins list and click Ok on the Add/Remove snap-in window.

    6. In the Certificate console, expand the Certificates (Local Computer) tree and verify that the “WSUS Publishers
    Self-signed” certificate exists under WSUS\Certificates.

    7. On the Details tab of the certificate, the “Issuer” property should be “WSUS Publishers Self-signed”. The “Thumbprint” property should match what is in the WSSUCodeSigningCertHash value in HKLM\Software\Microsoft\System Center Essentials\1.0\PolicySettings. This can be used to compare with the Thumbprint of the certificate on the client machine to verify that they are the same.


    To verify that the Code Signing certificate has been configured on the Essentials server and on client computers, use the Certificates MMC console to verify that it exists under Trusted Root Certification Authorities, Trusted Publishers, and Third-Party Root Certification Authorities in the Local Computer certificate store. To do this:

    1. Go to Start - Run - mmc.exe

    2. When the MMC console opens, select File - Add/Remove Snap-in, then click on Add.

    3. In the list of snap-ins, select “Certificates” and click on Add.

    4. Select “Computer account” and click on Next, then select “Local Computer” and click on Finish.

    5. Close the Snap-ins list and click Ok on the Add/Remove snap-in window

    6. In the Certificate console, expand the Certificates (Local Computer) tree and verify that the following certificate is listed under Trusted Root Certification Authorities\Certificates, Trusted Publishers and Third-Party Root Certification Authorities:

    Issued To:WSUS Publishers Self-signed
    Issued By:WSUS Publishers Self-signed
    Intended Purpose :<All>


    7. Verify that the Thumbprint properties on the above certificate matches the thumbprint on the “WSUS Publishers Self-signed” certificate under WSUS\Certificates in the certificate store on the Essentials server.

    --------------------
    Regards,
    Eric Zhang



    Thursday, June 19, 2008 9:38 AM
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

    If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.


    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks!
    --------------------
    Regards,
    Eric Zhang

    Wednesday, June 25, 2008 10:15 AM