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

Commented Unassigned: Manage Catalog Subscriptions greyed out? [300]

October 14, 2015, 7:37 am
$
0
0
I can't access the Manage Catalog Subscriptions as it appears to be greyed out. I've restarted the application and even rebooted the server with no luck. Any suggestions?

![Image](http://i.imgur.com/qMl1h5J.png)
Comments: That's not how I selected them the first time. I went to manage catalog subscriptions and just added them there. I did import them as you suggested so I could get the latest flash player, but it is still greyed out. I guess since I only have two, I can live with doing it this way.
↧
Search

Created Unassigned: "Update Level Rules" vs. "Package Level Rules"? [301]

October 14, 2015, 7:43 am
$
0
0
Have to make custom updates and have problems with the rules.

Is there any documentation about the difference between "Update Level Rules" and "Package Level Rules"? Which type of rules shoud be used for custom updates?

Thank you all in advance for any hint.
Franz
↧
↧

Commented Unassigned: "Update Level Rules" vs. "Package Level Rules"? [301]

October 14, 2015, 8:50 am
$
0
0
Have to make custom updates and have problems with the rules.

Is there any documentation about the difference between "Update Level Rules" and "Package Level Rules"? Which type of rules shoud be used for custom updates?

Thank you all in advance for any hint.
Franz
Comments: I have read somewhere an explication for why there are two type of rules (update and package level). At first, when Microsoft started to think about Wsus, they have imagined that a package can contains more than one update (InstallableItem). So, they have designed a package-level rule and an Update-Level rule. Each InstallableItem should have his own update-Level rule. Imagines a package to install Office. One InstallableItem contains the main file for Office, a second InstallableItem contains a patch to apply if Windows is installed in French, another InstallableItem contains the same patch for the English version and so on....
↧

Commented Unassigned: Manage Catalog Subscriptions greyed out? [300]

October 14, 2015, 9:17 am
$
0
0
I can't access the Manage Catalog Subscriptions as it appears to be greyed out. I've restarted the application and even rebooted the server with no luck. Any suggestions?

![Image](http://i.imgur.com/qMl1h5J.png)
Comments: Afair This happens when wpp is trying to check for updates (catalog and program). Afterwards you should be able to manage the subscriptions.
↧

Created Unassigned: Unable to distribute custom update [302]

October 14, 2015, 9:23 am
$
0
0
Try to create a custom package with WPP, but it doesn't work. It is for me much more complicated than I expected. The Update installation on the client immediately produces error 80131700

Should execute the following VB script on the clients for installing two fonts:


__Const FONTS = &H14&

Set objShell = CreateObject("Shell.Application")
Set objFolder = objShell.Namespace(FONTS)
objFolder.CopyHere "\\srv-file01\data$\fonts\*.ttf"

Dim objShell
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.Run("""\\srv-file01\data$\fonts\FontReg.exe""")
Set objShell = Nothing__

The script works fine interactive, and was successfully used in the past with SCCM SW distribution.

In WPP, tried to create a custom update with "execute script" as the action. included all the files in the package foleder (ttf font files, "install-fonts.vbs" which contains the commands above and also fontreg.exe)

---------------
I'm lost. Have read "Custom Updates.pdf" from the WPP documentation. It seems that "custom updates" are only usable with a "normal" Update package, which I haven't. With a normal update package, the wizard screen says that I can specify an EXE, MSI or MSP file, but not a cmd- or Vbs script file. Have the following questions:

1. Should I create a normal update package instead of a "custom update"?
2. Is it possible and supported to run "cscript.exe <scriptfile>.vbs as the command line for the update?
3. Should I create an "application" or "update"?
4. Is there any documentation available that decribes such SW distribution tasks with WPP?
5. Has anybody othe tipps how to accomply such tasks with WPP?

Thank you all in advance for any support.
Franz

↧
↧

Edited Unassigned: Unable to distribute custom update [302]

October 14, 2015, 9:24 am
$
0
0
Try to create a custom package with WPP, but it doesn't work. It is for me much more complicated than I expected. The Update installation on the client immediately produces error 80131700

Should execute the following VB script on the clients for installing two fonts:


__Const FONTS = &H14&

Set objShell = CreateObject("Shell.Application")
Set objFolder = objShell.Namespace(FONTS)
objFolder.CopyHere "\\srv-file01\data$\fonts\*.ttf"

Dim objShell
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.Run("""\\srv-file01\data$\fonts\FontReg.exe""")
Set objShell = Nothing__

The script works fine interactive, and was successfully used in the past with SCCM SW distribution.

In WPP, tried to create a custom update with "execute script" as the action. included all the files in the package foleder (ttf font files, "install-fonts.vbs" which contains the commands above and also fontreg.exe)

---------------
I'm lost. Have read "Custom Updates.pdf" from the WPP documentation. It seems that "custom updates" are only usable with a "normal" Update package, which I haven't. With a normal update package, the wizard screen says that I can specify an EXE, MSI or MSP file, but not a cmd- or Vbs script file. Have the following questions:

1. Should I create a normal update package instead of a "custom update"?
2. Is it possible and supported to run "cscript.exe <scriptfile>.vbs as the command line for the update?
3. Should I create an "application" or "update"?
4. Is there any documentation available that decribes such SW distribution tasks with WPP?
5. Has anybody othe tipps how to accomply such tasks with WPP?

Thank you all in advance for any support.
Franz

↧

Commented Unassigned: "Update Level Rules" vs. "Package Level Rules"? [301]

October 14, 2015, 9:28 am
$
0
0
Have to make custom updates and have problems with the rules.

Is there any documentation about the difference between "Update Level Rules" and "Package Level Rules"? Which type of rules shoud be used for custom updates?

Thank you all in advance for any hint.
Franz
Comments: Thank you for your explications! So, when I understand this correct: In WPP, does in makes no difference in practice if Update- or Package Level Rules are used? Kind regards, Franz
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 14, 2015, 10:30 am
$
0
0
I no longer have it showing up multiple times now. I think it was doing it because I was using the wrong Product Code. It kept showing up in Windows Update because the Product Code would never be found so it would always show up. The install would still work because the MSP file was smart enough to know the update was already installed.

To build the initial Adobe Acrobat Reader base, I followed the instructions in the Adobe Reader XI Deployment with Custom Settings (skipping the custom settings section). In other words, I extracted the Adobe Reader EXE (7zip), and uploaded the SETUP.EXE file in the Update Creation Wizard. I added the 5 additional files minus the MSP update file. If you view the PDF I note above, you'll start with Page 9.

Once you've published that (don't forget to use the MSI tool to get the product code), create another Update for Adobe Reader and add just the MSP file (use my instructions in the previous post to get it published). You'll create multiple of these as Adobe releases.

Do not use supersede. I was confused on that. Supersede means it replaces a previous update. That would be correct except Adobe doesn't repackage the downloadable executable into one file--i.e. all of their downloadable executables (for this year) will come with the MSI for version 15.007.20033 and an MSP for the update. What we were doing was superseding the full blown Adobe Reader with just the Update (MSP file)--i.e. kinda like trying to install Windows 7 from scratch with just the Windows 7 SP1 disc.

Hope this helps. I've been testing this quite a bit and it works flawlessly. I'm now tackling Java.
↧
Search

New Post: Non applicable Statut

October 15, 2015, 2:09 am
$
0
0
I had this happen once. I created a GPO to setup the computers to use WSUS to include adding WPP's certificate. For some reason, one of the computers was moved out of the container assigned the GPO so it did not have the settings any more. When I used WPP to check the status of the computers, one kept showing 'Not Applicable'. After I discovered this, I moved it back and the group policy settings were re-applied. If you used local policy, check and make sure the certificate and relevant policy settings are still intact. In any case, just passing this along.
↧
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 15, 2015, 2:55 pm
$
0
0
@triton53
i modified the package rules as in your comment from Tue at 11:14 PM
At first windows update Service found Adobe Reader DC 15.007.20033. After that it found update 15.009.20069 and installed to. But if i search now for updates again, the Adobe update will be displayed for Installation again.
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 15, 2015, 6:37 pm
$
0
0
My apologies for that. I did leave out some things so let's get you going as I've got a fully functional solution that handles Flash, Reader, and Java. You've got the base package done, so we don't need to worry about it. It sounds like you have the update almost correct as you only see it in Windows Update after the base has been installed.

I'm assuming you created the 15.009.20069 Update using the MSP file and did not add any other files when you built the update.
  1. Revise 15.009.20069
  2. Update Classification: SecurityUpdates
  3. Package Type: Update
  4. Prerequisites: 15.007.20033
  5. Next
    Msi Patch Installed For Product
  6. Patch Code: ac76ba86-7ad7-0000-2550-ac0f094e6500
  7. Product Code: ac76ba86-7ad7-1033-7b44-ac0f074e4100
  8. OK
  9. Delete Rules at Package Level
  10. Next
    Msi Patch Installed For Product
  11. Patch Code: ac76ba86-7ad7-0000-2550-ac0f094e6500
  12. Product Code: ac76ba86-7ad7-1033-7b44-ac0f074e4100
  13. Reverse Rule
  14. OK
  15. Delete Rules at Package Level
  16. Next
  17. Revise
That should do it. Let me know if it doesn't. When you approve both, if a client doesn't have the base (15.007.20033), WSPP will report the status for 15.009.20069 as Not Applicable since the client needs the base first.
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 16, 2015, 4:36 am
$
0
0
I created (step for step) the Packages as described by you.
Both packages Adobe Acrobat Reader DC - 15.007.20033 and Adobe Acrobat Reader DC - 15.009.20069 was installed sucessfully on the lab pc:
http://www.bilder-upload.eu/show.php?file=45052f-1444995716.png

After that Windows update search again and found the packges Adobe Acrobat Reader DC - 15.009.20069:
http://www.bilder-upload.eu/show.php?file=ab9a68-1444995852.png

In the package is only the msp file:
http://www.bilder-upload.eu/show.php?file=24a969-1444996129.png

Here the Details of my package for 15.009.20069:
http://www.bilder-upload.eu/show.php?file=acabed-1444996165.png
http://www.bilder-upload.eu/show.php?file=e2d374-1444996185.png
http://www.bilder-upload.eu/show.php?file=38a3da-1444996207.png
http://www.bilder-upload.eu/show.php?file=dd9601-1444996226.png

No idea where the error should be?!
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 16, 2015, 8:58 am
$
0
0
I bet Patch Code is the problem. Verify the patch code. Install patch on client, scan registry. There will be a registry entry for it. This update is checking for only 2 conditions. If it finds both conditions on the client, the update is already Installed. If not, it shows it in windows update. Sorry about missing that.
↧
↧

New Post: Adobe Acrobat Reader DC - MSP don't work

October 19, 2015, 6:50 am
$
0
0
In business inviroment, I recommend NOT to use the "Adobe Reader DC Continuous ( Base DC)". This product is for consumer enviroment.
Use the Adobe Reader Classic ( Base 2015). (Base installation: 15.006.30033 , MUI Updates: 15.006.30060 / 15.006.30094 ). This product is for business enviroment.
Why: only security updates, no feature updates, no "pay-features", GPO administation possible. No automatic updates.

I roll out the master installation manual with special config via WPP/WSUS, and all updates via WPP/ Adobe Update-Katalog. Its a 2-click rollout.

If you can read german ( with this nickname - i think so ) you can take a look in my documentation on:

http://road-books.jimdo.com/2015/07/09/howto-adobe-acrobat-reader-dc-2015-classic-track-angepasstes-software-deployment-mit-wsus-package-publisher/


maybe you see helpfull ideas.

enjoy it!
↧

New Post: Rules

October 19, 2015, 6:58 am
$
0
0
The configuration with OR and AND are difficult to handle with WPP.

If I use a ODER option in WPP ( for instant to check 32 / 64bit )

it looks like:

START OR

option one

option two

END OR


with no OR between the options. Maybee a srennshoot is helpfull to give more help.

Good luck!
↧
Search

New Post: NET Framework 4.6 Installation

October 19, 2015, 7:04 am
$
0
0
.NET. Hm. Interesting question. Never test it before.

because WPP need and use WSUS, why not deploy directly with WSUS?

We need more information, error codes and so on.
↧

New Post: greenshot upgrade

October 20, 2015, 12:50 pm
$
0
0
We have Greenshot installed for our users as a replacement for the sniping tool, and it works very well.

I'm having some trouble deploying an update, however.

Greenshot is running in the test user profile and I can't seem to turn it off from the WPP package. I've tried with bundling or calling a simple powershell script from a custom update and it doesn't seem to do anything. If I run the script manually from the test user it shuts down like I expect.

"Get-Process Greenshot | Stop-Process -Force"

Does anyone have any pointers?
↧
↧

New Post: Java Update mit deinstallation der alten Version

October 21, 2015, 2:11 am
$
0
0
Hallo zusammen,

wir benutzen WSUS Package Publisher vor allem zum Verteilen der Updates von Flash und Java.
Bei den Adobe Produkten kommt der Updatekatalog zum Einsatz und funktioniert reibungslos.

Das Vorgehen für die Updates von Java ist ziemlich klar und funktioniert.
Allerdings wird bei einem Update die alte Version von Java nicht gleichzeitig deinstalliert - gibt es hierfür eine Lösung?


Momentan warten wir dann eine gewisse Zeit und geben dann die alte Version zur Deinstallation frei.
Der Grund warum wir das nicht mehr wollen ist einfach. Wir müssen in den Java Einstellungen einige Seiten zu den Ausnahmen hinzufügen - durch die jetzige Methode werden die Einstellungen nicht übernommen und wir müssen doch wieder an jeden PC ran.

Installiert man die Java Version manuell an einem PC werden die Einstellungen übernommen UND die alte Version deinstalliert.

Hier noch eine kurze Beschreibung wie wir Java installieren
  • Java wird manuell an EINEM Arbeitsplatz installiert damit man die MSI Datei erhält
  • Die MSI Datei holen wir aus dem AppData\LocalLow\Oracle\Java Verzeichnis
  • Wir erstellen ein "ersetzendes" Update der vorherigen Version
  • die Verteilung an die Workstations lösen wir über die Computergruppen (*)
  • In den Regel ist ansonsten nur eine MSI Nummer enthalten
(*) leider wird die Regel bei einem ersetzenden Update nicht übernommen)

Gruß Markus
↧

New Post: .msp files now longer work for Adobe Reader XI

October 21, 2015, 7:26 am
$
0
0
Dear Community,

we have a standard image for our clients which includes Adobe Reader 11.0.10 MUI.
On WPP we've created an update package via .msp file for version 11.0.11 (MUI) which runs perfectly.
Meanwhile Adobe released update versions .12 and .13, but neither .msp file will show up in Windows update.
We've created the packages in the same way as for version 11.0.11, the WSUS report shows installs for approval and not applicable for status.
Any thoughts or ideas?

Thanks in advance
-Andreas-
↧

New Post: .msp files now longer work for Adobe Reader XI

October 21, 2015, 3:29 pm
$
0
0
I have noticed that .12 and .13 do not report as needed if you use the Adobe SCUP catalog or you create a standard update package. However, the msp file will install OK manually. I ended up creating custom scripted packages like this:

@echo off
call msiexec.exe /update "%~dp0AdbeRdrUpd11013.msp" /quiet /norestart
exit /B %EXIT_CODE%

I tried to troubleshoot the metadata in the msp file but it is beyond my capability.

-Jim B.
↧
Viewing all 3825 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>