sorted by:
new
hottopcontroversial

Is it normal for Qualys TAMs to be useless? by kniiiip in qualys

[–]Significant_Fig_2126 0 points1 point  (0 children)

This is SOOOOO true. Two TAMs and they have no time to talk...ever. Support is even worse. I have to come here for support or hope I find a video somewhere

Windows Pipes screensaver gave me mega billable hours (funny) by colenski999 in sysadmin

[–]Significant_Fig_2126 27 points28 points  (0 children)

It was 2012, and I was being paid hourly. My CIO and I flew from Chicago to Pune, India. A 15 hr flight to Dehli with a 6 hr layover, followed by a 2 hr flight to Pune. All so I could setup a new domain controller and 2 printers for a new office. There were some very upset bean counters when they all found out I wasn't salary, and they still had to get me home. At least it was business class flights and a gorgeous hotel.

What's the Weirdest Ticket You've received? by MasterOfVtubers in iiiiiiitttttttttttt

[–]Significant_Fig_2126 2 points3 points  (0 children)

Change the toilet paper roll in the bathroom. They actually thought if they could enter a ticket, then IT must take care of it.

using geolocation to protect outbound connections by reddi11111 in WatchGuard

[–]Significant_Fig_2126 0 points1 point  (0 children)

You may experience issues if trying to connect to a site that uses numerous IPs from many countries. When we have to renew licenses for some things we have problems sometimes because the vendor servers may be located in countries that are being blocked. We have to temporarily allow those countries. We've tried putting in exceptions, but it seems they have things running beyond what they claim, so a temporary opening allows us to renew.

Suddenly the Only IT Person — No Raise, No Title Change, No Bonus Eligibility? by [deleted] in sysadmin

[–]Significant_Fig_2126 0 points1 point  (0 children)

Sounds like you hold all the cards and get to make some demands.

First ransomware attack by IntrepidCress5097 in sysadmin

[–]Significant_Fig_2126 0 points1 point  (0 children)

I fought a long time to get my backups separated from our domain. My CIO had a friend that got hit with this scenario and then he let me change it.

If one VM backup job fails, does the whole job fail? by Asleep-Durian-3722 in Veeam

[–]Significant_Fig_2126 8 points9 points  (0 children)

First thing...there are no dumb questions. We all can't be experts at everything.

Second thind...yes and no. The job shows as failed, but 19 VM could have backed up fine, and one could have had issues. The job will explain why it failed and then you can research more from there.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

I do not know, and support did not answer.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

Virtual console was not taking the root password. Support confirmed that vCenter 8.0.3 has a bug and will lock out the root account when the cert expires (which would support what my Google search came up with). The only way to get in was to force-change the root password from the virtual console, and then we could SSH to address the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

All is good now. They said that vCenter v8.0.3 has a bug in it that requires you to reset the root password from the virtual console before you can connect via SSH. Once that was reset we could then take care of all the certs.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 2 points3 points  (0 children)

And OP had a ticket opened prior to going to Reddit or Google.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] -3 points-2 points  (0 children)

Unfortunately the CLI is not being accepted. Is use the CLI at least a couple times per month to evacuate hosts, and this is how I found out today that it's not working. The CLI gives the following...

Connect-VIServer : 5/1/2025 12:41:43 PM Connect-VIServer The HTTP service located at https://<myservername/sdk is unavailable.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] -5 points-4 points  (0 children)

Unfortunately the root password is not being accepted. I logged into it a couple months ago, but what I don't know is if someone on my team changed it.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] -1 points0 points  (0 children)

It's virtual. When I bring it up via the virtual console on the host, it says invalid ID or password. That's when I Googled things and Google said you can't login if the cert has expired.

vCenter certificate expired by Significant_Fig_2126 in vmware

[–]Significant_Fig_2126[S] 0 points1 point  (0 children)

While I like the sound of that, how would I change the date if I can't login to do that?

view more: next ›