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

New Post: Unable to connect to local server

$
0
0
I am running WPP on the WSUS server.

Should I run WPP remotely?

Also, Load a certificate is greyed out so I am unable to load a cert. I am also unable to create my own certificate (that's the reason for my post).


As you can see below, I am connected to my WSUS and this IS running on the WSUS server itself.

This is my Manage Certificates
Image

This is what happens when I click on Generate Certificate
Image

New Post: Unable to connect to local server

$
0
0
Also, Load a certificate is greyed out so I am unable to load a cert.
Fill the 'Password' textbox and the button will not be greyed out anymore.
I am also unable to create my own certificate . This is what happens when I click on Generate Certificate
This is because, you didn't have checked the checkbox "Connect to local server". "Local" needs to be displayed aside of the server name.

New Post: Unable to connect to local server

$
0
0
DCourtel,

My whole issue is I cannot check "connect to local server" and connect. I will try and upload a certificate and see what happens.

New Post: Unable to connect to local server

$
0
0
Can I remotely connect to your Wsus server via Teamviewer or other tool ?

New Post: [Solved] Issue deleting products

$
0
0
I'm having the exact same issue. I'll send the logfile to you...

New Post: Auto Deletion of Updates and Failing in Windows 8

$
0
0
Dear Team,

Kindly suggest me on these issues,

->. We have been recently started pushing Windows 8, 8.1 machines in production and WSUS package publisher is used to push custom updates, but updates are failing in Windows 8 whereas no issues in Windows 7 (running perfectly). Tried with clean, reset of updates folder and WU service and .NET Framework 3.5 installation but with no success.

FYI:
Server OS: Windows Server 2008R2
WSUS Version: 3.2.7600.256

->. Old published (inactive) updates are getting auto deleted

New Post: Auto Deletion of Updates and Failing in Windows 8

$
0
0
In WSUS-FAQ No. 44 http://wsus.de/faq you will see which updates for your WSUS you are missing:

WSUS 3.0 (SP2) + KB2720211: Build 3.2.7600.251
WSUS 3.0 (SP2) + KB2734608: Build 3.2.7600.256
WSUS 3.0 (SP2) + KB2828185: Build 3.2.7600.262
WSUS 3.0 (SP2) + KB2938066: Build 3.2.7600.274

Pls install Updates your WSUS is missing, after this restart W8.1 Clients and try again. If it is failing again, post the last 50 Lines from the local %windir%\WindowsUpdate.log.

New Post: "reactivate" a replaced package

$
0
0
Hello,

is there a way to change the "Approved (Replaced)" status to "Approved" when the option replace was a fault?

New Post: "reactivate" a replaced package

$
0
0
Hello,
Yes. Revise the supersedes update, and untick the checkbox aside of the superseded update (in the list of updates).

New Post: Auto Deletion of Updates and Failing in Windows 8

$
0
0
Does it only occurs with Custom Update (regular update from WPP are working) ?
If yes, it's probably because your clients are unable to run CustomUpdateEngine.exe (which is compile in .Net Framework 2.0)

Try this :
  • Open WPP
  • Connect to your Wsus server
  • Select a custom update
  • On the information tab, click on the 'ID' link. This will open a explorer window
  • Open the folder and search for CustomUpdateEngine.exe
  • Copy it on an USB key
  • On a Windows 8 client that have this problem, run the CustomUpdateEngine.exe and see what happen

New Post: "reactivate" a replaced package

$
0
0
i have tried this - but status is still "Approved (Replaced)". On the information tab of the superseded updated the "is superseded" checkbox is still active.

New Post: Auto Deletion of Updates and Failing in Windows 8

$
0
0
Apologies for the delay in reply.

Allow me some time to provide you with results after running CustomUpdateEngine.exe

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

$
0
0
I'm running Windows 8.1 on my adminstrative machine and Server 2012 R2 for my WSUS server. Should be identical versions of the console and in fact it is when I check the versions. Both show they're on 6.3.9600.16384, but I still get the error in WPP. Thoughts?

I realize I could run it directly from the WSUS server, but I'd rather not do that if I don't have to.

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

$
0
0
Yeah my server is too, but my client appears to be a step ahead somehow.

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

$
0
0
IMHO should you use WPP ONLY directly on the WSUS. Is this not possible?

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

$
0
0
It is currently. I was considering running without a GUI on that server so I would be prohibited from doing that. I also would prefer not to have to RDP first to do administration.

New Post: How to deploy msi files together with msp files that need FULL path? (e. g. Adobe Reader XI)

$
0
0
A Workaround is to use a network share (e. g. the wsus content share) to store the .msp files. In this case they must not be added to the wpp update.
It works with a command line like this: TRANSFORMS="reader11.mst" PATCH="\\server1\wsuscontent\share\patches\AdbeRdrUpd11010.msp"

But what about the Support of some variables for the command line of the wpp updates? In my tests from cmd it worked with PATCH="%CD%\AdbeRdrUpd11010.msp" so why can't this work with the wpp updates too???

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

$
0
0
I get the same results if I run WPP directly on the WSUS server. Does that make any sense?

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

$
0
0
If I check the setting to connect to local server I don't get the error. If I look at help-->About it shows the exact same versions I saw from my client though.

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

$
0
0
I've just seen that on my Wsus server, I have server version = 6.3.9600.16384 and console version = 6.3.9600.17477
It's kb3013769 that doing this update of the console but not the server !

When you check the option "Connect to local server", WPP connect to the same machine where it runs and don't check for console version, it assume that console version and server version will be the same.
It's the first time I saw this. KB3013769 change the game.
Viewing all 3825 articles
Browse latest View live


Latest Images

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