Adding Windows OEM information

1. Type regedit in RUN dialog box or Start Menu searchbox and press Enter. It’ll open Registry Editor, now go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Under this key, look for a key OEMInformation. If it doesn’t exist, create it.

2. Now select OEMInformation key and in right-side pane, create following String values and set their values as shown below:

Logopath_of_OEMlogo.bmp_file
ManufacturerAny_desired_name
ModelAny_desired_name
SupportHoursAny_desired_time_amount_like_24x7
SupportPhoneAny_desired_phone_number
SupportURLAny_desired_URL

https://www.askvg.com/add-customized-strings-in-system-properties-dialog-box-of-windows-vista/

 

 

Advertisements

Windows 10 Custom Start Menu and TaskBar sequences

Various issues and errors getting this imported and .lnk/ .url shortcuts have to be in a specific place.

<LayoutModificationTemplate
xmlns=”http://schemas.microsoft.com/Start/2014/LayoutModification
xmlns:defaultlayout=”http://schemas.microsoft.com/Start/2014/FullDefaultLayout
xmlns:start=”http://schemas.microsoft.com/Start/2014/StartLayout
xmlns:taskbar=”http://schemas.microsoft.com/Start/2014/TaskbarLayout
Version=”1″>

MBAM 2.5 SP1 does include Win 10 computers in “MBAM Supported Computers Group”

For some reason Win 10 computers would not appear in the “MBAM Supported Computers Group” so I have created an additional membership rule for WQL using the format below.  This is SCCM 2016 Mbam 2.5 SP1 with latest KB patch.

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_TPM on SMS_G_System_TPM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version like “10.%” and SMS_G_System_TPM.SpecVersion > “1.2” and SMS_G_System_COMPUTER_SYSTEM.DomainRole = 1

Server 2016 – A service installation section in this INF is invalid

After adding a PCI wireless card to a server and installing the manufacturer drivers it will not work and Device Manager reports Unknown device and the drivers are not installed with a “Service installation section in this INF is invalid” message.

Turns out the wireless features are not installed by default on Windows Servers now and once added back re-add the manufacturer drivers as normal to get working again.

Add-WindowsFeature -Name Wireless-Networking

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