Find AD users Password Expiration Date

Get-ADUser -filter {Enabled -eq $True -and PasswordNeverExpires -eq $False} -Properties DisplayName, msDS-UserPasswordExpiryTimeComputed | Select-Object -Property Displayname,@{Name=”Expiration Date”;Expression={[datetime]::FromFileTime($_.”msDS-UserPasswordExpiryTimeComputed”)}}

Find all users with password never expires

get-aduser -filter * -properties Name, PasswordNeverExpires | where { $_.passwordNeverExpires -eq “true” } | where {$_.enabled -eq “true”}| Format-Table -Property Name, PasswordNeverExpires -AutoSize

Problem:

Windows sever can not boot after upgrading CPU when Hyper V is installed

The server works fine with the old cpu i3-4150, however, it doesn’t work with Xeon E3-1270 v3.

Solution:

Turn off VT-D

System Options -> Processor Options -> Turn off VT-D

Problme:

The product key you entered didn’t work. Check the product key and try again, or enter a different one. (0x80070490)

Solution:

slmgr.vbs /ipk #####-#####-#####-#####-#####

slmgr.vbs /ato

Problem: WDS unattended filed doesn’t work on new dell laptop computer.

Error mesage: Windows could not apply the unattended answer file’s <DiskConfiguration> setting

Reason: It is failing because it can’t see the drive. The dell laptop is shipped with Raid ON Mode enabled in BIOS. The WDS server boot image file doesn’t have the driver.

Solution:  Injected correct RAID driver to boot image file.

Step 1: download the proper driver from dell.

Step 2: go to drivers and add driver package, select the driver that needs to be installed. In this example, we installed iastorvd.inf

Step 3: Go to Boot Images, and choose Add driver Packages to Image…

Step 4: Click add,  please make sure to use “Package Name”  and type the correct driver.

Click “search for packages”  and “next” to inject the driver to the boot image.

Step 5: restart the WDS server.

Problem: HP server shutdown randomly

iLo log shows: server power removed, embedded flash/sd-card:restarted

Tried update firmware, BIOS, drives, power supply etc. It seems to me that the motherboard is not good based on my online search.

However, after further investigation, it turns out that the sever is running out of trial period.

Windows logs shows Event 1074

Comment: the license period for this installation of Windows has expired. The operating system is shutting down.

Solutions:

Extend Windows Server trail period

Problem:

Even logged in as a local admin/or a domain admin on a DC, you can not change local time. It is greyed out

Error showing:” some settings are hidden or managed by your organization”

Solutions:

to correct the time, run timedate.cpl

Problem:

This error occurs when the operating system fails to complete the sysprep process. This might caused by 3rd party antivirus software.

Solution: uninstall the antivirus software and do Sysprep again.

If the original Hyper-V host computer was crashed, the best way should be restore the latest backup of Hyper-V.

However, if you don’t have a backup for the Hyper-V, here are the steps:

Scenario 1. No snapshots with the VM on the crashed Hyper-V computer

1 Create a new VM on the rebuilt Hyper-V server

2 Mount the existing VHDX to the VM.

Scenario 2.  There are snapshots with VM on the crashed Hyper-V computer

1 Merge the snapshots into the original VHDX first.

2 Repeat the steps in Scenario 1.

1 Open Hyper-V Manager

2 Click Edit Disk to open the Edit Virtual Hard Disk Wizard. Then click Next.

3 Click Browse to select the latest .avhd(x) file.

4 Click Next.

5 select Merge to merge the changes stored in a differencing disk into the parent or another disk. Then click Next.

6 click next and select To the parent virtual hard disk and click Finish.

Repeat above steps for each .avhd(x) file until all changes have been merged successfully into the parent virtual disk.

Problems:

PXE boot across different VLANS not working.

Quoted from Kervin   PXE Boot Basics.

Booting from the network using the PXE protocol involves a simple series of DHCP packets. There are three parties involved: the DHCP server, the PXE server, and the client.

1. The client broadcasts a DHCP packet asking for the address of DHCP servers (servers that can hand out IP addresses). In the same packet, the client also specifies that it is looking for PXE (network boot) servers. This is known as a ‘discover’ – the client wants to discover where the servers are.
2. The DHCP server responds with a broadcast packet (which simply tells the client that it is an address server). This is known as an ‘offer’ – the server is offering its services.
3. The PXE server responds (which tells the client that it is a boot server). This is also known as an ‘offer.’
4. The client sends the DHCP server a message asking for an IP address.
5. The DHCP server sends the client an IP address that is now assigned to it.
6. The clients sends the PXE server a request asking for the path to the Network Boot Program (NBP).
7. The PXE server responds with the NBP path.
8. The client downloads the NBP and runs it.

Solutions:

configure the routers/switches to forward the client request to the PXE server and DHCP server

For example: add those lines in the switch.

ip helper-address 192.168.33.20     (this is the WDS server address)

ip helper-address 192.168.33.10      (this is the DHCP server address)

Read more here