Server 2016 AVMA License Keys

https://www.enhansoft.com/blog/avma-license-keys-for-windows-server-2016

Windows Server 2016

Windows Server 2016 Datacenter – TMJ3Y-NTRTM-FJYXT-T22BY-CWG3J

Windows Server 2016 Standard – C3RCX-M6NRP-6CXC9-TW2F2-4RHYD

Windows Server 2016 Essentials – B4YNW-62DX9-W8V6M-82649-MHBKQ

Windows 10

Windows 10 Enterprise – NPPR9-FWDCX-D2C8J-H872K-2YT43

Windows 10 Pro – VK7JG-NPHTM-C97JM-9MPGT-3V66T

Windows 10 Home – TX9XD-98N7V-6WMQ6-BX7FG-H8Q99

Windows 2012 R2

Windows Server 2012 R2 Datacenter – Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW

Windows Server 2012 R2 Standard – DBGBW-NPF86-BJVTX-K3WKJ-MTB6V

Windows Server 2012 R2 Essentials – K2XGM-NMBT3-2R6Q8-WF2FK-P36R2

Windows 8.1

Windows 8.1 Professional – GCRJD-8NW9H-F2CDX-CCM8D-9D6T9

Windows 8.1 Professional N – HMCNV-VVBFX-7HMBH-CTY9B-B4FXY

Windows 8.1 Enterprise – MHF9N-XY6XB-WVXMC-BTDCT-MKKG7

Windows 8.1 Enterprise N – TT4HM-HN7YT-62K67-RGRQJ-JFFXW

Advertisements

Publishing printers from another forest

Assuming that a trust is established between sites then create an OU in AD and then extract printers from the other forest into AD using pubprn.vbs

https://technet.microsoft.com/en-us/library/cc753116.aspx

In my server 2016 environment for some reason the last letter of the servername is missing and breaks the print object.  Using ADSIEDIT.MSC it can be fixed just edit the servername and shortservername attributes of each printer object.  Also the comments and location attributes can be updated in this way if required.

 

 

Network Capture on Server Core

Rather than installing 3rd party tools that may or may not work with server core this is built into most recent Windows Server operating systems.

netsh trace start persistent=yes capture=yes tracefile=c:\temp\trace.etl
netsh trace stop

The .etl can be examined using Microsoft Network Monitor or Microsoft Message Analyser

https://blogs.msdn.microsoft.com/canberrapfe/2012/03/30/capture-a-network-trace-without-installing-anything-capture-a-network-trace-of-a-reboot/