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

Commented Task: Ideas for WPP V2 - Call for contributions [109]

$
0
0
* New GUI, based on Office Ribbon look & feel.
* Enhance Multi-threading to avoid hangs.
* Show Microsoft official updates.
* Add ability to drag&drop rule when creating/editing an update.
* Add the ability to filter datagridview like Excel does.
* Enable displaying/modification of rules at package level.
* When importing updates from Catalogs, enable to filter on already imported updates.
* Allow users to edit Vendor name and product name when importing from Catalog. Create a "Substitution Dictonnary" to automatically make these changes.
* Redesign Rule Assistant. Separate IsInstalled and IsInstallable. Separate UpdateLevel Rules and PackageLevel Rules.
* Allow to publish MetaData only updates from catalogs.

__Suggestions are welcome !__
Comments: A Service who is checking daily the subscribed catalogs for new Updates. If a new update is available send a mail to a admin.

New Post: old updates

$
0
0
I have WPP running for both Adobe products and Java now. (Great product, by the way. Thank you!)

But a question has arisen. What happens when the next Flash update comes along? Do I decline/delete my entry for 12.0.0.44 and add the next one? If not, I can see how things will get very cluttered in a short matter of time.

Also, I have seen some odd behavior from the Adobe Flash 12.0.0.44 catalog. I got it from Adobe via the subscription. When I approved it, I started seeing a number of failures listed in WSUS. However, upon closer inspection, the update has succeeded. If I run a report on the update and look at page 2, most of the computers show that it failed. However, if you click on "Failed" for a given computer, you get a message that it succeeded. This is true for most entries. Checking Programs and Features confirms this. Perhaps there was a problem with the catalog provided by Adobe. Has anyone else seen this?

New Post: old updates

$
0
0
You can decline delete the update, or just configure the new update as superseding update.

Regards
Norbert

New Post: Need help to deploy Adobe Reader 9.3.3 to Client Workstation

$
0
0
Hi there,

Thanks for your help. I realise that there was an 0x800b0109 error in the C:\Windows\WindowsUpdate.log on the client workstation. Then I added the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AcceptTrustedPublisherCerts = 1 key into the registry and it works fine.

New Post: Need help to deploy Adobe Reader 9.3.3 to Client Workstation

$
0
0
Hi there,

I would like to know the command to silent install Adobe Reader 9.3.3, AdbeRdr 933_en_US.exe, and to a specific path (different drive), inside the Command Line field of the Update Creation Wizard. Thanks!

New Post: Return Codes

$
0
0
Hello guys,

I have a couple of questions about the return codes...

Can you please give me more information about return code and how they work and how I make them some use of them ?

Let say this scenario:

I create a custom upgrade with following structure:
  1. Create a variable - int var1
  2. Create a variable - int var2
  3. Run PowerShell scripts - Store Retrun Code to: var1
  4. Defire the return code for this Custom Upgrade - Return Code to var2
At the final page of the wizzard I have Vendor Name, Product name ... etc ... and Return Codes what are they about and what they have to do with the variables of Return Code I set in custom upgrade block.

And my second question os:

How can I put in use the Return Code from the PowerShell script and the Return Code variable from the whole Custom Upgrade where are they stored, how can i see them ?



Thanks guys,
Best Regards,
Martin

New Post: Return Codes

$
0
0
Hi mnikolaev,

First, a custom update can return only one 'Return Code', so you don't have to declare two variables.

In the update Wizard, the return code section allow you to define the meaning of the return code. For example, let's say your powershell script return -1 if success, 255 if success but a reboot is required and 254 if failed. Then you can create these return codes here.

New Post: Publishing Issue Code 6BA

$
0
0
I have a strange issue when installing flash player through the publisher. It seems to be failing on computers that already have the same version installed. E.G Test computer A: installs flash MSI. Report says Installed and green. 2 days later the update is back and it is showing as failed!
I have tried to uninstall flash and run it again. But the update fails.

I have downloaded flash from Adobe over the internet and it installs fine. But it still is trying to install the update. It seems that it is not checking if the update is required or not and keeps sending it out regardless.

New Post: Set a client's WSUS client service to debug mode

$
0
0
I'd love to have the feature to be able to set a WSUS client's service to debug mode to troubleshoot (set registry keys to debug then restart service). And once done be able to have them be in non-debug mode. I would think the best place would be when you right click on the client in the package status window.

