@heykip
Jakob Strøm commented on When the trust relationship between a workstation and the primary AD domain fails 4 hours, 12 minutes ago
Well i get what the article is about and it’s great! Would also prefer no reboot of course..
But in situations where the trust relationship is broken because of either a restore, Azure migrate situation or something else that already has reboots/startups baked into the situation, we are just talking about an alternative quick-fix here.
If one can live with i single reboot to solve the issue, it is pretty easy to log in, unjoin, rejoin, reboot.. It’s only an alternative if the situation fits of course 🙂Jakob Strøm commented on When the trust relationship between a workstation and the primary AD domain fails 4 hours, 29 minutes ago
Actually only one Reboot is required. When dejoining the domain and asked to Reboot, just don’t and join again, then reboot. This will re-establish the domain join and work.
You would need to update your “Name the administrator account to manage” GPO by specifying your own Admininstrator account name. This example assumes you’re using the built-in Admin account so they haven’t told you to modify this GPO.
Congratulations on your generosity in taking the time to create such a useful guide!
Thank you!Tony commented on When the trust relationship between a workstation and the primary AD domain fails 23 hours, 40 minutes ago
you could also unjoin the domain and rejoin. You would also need admin cached creds (domain) for this.
Lee Roy Anthony commented on
Change remote IP address and DNS entry with a PowerShell script 1 day, 6 hours agoHI Emanuel!
Thank you!!!
With your expert guidance, I was able to come up with this:
PS C:Windowssystem32> Invoke-Command -VMName Win10VMTest004 -ScriptBlock {
$InterfaceIndex2 = Get-NetAdapter | Select-Object -ExpandProperty InterfaceIndex
$InterfaceAlias2 = Get-NetAdapter | Select-Object -ExpandProperty InterfaceAlias
If ($InterfaceAlias2 -eq “Ethernet 2”)
{
$InterfaceIndex4Set = $InterfaceIndex2
Write-Output $InterfaceIndex4Set, $InterfaceAlias2
}}
cmdlet Invoke-Command at command pipeline position 1
Supply values for the following parameters:
7
4
Ethernet 2
EthernetPS C:Windowssystem32>
What I need is to ‘do something’ once I catch InterfaceAlias value of Ethernet 2, and it’s basically using the InterfaceIndex value of ‘7’ somewhere down the road.
So I have very obvious questions in here. Am I dealing with an array when I access the contents of Get-NetAdapter? How do I ‘capture’ the same ‘row’ of data once I get the ‘Ethernet 2’ value of InterfaceAlias? Sorry about my ignorance. I did COBOL programming and as you can see, my knowledge is pretty Jurassic at best. 😉
Thank you again!
Most likely because Microsoft wants people to upgrade to Windows 11.
It’s been stuck in preview builds for Windows 10, so they’ll probably gonna wait another 2 years or just not release it for Windows 10 because of the above reason.
bgavin commented on
