Quantcast
Channel: Wsus Package Publisher
Viewing all 3825 articles
Browse latest View live
↧

New Post: Failed to load the certificate

February 28, 2015, 1:09 am
$
0
0
There is another difference. The self-signed certificate don't rely on another cert to be valid. The problem may be in the cert of the root authority.
↧
Search

New Post: [Solved] Server version is different from console version (even though it's not)

February 28, 2015, 4:43 am
$
0
0
Thank you DCourtel. I have been checking often for this new release, but haven't seen it. When you plan on releasing this?
↧
↧

Created Feature: Add the ability to add several folders [252]

March 1, 2015, 12:46 pm
$
0
0
When creating an update and adding folders, add the ability to add several folders at once.
↧

New Post: tracker software xchange PDF editor error WindowsUpdate_80070667 when publishing from wsus

March 2, 2015, 2:48 am
$
0
0
hi,
i'm trying to publish xchange editor ( http://www.tracker-software.com/product/downloads )with msi package.
My package is published on my selected computers (i've already done this with acrobat/flash update from the same wsus server) but when I try to install it, Windows update report an error "80070667".

I've only add this command line parameter when i publish the package:
/quiet /norestart EDITOR_LANGUAGE="fr-FR" DESKTOP_SHORTCUTS=1 PROGRAMSMENU_SHORTCUTS=1 SET_AS_DEFAULT=1 VIEW_IN_BROWSERS=1

http://help.tracker-software.com/EUM/default.aspx?pageid=PDFXEdit3:switches_for_msi_installers

I have also tried only "/quiet" in the command line with same error message.
↧

New Post: tracker software xchange PDF editor error WindowsUpdate_80070667 when publishing from wsus

March 2, 2015, 3:09 am
$
0
0
Hi,
Windows update report an error "80070667"
Which mean, Invalid_Command_Line_Error
Wsus will automatycally add /qn to your package to install it silently, so remove the /quiet from your command-line.
↧
↧

New Post: Failed to load the certificate

March 2, 2015, 9:49 am
$
0
0
Correct me if I am wrong but if there was a problem with the cert of the Root CA clients wouldn't install any updates signed with any cert generated by the Root CA.

The fact that I can get it all to work just by telling Package Publisher to ignore Cert Errors suggests that the cert itself is fine but rather something in the detection mechanism just doesn't like it.

I suspect the "Key Usage" Extension

The Self-Signed cert does not have a "Key Usage" extension.
Both keys have an "Enhanced Key Usage" Extension with a value of "Code Signing (1.3.6.1.5.5.7.3.3)" but the Root CA Generated key also has "Key Usage" with a value of "Digital Signature (80)" that by default is critical (unchecking critical doesn't help). This should not be a problem unless the detection method is looking for "Code Signing" in the "Key Usage" extension rather than "Enhanced Key Usage".
↧

New Post: HOW TO: Deploy Java 7 Update 45 (32-bit) & (64-bit) with UAC on or off in the client environment.

March 3, 2015, 7:32 am
$
0
0
Hello,

DParks256 wrote:
To test, approve for WSUS test group.
How do I manage to test one update with a certain test group? I would like to configure eg. Java Updates. JRE 7 for the staff, JDK 7 for the developers, JDK 8 for a special test group. Corresponding groups are configured on the WSUS Server.
Can this be done?

Thanks in advance.
Best regards
Heiko
↧

New Post: HOW TO: Deploy Java 8 (while uninstalling previous versions)

March 3, 2015, 8:12 am
$
0
0
First of all a big thanks to developers, for the great product, thanks to anyone who contributes to this board and thanks to DParks256 for posting a guide for Java 7.

I have finally started deploying Java 8 in our network, and decided share this short guide that I've created for internal use.
It's nothing new, but a good step by step manual on how to publish Java 8 using WPP. Any feedback is welcome.

Also, FYI, I've test deployed Java 8 Update 31 MSI on our XP machines, and so far it works without issues, with the apps that we need it for.

My current MSI installation command looks like this:

msiexec /i jre1.8.0_XX.msi JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q /norestart /log C:\JavaInstall.log

The guide
  1. Extract MSI from EXE:
    • Run the Java Installation executable, don't need to install
    • Go to C:\Users\<yourusername>\AppData\LocalLow\Sun\Java\ and copy your version's MSI file to some dedicated work folder/location.
  2. Read MSI ProductCode using WPP's MSI-reader function and copy it to a text file in a work folder. Looks like this {26A24AE4-039D-4CA4-87B4-2F83218031F0}
    • WSUS Package Publisher>Tools>MSI Reader
    • Find and copy Product Code field under Properties.

3. Create a Java8_XXInstall.bat (replace XX with your update version) file with the following content, This will uninstall the previous versions of Java(7) and install Java 8, (the list for 7 might not be complete, so modify if needed):

REM Uninstall Java 7 Update 45
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217045FF} /q
REM Uninstall Java 7 Update 51
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217051FF} /q
REM Uninstall Java 7 Update 55
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217055FF} /q
REM Uninstall Java 7 Update 60
msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217060FF} /q
REM Uninstall Java 7 Update 65
msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217065FF} /q
REM Uninstall Java 7 Update 67
msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217067FF} /q
REM Uninstall Java 7 Update 71
msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217071FF} /q
REM Uninstall Java 7 Update 75
msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217075FF} /q
REM Install Latest Java Version X86

