Active Directory
-
Default location rules
After domain join, the default computer location is the Computers OU. It can be changed but it is static. It would be better if there is an option to add rules for default locations like moving recently joined Server 2016 devices into "MS Server 2016 Member Servers" OU.
1 vote -
Set 802.1X as default for both wired and wireless networks
We implement 802.1x for Wired Networks utilizing RADIUS with AD. Yet, it becomes complicated for new deployments. After the OS deployment, joining the workstation o the network using a RADIUS portal, then conducting a domain join operation is time consuming.
Combining NPS role into AD role by default for next "forest functional level" would be a great leap forward for security. It would help an AD domain being "secure by default" but also the sysadmins who try to secure their clients would appreciate the saved time.
Of course, the "guest network", where non-domain guest computers should be allowed in another…
1 vote -
BUG: 2016 server allows you to create machines with same name
I added a 2016DC to my 2012 and 2012r2 DCs a couple weeks ago.
Today I added a new PC into the network.
The problem is I used the same name as a PC already on the network (shouldn't be an issue Windows always catches this and doesn't allow it).
AD didn't catch this and actually updated the original PC in AD and did not add a second PC or warn that the name was already in use. If I look at the modified date of the original pc in AD it shows it was modified at the same time…
3 votes -
Join the Physical and Logical Layers
Add the BIOS UUID as a property on AD computer objects. This will finally tie the Physical and Logical layers together once and for all.
3 votes
- Don't see your idea?