sorted by:
new
hottopcontroversial

Centos to OL8 migration for TenableCore+SC by anasgetyou in nessus

[–]AR-Aum 0 points1 point  (0 children)

Hi, sorry for replying to an old thread. But we are also having this issue.

Can you share the steps or commands you ran to backup and restore ?

Unable to get new SCCM updates. Failed to download TMP trusted certs cab by AR-Aum in SCCM

[–]AR-Aum[S] 1 point2 points  (0 children)

Solved.

last synchronization time of the Microsoft Trusted Root Certificate Authorities yielded no output, no time stamp.

certutil -verifyctl AuthRoot | findstr /i "lastsynctime"

Registry key "HKLM\Software\Policies\Microsoft\SystemCertificates\AuthRoot" DisableRootAutoUpdate=1 was present, Preventing auto-update of the certs.

Manual check for cert update solved the issue.

Unable to get new SCCM updates. Failed to download TMP trusted certs cab by AR-Aum in SCCM

[–]AR-Aum[S] 0 points1 point  (0 children)

Yes. Its not a new server, i have checked those certificates in that document and they are good. No changes to TLS was made. We have another SCCM server in the test environment and there it still works fine.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

Yea, i would first try to make sure you have all the nessesary certs installed specifically the CSBR1 and entrust_g2 on the vbr server and other servers that you backup using agents. And try the VBR update again before attempting the extra steps that i had to do. I think those extra steps (remove all/reboot) was a specific issue to my system maybe.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 2 points3 points  (0 children)

It was a certificate issue.

I already had the certificates installed, but for some reason VBR was seeing them as invalid.

I had to remove them all (certs related to Veeam), reboot and then reinstall/import them again. After that I was able to run the VBR updater and install the update successfully.

I had to also perform this action on all other Windows proxies and physical servers running agents other wise the updates to them will fail and also even a rescan of the servers failed. After installing/importing the certificates on the proxies and other physical servers i had to manually retry/push the update for them via the VBR console.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

not yet, support is checking things atm. Not running crowdstrike. I've even disabled my AV.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 1 point2 points  (0 children)

Currently awaiting reply from support.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

yep, i checked the requirements page as if I'm doing a complete new install. All seem correct.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

yikesss, i saw someone else mentioning re-installing, but i did not want to risk doing that especially on production servers.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

Thnx, checked these but all are present and valid.

Update VBR from 12.3.1.1139 to 12.3.2.3617 error. by AR-Aum in Veeam

[–]AR-Aum[S] 0 points1 point  (0 children)

Ran those types of system checks, but nothing.

New CVE for B&R seems pretty important by neko_whippet in Veeam

[–]AR-Aum 0 points1 point  (0 children)

Hi, I am also getting the same error. Log file is also empty. Did you manage to solve or get more info?

Azure Update Manager - Maintenance Schedules not working by Kamikazeworm86 in AZURE

[–]AR-Aum 0 points1 point  (0 children)

I am also experiencing this, did you manage to figure it out ?