msiexec /i jre1.8.0_XX.msi JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q /norestart /log C:\JavaInstall.log

  1. Create a new Custom Update:
    • Open WSUS Package Publisher>Updates>Create Custom Update
    • Add "Decalre variable to store data and use it later" - name it ReturnCode, type - Int
    • Add "Allow to execute a file":
    Path to file: Java_8_XX_Install.bat
    Parameters: leave empty
    Kill process after 30 minutes
    Store Return Code to select our "ReturnCode" variable
    • Add "Allow to define a return code for this custom update “Select Variable, choose ReturnCode
    We are now done with custom update XML generator, continue on.
  2. Add the .MSI and the Java_8_XX_Install.bat file to the package; Mark it as an Update - Critical update. Next>
  3. IsInstalled. Add rule “MSI Product Installed” - For MSI Product Code use the value copied to the text file in step 2. Next>
  4. IsInstallable. If deploying 32bit and 64bit versions of Java and if Itanum machines report to your WSUS, then you can add the “Processor Architecture” rule. You should also be able to use Reverse rule for Processor Architecture = Architecture IA64 (not equal to Itanium) if you want to just skip IA64 machines. If you are deploying either just 32bit or just 64bit version across the board then you can leave this section alone. Publish>
    Related links/documents:
    https://wsuspackagepublisher.codeplex.com/discussions/570492
    https://wsuspackagepublisher.codeplex.com/discussions/462519
    https://www.codeplex.com/Download?ProjectName=WsusPackagePublisher&DownloadId=903843
↧
Search

New Post: HOW TO: Deploy Java 8 (while uninstalling previous versions)

March 3, 2015, 8:16 am
↧
↧

New Post: HOW TO: Deploy Java 8 (while uninstalling previous versions)

March 3, 2015, 9:12 am
$
0
0
First of all a big thanks to developers, for the great product, thanks to anyone who contributes to this board and thanks to DParks256 for posting a guide for Java 7.

I have finally started deploying Java 8 in our network, and decided share this short guide that I've created for internal use.
It's nothing new, but a good step by step manual on how to publish Java 8 using WPP. Any feedback is welcome.

Also, FYI, I've test deployed Java 8 Update 31 MSI on our XP machines, and so far it works without issues, with the apps that we need it for.

My current MSI installation command looks like this:

msiexec /i jre1.8.0_XX.msi JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q /norestart /log C:\JavaInstall.log

The guide
  1. Extract MSI from EXE:
    • Run the Java Installation executable, don't need to install
    • Go to C:\Users\<yourusername>\AppData\LocalLow\Sun\Java\ and copy your version's MSI file to some dedicated work folder/location.
  2. Read MSI ProductCode using WPP's MSI-reader function and copy it to a text file in a work folder. Looks like this {26A24AE4-039D-4CA4-87B4-2F83218031F0}
    • WSUS Package Publisher>Tools>MSI Reader
    • Find and copy Product Code field under Properties.
  3. Create a Java8_XXInstall.bat (replace XX with your update version) file with the following content, This will uninstall the previous versions of Java(7) and install Java 8, (the list for 7 might not be complete, so modify if needed):
    ...........................................................
    REM Uninstall Java 7 Update 45
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217045FF} /q
    REM Uninstall Java 7 Update 51
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217051FF} /q
    REM Uninstall Java 7 Update 55
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F83217055FF} /q
    REM Uninstall Java 7 Update 60
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217060FF} /q
    REM Uninstall Java 7 Update 65
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217065FF} /q
    REM Uninstall Java 7 Update 67
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217067FF} /q
    REM Uninstall Java 7 Update 71
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217071FF} /q
    REM Uninstall Java 7 Update 75
    msiexec /x {26A24AE4-039D-4CA4-87B4-2F03217075FF} /q
    REM Install Latest Java Version X86
    msiexec /i jre1.8.0_XX.msi JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q /norestart /log C:\JavaInstall.log
    ...........................................................
  4. Create a new Custom Update:
    • Open WSUS Package Publisher>Updates>Create Custom Update
    • Add "Decalre variable to store data and use it later" - name it ReturnCode, type - Int
    • Add "Allow to execute a file":
      Path to file: Java_8_XX_Install.bat
      Parameters: leave empty
      Kill process after 30 minutes
      Store Return Code to select our "ReturnCode" variable
    • Add "Allow to define a return code for this custom update “Select Variable, choose ReturnCode.
