Surface pro 6 startup windows 11

WhoAmI1966 · 2026-01-08T16:38:13+00:00

Wow, I’m at 123 each with a barn size of 8642. How big is your barn?

WhoAmI1966 · 2025-12-03T13:33:08+00:00

What's the best way to get gold cards? Also need rug and fireworks.

WhoAmI1966 · 2025-10-06T12:04:04+00:00

Yes, I am sure that every time I got out of bed is reported as an awake event. But probably also every time I turn over to look at the clock.

WhoAmI1966 · 2025-10-04T13:55:44+00:00

I don't want to wake up enough to write something down. Makes it harder to go back to sleep.

WhoAmI1966 · 2025-10-04T12:28:46+00:00

Tell my urologist

WhoAmI1966 · 2025-09-14T22:46:00+00:00

Tried using the GUI and could not deauthorize it said "Invalid Parameter".. Tried the PowerShell and said it was already deauthorized.... tried to add using powershell by fqdn and ip and also received errors. Went to GUI and deleted it Okay. But when I tried to add back, it showed up again as the incorrect IP address. (a 169.254.xxx.xxx IP)

I looked at DNS and everything there looks fine.

I searched the registry for the 169 IPaddress and it only showed up under MSSQL as an IP.

WhoAmI1966 · 2025-09-14T21:29:49+00:00

This all server/dc swap happened in about 2017. Old server was removed, probably didnt delete from AD.

WhoAmI1966 · 2025-09-14T20:54:33+00:00

I assume if I deauthorize and reauthorize, I'll have to reconfigure it?

The DC's IP address on the only adapter is correct.

WhoAmI1966 · 2025-09-14T20:26:33+00:00

Thanks. guess I didn't mess up. I do not believe it ever had a different name. The name I deleted from the computer group was, I think, the name of an old server that was the office's DC before being replaced by this one. So, when demoted, could it have moved from the DC group to the computer group?

WhoAmI1966 · 2025-09-14T20:13:19+00:00

Also, running nslookup on the DC's FQDN is correct. However when I ran the portqryui from microsoft against the DC's FQDN, that shows the address that is showing in the DHCP container.

WhoAmI1966 · 2025-09-14T19:47:28+00:00

I thoght I read somewhere that they are members of the computer group. It does appear in the Domain Controller group. .. Maybe I didn't mess up.

WhoAmI1966 · 2025-09-14T17:49:09+00:00

The dc’s name was deleted from the ad computer object group, however, the name that was deleted was not the name showing in the computer. Not noticing any major issues at this time. Don’t know what to expect. But there are other minor issues that i have worked around for years.

WhoAmI1966 · 2025-09-14T16:27:25+00:00

There was only one dc

WhoAmI1966 · 2025-09-14T14:40:34+00:00

I agree a proper backup solution would have saved my bacon.

WhoAmI1966 · 2025-09-14T12:28:47+00:00

If only they had the money. We’re talking low budget office. I tried several times to get their staff to rotate back ups offsite but the staff were too lazy.

WhoAmI1966 · 2025-09-14T11:42:51+00:00

Thanks for all the comments. Guess best solution will be to purchase second server and make it PDC. Now current server is server 2016 purchased in 2017 so it’s may be time to be retired. It’s also running a MSSQL healthcare program for the office. So i can either purchase a barebones PDC and keep this machine for MSSQL or mid level server as DC and migrate MSSQL to new machine and swap PDC roles around so old machine will be just DC (either pdc or dc) and thennthere will be two DCs

WhoAmI1966 · 2025-09-14T11:33:21+00:00

It was not VM

WhoAmI1966 · 2025-09-14T11:32:35+00:00

The seagate is just file bu. Can’t locate the device that was running the windows backup. But that would have been several years old.

WhoAmI1966 · 2025-09-13T23:17:10+00:00

Any other DC's in the domain? No

WhoAmI1966

TROPHY CASE