solarwinds-admin

As long the installation is a single EXE, MSI, or MSP and can be installed completely silent, then yes.

The cause of this particular problem with Ibrahim was that MSI was not working on the machines showing this error. Re-registering MSIEXEC resolved the problem. From a commandline run MSIEXEC /REGSERVER -Sean

You can rebuild the <Default> credential ring using the Credential Ring Wizard. Start the wizard, enter the name <Default> into Step 1, add the necessary credentials from the stored collection in Step 2 and Step 3 of the first screen, and then map those credentials to the domain, workgroup, and WSUS server resources they…

Good question. A exclusive update is an update that must be installed by itself. IOW, if you pick it, it HAS to be the only one you pick. Also, there is an option to ignore exclusive if you are using the Update Management Wizard. It is on the second page of the wizard. If you tell it to, it will ignore exclusive updates.

What "Date Range" are you interested in filtering by? [a] Release Date, [b] Approval date, [c] Installation Date? The base level report for this data is in the Computer Update Status report in Windows Server Update Services Analystics. The only thing missing from that report is the desired date range. Arrival Date and…

Hi Oerlemans, if you look in the EminentWare installation directory under the server folder, there should be some log files (the extension ends with .log). Please zip the log files up and email customersupport@eminentware.com and we will have a look. Please also include your contact information. Thanks for your patience.

Hi Fabry, Can you run the 'Server Publishing Verification Wizard'? That may give you details on where the problem might be. Thanks, Sean

We do have a tool that will export some of the 3rd party package info from WSUS. The files can then be made into a .cab which can be imported as a catalog back into EminentWare. Please send an e-mail to customersupport@eminentware.com, and we can discuss how the tool works and what the limitations of the tool are. -Kelly

We need to have a look, so please email Customer Support with your availability. One thing that comes to mind here is that the version you are installing on the DMZ env. is NOT based on EW-CDS-004. If it isn't, please download the latest EW-CDS-004 version of the full installer.

The service account needs to be an administrator equivalent on the target machine. Also, if you are performing reboot along with the update management task, you will need to ensure that the account has "Remote Shutdown' user rights (which Admins have by default)

Yes, in fact, there are several datasources in the WSUS Analytics report category that contain group membership information. The datasources Approved Updates Installation Summary Info By Group, Approved Updates Installation Summary Info With Approval Details, and Computer Update Status With Approval Information contain a…

Hi cteague, What version of SQL are you running for the EminentWare database? If it is the one that is installed by default with the product (SQL Server 2005 Express), there is a limit of 4GB for the database. it is possible that you are hitting that limit. Another possibility is disk space could be full on the drive where…

Hi Dan, Typically that error means just that - the Prerequisite or Applicability rules for those particular clients are not evaluating as TRUE, and therefore the WU agent evaluates the update as Not Applicable. I'd review those Rules against one of the clients you are attempting to update. -Kelly

Hi Jeff, Is this a Win2k machine? If so, we have a new provider version that should address this. John

The fix in KB226417 provides no features with regard to the MSU functionality; nor did this update introduce the MSU packaging capability. The MSU and WUSA.EXE capabilities were created with the release of Microsoft Windows Vista in 2006. MSU files were created expressly for use with the standalone WUSA.EXE utility for…

Hi Paul, To answer your first question, you could co-locate the Extension Pack with a Site Server - under certain conditions. Please reference our deployment guide, which has a wealth of information on planning your Patch Manager deployment. The trial is fully functional - the only limitation is that the 3rd Party content…

Greetings Pam. I would offer two possible approaches, but both involve the same fundamental setup. Step 1: Create a WSUS Target Group designed to hold machines with new OS installations. Approve ALL current and valid OS updates for this target group. From there, you have two approaches, one requires the Extension Pack, the…

The easiest way that I can think of is to log on to the EW server and fire up a command shell, change directories to c:\Program Files\EminentWare\Server\templates\cmdb, and then do a 'dir /S *.xdq' - perhaps piping the output to a file. Currently, we don't have any great documentation on reporting. There is some…

Your approach is solid, and you are correct that approvals only apply to WSUS Target Groups. However, Patch Manager doesn't provide a way to manage WSUS Target Group memberships, except from an existing WSUS Target Group. So, you can use the report to identify the machines, but you'll need to select them from the existing…

Any update as to when these are likely to be released?

Hi Russo1203, That is interesting; crossing datasources isn't supported, and wasn't supported in the past although it appears it may have been working for you in some cases. If you or someone in your org has SQL skills, it is possible to write SQL queries to query the EW database directly, and we also expose all the SQL…

Hi Taylorje, This will allow the end user to have the choice to accept installing the update vs having the windows update agent install it automatically at the schedule install interval set in the windows update policy. -Sean

Hi easservciemgmt, If you enable logging on a client and attempt the update, afterwards in the Windows\SoftwareDistribution\Download\Install folder on that client you should see a packageboot.exe.xxxxxxxxxxx.xxxx.xxxx log file that has details on the operation. To enable logging on the client, you'll need to edit the…

Hi Brad, To clarify, EminentWare does not really act as a repository for any updates. For the MS updates, the WSUS server still houses the update content. For third party updates, the ‘Publish’ action transfers the file from the EminentWare server to the WSUS server. If you have downstream servers in the remote locations,…

Mark, this error is indicative of an SSL issue. If the WSUS server has SSL enabled and the ExtPack WSUS Server registration is using port 80 or 8530, this is an expected result. I emailed you instructions on how to change the console registration from port 80 to 443 to faciliate an SSL-enabled connection. You'll also need…

It tells whether an older revision of the update contains an approval.

Yes. Under EminentWare System Configuration-> Management Groups -> Managed Enterprise -> Setting (tab) there is an option to disable automatically provisioning the WMI providers.

What version of the Extension Pack do you have installed? From the EminentWare (root) node, click on Version.

Hi Jay, No, we can collect some data from Event Logs on Windows Update and Update Services Server Events, but not for specific Event IDs. You may wish to take a look at a new feature in Windows Server 2008, Event Log Subscriptions - but it is not available on Windows Server 2003.

Greetings Jason. The MSRT updates are cumulative "updates". (Actually it's just a scanner with a regularly updated data file.) You should decline the older MSRTs and approve/deploy only the latest update. The updates have supersession links, but they only go back for a few months, so that would explain something as old as…