[doug]

Hi Erwin – 1611 is a BatchPatch internal code, not a system error code. The important number here is the 64, which means

ERROR_NETNAME_DELETED

64 (0x40)

The specified network name is no longer available.

The questions I have for you are:

1. What version of BatchPatch are you using? Does the problem occur with the latest version of BatchPatch?

2. Are you using Integrated Security or are you specifying alternate credentials for the hosts in question?

3. What OS are you running BatchPatch on?

4. What OS is running on the problematic target host?

Something appears to be causing the network connection to be severed before BatchPatch finishes its work. However, it’s unclear what that might be. Maybe some type of host intrustion protection software running on the target? I’m not sure.

Thanks,

Doug

[doug]

The uninstallation method used by BatchPatch invokes WUSA.exe, which does not exist on Windows 2000, 2003, and XP.

You can uninstall an individual update on these OSes by executing a ‘Remote Command’ action in BatchPatch with the following syntax:

C:WINDOWS$NtUninstallKB1234567$spuninstspuninst.exe /quiet /norestart

[doug]

This is definitely an odd issue. There is either an problem with the update file itself or with the windows updates database information about the particular update. You might have success in fixing the problematic update if you stop the wuauserv service, then rename the C:WindowsSoftwareDistribution folder, then start the service.

However, as a workaround for right now, I believe you should be able to hide the particular problematic update using BatchPatch Windows Updates > Hide/unhide action, after which you would then be able to continue installing all the other updates. You can later unhide it if you wish.

Separately, in the next release of BatchPatch we will modify the code so that instead of failing to install all updates, when an issue like this is encountered it will simply skip the problematic update and continue installing the other updates (in most cases it already does skip issues like this, but for this particularly case it does not, apparently).

Thanks

Doug

[doug]

camadatacom – jday_23 never responded to my email, and no one else reported it, so we were unable to test or troubleshoot further. I will email you so that we can work on the issue more directly.

Thanks,

Doug

[doug]

Thank you for reporting this error. It has been fixed in the build published 8/13/2014.

Thanks,

-Doug

[doug]

The only other currently available method for export of the grid would be to just highlight the entire grid and use ctrl-c to copy it. You could then paste it into Excel and do whatever you want with it from there.

Additionally, you could save the grid to a .bps file using File > Save. The .bps file is pure xml, which means that it can be loaded into a spreadsheet app like Excel, or a database.

We are considering more options for a future version, including database interaction of some kind. However, at the moment this is not available in the currently published build, and I’m not sure what the timeline is for it to become available or if it will definitely become available.

-Doug

[doug]

The consolidated update history report is designed to simply report what updates have been installed/uninstalled on target hosts. If you want the actual BatchPatch activity for a given session, you can export the actual BatchPatch grid to a .html file. When you initiate a Windows Update action in BatchPatch, the log info that is written to the BatchPatch.log file is also written to the Remote Agent Log column in the BatchPatch grid. If you make sure that this column is visible and then select File > Export grid to HTML file, you’ll get the information you’re looking for.

I hope this helps.

-Doug

[doug]

I emailed you directly to troubleshoot the issue.

Thanks,

Doug

[doug]

Hi DJ – the tab names are based on the saved .bps files. So if you simply save a tab to a .bps file, the tab name will take on the actual file name. Does this suffice for your needs?

[doug]

1. Highlight your hosts in the grid and select Actions > Execute remote process/command > Create/modify remote command 3 (logged output)

2. In the command window type the defrag command that you want, such as: defrag c: -v and then click OK.

3. With the same hosts still highlighted, select Actions > Task scheduler > Create/modify scheduled task

4. From the task drop-down list in the scheduler window, select Execute remote command 3 (logged output), and then select the run time and recurrence options that you would like. Then click OK.

5. The last thing you need to do is enable the scheduler. Click on the small clock image in the upper right corner of the BatchPatch window to enable the schedule.

[doug]

Yes, it will support PowerShell scripts too. We expect it will be published probably within the next 6 weeks.

Thanks,

Doug

[doug]

Hi Lee – We’ll do some more testing here to see if we can reproduce it and also determine why it’s happening. Thanks for the additional info. I’ll contact you and post more info in this thread if/when there is anything to report.

-Doug

[doug]

Hi Lee – This is unexpected. The Windows Update Agent maintains the database on each machine that contains the information about what updates have been installed or uninstalled. In the case of the “Uninstall individual update” action, BatchPatch uses WUSA.exe to uninstall the update. In the Update History Report, “wusa” would normally appear in the ‘Application’ column next to the entry for the uninstallation of the update. I don’t know why it wouldn’t show in your case. Outside of rebooting the machine after the uninstallation to make sure that the uninstallation is committed to the database, the only other thought I have is that perhaps you weren’t sorting properly in the Update History Report and maybe you were expecting to see the ‘Application’ as BatchPatch when in reality it will be listed as ‘WUSA’ ? BatchPatch doesn’t actually commit changes to the database itself. The Windows Update Agent makes the changes. I’m sorry to say that I’m unsure why that change wouldn’t have been committed in your case.

-Doug

[doug]

Hi Eric – please read through the details of this thread. Error 2 Very Often – Server 2012 R2

Let me know how it goes…

Thanks,

Doug

[doug]

Strange. BatchPatch retrieves the LastBootUpTime and LocalDateTime properties from Win32_OperatingSystem to calculate the uptime. Somehow the machine was in a state where Win32_OperatingSystem wasn’t reporting the correct values, but I have no idea why/how. I’ve never seen that happen before. Glad to hear that rebooting fixed it.

-Doug

[doug]

