Natively PowerShell does not have any cmdlets that let you manage a device driver. You an use the Win32_pnpSignedDriver WMI class to enumerate the device drivers on your system. There are two methods present; StartService and StopService. At the very lest you can start and stop them. Looking around MSDN, I was not able to find any addition methods for rolling back or disabling a driver which would be a nice feature to have. In conclusion, you have some limited management functionality of device drivers using PowerShell
With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?
This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Comments