Thanks!

New Post: Set a client's WSUS client service to debug mode

$
0
0
Do you really think this feature can be needed often ?
I think that most of Wsus Clients issue can be solved by other ways.

New Post: Publishing Issue Code 6BA

$
0
0
Which version of Flash Player do you have published ? do you have used the Adobe catalog or directly the MSI file ?

New Post: Publishing Issue Code 6BA

New Post: Publishing Issue Code 6BA

$
0
0
What do you have set in the "IsInstalled" and "IsInstallable" tab ?

New Post: Set a client's WSUS client service to debug mode

$
0
0
The reason for the request is from this "adventure" I had last week:

I had spent about 3 days trying to setup the proper Installable, Installed rules for Trend Micro Officescan. I was only able to actually see the reason why Installable was false and Installed was false after I enabled debugging of the WSUS client service and hammered on the rules.

Turns out Trend Micro includes a installed & installable rule where the MSI code matches an existing code found it won't install despite the version of each package being different. Only after running a client in debugging did I see a package rule show up (didn't see them in the WSUS package Publisher publishing view, but then again I've never seen a package have rules already defined). I deleted the package rules during the initial publishing (the second time I published it) and it fixed that issue.

The second issue was a Reg_SZ key wasn't being evaluated when set to "equal" as opposed to "contains" when comparing the registry key against a DisplayVersion "10.6.5162". The debugging showed it completely fail attempting to validate the installed rule and instead report an error about the "C:\Program Files\Update Services\v4\xml" was corrupt on the client, which made no sense. In a blind guess I flipped it to "contains" and it successfully reported it matched therefor was installed already.

New Post: Unable to publish updates due to WPP certificate problem

$
0
0
Hi there,

I have the following WSUS Architecture:
WSUS-Main -> Contains all the CAB files (works together with WSUS-SQL).
WSUS-SQL -> The database needed by WSUS-Main.
WSUS-Servant -> Gets patches from WSUS-Main/SQL so that it can deploy patches to Client Workstation
Client Workstation -> Gets patches from WSUS-Servant because of security reasons.

I had installed the WPP into WSUS-Main and WSUS-Servant and had used the WPP in WSUS-Main to generate the certificate. Then when I used that certificate on WSUS-Servant, it displayed a "You don't have any certificat,. You will not be able to publish updates".

Is there something that I am missing? I've already set all computers to install Locally Publish Updates, according to the Installation Guide.pdf

New Post: Unable to publish updates due to WPP certificate problem

$
0
0
Hi, I will assume that your Wsus-Servant is a Wsus Downstream server and Wsus-Main is the Upstream server.

Your workstations pulls updates from the downstream server, so the downstream server needs to get updates from the upstream server, so the downstream server needs to trust the upstream server.

You have to add the code signing certificate into the 'Trusted Publisher' store of the downstream server. If the certificate is an self-signed cert then the same certificate must be add to the "Trusted Authority" on the downstream server. Otherwise you have to add the certificate of the root authority that have issued out the code signing certificate, into the "Trusted Authority" . This will allow the downstream server to pull locally published updates from the upstream server.

If you want to locally publish onto the downstream server directly, you have to create a self-signed code signing certificate from the downstream server (don't forget to spread this certificate onto clients workstations).

I do recommend to publish only on the upstream server, because it's much more complicated to manage certificate otherwise.

New Post: Set a client's WSUS client service to debug mode

$
0
0
I suppose that the Wsus client have tried to compare "10.6.5162" with "10.6.5162.0" which is totally different (from the point of view of a computer :-) )

New Post: Publishing Issue Code 6BA

New Post: Set a client's WSUS client service to debug mode

$
0
0
Ha- I tried that out of desperation. The number the pack was comparing was 10.6 so I was rather urked when it still failed even after I changed the value in the registry to the same thing (10.6).

If any option would be helpful it would possibly be something that takes the deployment's Installable, Installed logic and compares it to a test machine(s) of your choosing (similar to Active Directory's Group Policy Modeling Wizard ) but this request would be a rather huge lift coding wise.

New Post: Can I detect when Windows Updates are finished ?

$
0
0
Is there an option that I could see if there are regular MS Updates are finished after I clicked Install Pending Updates ? or I just have to check it via Show Pending Updates ?



Best Regards,
Martin
Viewing all 3825 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>