Hi Stuart – It sounds like you’ve got everything configured the way that it needs to be. If the firewall is disabled on the destination computer and the RPC service is started, then there is no (logical) reason for you to receive “RPC server is unavailable.” So, you may be correct that there is a timeout issue. Or perhaps there is some type of other issue such as the one described here: https://support.microsoft.com/kb/935677

I wish I had another suggestion, but unfortunately it really does sound like you have everything configured properly, so I’m not sure what else to make of it. You might consider checking in the target computer’s event log to see if there are any indications of what might be happening or if a connection is ever being attempted. Another thing you could try is to run a packet capture utility like Wireshark on the target system to see if you see the connection attempt.

-Doug

[doug]

The way this will be addressed in the next build is through the Deployment action. You will be able to choose “Actions > Deployment” to deploy a script just like you can already do, but there will be an additional checkbox to “retrieve logged output.” When that box is checked, not only will BatchPatch copy the script from wherever it’s located to the target computer for execution, but upon completion the output of the script will be returned back to BatchPatch for viewing.

-Doug

[doug]

Note – PsExec v2.1+ now uses an encrypted channel for communication between the source and destination computers. Passwords are NO LONGER sent in clear text, which is very cool. This means that using alternate credentials in BatchPatch is no less secure than using integrated security.

-Doug

[doug]

Thanks for letting us know about this. We’ll see what we can do to address it in the next build.

-Doug

[doug]

Cory determined that the issue appears to be resolved after manually the running Windows Update GUI on the problematic machines, installing the updates, and rebooting. After that, BatchPatch once again worked normally.

At this time, it’s not clear exactly what the cause of the problem was/is, but I will update this thread if/when there is more to report.

-Doug

[doug]

Cory – I’m going to email you so that we can iterate more easily. Once we’ve gotten to the bottom of the problem I will post an update here in the forum.

-Doug

[doug]

Cory – When you say “no longer wants to check for updates” what do you mean? Could you please provide details?

Is there an error? If yes, what is the exact error text?

Additionally, do you see a BatchPatchError.log file on the target machine in the remote working directory? (this directory defaults to C:Program FilesBatchPatch, if you haven’t modified it)

What happens if you run the Windows Update GUI (from control panel) manually on one of the problematic machines? Does this work as expected?

The more information you can provide, the more likely I’ll be able to help you. At the moment, however, I simply don’t have enough information to go on. There is no reason that I am aware of why things would all of a sudden stop working on your 2003 machines. Nothing changed in the BatchPatch code that would prevent it from working, so I suspect there is something that changed in your environment.

What version of BatchPatch are you using? (Help > About)

Are you using WSUS?

Thanks,

Doug

[doug]

This is odd/unexpected. My guess is that the termination itself might not have completed and that BatchPatchRemoteAgent.exe is actually still running on the target. The reason I say this is because I can’t think of another reason why there would be an access problem all of a sudden. It seems like the Remote Agent is still sitting there and Windows has it open/running, so it can’t be overwritten. This is similar to the behavior that I would expect if you tried to delete an open Word document, for example. I would start by rebooting the target machine and see if that does the trick. Let me know how it goes.

I know you said other actions appear to work, but if that doesn’t fix it, could you please test “Services > List all services” and let me know if that also doesn’t work, and if so what is the error message?

Thanks,

Doug

[doug]

Hi Stephen – This will be fixed in the next release.

Thanks,

Doug

[doug]

nolant – Yes, you can simply disable a row (or rows) that you don’t want to execute. Actions (or right-click) > Disable/enable row(s). After you’ve disabled the rows, wait X seconds, where X is the number of seconds you’ve set the Row Execution Interval to be, and all will be skipped. When the execution thread reaches a disabled row, it immediately moves to the next row (instead of waiting for the Row Execution Interval time to pass), so if row 1 is executing and you disable rows 2-10, once you wait the 30 seconds (or whatever the REI is), all disabled rows will be looked at and skipped immediately.

-Doug

[doug]

Vince – We’re working on improving error codes, and we generally try to put descriptive text next to errors whenever possible. In this case, the issue is just that you need quotes around you query, so exit code 1 is signifying Invalid Syntax:

So, for this to work for you now, try: “HKLMSOFTWAREMicrosoftInternet ExplorerSetup”

We will get this fixed in the next build so that quotes won’t be necessary. This was an oversight in the code.

Thanks for making us aware.

-Doug

[doug]

Tony – Great news is that the latest version of PsExec (v2.1 published in March 2014) actually sends all data over the network via an encrypted channel, so this is no longer an issue!

http://msdn.microsoft.com/en-us/library/bb897553.aspx

-Doug

[doug]

Thanks for the feedback and suggestions. At the moment we don’t anticipate any integration with Royal TS.

-Doug

[doug]

Excellent. Glad you got it working. Thanks for letting me know.

-Doug

[doug]

vinceco – I’m sorry that you’re having problems with importing old .bps files. There were some changes made to the 2014.5.2.9.48 version that could have caused this. In any case, if you simply create a brand new .bps file from scratch with this new version of BatchPatch, those problems should disappear.

As for ways that you can share lists of computers, there are a couple:

1. You can use .bpt files instead of .bps files. With the new BatchPatch Template (.bpt) format, you can create a single .bpt file and then load it multiple times to create multiple identical tabs in an instance of BatchPatch. BatchPatch won’t let you save over a template file, so when you click the save button you’ll be prompted to save a new .bps file for the grid. You can create your own .bpt files by simply renaming existing .bps files, or you can use the File > Generate template file (.bpt) menu option to create a .bpt file from a BatchPatch grid.

2. You can use simple .txt files. If you drag and drop a .txt file onto BatchPatch, it will load those hosts into a BatchPatch grid.

I hope this helps. Let me know if you have any other questions or problems.

Thanks,

Doug

[Author]

Posts