We are now done with custom update XML generator, continue on.
  • Add the .MSI and the Java_8_XX_Install.bat file to the package; Mark it as an Update - Critical update. Next>
  • IsInstalled. Add rule “MSI Product Installed” - For MSI Product Code use the value copied to the text file in step 2. Next>
  • IsInstallable. If deploying 32bit and 64bit versions of Java and if Itanum machines report to your WSUS, then you can add the “Processor Architecture” rule. You should also be able to use Reverse rule for Processor Architecture = Architecture IA64 (not equal to Itanium) if you want to just skip IA64 machines. If you are deploying either just 32bit or just 64bit version across the board then you can leave this section alone. Publish>
Related links/documents:
https://wsuspackagepublisher.codeplex.com/discussions/570492
https://wsuspackagepublisher.codeplex.com/discussions/462519
https://www.codeplex.com/Download?ProjectName=WsusPackagePublisher&DownloadId=903843
↧

New Post: Failed to load the certificate

March 3, 2015, 9:50 am
$
0
0
I have given up and am now just using a self-signed certificate. I don't particularly like this option but it's not worth the hassle the other way around.

Thanks again for your help.
↧

New Post: Publisher certificate renewing

March 3, 2015, 11:45 pm
$
0
0
Hello,
I used WPP last year in AD environment with CA signed publisher certificate successfully.
But now this certificate is expired and I've got the new one.

Unfortunately all of my updates, created with WPP, stopped working.

I suppose the cause is that these updates are signed with old certificate. How I can resign they?

I tried to revise an update, but have got this error:
Verification of the signature failed for file: \\wsusserver.domain.ru\Update Service Packages\...._1.cab
↧

New Post: Publisher certificate renewing

March 4, 2015, 2:52 am
$
0
0
Hello, try to right-click on an update and select resign
↧
↧

New Post: Publisher certificate renewing

March 4, 2015, 3:12 am
$
0
0
Thank you very much!
This is my mistake - I cannot find this menu...
↧

New Post: Import is successful in WSUS, but disappear in WPP after closing WPP

March 4, 2015, 5:53 am
$
0
0
I use WPP on a Windows Server 2003 R2. I done these PDF:
  • "Installation Guide.pdf",
  • "Creating a Code Signing Certificate.pdf",
  • "Catalogs' subscriptions management.pdf"
  • "Importing Updates from Vendor's Catalog.pdf"
    I added some Adobe Catalogs and imported packages and then I deleted some packages in WPP. New Package are visible in WPP and WSUS, but disappear in WPP after closing WPP.
    Is there maybe something corrupted in the SQL Database?
↧
Search

New Post: Import is successful in WSUS, but disappear in WPP after closing WPP

March 4, 2015, 11:46 am
$
0
0
Thats not a Problem with SQL. Just click the Checkbox unter Tools/Settings/Updates "Show Locally-Published Updates that..."
↧

New Post: Fehler - Errors - Verbesserungsvorschläge

March 4, 2015, 11:51 am
$
0
0
Danke. Einiges davon wird in der nächsten Version gefixt.
↧
↧

New Post: Import is successful in WSUS, but disappear in WPP after closing WPP

March 5, 2015, 12:32 am
↧

New Post: Unable to make updates visible in WSUS console

March 6, 2015, 5:28 am
$
0
0
Hello,

I've been playing around with WPP for the past week or so on a 2012 R2 WSUS server and have had some great success with deploying Adobe Reader, Chrome and a few other applications out to Windows 7 and 8.1 client PCs.

But, I can't get the updates to show in the WSUS Console itself at all. Previously, when right clicking on an update and choosing "Make visible in WSUS Console" I was getting an error of "Login failed for Domain\MyUsername". This is despite me being a domain admin and also having my account in the WSUS Administrators group locally on the server.

I've since reinstalled WPP to see if that will make any difference and now the options to "Make visible in WSUS Console" or "Hide in WSUS Console" are both greyed out.

Otherwise things are working great with our third party updates but I would like to see them in the WSUS console to be able to report on them more easily.

Anyone have any thoughts or experienced this themselves?

Let me know, thanks

Martin
↧

New Post: Unable to make updates visible in WSUS console

March 6, 2015, 8:44 am
$
0
0
Hello,
There is two prerequisites to have this option enable :
  • In Settings -> Server Tab : The option "When publishing a new update", must not be set to "Never..."
  • In Settings -> Server Tab : "Connect to local server" must be tick. That mean, you must run WPP directly on the Wsus server.
Now, why have you this error message (Login failed...).
  • Are you using the Windows Internal Database (defualt Wsus installation) or a SQL database ?
  • If you use a SQL DB, is it on the Wsus server or another server ?
↧
Viewing all 3825 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>